SPQR / forwardable decision brief
One page for the executive, risk, technology and audit conversation.
When software proposes a consequential action, what independently authorises it before the effect occurs? Knowing a policy is different from holding permission to execute.
Ask where authority is enforced, what happens on a new route, which active policy governed the action and what stops execution when required authority is absent.
Praxis supports policy assessment and reviewed governance material. Explicit approval, compilation, signing and independent verification establish the active runtime authority.
Aegis evaluates the proposed action. The enforcement point applies allow, deny or escalate before a governed effect. Direct credentials and alternative routes must be addressed in the integration.
The reported 6,300-row sandbox evaluation includes 79 risky comparator leakage rows. Across 2,100 governed rows: zero risky side-effect completions and zero governed mock-tool applications. Trusted provenance was retained for all 1,832 attempted governed decisions.
These are different endpoints, not a percentage reduction. Useful allowed-task completion and universal safety are not established by this result.
Bring one workflow and its existing controls to a short authority review. Decide whether there is a useful scoped test, not whether to approve an enterprise rollout.
Keep safeguards. Use an isolated environment. Agree useful completion, false denials, unauthorised effects, bypasses, latency and a stop rule before testing.
Adam Mazzocchetti · SPQR Technologies · adam@spqrtech.ai · Melbourne, Australia
The model proposes. Aegis decides. Proofs, not promises.