Output from each checker — what's covered, what's flagged, what's still open.
Sample data. These four checkers are built and run end to end, but against a sample dataset, not a production documentation set. The code is real; the content it checks is not. The pattern behind them is one I proved in production with a team at Zeta.
Loading…
How to read this
The ratio is covered tickets over total tickets in that sprint or feature.
No tag — no documentation page references this ticket at all.
Stale tag — a doc page does tag this ticket, but was last edited before the sprint started.
Sprint progress
Feature coverage
Loading…
How to read this
The ratio is content pieces with a recorded sign-off over total AI-touched content checked.
No sign-off — AI-touched content published with no reviewer recorded at all.
Backfilled sign-off — a reviewer is recorded, but the review date is after publish.
Compliance by owner
Loading…
Cross-page consistency
Pages
Loading…
How to read this
Each row is one run of the Release Notes Automation sub-workflow against the sample dataset — a batch of release tickets synthesized into structured notes, gated by a pull request.