Establish REGRESSORIUM recourse object minimum#4
Merged
verifrax-systems merged 1 commit intoApr 18, 2026
Merged
Conversation
verifrax-systems
approved these changes
Apr 18, 2026
Member
verifrax-systems
left a comment
verifrax-systems
left a comment
There was a problem hiding this comment.
REGRESSORIUM recourse doctrine, schema, and current-object minimum are explicit and machine-checked. Approved.
verifrax-systems
deleted the
midiakiasat/regressorium-recourse-object-minimum
branch
verifrax-systems
approved these changes
Apr 18, 2026
Member
verifrax-systems
left a comment
verifrax-systems
left a comment
There was a problem hiding this comment.
REGRESSORIUM recourse doctrine, schema, and current-object minimum are explicit and machine-checked. Approved.
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
2 participants
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.
Why
REGRESSORIUM was still a boundary-first repository.
Gate C requires terminal recourse to exist as an inspectable object system rather than recourse naming alone.
REGRESSORIUM must publish explicit recourse doctrine, object structure, current/history separation, and machine-checked minimum surfaces so burden, remedy, escalation, and closure can bind to recognized claims without collapsing into prose-only interpretation.
What changed
COUNTERPARTY.mdCLAIM_CLASSES.mdBURDEN_ASSIGNMENT.mdREMEDY_MATRIX.mdESCALATION_FLOW.mdCLOSURE_STATES.mdschemas/recourse-object.schema.jsonclaims/current/index.jsonclosures/README.mdmatrices/README.mdtests/test_recourse_surface.pyResult
REGRESSORIUM now exposes a bounded recourse-object minimum that can follow recognition objects without redefining law, accepted epoch, execution, or verification.