About
Making Autonomous Software Execution Verifiable
Archipelo develops Salmon, Execution Verification Infrastructure for establishing cryptographically verifiable execution history and state lineage.
Autonomous software requires verifiable execution history.
S1 Execution changes state.The history should be verifiable.
Why Salmon exists
Software Is Becoming Increasingly Autonomous.
The infrastructure beneath it must evolve with it.
Software has historically evolved around human-directed execution. Today, autonomous agents, tools, runtimes, and controllers increasingly perform consequential actions themselves.
Archipelo develops infrastructure that makes autonomous multi-actor software execution independently verifiable — enabling more transparent, accountable, and reliable autonomous systems.
- Human-directed execution
- Autonomous multi-actor execution
- Verifiable execution infrastructure
Salmon and Archipelo
One Mission. Two Parts.
Salmon is the Execution Verification Infrastructure. Archipelo, Inc. is the company developing and stewarding Salmon.
Cryptographically verifiable execution history for autonomous multi-actor systems.
Developing and stewarding Salmon for verifiable autonomous software systems.
The story behind our name
Why Salmon.
Our name is inspired by the fish — salmon swim upstream to their origin. Our protocol follows the same principle: moving upstream from resulting software state through its execution history and state lineage toward its origin.
The name also encodes core concepts underlying the protocol.
slmn
Our command-line interface carries the same identity.
Salmon, without the vowels.
S1 S2 S3
- State
- Software state.
- Actions
- State-producing execution activity.
- Lineage
- Relationships among states, transitions, and execution.
- Mapping
- Attribution across actors, actions, and state transitions.
- Origin
- Starting point of a state lineage.
- Normalization
- Structured execution evidence for verification.
Our principles
Architectural Principles for Verifiable Autonomous Execution Systems.
Safe and reliable agents need verifiable evidence of their execution history. These principles guide our approach.
Building infrastructure that makes autonomous systems safer and more reliable.
- 01
Capture before Reconstruction
Where execution history can be captured during supported execution, downstream systems should not be forced to establish it solely through retrospective inference.
- 02
Preserve Boundaries
Evidence should remain bounded by what the system can establish. Unknowns and gaps should remain explicit.
- 03
Separate Authority from Execution
What an actor was permitted or instructed to do is distinct from what it actually executed.
- 04
Build for Machine Consumption
Machine-speed software systems require execution evidence that other software systems can consume and verify.
- 05
Strengthen the Stack
Identity, policy, observability, security, engineering, and governance systems solve important adjacent problems. Execution Verification provides evidence that strengthens those systems.
Our team
The Team Working at the Systems Boundary.
Protocol architecture, distributed systems, infrastructure, AI systems, and cybersecurity.
Matthew Wise CEO & Protocol Architect
Jason Dusek CTO & Engineering Architect
Paul Calatayud, PhD CISO & Strategy
Jakub Jarzyński Senior Data Engineer
Christophe de Carvalho Senior Backend Engineer
Vasile Staver Senior Product Designer
Stan Kapusta Tech Program Manager
Alex Saifullin Product Manager
Kacper Skawinski Product Lead
Archipelo
Investors & Advisors
Andy Bechtolsheim Investor 
Bill Tai Investor 
Jure Leskovec Investor & Advisor Professor of Computer Science,
Stanford University
Dawn Song Advisor Professor of Computer Science,
UC Berkeley
Anima Anandkumar Investor Bren Professor of Computing at California Institute of Technology
What we're building
Execution Verification Is a Distinct Infrastructure Layer
As autonomous software actors become increasingly responsible for consequential execution — durable and independently verifiable execution history becomes foundational infrastructure for systems that investigate, evaluate, govern, and depend upon that execution.
Consequential execution
Execution Verification Infrastructure Capture · Execution Record · State Lineage · Verification
Execution evidence
- AI / Agents
- Security
- Engineering
- Audit
What we don't know matters too
Explicit boundaries. Stronger systems.
If continuity has not been established by the recorded evidence, the system should not manufacture it.
S3 Unaccounted-for state transitionThe company
Archipelo, Inc. develops Salmon.
Archipelo is a deep tech company building foundational infrastructure for verifiable autonomous systems.
San Francisco, CA
Global Remote
Focused on Infrastructure