Restricted corpus disposition
This publication-safe matrix accounts for all 26 admitted restricted documents without exposing private filenames, links, revisions, excerpts, or implementation details. Exact source mapping remains in the owner-approved restricted evidence location.
| Corpus ID | Document role | Disposition | Capability-library result | Evidence limit |
|---|---|---|---|---|
RAS-DOC-01 | application-wide master | cross-cutting context, declared schema, capability evidence | existing CRDs plus observed-pattern gap extraction | not current PIOS authority; schema is not runtime proof |
RAS-DOC-02 | companion rationale and behavioral checklist | cross-cutting rationale and acceptance requirements | existing CRDs plus observed-pattern gap extraction | checklist is not passing-test evidence |
RAS-DOC-03 | storage and processing specification | capability and realization evidence | pilot retention, derivation, allocation | static trace only where recorded |
RAS-DOC-04 | conversation memory and retrieval specification | capability and realization evidence | pilot retrieval and consolidation | partial static trace; full realization unknown |
RAS-DOC-05 | execution object model | capability evidence | action, plan, project, routine, task, workflow and result CRDs | implementation reachability incomplete |
RAS-DOC-06 | agent execution reference | rationale and capability evidence | execution and workflow boundaries | implementation reachability incomplete |
RAS-DOC-07 | onboarding requirements | capability and conflict evidence | guided journey, verification, preparation and first-entry CRDs | documented journey not confirmed in code |
RAS-DOC-08 | owner profile specification | capability evidence | owner-authored and evidence-backed profile CRDs | implementation reachability incomplete |
RAS-DOC-09 | personal-AI configuration specification | capability and partial realization evidence | identity, preferences and execution-policy CRDs | durable realization incomplete |
RAS-DOC-10 | owner attention/update specification | capability evidence | attention lifecycle CRD | delivery and runtime reachability incomplete |
RAS-DOC-11 | workflow and result specification | capability evidence | package, installation, run and result CRDs | implementation reachability incomplete |
RAS-DOC-12 | capability-application catalogue | boundary and audience-projection evidence | app groupings decomposed into existing CRDs | catalogue does not prove availability |
RAS-DOC-13 | note-to-capability linking specification | realization-pattern evidence | no separate capability; shared composition pattern | relevant code reachability incomplete |
RAS-DOC-14 | system and operations application specification | capability and audience-projection evidence | source/import, event registry and inspection CRDs | implementation reachability incomplete |
RAS-DOC-15 | export and portability specification | capability evidence | export, validation, restore and connector CRDs | operational evidence absent |
RAS-DOC-16 | context-assignment specification | capability evidence | contextual classification and active-context boundaries | complete reachability not confirmed |
RAS-DOC-17 | extended Role specification | capability and partial realization evidence | Role, outward-intent and outward-representation CRDs | access/publication not established |
RAS-DOC-18 | glossary extension specification | capability evidence | glossary term and relationship boundaries | implementation reachability incomplete |
RAS-DOC-19 | glossary terminology specification | terminology and audience-projection evidence | glossary/label naming decisions | UI wording does not define capability meaning |
RAS-DOC-20 | automated naming specification | capability evidence | candidate glossary-term detection | implementation reachability incomplete |
RAS-DOC-21 | AI-assisted label specification | capability evidence | label-vocabulary and assignment CRDs | implementation reachability incomplete |
RAS-DOC-22 | action-intent specification | capability evidence | action-intent labeling | implementation reachability incomplete |
RAS-DOC-23 | background-action specification | capability evidence | governed action and background-operation CRDs | implementation reachability incomplete |
RAS-DOC-24 | web capture integration specification | capability and realization-pattern evidence | governed capture and pending reconciliation | code reachability incomplete |
RAS-DOC-25 | interface design standards | realization and audience-projection evidence | no separate capability; shared interface patterns | design declaration is not runtime proof |
RAS-DOC-26 | owner welcome guide | intent, terminology and experience context | source context and existing capability corroboration | guide does not prove implementation |
Every document has a bounded substantive disposition. This does not mean every declared feature has a CRD, every code path has been traced, or any realization has been tested, deployed, or observed in production.