When autonomous software changes consequential state, existing records can show fragments of what happened without preserving the execution that produced the result. Salmon provides the execution record needed to inspect how supported software state was produced.
Which recorded execution is associated with the state change under investigation?
A production failure points back to code or configuration. Git identifies the artifact and commit; production telemetry shows effects. Salmon preserves the supported execution that produced the changed state: the recorded actor, actions, and intermediate transitions.
What did the agent execute before this change reached production?
An agent can read files, invoke tools, modify multiple artifacts, run commands, and delegate work before producing a commit. The commit preserves the resulting artifact; Salmon preserves the supported execution that produced it.
Which execution changed this authentication, secrets, infrastructure, or security-critical state?
When sensitive state changes, teams need more than the resulting diff. Salmon links supported recorded execution to the state transition so investigators can inspect the execution associated with the change.
What happened after execution was delegated from one actor to another?
A human delegates to an agent; the agent invokes tools or other agents; those actions produce durable software state. Existing records may identify individual events without preserving one coherent execution history across the supported chain. Salmon is designed to preserve that record as execution occurs.
What execution occurred when an automated security system changed production state?
Security agents increasingly isolate systems, modify configurations, revoke access, trigger workflows, and initiate remediation. When automated defense becomes a consequential software actor, Salmon can preserve supported execution and resulting state transitions so downstream security systems can investigate and verify what actually executed.
What execution is associated with this infrastructure state change?
Automation can modify cloud resources, deployment environments, configuration, access, and other durable infrastructure state across multiple tools and systems. Salmon can preserve supported execution events and state lineage so infrastructure changes can be evaluated from a verifiable execution record rather than reconstructed solely from fragmented downstream observations.
One execution record can support downstream security, AI evaluation, engineering, governance, compliance, and verification workflows.
Execution now comes from AI agents, humans, and automation. Salmon establishes a verifiable execution record for supported execution, captured as it occurs rather than reconstructed solely afterwards.