OBL-003: drift-resolution ruling — policy dictates and performs - #120
Merged
Merged
Conversation
The deliberately-open accept fork is ruled (UDLM ADR-060, 2026-08-05): a drift finding routes to policy first; the substrate ships no built-in action or decision. The enabled vocabulary is nine actions (adopt, accept-with-note, three replay depths, re-observe/false-positive, quarantine, defer, decommission) plus external handoff landing as a DecisionRecord. Every action is an ordinary governed request, so audit capture needs no new machinery. DCM ships example resolution policies and profile bundles that MAY bind defaults; nothing binds otherwise. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Lands the drift-accept ruling (UDLM ADR-060, ruled 2026-08-05) in its mechanism home.
A drift finding routes to policy first; policies dictate and perform the action — the substrate ships no built-in action or decision. The enabled vocabulary: adopt, accept-with-intent-note, replay at three depths (intent/request/realized), re-observe (false-positive closure), quarantine/suspend (containment, not resolution), defer (recorded, review-timed), decommission — plus external handoff (human/AI/external policy) landing as a DecisionRecord citing the finding. Every action is an ordinary governed request, so the audit chain (routing → evaluations → handoff → decision → action) is captured by existing surfaces.
DCM's follow-through named in the obligation: example resolution policies (one per vocabulary row) and profile bundles that MAY bind defaults — nothing binds unless a profile or org policy says so.
Companion: the UDLM side is ADR-060's resolution-routing section on croadfeldt/udlm#348.
🤖 Generated with Claude Code