Mythos Router

Claude Opus 5 · Strict Write Discipline · Zero Slop
A local CLI power tool for verifiable AI-assisted coding.

What is this? • Features • Installation • Examples • Usage • Architecture • Token Budget • SDK • SWD Protocol

What is this?

mythos-router is a local CLI power tool built around Strict Write Discipline (SWD): a verification layer that checks every file operation an AI agent *claims* to perform against the actual filesystem using SHA-256 snapshots. If a claim doesn't match reality, the batch is rolled back so a bad write never half-lands, and successful runs leave a hash-chained, locally tamper-evident receipt.

The key idea is that the trust boundary is the filesystem, not the model. That makes SWD model-agnostic: it ships with a built-in Claude Opus 5 agent (mythos chat / mythos run), but the same engine verifies file actions from *any* agent — GPT, DeepSeek, a local model, or your own script — with no Mythos model key, over stdin/JSON, the SDK, or MCP. See examples/verified-writes for a runnable "the agent hallucinated a write, SWD caught it" demo.

Zero slop. Zero hallucinated state. Every write verified.

Features

Core Architectural Pillars

1. Configurable Model Selection
Choose the right model for the job via the --effort flag:

The dream command automatically uses low effort (Haiku 4.5) for cost-efficient memory compression, and verify uses lightweight scanning — so you only burn Opus/Fable tokens when you need deep reasoning.

2. Authority-Based "Self-Healing" Memory
Most agentic systems stored state in opaque databases or messy JSON files. Mythos Router treats MEMORY.md as the Sole Authority.

Every action is logged in Markdown first. On startup, the system verifies the integrity of the log via SHA-256 manifest hashing and reconstructs a…