Skip to main content

​
The Story

Every prompt architecture needs a tool. Not a web UI, not a library — a CLI that a developer reaches for without thinking. stratt new task dev extract-logs → a valid YAML skeleton appears. stratt validate → schema, imports, constraints checked in one command. stratt publish → fingerprinted, pushed to R2, committed to Git. stratt run → chain executes with gate checkpoints where humans decide. STRATT’s CLI is called the Commander’s Tool because it embodies Eva Stratt’s philosophy: relentless precision and zero deviation from protocol. Every command has defined exit codes. Every failure mode has a recovery path. Every publish is a saga with atomicity guarantees.

​
Key Messages

  • “Seven commands, full lifecycle” — new → validate → fingerprint → publish → run → deprecate → verify. No gaps. Every prompt unit state is reachable through the CLI.
  • “Exit codes are contracts” — 0 success, 1 validation fail, 2 tampered, 3 broken import, 4 R2 error. Scriptable. CI-ready. No ambiguous failures.
  • “Gates are architectural, not optional” — stratt run pauses at gate steps and waits for human judgment. --gate-mode auto exists for testing but requires conscious opt-in. Production chains always gate.
  • “R2-first-then-Git” — the publish saga writes to Cloudflare R2 before committing to Git. If R2 fails, nothing happens. If Git fails, R2 has the correct state. Partial publishes are impossible.

​
Positioning

The STRATT CLI is not a prompt manager — it is a prompt architecture tool. The distinction matters. Managers store and retrieve. Architecture tools enforce schemas, verify integrity, resolve dependencies, compute blast radius, and gate execution. The CLI is the enforcement layer for the seven principles in the TAD.

​
Status

Layer 5 implementation complete as of 2026-03-28. The CLI scaffolds all 5 unit types, validates against the full @stratt/schema pipeline, computes Blake3 fingerprints, and executes chains via Anthropic API with gate enforcement. 39 tests passing. Ready for integration testing with real prompt units during the VERITAS migration (Phase 1, weeks 1-3).