§07 · THE HOUSE · THE FLEET
A house with divisions
Hover a room to read its division.
A floorplan, not a status board. The Floor next door is live — every posture there is a pure function of the process table. These are in-process subagents rather than scheduled lanes, so there is no per-unit liveness to read and none is claimed. What is true here is the shape: which divisions exist, who coordinates each one, and how far each unit actually got.
35 agents: 15 built, 7 partial, 13 scaffold. A scaffolded station is drawn as studwork — framed, not fitted out — because that is what the module is. Measured from source, not judged: an agent is `built` if its module carries no stub markers and runs to 300+ lines, `partial` if it is 240+ lines with stub markers left in it, and `scaffold` if the module is under 240 lines — thin enough that most of what it returns is still placeholder. The whole Red Team is scaffold: the adversarial division was designed before it was built, and a security division is the last place to round that up. 34 of the 55 files in the package define one agent each and the other 21 are infrastructure; Hephaestus is the 35th agent and lives outside the package.
Moirai3/3 built
Self-development and internal improvement
- ClothocoordinatesAutonomous researcher / skill discoverer
- Lachesis683 linesRoadmap gap scanner / measurer
- Atropos620 linesBug hunter / dead-code cutter
Red Team0/8 built
Security testing and adversarial analysis
- DajjalcoordinatesPhishing simulation and social-engineering testing
- Yajuj Majuj150 linesPaired attack-surface identifiers
- Dabbat al-Ard144 linesExternal vulnerability identification
- Maalik243 linesRed Team information keeper
- Az-Zabaniyah113 linesOperational data reader
- Hudhud121 linesSearch and range reconnaissance scout
- An-Naml127 linesNetwork and swarm reconnaissance
- Dhul-Khulud117 linesOSINT sourcer
Athena's Council0/3 built
Strategy, wisdom and decision support
- GilgameshcoordinatesPower dynamics, strategic positioning, historical parallels
- Philosopher86 linesPhilosophical framework application and Utopia Index
- Relationship Advisor76 linesCommunication pattern analysis — explicitly not therapy
Operations4/4 built
Infrastructure monitoring and security
- DragoncoordinatesSystem guardian — resource and health monitoring
- Cerberus690 linesSecurity guardian — permissions and audit log
- Fenrir598 linesFast retrieval and scraping
- Kitsune500 linesLegal and ethical reasoning gate
Creative1/2 built
Content generation and voice
- SirencoordinatesCommunication and alias management
- Murasame692 linesHealth and performance tracking
Intelligence3/3 built
Research, analysis and intelligence
- LeviathancoordinatesDeep research analyzer
- Pegasus567 linesCreative proposal generator
- Davis510 linesSkeptical challenger — interrogates proposals, never votes
Engineering0/2 built
Code implementation and teaching
- PhoenixcoordinatesProject automation, CI/CD and code implementation
- Centaur815 linesLearning, skill-gap analysis, testing
Hephaestus0/1 built
Browser automation and web interaction
- HephaestuscoordinatesBrowser automation — gates every browse through Kitsune
Finance1/4 built
Financial intelligence across futures, options and prediction markets
- HarpycoordinatesFinancial tracking
- Chronos258 linesFutures desk
- Janus287 linesOptions desk
- Sibyl270 linesCrypto and prediction-markets desk
Detached3/5 built
Real agents that answer to no division.
- Kirin571 linesThorough evaluator — the quality gate on every Pegasus proposal
- Minotaur71 linesLearning gatekeeper — reviews packages and skills before they reach the code
- Panther403 linesPrivacy, stealth and trace elimination — the post-execution scrubber
- Moirai641 linesCoding division overseer — grades internal improvement proposals A to D
- Hafiz72 linesIslamic studies — Quranic analysis, hadith, fiqh
The terminal
The same box that sits under The Floor, reading a different thing. That one reads a live process table; this one reads the roster. Arrow keys move, or click.
The bus
Divisions are a filing system. This is the part that moves. A request enters on the left, runs the shared bus, drops into a division, and comes back out as one aggregated proposal — then Kitsune classifies it and it passes, waits for me, or is destroyed.
Hover a dock to read who is in it.
Everything in that diagram is read out of the source. One bus, shared with the triplet
(protocol.py: “Subagents use the SAME bus — no separate infrastructure”).
Aurora, Borea and Lis get TRIPLET_PRIORITY_BOOST = 100, so their lane merges ahead of
everything — the three on The Floor are always served first. A coordinator turns many member
opinions into a single proposal, which is AD-209, which is why several small packets enter a dock and
one larger one leaves it. And RED is hardcoded, not model-evaluated: kitsune.py
says it “must be auditable, deterministic, and non-bypassable”, so a RED packet hits a wall
rather than an exit.
What it is not: live. No packet on that canvas is a real message. The lab's bus is not exposed to the internet and it is not going to be. The topology is true, the priority rule is true, the aggregation rule is true and the four verdicts are true — the traffic is illustrative, and saying so is cheaper than being caught not saying it.
Names are drawn from mythology because a fleet this size needs names you can hold in your head: Cerberus guards, Kitsune classifies risk before anything external happens, the three Moirai spin, measure and cut the codebase, and Davis exists only to argue — it interrogates every proposal and never votes on one. The names are the ones in the source.