Complete ontology authority activation - #374
Merged
Merged
Conversation
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
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
Why
Tier-3 activation of JVNAUTOSCI-2632 exposed two release blockers after the core authority deployment: the replay final answer overclaimed one stopped stale-ID mutation, and a real-shaped merge preview either rejected derived metadata or would have introduced target self-loops. These changes make the result evidence-honest and the governed merge plan executable without weakening fail-closed handling of unfamiliar canonical metadata.
Impact and safety
367e997ab34186fc29bbbde16f90fb45dce68e30e86d110a9b690b544af6a267: seven affected concepts, five incoming rewrites, four text relations, zero residual source references, and zero structural target self-edges.Root cause
The ordinary-turn finaliser preserved a model-written per-item table for mixed no-change failures without reconciling cited claims against effect finality. The identity merge planner treated derived index/cache fields as canonical conflicts, read alias TextValues through an ID-shape-sensitive path, and did not distinguish a pre-existing target self-edge from one created by source-to-target collapse.
Checks
138 passedacross authority, merge, workflow, gateway, scope, stdio, HTTP provenance, and route suites.4 passedfocused adaptive finaliser regressions, including the liveev_*citation shape and case-sensitive exact identity matching.py_compile, andgit diff --checkpass.Jira: JVNAUTOSCI-2632