Proof Orchestrator

Use this skill to choose the proof plan. Do not use it as proof by itself.

Core Rule

Map the claim to the weakest proof level that would still be honest. If the user asks for a stronger proof level, use the stronger one.

• implemented: files/config/docs changed and inspected.
• code_proven: current source inspection supports the claim.
• test_proven: fresh automated tests support the claim.
• runtime_proven: fresh evidence on the supported runtime path supports the claim.
• end_to_end_proven: fresh evidence across the real user-visible path supports the claim.

Never upgrade one level into another. Say not_proven_yet when the available evidence is weaker than the claim.

Routing