Source Context Reference — PIOS Capability Library pilot
Sources and roles
| Source | Revision | Role | Limits |
|---|---|---|---|
| Current PIOS framework | committed baseline d6c4ccbb55db98b63b8ad8d0e7bca57bb4a427dc | Current architecture alignment and public provenance | Does not prove capability adoption, implementation, deployment, or availability. Unpublished working-tree changes are not evidence for this milestone. |
| PIOS Global ↗ | 4f1498ce5c390555abfad877d8284736f94d200b | Historical design evidence | Does not govern current PIOS architecture or prove implementation. |
Restricted application evidence RAS-01 | exact binding retained privately | Requirements and static implementation assessment | Identity, excerpts, links, code details, and source revision are not public evidence. No tested or deployed behavior is inferred. |
| CRD methodology | 8f24ab01b2bf30409b364df5fd6b77b7bf89c29d | Documentation model and validation rules | Does not supply PIOS product facts. |
Cross-cutting interpretation
- Current PIOS is the whole personal information operating-system framework, not a historical app catalogue or only its storage layer.
- Core-contract membership, PIOS-system membership, physical placement, and state treatment are separate classifications.
- Derived or rebuildable state is not automatically outside Core, PIOS, or a PIOS distribution.
- Historical pillars are not the current five Core zones.
- A proposal is a governed decision object; a notification or Update is a possible presentation of it.
- A schema declaration is not evidence of a reachable, tested, deployed, or available capability.
- Personal glossary terms, owner-confirmed organizing labels, AI-assisted labels, Roles, and Modes carry different authority and meaning; shared UI presentation does not merge them.
- Cotton governs contextual organization but is not itself a database schema, fixed taxonomy, or app-specific feature catalogue.
Restricted-evidence policy
Restricted evidence may corroborate, contradict, or leave a public capability claim unresolved. Public documents record only the evidence maturity and publication disposition needed to interpret the CRD. Unique private requirements and implementation details remain outside this repository until explicitly cleared.
Non-normative source sequencing
The historical source grouped behavior into application-oriented pillars. The capability library instead decomposes that material by independently meaningful outcome. This extraction order is project workflow and does not prescribe implementation order.