Repository navigation
The prov guest: turn records checked against W3C PROV-CONSTRAINTS - #168
Conversation
…es and inventory generator (work in progress) The LexLean module PrismProv judges a PROV-N document against W3C PROV-CONSTRAINTS; W3C's 166 PROV-N cases are pinned and kept, and are the acceptance vectors of the guests prov and prov-invalid. The guests' wasm, the generator program's binary and the standards register follow. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
The guests prov and prov-invalid (one module, app/src/PrismProv.lex.tex) carry W3C's 166 PROV-N constraint cases as acceptance vectors: the 99 valid ones and the 67 invalid ones, since one guest build holds about 110 vectors. The request is check, a newline and a PROV-N document; the answer is valid, invalid and the constraint numbers, malformed, or unjudged past the guest's bounds. generators/prov reads the Recommendation's 56 numbered definitions, inferences and constraints into ST-01. The suite shows 14 of them enforced (a case's verdict changes when the rule is switched off); the other 42 are debt, and the oracle's gaps say why. PROV-N is registered without an inventory yet. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
…-85vrxq # Conflicts: # app/specs/guests/lock.json
|
Merge train notice: the merge train merges this pull request once it is green on current main; don't enable auto-merge. Generated by Claude Code |
|
This change does not touch what that test times: no page module loads the prov guest yet, and the diff adds only the model, its specs, pinned texts and a generator. #164's description records the timing budgets failing on main since #145 and #161. I have not re-run the job: this pull request is a draft until #164 merges, and the push that then merges main and moves the guest entries into the per-guest files runs the gates again. If QR-05 is still over budget on that run I will look at it there. Generated by Claude Code |
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
|
Merge train: 1b37ac7: not merged, because it conflicts with main (0f9d804) and the pull requests the train takes before it. Fix it on this branch (merge main first) and the train tests it again. Generated by Claude Code |
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
|
Merge train: 0a4fffb: not merged, because it conflicts with main (7815f8e) and the pull requests the train takes before it. Fix it on this branch (merge main first) and the train tests it again. Generated by Claude Code |
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
|
Merge train: b5521ca: not merged, because it conflicts with main (e8a7ee4) and the pull requests the train takes before it. Fix it on this branch (merge main first) and the train tests it again. Generated by Claude Code |
Keeps the prov guest entries beside main's new parts, standards and oracle records; the oracle gap for prov now points at the debt file so the person generator's request stays inside its bound. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
|
Generated by Claude Code |
|
Merge train: 7777c31: not merged, because its check "page / gates" ended failure on this head, so it is not green; push to this branch to run it again. Fix it on this branch (merge main first) and the train tests it again. Generated by Claude Code |
Keeps the prov parts entries beside the EMMA records main gained. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
With the oracle sources in their own files the prov gap carries its full text again. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh
|
Live: this change is on the published page, as main The publish job opened the published page in a fresh Chromium and its live checks passed (PG-01, PD-01, PD-02): https://github.com/afflom/me/actions/runs/43977249372 |
Requested by Alex · project thread
What this adds
A LexLean guest,
prov(site/prov/guest.mjs, moduleapp/src/PrismProv.lex.tex), that judges a PROV-N document against W3C's Constraints of the PROV Data Model (Recommendation 30 April 2013). It is the check the chat's turn records have to pass.check, a newline, a PROV-N document (at most 4096 bytes).valid;invalidand the numbers of the constraints that do not hold;malformedwhen the text is not PROV-N;unjudgedwhen normalization would pass the guest's bounds (4,000 statements or 30,000 existential variables in one instance).unjudgedis not a verdict.The oracle
W3C's own PROV-N cases for the constraints (166 files, 99 PASS and 67 FAIL), listed by the working group's test page. Every source is pinned by SHA-256 in
app/specs/prov/spec.jsonand kept atapp/specs/standards/texts/<sha256>, so no gate fetches.provcarries the valid cases andprov-invalid(the same module, the same wasm bytes) the invalid ones. Four cases W3C serves as two pairs of identical files are two vectors.What the suite does and does not show
Each numbered rule was switched off in the checker in turn, to see which cases notice (
shownin the spec).enforcedByin ST-01.gapssays why. They are not claimed as verified.unpinned).Mechanics
generators/prov(LexLean, generatorprovrules) reads the Recommendation's 56 numbered definitions, inferences and constraints intotest/standards/generated/w3c-prov-constraints.jsonl.app/specs/guests/prov/prov.jsonandprov-invalid.jsonwith their locks, andgenerators/guests/steps/prov.jsonwrites the pinsite/prov/guest.mjs(the layout of One file per guest; the train runs the browser acceptances and says why it waits #164).--base origin/main), GN-01, GU-01, PT-01, RZ-01, and the conformance suitesguests,generators,privacy,standards,oracle.Bounds
Made-up documents at the 4096-byte limit were used for capacity only, never as evidence of conformance: every shape tried is answered, the heaviest in about 10 seconds and 400 MB before answering
unjudged. W3C's cases each take a few milliseconds and under 2 MB.🤖 Generated with Claude Code
https://claude.ai/code/session_013Asa3N1XfPZYedNcr3hPNh