Cite a PubLedge original draft as its own source - #18
Merged
Merged
Conversation
The draft JIA's instrument, parties, term and duty took `source` from the instrument's official_url (the OAIP page) while the term and duty took `source_locator` from the statutory section it interprets. That pair told a consumer the text came from OAIP at Utah Code section 13-72a-203, but the text is PubLedge's unissued draft. For publedge-original-draft instruments, OF records now cite the draft's canonical PubLedge URL as source, and terms and obligations use the draft's own section heading as locator. The interpreted statute stays linked through the existing source-owned anchor to the EveryAILaw term. Authority-published records are unchanged; only the five JIA records move. Adds a projection test with an authority-published control and regenerates the Obligation-First fingerprint (seven provenance claims). Part of PUB-2 (EV02). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4 tasks done
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.
Summary
Part of PUB-2 (EV02). This is step 2 of the handoff: the provenance pairing decision.
The draft JIA's OF records (instrument, two parties, term, duty) took
sourcefrom the instrument'sofficial_url, the OAIP page. The term and duty tooksource_locatorfrom the statute section they interpret. Read together, that pair said the text came from OAIP at Utah Code §13-72a-203. In fact the text is PubLedge's unissued draft.For
publedge-original-draftinstruments, the OF records now cite the draft's canonical PubLedge URL assource. Terms and obligations use the draft's own section heading assource_locator. The interpreted statute stays linked through the existing source-owned anchor to the EveryAILaw term. Authority-published records are unchanged; only the five JIA records move.issuedBystill names OAIP as the interpreting authority.Review this choice: the alternative was to keep OAIP as
sourceand change only the locator. I chose the draft record because the text's origin is PubLedge, and OAIP hasn't issued it.Merge together
Companion OF PR: snapsynapse/obligation-first#14. It adds source and locator to the EV02 answer, and its Utah expectation reflects this change.
Test plan
node --test tests/*.test.js(61 pass) andnpm run evalspassOBLIGATION_FIRST_DIR=../obligation-first npm run verify:cipassesverify:federationpasses with the companion OF branch🤖 Generated with Claude Code