docs(explainer,readme): the page says what Groundwork does, including the proof - #68
Merged
Merged
Conversation
… the proof Audited both front doors against the repo rather than against memory: all 21 skill cards, the gate cards, the six reason tabs, the lifecycle phases and the "what lives where" table. Three things did not match, and the direction of the mismatch matters: two understated what is there, and the third left out the strongest thing in v0.2.0 entirely. The copy route was the omission. Every push already unpacks a fresh copy, walks it to a first guarded commit and throws it away again, which is exactly the claim both documents open with, and neither mentioned it in any wording. It is a gate card now, next to the self-test card whose logic it extends, and one sentence in the README beside the same idea. Both say the build turns red on the commit that broke the route, and neither says the merge is blocked, because the drill is not a required status check: gate and trace are. code-review was wrong, not merely thin. The card said "two axes", which was true before the security axis landed and survived the rebuild that made this page English. It now names the gate-weakening scan, the two always-on axes and the conditional security axis, which is the one a reader on the Safe tab is being promised elsewhere on the same page. comply listed four regimes where the register carries nine, so the card now names the product and cyber security duties too and says the dates are verified against the source. Verified in the rendered page, not in the source: ten gate cards, every icon resolving, the grid landing on five even rows instead of four and an orphan, and both corrected skill cards wrapping inside their card. Counts on the page are derived and unchanged: 21 skills, 21 checks, 19 decisions. Traces-to: SC-11
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
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.
What changed and why
Both front doors were audited against the repo instead of against memory: all 21 skill cards
checked against each skill's own
description:, the gate cards against the registry, plus thesix reason tabs, the lifecycle phases, the "what lives where" table and the requirements. Three
mismatches, all in the same direction of harm: the page claimed less than the framework does.
The copy route was missing entirely. Every push already unpacks a fresh copy, walks it to a
first guarded commit and throws it away again. That is the exact claim both documents open with,
and neither mentioned it in any wording, in the release where it shipped. It is a gate card now,
placed next to the self-test card whose logic it extends, and one sentence in the README beside
the same idea. Both are careful about what they promise: the build turns red on the commit that
broke the route. Neither says a merge is blocked, because
drillis not a required status check(
gateandtraceare).code-reviewwas wrong, not merely thin. The card said "two axes". True before the securityaxis landed in PR #24, and it survived the rebuild that made this page English. It now names the
gate-weakening scan, the two always-on axes and the conditional security axis, which is the thing
a reader on the "Safe" tab is being promised elsewhere on the same page.
complylisted four regimes where the register carries nine. It now also names the productand cyber security duties, and says the dates are verified against the official source.
Everything else matched: 21 cards for 21 skills, every named skill exists, the nine gate cards
describe real gates, and the three counts on the page are derived by
explainer-statsratherthan typed.
Verified by
node checks/check.mjsgreen, and the page exercised in headless Chrome rather than read assource:
Self-testandAnd the rest, and the two-column grid lands onfive even rows instead of four plus an orphan
Screenshot check was done on a scratch copy with the scroll-reveal forced visible and the
sections above hidden, because a static shot of the real file only captures the hero. The DOM
assertions above ran against the unmodified file.
Not verifiable here: how the section looks on a real phone. The grid collapses to one column
under 680px by an existing media query that this change does not touch.