Skip to content

End the demo on a named provision, not on a score - #93

Merged
kmadan merged 1 commit into
mainfrom
fix/demo-ending
Aug 30, 2026
Merged

End the demo on a named provision, not on a score#93
kmadan merged 1 commit into
mainfrom
fix/demo-ending

Conversation

@kmadan

@kmadan kmadan commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Three changes from your review.

Act 3 ended on 0 green, 29 red

True, and it is the argument act 2 makes, but as an ending it reads as the tool does not work to anyone who has not followed the reasoning.

It now answers the 150 declarations first, the way a reader actually would, and ends on:

- **Article 14 Controls Not Satisfied:** ['Article 14(1)-(2) oversight designed into the system']

A named provision and the specific control outstanding. That is where this tooling is differentiated: a count is a grade, a provision is something you can act on.

Answering the declarations is done by _answer_declarations, which takes field types from GOPAL's coverage data where it has inferred one and from the field name otherwise. A guard refuses to record if fewer than 100 of the 150 get answered, since that would mean the scaffold shape changed and the act would silently go back to showing an unanswered contract.

Act 4 is gone

The metric gap report is a good thing to show a contributor and a poor thing to show someone deciding whether to adopt. It stays as a command in the contributing section of the page, where the audience is right.

Pacing

Before After
README cut 48s 36s
Page cut 93s 69s
Typos 55% of commands 25%

The README cut also drops its framing line, since it autoplays above the fold and has to be watchable before a reader decides to scroll. The page cut keeps it.

Verification

Both casts replayed through a VT emulator: every row carrying a highlighted phrase matches what the command actually printed, including the new Article 14(1)-(2) sweep. 216 tests pass.

Pairs with website#36.

Three changes from reviewing the recording.

Act 3 ended on an empty contract failing all 29 policies. True, and the
argument act 2 makes, but as an ending it reads as "the tool does not work" to
anyone who has not followed the reasoning. It now answers the 150 declarations
first, the way a reader would, and ends on:

    Article 14 Controls Not Satisfied:
      ['Article 14(1)-(2) oversight designed into the system']

A named provision and the specific control. That is what the product is
actually differentiated on and what a reader can act on, where a count reads as
a grade.

Act 4, the metric gap report, is dropped. Enumerating the metrics nobody has
written an evaluator for is a good thing to show a contributor and a poor thing
to show someone deciding whether to adopt. The command stays in the
contributing section of the website page, where the audience is right.

The README cut is 36 seconds rather than 48. It autoplays above the fold, so it
has to be watchable before a reader decides to scroll. The page cut keeps its
framing line and runs about 70 seconds, where a reader has chosen to watch.

Typos now fire on a quarter of commands rather than half, which reads as a
person typing rather than as someone who cannot type.

Highlights re-verified by replaying both casts through a VT emulator: every row
carrying a highlighted phrase matches what the command actually printed.
@github-actions github-actions Bot added 📝 documentation Improvements or additions to documentation 🚀 enhancement New feature or request 🤝 good first issue Good for newcomers labels Aug 30, 2026
@kmadan
kmadan merged commit eca25a2 into main Aug 30, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📝 documentation Improvements or additions to documentation 🚀 enhancement New feature or request 🤝 good first issue Good for newcomers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant