Documentation Completion Manifest

Status: Current documentation control index — derived from frozen authority
Date: July 29, 2026
Purpose: Make the final documentation set discoverable, distinguish governing
documents from evidence and history, and record the remaining documentation
closure checks.

1. Authority order

1. AGENTS.md
2. ARCHITECTURE_LOCK.md
3. IMPLEMENTATION_CONTRACT_v1.1.md for
   later implementation detail
4. CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md
   for the reconciled runtime, environment, marketplace and frontend/API
   implementation standard
5. SOURCE_PACK_RECONCILIATION_2026-07-28.md
   for source classification, conflict resolution and deliberate exclusions
6. FOUR_BUTTONS.md and TWIN_BEHAVIOR.md
   for specialized OODA controls and Silent Twin behavior
7. TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md
   for the corrected four-flow, Operational Spine, Fortress, search, promotion,
   retention and environment lifecycle
8. IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md
   for Plugin Directory and MCP Marketplace publication, embedded host UI,
   browser Workbench, discovery and connection composition
9. Approved implementation and release evidence, only where it does not
   conflict with the sources above

No presentation, conversation export, prototype, provider documentation, or
historical architecture file may redefine the frozen product or platform.

2. Final documentation coverage

The primary derived implementation handoff is
CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md. The detailed documents below
support it; none overrides the frozen authority order.

Coverage	Governing / primary documents	Required use
Product and Workbench	ARCHITECTURE_LOCK.md, FOUR_BUTTONS.md, TWIN_BEHAVIOR.md, WORKBENCH_MATRIX.md, WORKBENCH_ROLE_CAPABILITY_MAP.md, FRONTEND_PLATFORM_API_AND_DISCOVERY_SPEC.md	Product design, UX, role/view composition, Gateway wiring and discovery
Platform and runtime	IMPLEMENTATION_CONTRACT_v1.1.md, PLATFORM_ARCHITECTURE.md, CANONICAL_PLATFORM_ARCHITECTURE.md, RUNTIME_SUBSTRATE_AND_SURFACE_CONTRACT.md	Service boundaries, runtime guarantees, data ownership, surface contracts
Spine, projection, and governance	TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md, ADAPTIVE_SPINE_MODEL_v1.md, PROJECTION_CONSTITUTION.md, GOVERNANCE_CONSTITUTION.md, EXECUTION_CONSTITUTION.md, PLATFORM_PRODUCT_DATA_AND_PROJECTION_REFERENCE.md	Four flows, schema, Operational/Fortress split, connector-to-Spine mapping, search/read paths, canonical writes, approvals and retention
Connectors and Marketplace	IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md, CONNECTOR_CONSTITUTION.md, CAPABILITY_CONSTITUTION.md, PRODUCT_PLATFORM_BOUNDARY_AND_GO_LIVE_STANDARD.md	Plugin/MCP publication lanes, host UI, browser Workbench, connector lifecycle, discovery and activation
Engineering agent work	SPINE_INTELLIGENCE_AGENT.md, PRODUCT_PLATFORM_BOUNDARY_AND_GO_LIVE_STANDARD.md	Bounded code proposals, testing, approval, execution
Release and verification	MASTER_EXECUTION_PLAN.md, docs/wiki/20-release-readiness-and-verification-evidence.md	Environment gates, launch evidence, stop-ship checks
Full source-traced company set	docs/wiki/README.md, docs/wiki/00-master-canon-and-source-registry.md, docs/wiki/22-source-traceability-appendix.md	Internal knowledge, Coda publishing, source traceability
Supplied attachment/source reconciliation	SOURCE_PACK_RECONCILIATION_2026-07-28.md	Exact duplicates, source authority, adopted decisions, superseded claims, archive treatment and sensitive exclusions

3. Required documentation for every delivery

Every capability, connector, MCP channel, coding-agent change, and Product
surface must include:

1. Owner and bounded responsibility.
2. Entry, input, output, state ownership, authority boundary, and failure path.
3. Development readiness, Platform release readiness, and Customer activation
   readiness.
4. Identity, consent, credential, tenant, and audit requirements.
5. Test and verification evidence, rollback/removal conditions, and documentation
   updates.

4. Documentation migration state

The July 29 lifecycle reconciliation is complete at the authority and active
handoff level:

• Flow A/B/C/D and Flow D precedence are documented;
• Operational Spine is D1/KV and Canonical Fortress is Neon;
• aging is separated from promotion;
• Triage is separated from authority and write ownership;
• Twin is the contextual AI Co-worker behavior, not a second runtime;
• Development, Customer Zero and Customer Production are isolated;
• Workers for Platforms is optional for isolated customer/agent code, not the
  default multi-tenant Platform topology;
• historical, extracted, archive, outbox and status collections are explicitly
  classified as non-authoritative.

Historical files retain their original claims for traceability. Their presence
is not an unresolved canonical contradiction when the file or its collection
index routes readers to the governing set.

5. Closure state

The maintained wiki pack and the docs/frontend-v0 implementation handoff are
complete as indexed document sets. The frontend handoff now includes the work
interaction, connector marketplace, Customer Zero MCP operations, Platform
modules, Administration, shared state, responsive and testing contracts.

“Complete documentation” means the required responsibility and communication
contracts exist and route to frozen authority. It does not mean every documented
runtime feature is implemented or deployed. Implementation and live-environment
claims still require the evidence gates in MASTER_EXECUTION_PLAN.md.

6. Historical material

Older architecture snapshots, implementation plans, generated exports, and
conversation transcripts are retained for rationale and evidence only. When they
disagree with the authority order above, label them Historical or
Superseded rather than silently blending their claims into current work.