Docs(claims): Pre-v0.11.0 claim-accuracy sweep — first-mover registry, parity 93.4%, machine-gated counts#197
Merged
Merged
Conversation
…, parity 93.4%, machine-gated counts Walks the ~18-item claim-accuracy debt list from the 2026-07-15 primary-source verification pass, plus 30+ additional stale claims surfaced by a 39-agent verification fan-out and a triple validation round. Every change traces to a ledger row (private). - Parity claims recomputed from the manifest: 98% -> 93.4% everywhere presented as current state (README badge, parity-coverage.md regenerated, positioning, enterprise-grade, ROADMAP); the 7 api-only leaves named honestly (5 v0.11 federal verbs + version/init). - Machine-gated counts fixed doc-wide: 96 catalogs (tier arithmetic 50+4+22+20), 16 crosswalks, 14 collectors, 13 MCP tools, 4,900+ tests, mypy 292 files — including api-stability, gemara-mapping, and four stale wiki pages (92-era). - FedRAMP first-mover registry row re-based to the shipped 'conmon ksi' verb + CR26 SDR schema framing with explicit caveats (Palladium, FedPy, RegScale/Paramify); two NEW first-mover rows registered: M-25-21 practice/waiver-clock tracking and M-25-22 six-phase acquisition lifecycle. - CISA SbD Pledge described as an alignment self-attestation everywhere (never a signatory claim; formal signing planned at v1.0); OSCAL-MCP landscape aligned to 'one of several'; false SSP/VEX/VSA emit attributions corrected. - Stale 'Sept 30 2026 FedRAMP mandate' framing replaced with CR26 FRC-CSO-JSN (mandatory 2027-01-01) + NTC-0009 (2027-11-01, Class D High, format-agnostic — never an 'OSCAL mandate'); unverified dates dropped (CR26 'effective July 1', 'initial-compliance'); the unverifiable '18 months ahead' claim removed. - GovReady-Q: dormant, not defunct; OpenVEX/VSA rows to planned tense with roadmap-accurate verb names; TPRM/risk-register honest-gap rows updated to shipped state. - Federal-SI walk-through refreshed: M-25-21 primary lens consistently, M-26-05 rescission of the M-22-18 form, deprecated conmon flag replaced, resolved limitations pruned, and a new 'What's new at v0.11' section with source-verified CLI examples for set-practice / acquisition / conmon ksi. - Wiki mirrors + parity-coverage regenerated; ai-governance guide's 'per-practice tracking is a planned follow-up' corrected to the shipped verbs. Gates: pytest 4939 passed, ruff, mypy, docs-health --strict 0 FAIL, doc-counts, parity, version-consistency, roadmap-currency all green.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
allenfbyrd
enabled auto-merge
July 17, 2026 02:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pre-v0.11.0 claim-accuracy sweep
Docs-only accuracy pass (plus one docstring) ahead of the v0.11.0 release:
every public claim re-verified against primary sources and the machine-gated
counts, with stale or over-broad claims corrected in place. Historical records
(dated per-release tables,
docs/releases/reviews/*, version-history rows)are untouched.
What changed
7 api-only / 0 cli-only) — everywhere presented as current state: README
badge, regenerated
docs/parity-coverage.md, positioning, enterprise-grade,ROADMAP, and the parity manifest header. The 7 api-only leaves are named
honestly (the five v0.11 federal AI-governance verbs +
version/init).50 + 4 + 22 + 20), 16 crosswalks, 14 collectors, 13 MCP tools, 4,900+ tests
— including
api-stability.md,gemara-mapping.md, and four stale wikipages.
integration-survey.md§8.6): the FedRAMP rowre-based to the shipped
conmon ksiverb + CR26 SDR schema framing withexplicit caveats; two new rows registered for the shipped OMB M-25-21
practice/waiver-clock tracking and M-25-22 acquisition-lifecycle surfaces.
self-attestation (never a signatory claim); OSCAL-MCP landscape statements
aligned to "one of several"; incorrect SSP/VEX/VSA emit attributions fixed.
replaced with CR26 (mandatory 2027-01-01) + NTC-0009 (2027-11-01, Class D
High, format-agnostic); unverified dates removed; the unsupported
"18 months ahead" claim removed.
throughout, M-26-05's rescission of the M-22-18 self-attestation form
reflected, the deprecated conmon flag replaced, resolved limitations pruned,
and a new "What's new at v0.11" section with source-verified CLI examples.
names; GovReady-Q described as dormant (not defunct); TPRM / risk-register
honest-gap rows updated to shipped state; wiki mirrors regenerated.
Verification
check_docs_health --strict0 FAIL ·check_doc_countsPASS ·check_parityPASS ·check_version_consistencyPASS ·check_roadmap_currencyPASStriple-validated (mechanical gates, independent multi-agent review with
adversarial verification, manual diff read).