Skip to main content

​
The Pitch

STRATT doesn’t just build prompt infrastructure — it runs on it. The Pathfinder council is a 6-agent crew (named after the Ares III crew from The Martian) that handles every dev task from project intake to CI bootstrap. It’s the first domain activated in the Sol-by-Sol launch sequence, and it exists to prove one thing: the system works on itself before it ships to anyone else.

​
What’s Live

  • 6 specialised agents: architect, hostile reviewer, documenter, CI/CD operator, test architect, and planner — each with defined expertise boundaries and a Zod-validated persona
  • Sol-1-Boot chain: A 6-step pipeline that takes a raw project idea and delivers a validated, CI-ready scaffold — with two mandatory gate checkpoints where humans must approve before proceeding
  • Protected agent enforcement: BECK-02 (hostile reviewer) cannot be removed from any dev chain — CI fails automatically if skipped
  • Gate authority: Only LEWIS-06 (planner) can approve the final gate — no rubber-stamping

​
Why It Matters

Most prompt engineering tools ship demos. STRATT ships its own CI pipeline checking its own prompt changes. The stratt ci command runs 9 automated checks — fingerprint integrity, import resolution, cycle detection, protected agent enforcement, gate preservation, contract stability, draft isolation, and blast radius analysis — on every PR that touches a unit file. The Pathfinder council is the proof that this pipeline catches real problems, because it’s the first content set to run through it.

​
Sol-by-Sol Activation

Week 1 (now): Dev domain — Pathfinder council online, validating all tooling. Week 2+: Domain councils activate one-by-one (neuro, finance, nutrition, legal, film, artist), each following the same bootstrap pattern proven by Pathfinder.