Keep obligations created by draft terms in the draft state - #17
Merged
Merged
Conversation
A concrete obligation took its lifecycle from the shared obligation definition before its creating term. The draft JIA's first-session duty therefore projected lifecycle, operative and enforcement status as unknown, because the shared definition declares "operative", even though its only creating term is a draft. Joined into a consumer answer, that duty could read as binding. When the creating term is draft or proposed, the concrete obligation now takes the term's lifecycle and derives operative and enforcement status from it, ignoring the definition's generic values. Issued creators are unchanged. One record changes: the JIA duty now projects draft, future, unsignaled, matching its term. Adds a projection test with draft, proposed and issued-creator controls, and regenerates the Obligation-First fingerprint (one Requirement moves from unknown to populated on three fields). Part of PUB-2 (EV02). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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), for the chosen consumer question: what a mental health chatbot supplier must disclose to a Utah user, and what the draft JIA adds.
A concrete obligation took its lifecycle from the shared obligation definition before its creating term.
disclose-genai-on-first-sessiondeclareslifecycle_status: operative, which normalizes to unknown. So the draft JIA's own duty projected lifecycle, operative and enforcement status as unknown, even though its only creating term is a draft. In a consumer answer, that duty could read as binding.When the creating term is draft or proposed, the concrete obligation now takes the term's lifecycle and derives operative and enforcement status from it, ignoring the definition's generic values. Issued creators are unchanged. Exactly one record changes: the JIA duty now projects
draft/future/unsignaled, matching its term.Deliberately not changed
providerrole means an AI developer or market placer, so borrowing it would strengthen the meaning. A PubLedge role vocabulary is left for a later decision.source_versionstays unknown for this journey's records, which draw theirsourcefrom the draft's authority page. The statutory version evidence sits on PubLedge's statute instruments and receipts, outside this journey.Merge together
Companion OF PR: snapsynapse/obligation-first#13. It adds the draft's own duty to the Utah journey's expected answer, and its expectation needs this projection. Merge both together, or the federation check fails.
Test plan
node --test tests/*.test.js(60 pass) andnpm run evalspassOBLIGATION_FIRST_DIR=../obligation-first npm run verify:cipassesverify:federationpasses with the companion OF branch🤖 Generated with Claude Code