How it works

From Unknown Execution to a Verifiable Execution Record

Salmon captures supported execution as signed execution events, records associated state transitions, preserves their relationships, and produces machine-consumable execution evidence.

Autonomous execution.
Verifiable history.
Safer and more reliable agents.

Supported execution environments

Execution Capture Occurs Continuously Inside Supported Environments

Salmon captures execution as it occurs upstream within supported environments, not downstream after the event has already taken place.

Supported execution environment

  • Actor
  • Tool / API
  • State before / after

Execution is captured

Execution Is Captured Continuously

Salmon captures execution context and recorded state transitions.

Salmon
actor
agent-a
action
write
artifact
/src/auth/session.ts

State before

S0

State after

S1

An execution event

Captured Execution Becomes a Structured Execution Event

Execution is represented as a cryptographically signed event with explicit context.

Execution event04F7A2
actor
agent-a
action
write
artifact
/src/auth/session.ts
state_before
91d7a4e2...
state_after
a4e8c1f9...
predecessor
04f79d11...
timestamp
2026-09-13T14:32:08Z
signature
ed25519:3a...
91d7a4e2... a4e8c1f9... S0 S1 EXEC
04F7A2
Signed

Events are signed and linked

Events Are Cryptographically Signed and Linked

Each event includes a reference to its predecessor, creating a tamper-evident event chain.

Event 04F7DD

actor
agent-a
action
read
signature
ed25519:9f...
state_after
91d7a4e2...

Event 04F7A2

actor
agent-a
action
write
predecessor
04F7DD
signature
ed25519:3a...
state_after
a4e8c1f9...

predecessor

The execution record

Individual Events Compose into an Execution Record

Events are linked in sequence, recording state transitions across multiple actors.

State lineage

Execution Relationships Produce State Lineage

State lineage preserves recorded relationships across supported execution.

Inspect the record

The Record Can Be Queried & Inspected

The execution record is a computational data structure that can be queried and inspected.

$ salmon lineage state:a4e8c1

STATE
a4e8c1f9...
EVENT
04F7A2
ACTOR
agent-a
ACTION
write
PREDECESSOR
state
91d7a4e2...
event
04f79d11...
SUCCESSOR
state
b1c92e3...
event
04f8110a...
S0 91d7a4e2... S1 a4e8c1f9... S2 b1c92e3... 04F7A2

Verify the record

The Recorded Execution Can Be Verified

Each event and its relationships can be cryptographically verified.

$ salmon verify 04F7A2

signature
VERIFIED
predecessor
RECORDED
state_before
RECORDED
state_after
RECORDED
record continuity
VERIFIED

Gaps are accounted for

The Record Shows Gaps and Unaccounted-For State Transitions

Execution outside the supported capture boundary is not silently incorporated into the record.

Reconstruction

The Execution Record Supports Reconstruction

Recorded execution events can be used to reconstruct state transitions within bounds.

Machine-consumable evidence

Execution Verification Produces Evidence that Other Systems Reason about

Salmon produces machine-consumable execution evidence for downstream systems to reason about.

Attribution boundaries

Execution Is Captured in Attribution Boundaries

Salmon organizes supported execution into labeled, nested attribution boundaries and makes explicit where each begins and ends.

Recorded / Available

  • Actor and signing evidence
  • Execution events
  • Recorded state transitions
  • Predecessor relationships
  • State fingerprints
  • Verification results

Explicitly Bounded

  • Execution outside capture scope
  • Unsupported external processes
  • Unobserved infrastructure actions
  • Relationships not established by recorded evidence

Unknowns remain unknown rather than being silently converted into execution history.

The complete mechanism

From Unknown Execution to Verifiable Evidence

Salmon establishes a structured, verifiable record of supported execution that downstream systems can evaluate, investigate, and reason from.

  1. Execution environment
  2. Execution capture
  3. Signed execution event
  4. Recorded state transition
  5. Salmon execution record
  6. State lineage
  7. Verification
  8. Machine-consumable evidence

Verifiable History of AI Agent Execution across Software Systems.