docs: nine statements that had stopped being true, and a closed issue four docs still cited - #592
Merged
Merged
Conversation
… four docs still cited The 2026-09-07 expert review accepted a documentation slice that never landed. This is that slice, re-verified against the tree today rather than taken from the review, plus three staleness defects the review predates. Always-loaded, so every session inherited them: CLAUDE.md said MM-2/3/4 were all blocked on externals. MM-2's build completed on 2026-09-12 and #574 shipped on 09-16; MM-3's design half shipped as #569. Only MM-3's wiring and MM-4 are blocked. CLAUDE.md's standing correction 1 said MIPS CQMs are "sunsetting ~PY2030". The fact sheets propose EXTENDING them for PY2027+. The sunset that does exist is a different policy — traditional MIPS as a reporting option, after PY2028 — and merging the two is what the correction was supposed to prevent. Also relabelled: the FHIR transition is an RFI seeking comment, which is weaker than a proposal, and the entry called itself PROPOSED while its own body said "seeks comment on". AI_GUARDRAILS attributed "the user must not proceed" to CDS Hooks' `critical`. The 2.0 spec defines it only as the top of an urgency ordering. The refusal is unchanged; it rests on WorkWell being supplementary to WebChart, not on a spec sentence that does not exist. Stakeholder-facing: WHAT_WORKWELL_IS said the Maui sandbox runs WorkWell's AUTHORED cms122/cms125. It has routed six official measures since ADR-078 on 2026-09-08. The sentence has been flatly false for twelve days in the document we hand to people. Governing: ROADMAP called the CMS137 final-rule confirmation "a formality to record". The sandbox routes cms137 today, so the rule decides whether the PHI phase inherits it or the routing comes out. The plan does not wait on it; the answer is not foregone. ARCHITECTURE described the test-fixture gate as if it executed measures. `validateTests` is four structural assertions — fixtures exist, each names a fixture, a subject and an expected outcome. Studio's tick on that row means well-formed, not run-and-passed. The Studio label itself still overstates and is a product change, not prose, so it is filed rather than fixed here. OSHA_1910_95_STS said the (g)(8)(ii) chapeau "switches off every follow-up action". (g)(8)(i)'s 21-day written notification is a separate paragraph and is unconditional — it survives a determination that the shift is not work related. A regulatory misstatement in our own measure documentation. STANDARDS_CONFORMANCE said occupational measures "cannot acquire" an answer key. A route exists and is on the record — a steward publishing specifications and expected results, or an independent implementation to disagree with. Neither exists nor is in progress, which is the claim that holds: nothing here is graded by anyone but us. Staleness the review predates: guide ch.9 is the chapter that claims to own current state and still called #557 blocked four days after it merged, and carried a 2026-08-08 suite count of 1,940 against today's 2,804. And #533 closed on 2026-09-08 with its ingest half unshipped, while MEASURES, DECISIONS, DEPLOY, DATA_MODEL_CONTRACTS and ROADMAP all cited it as the open tracker for that half. A closed issue cannot carry work, so #591 does; every citation now points there. Journal entries are left alone — they record what was true when written.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 71b057be4b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Review caught that the row I wrote reported 23 skips in one column while the next column still said "The 15 skips" — I updated the count in one half and left the prose in the other, which is the defect the row exists to prevent: a maintained state chapter giving two contradictory numbers for the same run. It also questioned the totals. Its arithmetic over journal deltas gave 2,801/2,777; I had written 2,804/2,780 from a run taken before #588's review-fix commit added two more tests. Rather than reconcile two pieces of reasoning, I re-ran the suite against main's backend: 2,807 total, 2,783 pass, 1 fail, 23 skip. Neither prior figure. Both columns now come from that one run, and the row says which run it was.
Taleef7
added a commit
that referenced
this pull request
Sep 23, 2026
… four docs still cited (#592) The 2026-09-07 review's documentation slice, never landed until now, re-verified against the tree rather than taken from the review — plus three staleness defects it predates. Always-loaded and therefore inherited by every session: CLAUDE.md said MM-2/3/4 were all blocked (MM-2 finished 09-12), its standing correction had the MIPS CQM policy backwards (the fact sheets propose EXTENDING them; the sunset that exists is a different policy about traditional MIPS as a reporting option), and AI_GUARDRAILS attributed 'the user must not proceed' to CDS Hooks' critical, which the 2.0 spec defines only as the top of an urgency ordering. The refusal is unchanged. Stakeholder-facing: WHAT_WORKWELL_IS said the pilot sandbox runs AUTHORED cms122/cms125. It has routed six official measures since 09-08. Governing: the CMS137 confirmation is not 'a formality' (the sandbox routes cms137, so the final rule decides whether the PHI phase inherits it); the test-fixture gate is structural and does not execute measures; the OSHA (g)(8)(i) 21-day notice is unconditional, not switched off by the (g)(8)(ii) chapeau; occupational measures have no answer key rather than being unable to acquire one. Staleness: guide ch.9 called #557 blocked four days after it merged and carried an 08-08 suite count, and #533 closed 09-08 with its ingest half unshipped while five documents cited it as that half's tracker — #591 carries it now. Review caught that the corrected suite row disagreed with its own next column; both halves now come from one re-run (2,807/2,783/1 fail/23 skip). Journal entries untouched: they record what was true when written.
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.
Docs only. No code, no behaviour change.
The 2026-09-07 expert review accepted a documentation slice ("PR 4") that never landed. This is that slice — re-verified against the tree today rather than taken from the review — plus three staleness defects the review predates.
Always-loaded, so every session inherited them
CLAUDE.md:130CLAUDE.md:137-140AI_GUARDRAILS.md §1.1criticalmeans "the user must not proceed"CLAUDE.md's correction 1 also called itselfPROPOSEDwhile its own body said "seeks comment on". It is an RFI; relabelled.Stakeholder-facing
docs/WHAT_WORKWELL_IS.md:20said "the Maui sandbox currently runs WorkWell's authored versions of those two measures." It has routed six official measures since ADR-078 on 2026-09-08 — flatly false for twelve days, in the document we hand to people. Now: six on the pilot, two on TWH, nine vendored at 455/455.Governing
ROADMAP:49called the CMS137 final-rule confirmation "a formality to record". The sandbox routes cms137 today, so the rule decides whether the PHI phase inherits a measure the pilot has little data to compute, or whether the routing comes out. The plan does not wait on it; the answer is not foregone. (The review's B-3, accepted 09-08.)ARCHITECTURE.md:137described the test-fixture gate as if it executed measures.validateTestsis four structural assertions. Studio's ✅ means well-formed, not run and passed. The Studio label itself still overstates — that is a product change, not prose, so it is filed rather than fixed here.OSHA_1910_95_STS.mdsaid the(g)(8)(ii)chapeau "switches off every follow-up action".(g)(8)(i)'s 21-day written notification is a separate paragraph and unconditional — it survives a determination that the shift is not work related. A regulatory misstatement in our own measure documentation.STANDARDS_CONFORMANCE.mdsaid occupational measures "cannot acquire" an answer key. A route exists and is on the record (a steward publishing specs + expected results; or an independent implementation to disagree with). Neither exists nor is in progress — which is the claim that actually holds: nothing here is graded by anyone but us.Staleness the review predates
docs/guide/09-state-and-roadmap.mdis the chapter that claims to own current state. It still called MM-2 PR 3: import the ACO's attributed patient list and report num/den/exclusions with patient-level evidence #557 "blocked on owner DDL and three ACO inputs" four days after it merged, and carried a 2026-08-08 suite count of 1,940 against today's 2,804.MEASURES,DECISIONS,DEPLOY,DATA_MODEL_CONTRACTSandROADMAPall cited it as the open tracker for that half. A closed issue cannot carry work, so cms165 blood pressures are not profile-stamped at WebChart ingest — #533's other half, which closed with the issue #591 does; every citation now points there.Journal entries are deliberately untouched — they record what was true when written.
Verification
Every claim re-checked in the tree today, not inherited from the review. All twelve files NUL-checked (this repo has had three control-byte incidents). No
.tstouched, so no typecheck or suite implication.