Documentation reality and status

Audit date: 2026-08-31.

This index classifies the repository documentation against the live AncientOS Platform v1 Alpha runtime. It is the routing authority for deciding whether a document states present truth, future intent, or historical context. Generated documentation must never be edited as source.

Classification

Document or family	Classification	Current use
README.md, docs/index.md	Canonical	Platform entry points and current operator-facing status.
AGENTS.md, CONTRIBUTING.md	Canonical	Engineering governance, validation, and bootstrap process.
docs/canonical_terminology.md	Canonical	Current names and authority boundaries.
docs/architecture/capability_taxonomy.md	Canonical taxonomy	Portfolio lifecycle, independent posture dimensions, documentation authority hierarchy, and selected verified platform posture.
docs/architecture/capability_availability_truth.md	Canonical runtime truth contract	Registration, configuration, dependency/runtime readiness, operator/transport reachability, operation authority, evidence freshness, Oracle projection, Rubick semantics, and capability-author requirements.
docs/architecture/live_governed_operator_loop.md	Canonical	Shared runtime, Runtime Composition, Kernel Records, history, and explainability.
docs/architecture/just_in_time_cognition.md	Canonical	Capability-driven cognition contracts, deterministic request-scoped resolution, package trust, and model-context assembly.
docs/architecture/media_episode_inventory.md	Canonical capability boundary	Read-only canonical TV metadata, scoped Plex episode comparison, bounded evidence, routing, and limitations.
docs/architecture/media_acquisition_discovery.md	Canonical capability boundary	Read-only canonical candidate discovery, deterministic eligibility/ranking, evidence, and explicit mutation deferrals.
docs/architecture/media_acquisition_proposals.md	Canonical capability boundary	TV episode proposal integrity, Lich review-only semantics, readiness observation, hostile metadata handling, and the qBittorrent mutation prohibition.
docs/meeting_intelligence.md	Canonical capability and runbook	Implemented meeting producer boundary, LifeVault evidence model, read-only Luna queries, governed follow-up proposal path, privacy, limitations, and Meetily attribution.
docs/governed_development_delegation.md	Canonical capability and runbook	Durable development intent, immutable LegionCommander plans, separate Lich authorization, Codex instruction policy, and operations.
docs/architecture/rubick_settings_dashboard.md	Canonical capability boundary	Metadata-driven Rubick settings inspection, runtime evidence ownership, Web adapter security, and governed proposal limitations.
docs/architecture/action_preparation_preflight.md	Canonical capability contract	Observational prepared actions, exact binding, execution preflight, family boundaries, and future executor requirements.
docs/experiential_learning.md	Canonical capability boundary and runbook	Implemented governed receipt-bound certification, Lich-scoped LifeVault promotion, deterministic snapshots, post-boundary LegionCommander advice, replay, and prohibited authority uses. Future confidence/reinforcement posture is governed by the portfolio roadmap.
docs/architecture/durable_governed_actions.md	Canonical	The one live default-disabled mutation lifecycle.
docs/architecture/transport_integration.md, docs/terminal_transport.md, app/transports/README.md	Canonical	Shared Discord, Terminal TUI, Web TUI, and optional ingress boundaries.
docs/architecture/ancientos_kernel_spec_v1.md, governance_kernel.md, kernel_services.md	Canonical doctrine	Kernel-centric operating-system responsibility model and authority invariants; implementation readiness remains governed by Runtime Composition.
docs/architecture/rote/README.md, reconciliation.md	Canonical Rote source inventory and historical ingestion reconciliation	Preserves source authority and the original review baseline; current status links to the implemented bounded exchange. Ingestion alone grants no readiness.
docs/architecture/rote/sources/*	Preserved supplied design records	Three-document Rote corpus and two architecture-context sources, each at its own status. Addendum is an adopted reconstructed replacement, not a recovered verbatim original.
docs/architecture/rote/conceptual-specification-reading-copy.md	Faithful reading derivative	Original DOCX controls formatting; paragraph text and hierarchy preserved. Not a fourth specification.
Other docs/architecture/*.md	Canonical support or legacy seam	Component-specific doctrine. Pages that describe uncomposed surfaces are design boundaries, not readiness claims.
docs/proposals/governed_capability_portfolio_roadmap.md	Canonical roadmap authority	Governs capability adoption and delivery. It records completed work, non-authoritative candidates, deferred items, and explicit decisions.
docs/proposals/capability_backed_read_only_cognition.md	Candidate implementation proposal	Broad compositional observational cognition; no adoption, new framework or execution authority. Priority remains in the canonical roadmap.
docs/proposals/complete_governed_operator_loop_roadmap.md	Historical proposal	Completed foundation retained for rationale; its current-state tables describe the pre-foundation baseline.
Other docs/proposals/*.md	Historical proposal	Advisory design records unless a canonical page explicitly adopts them.
docs/luna_master_roadmap.md	Canonical operator-facing roadmap view	Human-readable portfolio view derived from the canonical roadmap and taxonomy; not an independent adoption authority.
Root ERA*_PLAN.md files	Historical plans	Prior metadata-only planning records, including retired Era 8 and Era 9 labels; none is an adopted current era or live runtime status.
LUNA_CLI_BRIDGE.md	Legacy	Historical CLI workflow; not the canonical Runtime Kernel transport contract.
docs/runbooks/*.md	Runbooks	Operational procedures. Optional integrations are not ready merely because a runbook exists.
docs/launcher/*, docs/terminal_transport.md	Canonical operator docs	Current launcher and transport setup; environment-specific addresses remain deployment examples.
docs/luna_core/*.md	Canonical runtime doctrine	Mounted identity and posture artifacts; not a second memory authority.
knowledge/**/knowledge/*.md	Knowledge surfaces	Bounded repository knowledge; capability statements require Rubick/runtime evidence.
docs/architecture/documentation_migration_plan.md	Historical audit	Earlier migration record superseded by this status index.
docs/api/, docs/_build/, site/	Generated	Build products; never hand-edit or include incidental output in source commits.

Present platform truth

AncientOS is transport-neutral and read-only by default. Discord, Terminal TUI, and Web TUI normalize operator input into the same Runtime Kernel. Runtime Composition reports wiring truth. Durable SQLite Kernel Records support scoped runtime history and restart-safe explanation. The Durable Governed Action lifecycle persists Governed Proposals, Lich approvals, Zeus evidence, execution receipts, and rollback receipts as separate stages.

The canonical architecture is kernel-centric. Applications and domains consume typed governed capabilities; Luna is an interface/application; transports and providers are replaceable boundaries. “Operating system” describes that mediation and authority model and does not claim replacement of the host OS or container runtime. The v3 application-platform page is historical design context, not current architectural authority.

Chen is the governed mutation orchestration layer. It provides the common proposal, approval, execution, evidence, receipt, and rollback lifecycle for capabilities that change system state.

Rubick owns capability discovery and readiness interpretation. Oracle interprets operational evidence into facts, observations, inferences, risks, and recommendations without executing. Lich is approval authority. Zeus is evidence authority and does not approve or execute.

Capability-driven just-in-time cognition is an implemented internal runtime layer. Rubick capabilities may declare cognition package references; the dedicated cognition registry owns package content, and the transport-neutral inference path can assemble that content for a resolved capability set. This registration does not imply that every existing route supplies capability IDs.

Meeting Intelligence is an implemented transport-neutral application capability. The Web TUI service exposes a bearer-authenticated, data-only producer endpoint; LifeVault artifacts preserve canonical transcripts and evidence-linked advisory claims; the shared Runtime Kernel supports listing, inspection, transcript search, summaries, decisions, commitments, actions, and questions. Direct operator follow-up requests enter the existing Keeper/Lich path. No desktop capture agent, audio storage, producer heartbeat, or automatic background cognition is currently implemented.

Governed experiential learning is implemented as an advisory LifeVault substrate. Supported governed-action and deterministic pytest receipts can support exact-bound certification; Lich approval governs durable promotion; deterministic scoped snapshots are attached only to LegionCommander plans and retain replay provenance. Experiential state cannot alter routing, Rubick readiness or authority, Lich requirements, mutation authorization, or executor selection. Confidence, reinforcement, ranking, automatic promotion, cross-domain transfer, and additional advisory consumers are not implemented.

Known limitations

• This is an alpha milestone for controlled single-operator use, not production.
• SQLite durability depends on preserving the configured /data volume.
• Identity and authorization remain transport/session scoped rather than a general multi-user identity system.
• Zeus evidence is durable for Governed Actions but is not universal across every AncientOS subsystem.
• Telemetry events remain process-local even when the resulting Kernel Record is durable; telemetry-sink failure can reduce observability.
• Capability readiness is not universally backed by durable freshness evidence.
• Cognition resolution is wired for callers that provide capability IDs, but capability extraction is not yet universal across all conversational routes; cognition resolution records are not yet persisted in every Kernel Record.
• Canonical portfolio mutation is limited to registered configuration scalars, no-overwrite regular-file renames, and configured Home Assistant light.* on/off state. There is no shell, Docker, Git, package-manager, generic network-write, arbitrary file, or autonomous executor.
• Home Assistant wiring and fixture evidence do not establish live deployment reachability. Runtime Composition and request-time inspection remain the readiness authority.
• Meeting capture/transcription remains an edge-producer responsibility. Stored meeting availability does not prove a live producer is connected.
• Experiential deterministic-test evidence is limited to one exact pytest node with exact file-content subject binding. Aggregate validation suites, generalized artifact or tree binding, and automatic receipt production are not implemented.

Audit method

The 2026-08-31 architecture review compared the canonical terminology, kernel specification, architecture overview, application/component boundary model, kernel service map, machine-readable architecture manifest, documentation index, and historical v3 page. It reconciled the remaining application-centric v3 wording with the implemented Runtime Kernel, Runtime Composition, governed capability, Lich, Zeus, LifeVault, Rubick, Oracle, and transport boundaries. No runtime readiness or new capability is asserted by that documentation pass.

The 2026-08-12 experiential reconciliation compared commit 775d0fe, the canonical experiential runbook, LifeVault and certification contracts, LegionCommander plan integration, Rubick metadata, and focused documentation tests. It records the completed advisory foundation and leaves governed confidence/reinforcement as deferred planning work rather than runtime capability posture.

The 2026-07-14 audit compared authored documentation with app/runtime/composition.py, app/runtime/kernel_factory.py, the governed action implementation, transport adapters, Docker Compose service topology, tests, CI configuration, and milestone commits f3b55d8 through 6c28244. Searches covered prototype/planned/future/legacy/deprecated/superseded markers, durability claims, transport assumptions, execution flags, ports, services, model names, roadmap phases, Chen, Kernel Records, proposals, and approvals.

Historical and speculative wording is valid inside documents classified above as historical, active roadmap, design doctrine, or knowledge. It must not be read as live capability evidence.

Roadmap authority

The Governed Capability Portfolio roadmap is the only roadmap adoption authority. Era 7, Oracle Operational Ergonomics, and Era 8, Governed Capability Portfolio, are complete historical programs. There is no active numbered era, no adopted Era 9, and no currently proposed, adopted, in-progress, or blocked capability work.

docs/luna_master_roadmap.md is the operator-facing portfolio view. All root ERA*_PLAN.md files are historical context and cannot adopt work. Historical Model-Portable Inference is substantially implemented and is not unfinished Era 8 work.

Posture terms in this index and canonical architecture pages use the Architecture and Capability Posture Taxonomy.