Repository navigation
Harden decision applicability and scope uncertainty - #91
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
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.
Unknown environment metadata could be overridden by an overconfident cross-source judgment, producing apparent agreement or a possible discrepancy without established applicability. Keep these comparisons explicitly uncertain and recommend confirming environment and current revisions. Refresh older interpretation contracts on the next update, including unchanged headless registries, then resume zero-call no-ops.
Add a compact source-passage matrix for environment/component boundaries, proposals, closed work, rejected approaches, grounded versus ungrounded supersession, actual documentary conflicts, A→B→A, OpenWiki authority, unknown environments, shared upstream evidence, missing policy, and advisory review acceptance. Regressions check exact evidence revisions and complete conflict groups under compression, plus the real evidence/review CLI surfaces. Existing authority types and registry schemas are unchanged.
Validation:
cargo test --all-targets --locked: 434 passed; final focused matrix/runtime/upgrade tests also pass.cargo clippy --all-targets --locked -- -D warningsand formatting checks pass./opt/homebrew/bin/python3.14 -m unittest discover -s evaluation/tests -v: 271 tests run, all passed with one Linux-only test skipped on macOS.The existing offline suites need host execution for loopback sockets and process-group cleanup on this macOS machine. Linux and Windows validation runs in the existing CI matrix.
Closes #83.