Skip to content

fix(compliance): delete g9 waiver and retract unperformed q1 sar - #771

Open
lahlfors wants to merge 5 commits into
docs/poam-ttm-monitoringfrom
fix/g9-waiver-and-sar
Open

lahlfors wants to merge 5 commits into
docs/poam-ttm-monitoringfrom
fix/g9-waiver-and-sar

Conversation

@lahlfors

@lahlfors lahlfors commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Deletes Gate G9's KNOWN_DOCUMENTED_GAPS waiver, corrects the references it hid, and retracts the 2026-Q1 security assessment report. Opens POAM-2026-224. Stacked on #770 (POAM-2026-222); retarget to main after #770 merges.

  1. The waiver is deleted.
    • It held 162 entries naming 160 targets. Classified against git history, 129 targets never existed in any commit, 28 were retired, and 3 exist at HEAD.
    • It was described as deliberate NIST RMF gap citations. In practice the gate skipped those paths in every document in scope, which hid citations of artifacts that never existed.
    • With it gone, the current DOC_SCOPE (69 documents) surfaced 17 broken references in 9 documents:
      • retired paths are pinned as <sha>^:<path>, or linked live where the file moved;
      • citations of artifacts that never existed are corrected to say so.
  2. The SAR is retracted, not edited. compliance/sar/SAR_2026Q1.md moves verbatim to compliance/archive/retracted/ under a dated notice that withdraws its §7 certification. It records a security assessment that did not take place:
    • no interview record or test output exists, and the assessor is not identified;
    • it cites its assessment plan at a path that exists in no commit. a2a338b8 re-pointed the citation there after the draft plan it first cited was deleted in 00442dec;
    • its disclosure of a rewrite was removed. c7174e05 rewrote its findings after its 2026-03-06 date and added a note saying so; 65949083, a rewrite of internal-facing documents for public release, deleted the note without replacing it. Its Document History still shows a single 1.0 entry.
  3. G9 has one exclusion, and it is verified. A file under compliance/archive/retracted/ is skipped only if all three hold; otherwise it is reported and checked in full:
    • its first non-empty line is a > **RETRACTED YYYY-MM-DD** notice;
    • the date is a real calendar date;
    • the notice names a POAM item that has a row in docs/POAM.md.
  4. Branch-name examples are checked as branch names. The examples in the branch-naming tables (AGENTS.md, CONTRIBUTING.md, docs/operations/GIT_WORKFLOW_STANDARDS.md) are verified against their documented pattern, including the 30-character description limit, instead of being resolved as paths.
  5. AGENTS.md now states the real scope. Most of docs/ is outside DOC_SCOPE. Without the waiver, all of docs/ except docs/partners/** had 299 broken references in 52 documents at eca0c553. POAM-2026-224 tracks widening the scope area by area. Each widening PR corrects its area's references, and deliberately missing artifacts use a marker G9 verifies: the path must not exist and must name an open POAM item.

Verification

  • uv run python scripts/check_doc_references.py: 69 documents, 0 issues, no waiver
  • uv run pytest tests/test_check_doc_references.py -q: 52 passed (14 new)
  • uv run python scripts/check_poam_lula_divergence.py: 0 divergences
  • uv run python scripts/check_oscal_claim_census.py: 209 census entries against 208 OSCAL claims, 0 errors
  • uv run bandit -r src/ scripts/ -c pyproject.toml -ll -ii: 0 High / 0 Medium

Gate G9's KNOWN_DOCUMENTED_GAPS waiver excused 160 targets in every
document in scope, 129 of which never existed in any commit. Delete it,
correct or pin the 17 references it hid in DOC_SCOPE, and retract the
2026-Q1 SAR, which records an assessment that did not take place, to
compliance/archive/retracted/ under a dated notice.

G9 now verifies a retracted record's first-line notice and its POAM row
before skipping the preserved body, and checks branch-naming table
examples against their branch patterns instead of the filesystem.
AGENTS.md states that most of docs/ is still outside DOC_SCOPE, and
POAM-2026-224 tracks widening it area by area.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant