Historical PIOS Global corpus disposition
This ledger records the public-safe disposition of every Markdown document at historical source revision 4f1498ce5c390555abfad877d8284736f94d200b. Assessment treats this repository as historical design evidence, not current PIOS architecture authority. A file can support several CRDs while remaining one source; indexes, applications, and repeated descriptions are not counted as independent realizations.
| Source file | Source role | CRD-library disposition |
|---|---|---|
README.md | repository orientation | project/source context; no independent capability |
action-tags.md | capability design | supports action-intent labels and governed execution boundaries |
agent-roles.md | agent architecture | supports agent definitions, runtime roles, attribution, and outward-agent boundaries; named hierarchy remains a profile |
ai-assisted-labels.md | capability design | supports assisted-label vocabulary and assignment CRDs |
ai-profile-app.md | application specification | decomposed into identity, preferences, execution policy, labels, patterns, and audience projections |
ai-twins.md | product concept | composed realization over agent, identity, knowledge, access, publication, retrieval, and conversation capabilities |
ally.md | architecture/identity context | supports personal-AI identity and agent-context boundaries |
app-navigation.md | interface realization | audience/navigation projection; state reuse mapped to existing capabilities |
app-state.md | implementation documentation | preference, navigation, onboarding, attention, and provider-selection state mapped to existing capabilities or presentation profiles |
area-chat.md | area index | navigation metadata; referenced sources assessed individually |
area-execution.md | area index | navigation metadata; referenced sources assessed individually |
area-foundation.md | area index | navigation metadata; referenced sources assessed individually |
area-glossary.md | area index | navigation metadata; referenced sources assessed individually |
area-governance.md | area index | navigation metadata; referenced sources assessed individually |
area-imports.md | area index | navigation metadata; referenced sources assessed individually |
area-memory.md | area index | navigation metadata; referenced sources assessed individually |
area-onboarding.md | area index | navigation metadata; referenced sources assessed individually |
area-profile.md | area index | navigation metadata; referenced sources assessed individually |
area-public.md | area index | navigation metadata; referenced sources assessed individually |
automated-naming.md | capability design | supports candidate glossary-term detection and name/term presentation boundaries |
background-processing.md | capability design | supports background-operation lifecycle, attention, result, and cost-governance boundaries |
canonical-home.md | architecture and capability design | supports canonical-home semantics and the artifact-promotion CRD |
capability-apps.md | application specification | decomposed into task, reminder, note-linking, and audience/realization concerns |
chat-boundaries.md | cross-cutting architecture | supports conversation, collaboration, result, attention, and canonical-home boundaries |
chat-history-pillar.md | capability design | supports personal conversation-history continuity |
chat-memory-retrieval.md | capability design | supports governed retrieval context, consolidation, budgets, logs, and representation profiles |
chrome-extension.md | application/connector realization | supports governed capture and pending reconciliation; browser extension is not a capability |
circle.md | composed application design | decomposed into channel, thread, message, attention, identity, and work-reference capabilities |
contacts-app.md | application design from code | supports contact profile, contact point, and relationship-context CRDs; list/UI remains a projection |
context-tags.md | capability design | supports contextual classification and Role/Mode relationships |
cost-credit-governance.md | capability design | supports estimate, reservation, reconciliation, and existing approval/policy reuse |
cross-cutting-layers.md | architecture context | terms distributed across context, action, label, source, governance, and shared-element records |
dataview-queries.md | implementation tooling | query/lint realization patterns; no independent capability |
dedicated-agent-computer.md | deployment architecture | runtime-node profile; agent identity/performance concepts compose existing definition, event, metric, review, and policy capabilities |
documentation-roadmap.md | project documentation | historical specification plan; no owner-system capability |
execution-model.md | capability and domain model | supports plans, projects, routines, tasks, workflows, actions, work starters, and results |
execution-workspace.md | capability design | supports task-scoped execution-workspace lifecycle |
export-portability.md | capability design | supports bundle composition, validation, restore, parity, backup, cutover, and connector reauthorization |
glossary-naming.md | capability and terminology design | supports personal glossary, aliases, naming, and label boundaries |
goals-app.md | application/capability design | supports goals, objectives, targets, metrics, and presentation boundaries |
governance-principles.md | cross-cutting architecture | reusable invariants applied across portability, views, promotion, inspection, and owner authority |
hierarchical-summary.md | capability design | supports daily and higher-period History compilation plus summary provenance |
home-panel.md | interface design | audience projection over attention, work, History, and navigation capabilities |
human-authority-first.md | governance context | cross-cutting owner-authority, review, override, and non-impersonation rules |
hybrid-work-model.md | execution architecture | supports actor attribution, execution state, background work, handoff, and result boundaries |
import-model.md | capability design | supports source registration, import sessions, ingestion gates, promotion, processing, and portability |
imported-history-memory.md | composition/context | maps imported sources through retention, promotion, retrieval, History, patterns, and profile governance |
inconsistencies.md | terminology decision record | historical conflict resolutions retained as evidence; no independent capability |
index.md | repository index | navigation/catalog metadata; all linked content assessed by source file |
knowledge-environment.md | architecture and implementation context | supports owner implementation documentation and knowledge integrity; vault/sync choices remain profiles |
log.md | source change history | provenance and chronology context; no independent capability |
market-surface.md | market/publication strategy | entry-page taxonomy and messaging context; publication capabilities already separated from market presentation |
note-capability-linking.md | implementation pattern | note-backed schema and UI composition pattern; does not define generic capabilities |
notes-pillar.md | capability design | supports deliberate knowledge-note and related source/context capabilities |
observed-patterns.md | capability design | supports pattern detection and lifecycle evaluation |
onboarding.md | capability and journey design | supports onboarding, identity, preferences, verification, environment preparation, and first entry |
open-questions.md | unresolved-decision register | questions mapped to current unresolved records or later profiles; no independent capability |
outward-identity-modes.md | governance/product design | supports outward identity, representative conversation, and exposure boundaries; named modes remain profiles |
overview.md | architecture summary | historical structural context; no independent capability |
persistent-personal-memory.md | architecture composition | cumulative outcome of source, event, knowledge, profile, conversation, retrieval, and representation capabilities |
personal-agent-computing.md | paradigm definition | historical rationale and architecture context; no independent capability |
personal-agent-ecosystem.md | system composition | historical whole-system context; not one Capability MLE |
personal-cloud.md | deployment/foundation context | historical durable-environment model; physical placement does not define a capability |
personal-interfaces.md | interface architecture | supports owner access-path governance; panels/devices remain projections or deployment profiles |
pios.md | historical PIOS architecture | source context superseded by current PIOS authority; feature/app descriptions decomposed into CRDs |
planning-app.md | application/capability design | supports execution plans and activation; UI sections remain projections |
profile-app.md | application/capability design | supports owner-authored profile, goals, targets, metrics, patterns, and profile boundaries |
profile-pillar.md | capability design | supports evidence-backed assertions, disputes, owner profile, and evidence lifecycle |
projects-app.md | application/capability design | supports one-off project management and linked work |
proposals-rules.md | capability design | supports governed proposals, standing-rule establishment, and rule application |
public-presence.md | capability and publication design | supports sharing, publication, access, discoverability, rights, and outward-representation boundaries |
reader-app.md | application design from code | supports personal reading queue; rendering, topics, PDF, and settings map to projections or existing capabilities |
results-app.md | application/capability design | supports workflows, workflow runs, results, reviews, and market/catalog projections |
roles-modes.md | capability/context design | supports Role, Mode, active-context, and outward-intent CRDs |
routines-app.md | application/capability design | supports reusable routine and routine-run capabilities |
shared-workspace.md | architecture principle | composition of shared information, interfaces, attribution, visibility, and promotion; no single additional CRD |
sources-model.md | capability and terminology design | supports source discovery/registration, trust, imports, derivation, and source identity |
storage-pillar.md | capability design | supports retention, derivation, allocation, processing, source, and portability boundaries |
structural-stack.md | architecture overview | historical layer/deployment model; current PIOS determines present boundaries |
system-app.md | application/governance design | inspection surface over run, rule, proposal, source, health, job, export, and representation capabilities |
technical-terms.md | terminology reference | vocabulary context distributed across CRDs and shared elements |
timeline-insights.md | capability and audience design | supports time-indexed History and derived insight/reflection boundaries |
ui-backend-terminology.md | terminology mapping | historical UI/backend vocabulary and migration decisions; no independent capability |
ui-design-standards.md | implementation/design standard | layout, component, icon, color, focus, and responsive profiles; no independent capability |
unified-personal-core.md | historical information architecture | supports canonical/derived separation, portability, graph/vector profiles, and PIOS/Core distinction |
unified-timeline.md | capability/architecture design | supports canonical events, daily History, aggregation, and time navigation |
updates-pillar.md | capability design | supports owner attention and completed-work publication |
view-based-architecture.md | interface architecture | app views are audience projections over shared state, not independent data silos |
visibility-model.md | capability/governance design | supports sharing, publication, access, discoverability, rights, and representation separation |
why-this-model.md | rationale | problem statement and architecture motivation; no independent capability |
Closure result
All 90 Markdown documents at the selected historical revision now have an explicit public-safe disposition. The corpus yielded reusable capability requirements, shared elements, architecture and terminology context, realization patterns, composed products, project/meta records, and unresolved questions. File count is not treated as realization count, and inclusion here does not make historical architecture current.