Proof

See what happened and why.

Proof connects the original task, its approval, and the result. Your team can review the record without exposing credentials, raw logs, or sensitive data.

Map your workflow Book a mapping session
Synthetic exampleNo connected tools

Support request → draft → human review

Recorded example

The draft stayed in review.

The owner requested current evidence instead of sending an unverified answer.

Task: support reply · Decision: request evidence

Result: waiting for a current source; no external action.

Proof operating boundary

One surface. Three questions.

Read what this view shows, how it works, and where to go next.

01 / 03 See the boundary

Proof owns the proof graph.

Proof preserves the evidence, decision, outcome, receipt, rollback note, and next owner.

Signal

The source event and reason for review are saved as the beginning of the record.

Decision

The human, agent, or policy judgment explains why the workflow moved, waited, or stopped.

Proof

The proof graph preserves the evidence, outcome, receipt, and rollback note.

Map

The map shows where the Proof belongs and what system relationship it affects.

Evidence
  • Signal: The source event and reason for review are saved as the beginning of the record.
  • Decision: The human, agent, or policy judgment explains why the workflow moved, waited, or stopped.
  • Proof: The proof graph preserves the evidence, outcome, receipt, and rollback note.
  • Map: The map shows where the Proof belongs and what system relationship it affects.
Receipts
Surface: proof-graph4 connected states
02 / 03 Inspect ownership

See what this view does and which records it keeps.

In production, Proof is required because it owns evidence, outcome, receipt, rollback note, audit trail.

Owns
The durable record

Proof owns the evidence, outcome, receipt, rollback note, audit trail, and next owner.

Consumes
Signal and Decision context

Proof consumes the incoming Signal and the Decision outcome so the record explains both source and judgment.

Protects
Public and private boundaries

Proof can show the business-readable record while keeping credentials, raw logs, and sensitive data out of the public surface.

Evidence
  • The durable record
  • Signal and Decision context
  • Public and private boundaries
Receipts
evidenceoutcomereceiptrollback noteaudit trail
03 / 03 Continue with context

Map shows how this view connects to the rest of the workflow.

Keep the workflow plan, incoming tasks, approvals, and results connected.

Inbox
Signal

Capture the source context before proof is written.

Queue
Decision

Name the judgment that produced the record.

Map
Map

Attach each proof record to the workflow map.

Evidence
  • Signal
  • Decision
  • Map
Receipts
Signal inboxDecision queueMapProduct overview
Signal inboxDecision queueMapProduct overview
Proof implementation

Attach this surface to a real workflow.

Start with one live task. Agree on who approves it and what record your team needs afterward.

Map your workflow Book a mapping session
Owner
Proof operator
Authority
Proof production contract
Proof
Connected workflow receipt
State
review
  1. 01 / Record Define the proof record

    Name the evidence, outcome, owner, receipt, and rollback note the workflow must keep.

  2. 02 / Boundary Separate public from private

    Show the audit trail without exposing credentials, raw logs, or sensitive client data.

  3. 03 / Map Attach the receipt to the map

    Make the proof record visible in the workflow where the decision happened.