Unclassified
17 — Implementation Alignment and Gap Register
Canonical reference: 00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md §28
Status: Canonical (evidence-based, continuously updated)
1. Alignment work that remains
The August codebase alignment document reported 30 services against a smaller canonical plane model and identified consolidation gaps. Key alignment work:
- consolidate loader/normalizer behavior into the canonical Pipeline boundary
- consolidate fragmented Twin runtime services into a coherent Twin/AI Workbench runtime
- create or harden Configuration Manager and Activation Bridge
- maintain clear separation of Spine, Spine Cache, Blobs, Business Memory, Personal Memory, AI Memory, Session Logs and Audit Logs even if physically co-located
- consolidate agent registry/workflow semantics into Capability Fabric and ADK boundaries
- keep Governance separate from Hermes execution
- move direct provider/writeback behavior behind outcome, verification, reconciliation and governed writer contracts
- ensure gateway/ADK middleware cannot silently bypass Governance or create implicit approval
- treat legacy n8n/product-plane orchestration or direct
spine.writesemantics as migration evidence rather than final doctrine
2. Readiness evidence model
Readiness must be evidence-based across at least: implemented, wired, deployed and verified end-to-end. Presence of code or a Wrangler manifest is not proof of production readiness.
3. Implementation status labels
| Label | Meaning |
|---|---|
| VERIFIED | Present in code, configuration or tests. Does not by itself prove live deployment. |
| INTENDED | Required target contract. Retained even when the complete runtime is not yet wired. |
| DRIFT | Present implementation contradicts or bypasses the target contract. |
| DECISION | The repository cannot safely settle the choice; named owner input is required. |