G‑14 Proof

Proof packets for actions, conclusions, and repair paths.

G‑14 proof packets are designed to show what was proposed, what evidence was checked, what decision was made, what changed, and what can be verified later.

Proof chain External review
01

Proposal captured

The system records the actor, target, requested operation, claim, policy context, scope, and expected consequence before reliance.

02

Evidence checked

Policy, source rights, confidence, freshness, custody, authority, and repair requirements are evaluated before action or conclusion.

03

Decision witnessed

Proceed, hold, repair, reject, block, or release decisions remain tied to the same proposal and evidence boundary.

04

Receipt exported

The packet preserves request, evidence, decision, outcome, timing, and verifier references for review outside the UI.

Receipt forms

Different domains, one proof-carrying record pattern.

The artifact name changes with the workflow. The standard does not: consequential AI should leave a record that ties proposal, evidence, decision, outcome, and review boundary together.

Action receipt

For tool calls, deployments, writes, robot commands, workflow approvals, and other effects that need admission before execution.

Verifier-oriented packet
Semantic receipt

For agent communication, reconstruction, scientific claims, repair cycles, and reject-with-witness outcomes.

Verifier-oriented packet
Proof receipt

For TargetLock physical-AI decisions: preserve, correct, hold, block, release, and outcome evidence.

Verifier-oriented packet
Reviewer questionsA packet is useful only if it answers the challenge.
Read the verify guide
01What was proposed before consequence?

Ties the record to the exact action or claim, before any effect existed.

02What evidence and authority were required?

Shows the bar the proposal had to clear, not just that it cleared.

03What changed after the decision?

Binds outcome to decision so drift between them is visible.

04What was held, repaired, rejected, blocked, or released?

Preserves the control states, including the ones that stopped action.

05Can the record be reviewed without trusting the dashboard?

The receipt has to verify outside the system that produced it.

Evaluation path

Bring one disputed action or conclusion.

A serious proof review starts with one workflow, one policy boundary, one receipt format, and one outside reviewer who needs the record to survive inspection.

Talk to an expert