Trust / Evidence model

What verification actually proves

A structurally valid proof object is not the same as factual correctness. This page states exactly what each verification level demonstrates and where the current boundary sits.

In development

Local integrity checks are implemented for the reference workflow. External, third-party non-repudiation is not available.

Event integrity and replay

Mission events are recorded in an append-only ledger local to the executing environment. Replay reconstructs mission state from that ledger for audit and debugging. This is a local integrity property: it shows the record was not altered after the fact within that environment, not that a third party can independently verify it without trusting the environment.

Verifier independence classes

A claim of "verified" always names which independence class produced the verdict.

ClassWhat it means
Same-contextThe verifier runs inside the same session as the executing agent. Weakest independence; used only for fast structural checks.
Separate-processThe verifier runs as a distinct process without access to the agent's reasoning state.
Separate-modelThe verifier is a different model or deterministic tool than the one that produced the artifact.
HumanA person reviews the evidence bundle directly; the strongest available independence class today.

Local integrity versus external non-repudiation

Local integrity means the record is internally consistent and tamper-evident within the system that produced it. External non-repudiation means a third party, without trusting Omnacta's infrastructure, can independently verify the record. Omnacta currently provides the former; the latter is a target capability, not a current one.

Remediation state

  • Gateway-finish arbitrary-JSON acceptance: remediation in progress, owned by security and architecture.
  • Process authorization argument-vector binding: remediation in progress, owned by security and architecture.
  • Both findings are reviewed on a monthly cycle; the next scheduled review supersedes or reaffirms this disclosure.
  • No synthetic or illustrative "verified" trace is ever presented as captured proof.

See recovery behavior

Reliability & recovery covers what happens when execution itself fails or is interrupted.