Creative Lineage Demo
PFC does not just govern execution. It proves how an explored possibility became an allowed action, while keeping exploration non-binding and execution authoritative only at the boundary.
Use this walkthrough to show how exploration, execution receipts, and cryptographic lineage stay distinct.
PFC can explore multiple possible actions without granting any of them authority. It evaluates each candidate under live policy, authority, and state conditions, and only an explicitly bound admissible action receives an execution receipt. The system also proves exactly which signed exploration artifact that execution came from.
The chain starts with a goal, moves through candidate evaluation, reaches explicit binding, then ends with an authoritative execution receipt plus independently verifiable exploration lineage.
Session `sess_req_creative_demo_001` begins with the goal to resolve account fraud case safely.
Freeze account, limit transactions, notify user only, and monitor silently are labeled and evaluated.
Only candidate `c1` is both admissible and explicitly bound. The others remain blocked or review-only.
The execution receipt is the only authoritative artifact. Exploration remains non-binding.
The signed receipt carries creative provenance and points to the exact signed exploration artifact hash.
The exploration artifact can be verified independently without becoming executable authority.
Business-readable scenario: fraud response for a high-risk account.
{
"request_id": "req_creative_demo_001",
"operation_mode": "explore_then_evaluate",
"goal": "Resolve account fraud case safely",
"context": {
"account_id": "123",
"risk_flags": ["velocity_spike", "device_change"]
},
"generation_config": {"max_candidates": 4},
"evaluation_config": {"bind_candidate_id": "c1"}
}
Operation mode `explore_then_evaluate` returns metrics, a selected candidate, and a signed exploration artifact.
{
"session_id": "sess_req_creative_demo_001",
"operation_mode": "explore_then_evaluate",
"goal": "Resolve account fraud case safely",
"metrics": {
"total_candidates": 4,
"execution_candidates": 2,
"admissible_candidates": 1,
"blocked_candidates": 3,
"bound_candidates": 1
},
"selected_candidate": "c1",
"exploration_artifact": {
"exploration_id": "exp_sess_req_creative_demo_001",
"artifact_type": "exploration",
"binding_status": "non_binding",
"artifact_hash": "exp_hash_4f17d7",
"signature": "sig_exploration_9u1"
}
}
The candidate cards make the distinction between non-binding exploration and authoritative execution obvious.
Temporarily freeze account
governance_result: allow
admissible: true
requires_human_review: false
Explicitly bound and issued an execution receipt.
Limit transactions
governance_result: block
admissible: false
requires_human_review: true
Notify user only
governance_result: block
admissible: false
requires_human_review: true
Monitor silently
governance_result: block
admissible: false
requires_human_review: true
Only an explicitly bound admissible action receives an execution receipt.
{
"decision_id": "dec_4b91",
"receipt_hash": "sha256:ab71e6c2",
"signature": "ed25519:sig_receipt_9k2",
"creative_provenance": {
"lineage_type": "explored_then_bound",
"exploration_id": "exp_sess_req_creative_demo_001",
"session_id": "sess_req_creative_demo_001",
"candidate_id": "c1",
"origin_operation_mode": "explore_then_evaluate",
"binding_status_at_origin": "non_binding",
"exploration_artifact_hash": "exp_hash_4f17d7"
}
}
This is a different artifact class: non-binding exploration, not execution authority.
{
"exploration_id": "exp_sess_req_creative_demo_001",
"artifact_type": "exploration",
"binding_status": "non_binding",
"artifact_hash": "exp_hash_4f17d7",
"signature": "sig_exploration_9u1"
}
Exploration artifact verification stays separate from receipt verification.
{
"verified": true,
"artifact_type": "exploration",
"binding_status": "non_binding",
"verification_status": "valid"
}
PFC does not just govern execution. It proves how an explored possibility became an allowed action. That makes the system useful for audits, demos, and enterprise review workflows.
This is not normal AI output filtering. PFC separates exploration from execution, keeps exploration non-binding, and places authority only at the execution boundary.
Next Step
Use this page alongside the API docs and SDK helpers when you need a concrete product story for governed creativity, lineage, and proof.