Where the practice runs.
Four tools you host yourself, stacked in the order the loop assumes — the runtime at the foundation, the surface where you work, and the method encoded on top.
All of it self-hosted — single binary, Apache 2.0, zero vendor lock-in. It runs on your hardware; your data never leaves it.
Layer by layer
The foundation · runtime
Gateway
the runtime the method assumes
A self-hosted agentic runtime — multi-provider routing with intent classification, DAG orchestration for real workflows, and SSE observability that streams every token as it lands.
The surface · where you work
CLI
where the practice happens
An interactive REPL wired to the Gateway. Every slash command maps to a named surface, and a hook runner with lifecycle gates keeps the method honest as you go.
dojo ~ /strategic-scoutsurface
tension in · analyzing 3 routes
→ recommend route 3 — ship, keep the interface clean
dojo ~ /senseisurface
Green Belt · streak 12
33 commands · 8 surfaces
The top layer · the method
Plugins + MCP
the method, encoded
The discipline written where the model reads it — skills across behavioral plugins, plus an MCP server that puts the method layer inside Claude Code as tools and seed patches.
The rest of the stack
Focused packages extracted from the core runtime — each one zero-dependency where it can be.
logwatcher
Zero-dependency Go log watcher — multi-file tail, bounded fan-out, silent drop on slow clients.
github.com/DojoGenesis/logwatchergit-for-strategy
Strategic thinking as installable Claude Code infrastructure — the scout move, packaged.
github.com/DojoGenesis/git-for-strategySurfaceIntelligence
Competitive surface analysis — output as seeds and decision logs, not unstructured text.
github.com/DojoGenesis/SurfaceIntelligenceorchestration-guide
A progressive curriculum for Claude Code mastery — first session to production.
dojogenesis.github.io/orchestration-guideEight open-source repositories. All Apache 2.0.
Origin
Built by a solo operator.
DojoGenesis began as internal tooling — built to ship software with autonomous agents. Every skill exists because it was needed, and then needed again. The discipline comes from using it, daily.
Cruz Morales · Tres Pies Design · Madison, Wisconsin
Every layer runs on hardware you own — and your data never leaves it.