doc-freshness-gate

What problem does it solve?

Phase merges generate documentation drift across five important surfaces; without a lightweight governance gate teams risk misalignment and stale narratives. The Doc-Freshness Gate ensures drift is detected, surfaced, and recorded as advisory only, enabling quick remediation without blocking progress.

Core Features & Use Cases

• Reconciles five surfaces: STATE, ROADMAP, PROJECT, CAPTURED, and LEARNINGS_SUMMARY at each phase merge to keep product context current.
• Uses a strict, non-blocking drift detector based on a dual check (mtime and git-blame) and an optional drift-probe to verify claims against the merge.
• Emits greppable markers for audit trails and provides a structured outcome suitable for downstream pipeline steps.

Quick Start

Run the gate on a real phase-merge to verify drift detection and advisory marking.