From Proposal to Proof

Proposal → Governance → Execution → Proof

What happens after a decision?

PFC does not stop at blocking or allowing an action. When an action is allowed, the system can also prove exactly how that decision was derived.

See how PFC connects explored possibilities to the final execution decision with verifiable lineage.

If you want measured hosted evidence for this boundary, see what has been proven live under governed load, mixed allow and deny traffic, and replay freshness probes.

The execution boundary governs the action. Creative lineage proves how the action was chosen.

View Creative Lineage Demo See the full control model

Execution Boundary Demo

Execution Boundary Demo

AI proposes, systems can commit, and PFC governs the action before execution.

Run the governed path to see the deny receipt.

Without PFC

The action executes after the proposal.

state changed

Without PFC

  • Action executes
  • No authority validation
  • System state changes
1
Request sentThe refund is proposed to the execution path.
18:42:16Z
2
No authority checkThe system proceeds without validating delegated authority.
18:42:16Z
3
Commit occursThe refund updates system state before review.
18:42:16Z

Outcome

  • Action executes
  • No authority validation
  • System state changes

With PFC

The action is evaluated before execution.

blocked before commit

With PFC

  • Action evaluated before execution
  • Authority verified
  • Blocked before commit
1
Request sentThe same refund is proposed through the governed path.
18:42:16Z
2
Authority verifiedPFC checks whether the actor can approve the refund.
18:42:16Z
3
Commit blockedThe deny decision stops the action before state changes.
18:42:16Z

Outcome

  • Action evaluated before execution
  • Authority verified
  • Blocked before commit

Demo Scenario

Refund request proposed to the wrong destination account. This shows how AI execution risk emerges when outputs become actions.

requestrefund_payment / req_demo_7F3A91
amount$5,000 USD
decisiondeny
commit statusblocked

Receipt Preview

Governed deny receipt

Visible before any protected commit.

Execution evidence 
{
  "receipt_status": "pending_demo_run",
  "decision_id": "dec_refund_20260323_19af",
  "request_id": "req_demo_7F3A91",
  "commit_status": "awaiting_demo_run"
}

Next Step

Verify this decision.

Review the governed path or see how the control point fits into the rest of the system.

Verify this decision See creative lineage demo Ready to try this in your own workflow? Get Started View how it works