Skip to main content
syscall verify performs read-only forensic verification of a recorded session. It checks internal consistency and evidence interpretability. It does not repair, migrate, rewrite, checkpoint, normalize, or complete missing evidence.

Run verification

The command opens the database read-only. When a safe read-only open is impossible, it fails with a structured error rather than mutating the database.

What verification checks

Checks are bounded and use paged reads rather than loading an unbounded event table. Unsupported or future schema versions produce an unable_to_verify report with DB_SCHEMA_UNSUPPORTED when the version can be read safely. Verification does not query unknown structures or run migrations.

Assessment meanings

valid does not mean collection was complete, the kernel was trustworthy, or the database is authentic. It means the checks that could run found no contradictions.

Exit codes

Automation should use these codes, not scrape text.

Finding shape

Each finding has:
  • Stable code.
  • Severity: info, warning, error, or critical.
  • Title and detail.
  • Evidence context.
  • Recommendation.
Finding codes are intended to be stable for automation. Human-readable details may be refined.

Activity finding codes

Additional lifecycle, accounting, schema, and scan findings are defined by the verification engine. Treat error and critical findings as contradictions, not as stylistic warnings.

Bounded reporting

Events are scanned in deterministic batches. Findings are bounded. If a limit is exceeded, the report marks truncation explicitly with findings such as FINDINGS_TRUNCATED. A truncated report is limited, not silently complete.

Verify an export

Export verification is a separate operation:
It checks the package format, manifest version, duplicate or missing component entries, byte lengths, and SHA-256 hashes. It exits 0 when valid and 1 when invalid. Legacy v1 packages with a manifest self-entry are reported as warnings. verify-export does not prove that the original database was authentic or untampered before export, and it is not a digital signature or chain of custody.

What verification cannot do

  • Prove runtime correctness or that every event was captured.
  • Recover missing events, provenance, or identity.
  • Prove that the kernel or host was uncompromised.
  • Provide adversarial tamper evidence.
  • Prove that a file path resolved to the file ultimately accessed.
  • Turn a connect attempt into an established session.
Use Limitations when a conclusion depends on a negative result or on completeness.