Unclassified

22 — Source Traceability Appendix

Status: Maintained registry seed

Frozen architecture

SourceStateGoverns
docs/architecture/ARCHITECTURE_LOCK.mdCanonicalKernel, laws, planes, runtime, Workbench, Twin, capabilities, Spine
docs/architecture/IMPLEMENTATION_CONTRACT_v1.1.mdCanonicalClerk, Neon, D1/KV bounds, Projection Engine, public MCP, execution
docs/architecture/PLATFORM_LOCK_v1.0.mdCanonicalFreeze declaration and implementation order
docs/architecture/FOUR_BUTTONS.mdCanonicalOODA interaction grammar
docs/architecture/TWIN_BEHAVIOR.mdCanonicalSilence, surfacing, authority
docs/architecture/WORKBENCH_MATRIX.mdCanonicalRole and department view matrix
docs/architecture/WORKBENCH_ROLE_CAPABILITY_MAP.mdCanonicalRole-to-capability mapping
docs/architecture/MASTER_EXECUTION_PLAN.mdCanonicalExecution phases and definition of done
docs/architecture/CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.mdDerived governing standardEnvironment, repository, marketplace, frontend and release contract
docs/architecture/IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.mdDerived publication contractPlugin Directory package, embedded host UI, MCP Marketplace package, browser Workbench, discovery and connection boundaries
docs/architecture/TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.mdDerived governing standardTenant entity schema, four flows, Operational/Fortress split, search, promotion, retention and environment lifecycle
docs/architecture/SOURCE_PACK_RECONCILIATION_2026-07-28.mdControlled reconciliationAdopted, corrected and rejected source claims

Approved July 27 decisions

SourceStateGoverns
docs/superpowers/specs/2026-07-27-auth-connector-spine-binding-design.mdApprovedConnector identity, Spine and schema binding, fail-closed
docs/superpowers/plans/2026-07-27-auth-connector-spine-binding.mdApproved planBinding implementation sequence
docs/superpowers/specs/2026-07-27-launch-infrastructure-freeze-design.mdApprovedJuly 30 identity, hosting, credential, binding, release lanes
docs/superpowers/specs/2026-07-27-customer-zero-publication-gates.mdApprovedCustomer Zero evidence and publication gates
docs/superpowers/plans/2026-07-27-to-30-go-live-runbook.mdApproved runbookFreeze and cutover work

Code evidence

AreaEvidence
Gateway identity and runtimeservices/gateway/src/
Clerk integrationservices/gateway/src/clerk-auth.ts
Connector controlservices/gateway/src/integrations.ts
Public MCPservices/mcp-connector/
Internal MCP Poolservices/mcp-pool/
Integration MCPservices/integration-management-mcp/
Provider MCPservices/provider-management-mcp/
Pipelineservices/pipeline/
Projection Enginepackages/projection-engine/
Spine entitiespackages/spine-entities/
Workbench rolespackages/workbench-config/
Governance and Hermesservices/govern/, services/hermes/
Customer Zeroservices/gateway/src/customer-zero.ts

Evidence gaps

  • strict binding tables are approved but not present in runtime migrations;
  • legacy Supabase and Descope code remains in parts of the repository;
  • host-to-host connected-tool inheritance is not proven;
  • code-backed catalog entries do not prove OAuth, read, write, sync, or live state;
  • marketplace publication and third-party review are not guaranteed by July 30;
  • deployed model and agent claims require environment-specific evidence;
  • Customer Zero journeys require recorded production proof, not local tests alone.

Source ingestion procedure

For every additional ZIP, PDF, PPTX, HTML, JSON, Markdown, text export, Coda page,
or chat transcript:

Inventory → extract → classify → reconcile → create page
→ link evidence → record version → review → verify

Historical sources remain available for traceability but cannot override frozen
canon without an approved decision.