Component · spec & evidence

Proof Derived Governed Mutation Authorization

Checks a synthetic change-authorization record for its proof-and-approval chain, bound to a real commit.

Contract

Does Replays a make-believe example of "should this change be allowed to run?" and shows, step by step, why each proposed action was permitted. All three actions (a look-only inspection, a small config write, and an undo of that write) had to carry proof evidence and two visible policy approvals before anything was admitted; on top of that, the two actions that actually change something (the config write and the undo) also had to show a logged record of the change and a matching undo result record. Just holding a password or account secret is never treated as permission, and nothing here touches a real account or makes any real change.

Scope limit It validates only a declared, synthetic governed-mutation contract and excludes live cloud/account action, standing account secrets, source or irreversible mutation, policy-after-execution, hidden votes, external model access, benchmark-score claims, or launch.

Run

PYTHONPATH=src python3 -m microcosm_core.organs.proof_derived_governed_mutation_authorization run --input fixtures/first_wave/proof_derived_governed_mutation_authorization/input --out /tmp/plectis-public-runs/proof_derived_governed_mutation_authorization

PYTHONPATH=src python3 -m microcosm_core.organs.proof_derived_governed_mutation_authorization run --input fixtures/first_wave/proof_derived_governed_mutation_authorization/input --out receipts/first_wave/proof_derived_governed_mutation_authorization --acceptance-out receipts/acceptance/first_wave/proof_derived_governed_mutation_authorization_fixture_acceptance.json

Evidence

ClassContract validatorevidence 5/5Import validation

Links to Release Public Wording Gate, Proof / Control / Runtime Import Bundle, Policy Engines Bundle

formal-methodstheorem-provinglean

Source

Source Design note · Source

Map Show on the map

Index Open compact index card

Paper module