Skip to content

v0.23.0 — Mandatory validity anchor

Choose a tag to compare

View all tags
@pedrofuentes pedrofuentes released this 05 Jul 10:14
· 10 commits to main since this release
v0.23.0
23984cd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Backlog-hygiene core-requirement release. The Sentinel validity anchor is now mandatory on every filed 🟡/🟢 issue (previously documented only as opt-in backlog hygiene). Ruleset stays v1, rubric stays v1 — the report protocol (Status: line, Required action mapping, verdict semantics, severity tiers) is unchanged; this adds a filing requirement only.

Added

  • Mandatory validity anchor (SENTINEL.md §Follow-ups & Actions): every filed 🟡/🟢 issue body MUST carry the anchor — a human+machine anchor line (**Anchor:** file:line @ <short SHA> · dim X plus the <!-- sentinel-anchor … --> marker) and the finding's quoted ≤3-line evidence in a fenced block — with a sentinel:security label for dim-A1/A2 or security-path findings. The evidence + reviewed SHA already exist in the report, so the anchor is free at filing time and lets any issue be cheaply re-checked against HEAD as code moves.

Changed

  • sentinel/BACKLOG-HYGIENE.md §1 reframed opt-in → required by SENTINEL.md §Follow-ups; §2–§5 (labels, sweep, example Action) remain opt-in. No safety rule weakened: automation flags but never reaps, sentinel:security never auto-closeable, stale ≠ resolved, closure needs positive resolution evidence + a human.
  • template/AGENTS.md §After Sentinel "Issue hygiene" line aligned with the mandatory anchor (names the <!-- sentinel-anchor … --> marker; states the anchor is required).

Full diff: #33

Assets 2
Loading