Harden Fable Mode with evidence-bound System 3 control loops - #8
Closed
REX-codebase wants to merge 6 commits into
Closed
Harden Fable Mode with evidence-bound System 3 control loops#8REX-codebase wants to merge 6 commits into
REX-codebase wants to merge 6 commits into
Conversation
REX-codebase
force-pushed
the
zapia/fable-mode-system3-verifier-final-20260902
branch
from
September 2, 2026 02:42
8252606 to
0659a3f
Compare
Owner
Author
|
Superseded by v1.3.0 frontier release on main |
REX-codebase
deleted the
zapia/fable-mode-system3-verifier-final-20260902
branch
September 2, 2026 14:18
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.
Summary
This PR consolidates the accumulated Fable Mode work into one reviewable change set. It adds a hardened, evidence-bound System-3-style control loop around compatible MCP hosts; it does not claim to alter model intelligence or provide a complete OS sandbox.
Control and verification
fable_control_planelifecycle: observe -> record prediction -> propose action -> record outcome -> request verification -> finalize.fable_sessioncompatibility through an explicit immutable compatibility mode rather than silently weakening strict paths.Runtime, MCP, and broker hardening
Validation
test_*redteam*.py): 47 passedcompileall: passed for source, tests, and docspip check: passedExplicit limitations
Please review the strict finalization, provenance/attestation binding, checkpoint restore path, and broker boundary assumptions in particular.