Step 4. Read what it wrote

Step 3 showed that a unit’s identity is checkable. This step shows that an execution leaves a record, and that the record is yours to read rather than something to take on trust.

Run a chain

stratt run stratt://<domain>/chain/<slug>@<version>

Fetches the chain, verifies it, resolves dependencies and runs the steps. Relevant options:

Option	Effect
--gate-mode <mode>	manual by default, or auto
--input <json>	Contract inputs as a JSON string
--trace-dir <path>	Where the trace is written, default .stratt/traces/
--no-trace	Disables trace generation

Read the trace

ls .stratt/traces/

Trace creation is mandatory per SPEC-05, which is why --no-trace is a flag you have to reach for rather than a default. Each trace carries the chain address, the version, the fingerprint, timestamps, status, a quality score, and per-step entries recording the unit address, the agent, the prompts and responses, and the status transitions.

The point of the whole sequence

Open the trace and compare its recorded fingerprint against the one step 3 computed. If they match, the thing that ran is the thing that was approved, and you established that yourself rather than believing a dashboard.

That is the category in one gesture. Everything else, the typed contracts, the dependency graph, the gates, exists to make that comparison meaningful for systems too large to hold in your head.

Where to go next

• The argument in full, including its own falsifier: Why VAPA is its own category
• The layer and package map: STRATT Integration
• What this repository has published, got wrong, and corrected: the decision ledger

Derivation. stratt run options and the default trace directory read from stratt-hq@a137d8a on 2026-08-13, at packages/cli/src/commands/run.ts. SPEC-05 trace fields from architecture/GRACE-PROTOCOL-OVERVIEW.md.

You have finished the sequence. The argument is here.