← Policy gallery

reasoning_required_for_high_stakes

formal-reasoning safety scoped_temporal safetyreasoninghigh-stakesformal-verification

Edits to high-stakes modules (payments, risk, matching) must be preceded by formal reasoning in the artifact dependency chain.

Formula

G(EditFile ∧ high_stakes_path → P_chain(VerificationResult(proved ∨ sat) ∨ Decomposition))

Hover any operator or symbol for what it means.

Requires a reasoner

This policy is satisfied by verification from codelogician — an automated-reasoning tool in the reasoner registry.

Why it matters

Critical code changes must be formally verified before implementation. The reasoning must be in the lineage of the edit, not just somewhere in the trace.

Examples

passes Formalize → Verify(proved) → EditFile(payments/charge.py)

fails EditFile(payments/charge.py) with no prior verification in the dependency chain

Use it

ponens policies add reasoning_required_for_high_stakes --into ./trace.json
ponens trace check ./trace.json