You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracking umbrella for completing the doc-drift merge gate work. Consolidates three existing issues into one execution cursor so the COO can drive them to completion as a sequence.
Origin
AA (ChatGPT-5.5 via Oracle) ideation session, 2026-07-03. Ranked #5 in consolidated top-10.
Child issues (execution sequence)
1. #117 — Spec: make documentation drift control merge-enforced
Status: OPEN, spec reviewed and approved (v3 operative spec, OpenClaw review, AA review completed)
What remains: Convert approved spec to implementation. Build authority registry (YAML metadata), CI merge gate (fail-closed on drift), post-merge verification from clean origin/main.
What remains: Build cron-driven sweep that detects drift bypassing the gate and opens evidence-backed reconciliation issues. Deduplicate. Never auto-fix docs.
3. #125 — Add doc-entrypoint freshness check to maintenance sweeps
Objective
Tracking umbrella for completing the doc-drift merge gate work. Consolidates three existing issues into one execution cursor so the COO can drive them to completion as a sequence.
Origin
AA (ChatGPT-5.5 via Oracle) ideation session, 2026-07-03. Ranked #5 in consolidated top-10.
Child issues (execution sequence)
1. #117 — Spec: make documentation drift control merge-enforced
2. #122 — Implement advisory documentation drift sweep issue creator
3. #125 — Add doc-entrypoint freshness check to maintenance sweeps
Oracle guidance
Do a tight version. Avoid documentation governance theatre. Do not overbuild the advisory sweep until the hard gate works.
Execution plan
Acceptance criteria (all three)
Authority boundary