Claude Code is powerful.
Without discipline, it's chaos.
Directives, agents, and skills that enforce engineering discipline at every step — session continuity, quality gates, behavioral tests, and ADRs, all automatic.
14-day free trial · $99/yr after · no charge today
Why DevArch
An architect in the room.
AI makes a lone developer fast. DevArch makes them disciplined — the expert presence that keeps architecture coherent and quality compounding, so a small team delivers like a big one.
Hold the boundaries
Domain-driven design shouldn't live in one person's head — or assume a blank page. DevArch finds the bounded contexts and ubiquitous language three ways: as they emerge, through a modeling conversation, or extracted from an existing codebase. Then a plain-language primer gets your domain experts to confirm the model.
How domain modeling works →
From BUILD: FAILED to all green
Behavioral tests, mutation checks, and quality gates turn a red build into a passing one — with the tests that prove it. You direct the work; DevArch keeps the discipline, so quality compounds instead of eroding.
How it works
The discipline is automatic.
DevArch hooks into Claude Code's lifecycle. Every session follows this discipline without you invoking it — and nothing is lost between sessions.
The category
This is harness engineering.
Prompt engineering got the words right. Context engineering got the information right. Harness engineering gets the environment right — the directives, agents, and feedback loops that govern how an AI writes code. DevArch is that layer for Claude Code.
Step 1
Prompt engineering
Language
Get the words right.
Step 2
Context engineering
Information
Get the inputs right.
Step 3
Harness engineering
Environment
Govern how the agent works.
Agent = Model + Harness
The model is half the system. The harness — everything wrapping it — is the other half, and the half you control. DevArch is the outermost ring: the discipline that governs everything inside.
The industry is converging on the name. Martin Fowler, Red Hat, and Loiane Groner all call it harness engineering. DevArch has been building it since v1.0.
What's inside
Four pillars, enforced — not suggested.
Every rule fires automatically through Claude Code's lifecycle. You direct the work; DevArch keeps the discipline.
Continuity
- Session start restores context and the last session's recap
- Work summaries capture state, blockers, and decisions
- Per-session IDs keep concurrent sessions from colliding
Coding Discipline
- Invariants and variants named before code is written
- Boundary Statements gate edits to cross-boundary state
- Cohesive modules with clear domain / infrastructure boundaries
Testing & Verification
- Behavior Statements precede every test
- Tests graded RED / YELLOW / GREEN
- Mutation checks and real-path integration tests
Architecture & DDD
- ADRs capture decisions that constrain future work
- Planning gates decompose goals into phases
- Bounded contexts and ubiquitous language — modeled in conversation or extracted from code
Every pillar is built from two kinds of control — Guides that steer the agent before it acts, and Sensors that catch what it did after.
CLAUDE.md directives
Guides
Steer before the agent acts · feed-forward
Agents — mutation-verification, pre-session-audit, seam-detector
Sensors
Observe and self-correct · inferential
Hooks — boundary-check, budget, gates
Sensors
Deterministic checks · computational
The Guides / Sensors vocabulary is harness engineering — DevArch supplies the mechanisms.
Proof
Real sessions, no mockups.
This is what a DevArch session actually looks like — install to commit, with the gates and agents firing along the way.
$ bash devarch-universal.sh && devarch init ✓ DevArch v4.6.0 installed · 14 agents, 15 skills, 8 hooks $ claude ↳ SessionStart · [session a78e93] ✓ recap: where we left off — v4.6.0 cut ↳ pre-session-audit ⚠ 1 blocker: no test for the new contact route $ implement the contact endpoint ↳ session-planner · 4 phases, plan.md written … writing code, behavior statements, tests … ↳ mutation-verification ✓ tests assert on real state changes $ ship it ↳ work-summary-writer · commit-remote ✓ committed + pushed 78237f0 (41s)
Proof
DevArch evolved from itself.
The rules were forged building the thing that enforces them. Every release ships under its own discipline — the changelog is the case study.
v1.0
CLI, agents, lifecycle rules
v2.0
Boundary Statements & Integration Reality
v3.0
Tuned for Claude Opus 4.7
v4.0
A product: installer, registry, offline licensing
v4.1
Decision-aware planning + plan-review
v4.2
Native Windows installer + PowerShell hook parity
v4.5
Domain modeling with three entry paths + SME primer loop
v4.6
Validated for Claude Fable 5 — rule-firing harness now real
Pricing
One product, everything included.
Annual license, priced by seats. Solo starts with a 14-day free trial — no charge today.
Solo
One Developer
$99 /yr
per year · 1 seat
All of DevArch, one seat. 14-day free trial, then $99/year.
More seats, invoicing, or custom terms? Larger teams come through conversation — get in touch.
Questions
Before you start.
Does DevArch work with my existing CI/CD and editor?+
Yes. DevArch is a layer for Claude Code — directives, agents, hooks, and skills. It doesn't replace your build, test, or deploy tooling; it enforces discipline around the work, then you commit and ship through your normal pipeline.
What's included in each tier?+
Everything. There is one product — all agents, skills, hooks, and the DDD capabilities are in every tier. Tiers differ only by seat count.
What happens when my license lapses?+
DevArch is an annual license. Your projects and their artifacts — summaries, ADRs, plans — are plain files in your repo and stay yours. Continued use of the methodology tooling requires an active license.
Is my code or data sent anywhere?+
DevArch runs locally inside Claude Code. It reads and writes files in your repo; it doesn't add a server or send your code to DevArch. Licenses are ES256 tokens verified entirely offline — no phone-home.
Which Claude models does it target?+
DevArch is tuned and validated for the latest Claude models — currently Opus 4.8 and Fable 5 — and rule-firing is re-validated on every model bump and on every new model line.
How do I install it after buying?+
Purchase through Polar checkout and you receive the self-contained installer plus a license token by email. One command installs to ~/.devarch and puts devarch on your PATH — no git clone, no dependencies.
Bring discipline to your Claude Code.
Start free for 14 days. Keep your summaries, ADRs, and plans whether you stay or not.