Protocol
A Cryptographic Protocol for Verifiable Execution History
Salmon establishes cryptographically verifiable execution history and state lineage across supported execution.
S0
S1 EXEC 04F7A2 actoraction
state_before
state_after
signature agent-a
write
91d7a4e22...
a4e8c1f9...
ed25519:3a...
Autonomous execution.
Verifiable history.
Safer and more reliable agents.
Start from the primitive
Software Execution Changes State
Consequential software execution can be represented as recorded execution events associated with state transitions.
S1 Agent A write()The Execution record
Execution Events Form a Verifiable Execution Record
Recorded execution events preserve relationships between supported execution and recorded state transitions.
S1 S2 
S3 EXEC 001 agent-awrite()
sig: 3a...EXEC 002 tool
deploy()
sig: 9f...EXEC 003 agent-b
configure()
sig: 7c...
Where it sits in the stack
Where Execution Verification Naturally Lives
Between consequential execution and the systems that consume execution evidence.
- AI / AgentsLLMs · Agents
- Tools / APIsCloud · Data · Services
- Containers / VMsKubernetes · Compute
- OS / InfrastructureCloud · Edge · On-prem
Consequential execution
Execution Verification Infrastructure Capture · Execution Record · State Lineage · Verification
Machine-consumable execution evidence
- AI / AgentsEvaluation · Supervision
- SecurityInvestigation · Response
- EngineeringDebugging · Reconstruction
- Audit / GovernanceAccountability · Compliance
What Salmon establishes
From Execution to Machine-Consumable Evidence
Salmon captures execution, records state transitions, and produces verifiable evidence with explicit boundaries.
- ExecutionConsequential execution occurs
- CaptureRecord execution context
- Signed execution eventsCryptographically signed events
- Recorded state transitionsState before → state after
- Salmon execution recordLinked, tamper-evident record
- State lineageRecorded relationships across events
- VerificationCryptographic verification
- Machine-consumable evidenceStructured for downstream systems
Anatomy of an execution event
Every Recorded Transition Carries Verifiable Evidence
Each execution event records the actor, the action, the state before and after, and a signature that makes it verifiable.
- actor
- agent-a
- action
- write
- state_before
- 91d7a4e2...
- state_after
- a4e8c1f9...
- signature
- ed25519:3a...
- verification
- verified
S1 EXEC04F7A2
VerifiedMulti-actor execution
Execution Is Increasingly Multi-Actor
Multiple actors, tools and runtimes interact to produce consequential state changes.
Human
Agent A- Agent B
Tool / API
Security agent
S1S2S3S4 
Agent A
Security agent
ToolBoundaries
Verification Requires Explicit Boundaries
If execution continuity has not been established, Salmon does not visually or structurally manufacture it.
S1 S2 
Unaccounted-for state transition S3
Supported capture External changeComplementary layers
A Distinct Systems Property
Salmon establishes execution evidence that complements other layers in the stack.
| Layer | Primary question |
|---|---|
| Alignment | What behavior should the model produce? |
| Identity / Authority | Who is the actor and what may it do? |
| Orchestration | What workflow should execute? |
| Monitoring / Observability | What does the system appear to be doing? |
| Runtime Control | Should execution continue, stop, or be modified? |
| Execution Verification (Salmon) | What actually executed, and what execution history and state lineage can be verified? |
Machine-consumable evidence
The Record Is Infrastructure for Other Systems
Salmon produces machine-consumable execution evidence for downstream systems.
Salmon execution record
Verification interface
- Security agentInvestigation · Response
- AI evaluatorReason
- Audit systemReview · Evidence
AI verifiers are actors too
AI Verifiers Are Actors Too
When AI monitoring or security agents modify, block, terminate, or remediate execution, they themselves become consequential software actors.
State change Security agent Security agentInfrastructure consequence
As AI agents become primary actors in deployed systems — execution history becomes foundational infrastructure.
- Identity
- Observability
- Control
Execution evidence