Establish REGRESSORIUM current recourse object#5
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.
Current recourse object is explicit, machine-readable, and aligned to the active REGRESSORIUM recourse boundary. Approved.
verifrax-systems
deleted the
midiakiasat/regressorium-current-recourse-object
branch
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.
Summary
Publish the current machine-readable recourse object for REGRESSORIUM.
Changes
claims/current/recourse-object-0001.jsonclaims/history/README.mdclaims/current/index.jsonso current recourse resolves to a concrete object of recordREADME.mdso the public surface names the current recourse-object entry surfaceBURDEN_ASSIGNMENT.md,REMEDY_MATRIX.md,ESCALATION_FLOW.md, andCLOSURE_STATES.mdso the current recourse object of record is explicittests/test_recourse_object.pyResult
REGRESSORIUM now exposes one current machine-readable recourse object for the active recognized boundary instead of leaving current recourse truth compressed only across doctrine text and an index without an object of record.