Source coverage
| Source set | Inventory | Substantive assessment | Implementation trace | Status |
|---|---|---|---|---|
| Current PIOS | master and companion set identified | pilot-relevant architecture read; whole-system context reviewed | not applicable | pilot alignment complete |
| PIOS Global | all 90 Markdown documents at the selected commit identified | all 90 documents substantively assessed and explicitly dispositioned | not applicable | document corpus complete; see historical disposition ledger |
Restricted application source RAS-01 | complete document and file inventory retained privately | all 26 documents have a bounded substantive assessment and explicit disposition | bounded storage, retrieval, onboarding/orientation, authentication, identity/preference, Role/Mode, active-context, patterns, goals, objectives, targets, metrics, selected system paths, and negative outward-exposure searches assessed privately; many code paths remain untraced | public details withheld; document corpus complete, realization coverage incomplete |
| CRD method | required normative set identified | required files read | validator behavior understood | active |
Phase 2 tranche coverage
| Tranche | Public historical material | Current PIOS material | Restricted material | Status |
|---|---|---|---|---|
| A1 — glossary, naming, labels, context attachment | glossary-naming.md, automated-naming.md, ai-assisted-labels.md, context-tags.md | Cotton §§4.1–4.5; Personal Glossary §9; Taxonomy §§10.2 and 10.4; Context §12.8; Cognitive Memory §§2, 7, 10–11 | four directly relevant specifications assessed; implementation details remain private | statement and boundary pass complete; six CRDs drafted |
| A2 — notes and profiles | notes-pillar.md, profile-pillar.md, and profile-app.md read | Knowledge §14 and profile/context guidance read | note/profile requirements plus basic owner-profile update path assessed; richer owner-authored knowledge and evidence-backed assertion lifecycles remain unconfirmed | statement and boundary pass complete; four CRDs drafted; bounded realization evidence recorded |
| B1 — action intent and governed execution | action-tags.md and execution-model.md read | Taxonomy §10.3, Functional Flow §13, Agent Architecture §17, processing/governance sections read | action-label vocabulary/assignment and workflow-specific execution paths assessed; generic action registry, background-operation and execution-policy lifecycles remain unconfirmed | statement and boundary pass complete; four CRDs drafted; partial realization evidence recorded |
| B2a — plans, projects, routines, tasks, task collections, reminders | planning-app.md, projects-app.md, routines-app.md, goals-app.md, execution-model.md, and related execution pages read | Functional Flow §13 and Agent Architecture §17 read | objective/plan/project/routine, plan activation, task/task-list and reminder paths assessed; separate routine-run model not identified | statement and boundary pass complete; eight CRDs drafted; bounded static realization evidence recorded |
| B2b — Work Starters, contextual ordering, workflows, and results | results-app.md and related execution material read | Functional Flow §§13.3–13.10 and Agent Architecture §17.2 read | workflow package/install/trigger/run/step/output paths assessed; Work Starter and contextual-ordering realizations remain unconfirmed | statement and boundary pass complete; six CRDs drafted; bounded workflow realization evidence recorded |
| C1 — events, Updates, completed work, and History | updates-pillar.md, unified-timeline.md, timeline-insights.md, and hierarchical-summary.md read | Event Model §8, Functional Flow §13.2, Knowledge and retrieval relationships read | update lifecycle, reminder-produced updates, daily summary and higher-period summary producers assessed; canonical event-spine, completed-work manifest and full History provenance remain unconfirmed | statement and boundary pass complete; six CRDs drafted; partial static realization evidence recorded |
| C2a — sources, imports, ingestion gates, event registry, operational inspection | sources-model.md, import-model.md, area-imports.md, and system-app.md read | Inbound Flow §7, Event Model §8.4, Portability §§21.5 and 21.8 read | import status is an explicit future placeholder; a read-only run panel projects retrieval and storage-job records; no source/import/promotion, ingestion-gate or generic event-registry lifecycle was identified | statement and boundary pass complete; eight CRDs drafted; partial inspection evidence and negative import evidence recorded |
| C2b1 — Core export, source-composed package, validation, restore, parity, backup | export-portability.md read | Portability §§21.1–21.3 and companion portability/compatibility specifications read | authenticated client-side export composition assessed; it writes selected datasets, graph, Markdown, file manifests and checksums, but no source-composed package, independent validation, restore, parity or backup path was identified | statement and boundary pass complete; six CRDs drafted; partial export-composition evidence recorded |
| C2b2 — cutover, rollback, decommissioning, erasure, connector reauthorization | portability and transition material reviewed | Portability §§21.1 and 21.6 plus companion portability/compatibility specifications read | no cutover, rollback, source-decommissioning, governed erasure or destination connector-reauthorization implementation was identified in the bounded portability/System assessment | statement and boundary pass complete; six CRDs drafted; bounded negative static evidence recorded |
| D1a — governed capture and pending reconciliation | chrome-extension.md read | Product Model/Core app capture responsibility, device-cache treatment, and Inbound Flow read | authenticated browser-capture server path assessed; linked storage/note creation, action-label assignment and optional instruction update identified; pending reconciliation not found | statement and boundary pass complete; two CRDs drafted; partial capture realization evidence recorded |
| D1b1 — onboarding journey, personal AI identity/preferences, initial environment, first entry | onboarding.md, area-onboarding.md, ally.md, and applicable experience pages read | agent definition, owner authority, metadata flexibility, context lifecycle, and interface boundaries read | onboarding, welcome, and interface requirements assessed; actual orientation, authentication, caller/state, and selected AI-profile paths traced privately | statement and boundary pass complete; six CRDs drafted; documented end-to-end onboarding realization not confirmed |
| D1b2 — Roles, Modes, active context, outward intent and representation | roles-modes.md, context-tags.md, home-panel.md, app-navigation.md, and outward-identity-modes.md read | Context §§12.1–12.8, context-tag lifecycle, exposure axes, and owner-authority boundaries read | extended-Role requirements and Role/Mode/context-selection paths assessed; outward-representation implementation not confirmed | statement and boundary pass complete; five CRDs drafted; interface-only concepts classified as projections |
| E1 — observed-pattern detection and lifecycle | observed-patterns.md read with related pattern/proposal/profile context | epistemic sequence, Knowledge/Profile relationships, History inputs, and derived-state principles read | full application master and companion assessed; pattern structures and disabled/planned system surfaces reviewed | statement and boundary pass complete; two CRDs drafted; active realization not confirmed |
| E2 — goals, objectives, targets, measurement definitions, and metric observations | goals-app.md, planning-app.md, profile-app.md, and profile-pillar.md read | Functional Flow §13 and Knowledge concept catalog §14 read | relevant requirements, schema, goal/target/metric UI and hooks, objective/plan hooks, and observation references assessed | statement and boundary pass complete; five CRDs drafted; target-achievement and observation-writer realizations not confirmed |
| E3 — controlled sharing, public publication, access policy, request evaluation, discoverability, and usage rights | visibility-model.md, public-presence.md, area-public.md, and applicable outward-governance material read | Core Self/Circle, exposure axes, sensitivity, external-action authority, and privacy/access sections read | bounded searches for public-asset and exposure-model terms completed; no relevant realization identified | statement and boundary pass complete; six CRDs drafted; implementation and availability not confirmed |
| E4 — structured reviews and reflective assessments | results-app.md, hierarchical-summary.md, and related History/execution material read | Functional Flow review windows and continuous adjustment loop plus Knowledge review/reflection concepts read | weekly-review requirements and server workflow path assessed | statement and boundary pass complete; two CRDs drafted; only a partial static review-note realization is confirmed |
| E5 — human contacts, contact points, verification, and relationship context | contacts-app.md, cross-cutting-layers.md, and related glossary/context material read | Cotton people/relationships, Knowledge profile families, with-whom context, Circle scope, and profile lifecycle read | contact hooks, components, schema, relationship-origin declarations, and verification gaps assessed | statement and boundary pass complete; four CRDs drafted; richer relationship and verification realization not confirmed |
| E6 — agent definitions, runtime roles, synchronization, outward identity, and representative conversation | agent-roles.md, ally.md, ai-twins.md, outward-identity-modes.md, human-authority-first.md, and personal-agent-ecosystem.md read | Agent Architecture §17, Governance of Agent Definitions §21.10, profile-family separation, exposure, and integration agent/runtime/memory/activity boundaries read | prior personal-AI and Role-intent traces reused; bounded searches for agent-profile/runtime-target/AI-Twin models completed | statement and boundary pass complete; five CRDs drafted; broader realizations not confirmed |
| E7 — collaboration channels, work-linked threads, attributed messages, and execution workspaces | circle.md, chat-boundaries.md, hybrid-work-model.md, execution-workspace.md, and background-processing.md read | Circle agent harness §§17.8–17.9, work/event boundaries, identity integrity, loop control, untrusted-content treatment, and durable handoff requirements read | chat-filter/channel and message-flow paths assessed; bounded negative searches for richer Circle and execution-workspace models completed | statement and boundary pass complete; four CRDs drafted; only partial collaboration realization confirmed |
| F1 — personal conversation history and owner access paths | chat-history-pillar.md, persistent-personal-memory.md, imported-history-memory.md, personal-interfaces.md, area-chat.md, area-memory.md, home-panel.md, app-navigation.md, and canonical-home.md read | purpose, product/interface model, event/History distinction, source promotion, hybrid work, Core-app boundary, and integration conversation-checkpoint rules read | chat-history requirements, history/filter/session code paths and read-only raw-history surface assessed; interface evidence remains requirements-level | statement and boundary pass complete; two CRDs drafted; panels and persistent memory classified as projections/composition |
| F2 — device-local cache, offline content, and personal reading queue | reader-app.md, personal-interfaces.md, chrome-extension.md, storage-pillar.md, action-tags.md, and view-based-architecture.md read or reused | PIOS-native interface responsibility, local-first capture, offline staging, non-canonical cache treatment, per-client authority, and required offline-sync profile topics read | Reader hooks, panels, article rendering/actions and topic organizer assessed; no complete cache/offline realization confirmed | statement and boundary pass complete; three CRDs drafted; detailed cache/offline profiles remain unresolved and Reader implementation conflicts are retained |
| F3 — operation cost and resource governance | cost-credit-governance.md, background-processing.md, import-model.md, proposals-rules.md, and results-app.md read or reused | guarded-action approval, retrieval token budgets, cost-aware service selection, measured-cost guidance, and deployment/cost separation read | restricted retrieval-budget requirements assessed; bounded path/document search found no generic estimate, reservation or reconciliation implementation | statement and boundary pass complete; three CRDs drafted; approval, usage measurement and partial completion reuse existing capabilities |
| F4 — candidate source discovery, owner implementation documentation, and knowledge integrity | sources-model.md, knowledge-environment.md, dataview-queries.md, unified-personal-core.md, personal-cloud.md, and technical-terms.md read | cognitive-memory source-discovery state machine and record, Knowledge Compilation, summaries/links/indexes, maintenance/linting, owner authority and projection boundaries read | bounded repository path search found no candidate-discovery, owner implementation-documentation, or knowledge-linting realization | statement and boundary pass complete; three CRDs drafted; vault/sync/tool patterns classified separately |
| F5 — personal Meaning, evidence-linked Learning, and derived-representation lifecycle | unified-personal-core.md, system-app.md, chat-memory-retrieval.md, and related pattern/profile material read or reused | cognitive-memory object families, non-authoritative lifecycle, epistemic sequence, representation records, source-local graph snapshots, registry lifecycle, context/adaptation boundaries, and required evidence read | bounded document, code and migration searches found no Meaning/Learning object lifecycle; an early embedding schema was later removed and no retained writer or registry lifecycle was confirmed | statement and boundary pass complete; three CRDs drafted; representation types and Meaning interface classified as profiles/projections |
| F6 — canonical artifact promotion and historical-corpus closure | canonical-home.md, governance-principles.md, shared-workspace.md, dedicated-agent-computer.md, app-state.md, market-surface.md, terminology/UI/meta documents, and all remaining historical files assessed | current provenance, authority, representation, state-treatment, deployment and interface distinctions checked | bounded searches found no named canonical-home or working-artifact promotion realization | all 90 historical Markdown files explicitly dispositioned; one CRD drafted; architecture, deployment, UI, market and meta material classified separately |
The complete restricted document disposition is recorded in Restricted corpus disposition. The complete selected historical Markdown disposition is recorded in Historical PIOS Global corpus disposition.
Coverage means substantive assessment, not merely finding a path. Static code evidence does not establish tests, deployment, or production behavior.