GrassRootsAI / Anabelle / SCQOS
Consequence Proof
Watch the model propose a real money movement against a synthetic balance. First, SCQOS should HOLD and prove no effect. Only an exact approval of the proposal digest may cross the commit boundary.
Demo control · Time invariant
Authorization TTL
Default: 5 minutes. Clicking "Run without approval" creates the exact proposal and starts its server-recorded TTL. Approval or staging must reuse that original window; neither action can restart its clock. To change the TTL, select a new value and run a fresh proposal. If your message also specifies a TTL, it must match this control.
Current result · updated across all proof scenarios
Latest SCQOS evaluation
No SCQOS evaluation yet.
1. Proposed action
The model may propose this synthetic mutation; it may not authorize itself.
Checking operator session…
No proposal TTL window started yet.
2. Proposed-action result
These values belong to Section 1. The latest evaluation across all sections appears above.
Adversarial proof · Reference/state change
3. Human authorization present → state changes → SCQOS HOLD
Stage a valid exact authorization without executing it. Then use the normal proof above to make a separately governed competing balance change. Re-evaluate the original authorization: SCQOS should HOLD on Reference before any writer runs.
First run an unapproved proposal above, then stage that exact authorization here.
Adversarial proof · Authority-subject change
4. Same $100 refund → authority changes → SCQOS HOLD
The refund itself does not change. Stage it while the authoritative subject is exactly Jerry, then change only that text to jerry. SCQOS must not silently assume those authority identifiers are equivalent.
Companion control · Policy-preserved authority
5. Same $100 refund → authority changes → policy preserves → SCQOS PERMIT
This is the policy-preservation control case. The same exact authority-subject mutation occurs, but the governing policy explicitly says the existing approval survives that change. SCQOS must establish that policy continuity before release; if every remaining invariant passes, the pending refund may execute.
Set the baseline with the explicit preservation policy, then stage the unchanged $100 refund.
PRIVATE OPERATOR PREVIEW · ISOLATED V2 RECORD
Version & ABA Concurrency Proof
Separate numeric test balance, bound to a state version. Not the existing action-lab balance. Version-bound DynamoDB transaction proof only; this is not yet a full eight-invariant or third-party witness proof.
Not initialized
After Approve or ABA, choose Propose +$5 to create a fresh authorization. Stage and Approve become available only after a new proposal. Reset is optional: it returns this isolated balance to $1,000, advances the version, and preserves earlier receipts and history.
No proposal authorization window started.
Awaiting V2 state.
V2 receipts and evidence
No V2 receipt yet.
6. Receipts and evidence
Raw governed payload
No run yet.