docs: visual judge proof and finished Build Week summary#4
Merged
Conversation
… week Restructure the README front matter for a non-technical first read: a 30-second version, a two-shot verifier proof, why it is more than a privacy test, the authority split, a verified-facts table, and a single Try it yourself path covering watch, challenge, and CI. Commit the two hosted-verifier screenshots under docs/screenshots. Add a finished-product summary and tag timeline to the top of BUILD_WEEK.md. Surface the existing model-authority tests by name in JUDGE_START_HERE.md. Correct the Action README so it no longer tells consumers to swap an already-pinned tag, and clarify in Limitations that the reusable Action runs on Windows, Ubuntu, and macOS while the repair lifecycle is Windows-verified. No product, verifier, evaluator, evidence, or model-boundary behavior changed.
Add a fourth Try it yourself path that reproduces a committed sealed report byte for byte and fails the gate on a committed broken bundle, so a judge can see both PASS and BROKEN_PROMISE on files that ship in the repo, with no init, scaffolding, or key. Document the committed artifacts/verify set and honest programmatic use of the evaluatePromise function in ADOPTION. Add a CI status badge to the README. No product, verifier, evaluator, evidence, or model-boundary behavior changed.
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.
Final presentation and provenance pass. Documentation, images, and one Action README wording fix only. No product, verifier, evaluator, evidence, schema, seeded-defect, or model-boundary behavior changed.
What changed
Verification
npm run typecheckpasses. Nosrc/,landing/, orpublic/source changed, so no site redeploy is required.git diff --checkclean. Screenshots confirmed 1920x1080 with no private data, paths, or keys.Owner follow-up
01-broken-promise.pngand02-models-without-authority.pngduring the video, drop them intodocs/screenshots/, and uncomment the ready image block in the README "See the proof" section to complete the four-image sequence.