Context
#16206 was re-scoped during the #16167 incident: the first unblocker is a tracked canonical target before any broader Compose decomposition. PR #16218 implements and proves that one-PR leaf; it needs an honest close target rather than falsely closing the broader parent.
Live latest-open sweep: checked the latest 20 open issues plus exact local/GitHub matches at 2026-07-31T05:18:41Z; no equivalent leaf exists. Memory Core semantic ticket search was unavailable (ask_knowledge_base is not implemented on the connected endpoint).
The Problem
The tracked local overlay bound the retired checkout data plane and did not pin a stable Compose project identity. Removing that bind also exposed two runtime gaps: KB/MC could not read orchestrator deployment state, and runtime discovery treated an optional local-model service as required.
The Architectural Reality
ai/deploy/docker-compose.yml owns Docker named volumes. ai/deploy/docker-compose.local-agent-os.yml is the local access/provider overlay. Runtime discovery keys off Compose project labels, so the tracked launch needs one stable project name and must monitor the services it actually starts.
The Fix
- Pin project
neo-local-agent-os.
- Inherit the base file's Docker-owned data volumes.
- Share deployment state read-only with KB/MC.
- Route the host LM Studio provider explicitly.
- Monitor only Chroma, KB, MC, and orchestrator.
Contract Ledger
| Target |
Authority |
Behavior |
Evidence |
| Local Compose launch |
tracked base + local overlay |
stable identity, Docker-owned data, four-service discovery |
PR #16218 |
Decision Record impact
None — this implements the re-scoped #16206 leaf without changing ADR authority.
Acceptance Criteria
Out of Scope
Compose fragment decomposition, runbook rewrite, re-embedding (#16208), and wake/reboot receipts (#16167).
Avoided Traps
No host-plane folder copy, Chroma downgrade, or new Compose abstraction.
Related
Parent scope: #16206
Implementation: #16218
Retrieval Hint: #16206 canonical Compose stable project Docker-owned volumes
Authored by Emmy (GPT-5.6 Sol Ultra, Codex) (@neo-gpt-emmy).
Context
#16206was re-scoped during the#16167incident: the first unblocker is a tracked canonical target before any broader Compose decomposition. PR #16218 implements and proves that one-PR leaf; it needs an honest close target rather than falsely closing the broader parent.Live latest-open sweep: checked the latest 20 open issues plus exact local/GitHub matches at 2026-07-31T05:18:41Z; no equivalent leaf exists. Memory Core semantic ticket search was unavailable (
ask_knowledge_baseis not implemented on the connected endpoint).The Problem
The tracked local overlay bound the retired checkout data plane and did not pin a stable Compose project identity. Removing that bind also exposed two runtime gaps: KB/MC could not read orchestrator deployment state, and runtime discovery treated an optional local-model service as required.
The Architectural Reality
ai/deploy/docker-compose.ymlowns Docker named volumes.ai/deploy/docker-compose.local-agent-os.ymlis the local access/provider overlay. Runtime discovery keys off Compose project labels, so the tracked launch needs one stable project name and must monitor the services it actually starts.The Fix
neo-local-agent-os.Contract Ledger
Decision Record impact
None — this implements the re-scoped
#16206leaf without changing ADR authority.Acceptance Criteria
Out of Scope
Compose fragment decomposition, runbook rewrite, re-embedding (
#16208), and wake/reboot receipts (#16167).Avoided Traps
No host-plane folder copy, Chroma downgrade, or new Compose abstraction.
Related
Parent scope: #16206
Implementation: #16218
Retrieval Hint:
#16206 canonical Compose stable project Docker-owned volumesAuthored by Emmy (GPT-5.6 Sol Ultra, Codex) (
@neo-gpt-emmy).