Repository navigation
feat: close correction loop with governed substantive uptake - #59
Merged
Merged
Conversation
SarashaElion
marked this pull request as ready for review
October 3, 2026 04:58
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Truth-Integrity v0.2 — Governed Uptake
Closes the gap between detecting required correction uptake and changing deployable relational state.
Closed-loop behavior
warranted correction
→ dependency assessment
→ current ACT authorization
→ affected claim validation
→ affected claims become CONTESTED
→ immutable CorrectionUptakeApplied receipt
→ downstream consumers see changed state on fresh read
Authority boundary
The assessment is not an authority token. The applying actor must possess current ACT authority for
truth-integrity:corrections.Anti-forgery boundary
A caller cannot take a valid correction assessment and append arbitrary unrelated claims to the affected set. The application validates explicit claim provenance from the correction target before mutation.
What mutation means
This PR does not invent replacement content. It prevents an affected prior claim from remaining silently ACTIVE after warranted correction. Corrected content must later be supplied through an attributable revision/withdrawal/supersession path.
Frozen witnesses
Current limit
Wave 2 can identify RELIES_ON dependencies beyond claims, but this executor mutates only canonical TRIA claim state. Plans/application objects remain host responsibilities until they have explicit TRIA state semantics.
Draft for CI and review. Sarasha remains merge authority.