OBL-003: provenance sealing obligations delegated by UDLM ADR-059 - #117
Merged
Merged
Conversation
…ort fidelity) delegated by UDLM ADR-059 Registered pending ADR-059 ratification (croadfeldt/udlm#342) so the obligations land with the decision. Follows the register's OBL shape: the invariant DCM must satisfy (full-lifecycle sealing incl. Discovered, state-claims-only working record, sole-hasher, no silent fidelity loss) and the six policy decisions DCM must make (emission completeness/delivery, Discovered-seal retention, provider-scope consumption permission, port-fidelity classes, ledger operation, L1-failure as tamper not drift). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AZUFo3Fe5ejQJwT71ELQWB
…tinuity citation Maintainer ruling (2026-08-03): discovery-run chains deliberately do not link cycle to cycle — runs are independent evidence, and chains prove integrity of what exists, never completeness of what should. The suppressed-run case is therefore a completeness obligation: declared discovery cadence + a finding on a missing seal (the ADR-048 expected_observation shape), which also survives seal retention where a chain would not. Profiles that want structural gap detection anyway (fsi/sovereign) MAY require each run seal to cite the previous run's head — the pathway_ref citation mechanism pointed backward — without making cross-run chaining the default or entangling RHY-008. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AZUFo3Fe5ejQJwT71ELQWB
…y posture (ADR-059 Decision 8) - Continuity citations generalized per pathway: the discovery-run option extends to provider event streams (the third pathway anchor), with a stronger SHOULD for fsi/sovereign there — a provider is an interested external party, not the platform's own probe. - The drift policy decision registered: per-field relevance, severity onto the canonical enum, flap debounce, and the deliberately open ACCEPT fork (adopt-into-intent vs accepted-deviation record — both priced in the ADR; this register is where the ruling lands). - Finding lifecycle operation: open-once keying, confirm-not-duplicate, closure by citing resolution seal; current status derived on read, never from a finding. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AZUFo3Fe5ejQJwT71ELQWB
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.
What this settles: the DCM-side register entry for ADR-059's delegated policy work — recorded with the decision (croadfeldt/udlm#342), not after it, per the established obligations pattern.
One new row + section, register shape unchanged: the invariant DCM must satisfy (full-lifecycle OL sealing including Discovered, state-claims-only working record, DCM as sole hasher, no silent port-fidelity loss) and the six decisions DCM must make — emission completeness/delivery, Discovered-seal retention, provider-scope consumption permission, port-fidelity classes, ledger operation (anchoring/verification/tenancy), and L1-verification failure as a tamper finding class distinct from drift.
Marked open + pending ratification; discharging any of it waits on #342.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AZUFo3Fe5ejQJwT71ELQWB