Proof

The proof graph that records what happened and why.

Proof turns Signals and Decisions into a durable record operators can inspect without exposing private credentials, raw logs, or sensitive data.

Start Workflow Map Talk Through a Workflow
Proof graph
Evidence that survives the action

Proof keeps the source, decision, owner, outcome, receipt, rollback note, and audit trail attached to the workflow.

  • Evidence
  • Outcome
  • Receipt
  • Rollback note
Atlas connection
Every receipt points back to the map

Atlas shows where the Proof came from, which Signal and Decision produced it, and what owner should inspect it next.

  • Composition: signal-decision-proof
  • Hub: Atlas
Proof surface

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.

Atlas

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

Production contract

The product boundary stays small enough for operators to inspect.

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.

Connected products

Atlas connects this product to the rest of the governance loop.

Each page describes one product surface, but production workflows need the four surfaces attached to the same map: Atlas, Signal, Decision, and Proof.

Inbox
Signal

Capture the source context before proof is written.

Queue
Decision

Name the judgment that produced the record.

Map
Atlas

Attach each proof record to the workflow map.

Proof implementation

Attach this surface to a real workflow.

Start with one live workflow, connect the source signal, name the decision owner, and decide which proof record must survive the action.

Start Workflow Map Talk Through a Workflow
Record Define the proof record

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

Boundary Separate public from private

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

Atlas Attach the receipt to the map

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