Skip to content

Tracking: Doc-Drift Merge Gate (#117 + #122 + #125) #141

Description

@marcusglee11

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

  1. Spec: make documentation drift control merge-enforced #117: Implement authority registry + CI merge gate from approved v3 spec. Substantive code — dispatch via EA (ea-dispatch 3-phase plan/implement/review).
  2. Implement advisory documentation drift sweep issue creator #122: After Spec: make documentation drift control merge-enforced #117 gate works, build advisory sweep. Detect drift, open issues, deduplicate. Wire into maintenance sweep after dry-run shows acceptable noise.
  3. Add doc-entrypoint freshness check to maintenance sweeps #125: After Implement advisory documentation drift sweep issue creator #122, add doc-entrypoint freshness check as named check.

Acceptance criteria (all three)

Authority boundary

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestops

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions