Full House specifications
The engine's architecture, execution flows, per-layer state machines and byte-level contracts — rendered from the repository's docs/ at commit 7d7b037dd644: 9 documents, 48 diagrams. Every diagram is drawn from its source in the page; open Diagram source under any of them to copy it. Headings carry the same anchors as on GitHub, so a link into a section can be shared.
Allocation Market — the vault-capacity epoch, read by the engine
Companion to architecture.md (the Allocation Layer in the Level-3 DAG), state-layers.md (§12, the epoch state machine), flows.md (Flow 8), event-catalog.md (§6.16–§6.17, the epoch log and the allocation stream) and matching-engine.md (§6, sleeve ceilings).
Dust2 Live Kill Market — Architecture (C4)
The system is a DAG of append-only, offset-addressed logs ("streams") connected by deterministic transformers. Every runtime component obeys one contract:
Event Catalog & Canonical Serialization
Companion to architecture.md (stream store, lineage), state-layers.md (every transition names an event from this catalog), and flows.md. This doc resolves the storage contradiction (JSONL vs canonical bytes), defines the one canonical encoding every hash in the system is computed over, and catalogs every event type per stream.
Dust2 Live Kill Market — Execution Flows (C4 Dynamic Diagrams)
Companion to architecture.md. Each diagram traces real data through the stream DAG. Offsets, state_version, and the spec's worked example ($0.47 entry, 3 final kills, $60 settlement) are used throughout.
Gateway Wire Protocol
The byte-level contract between the gateway and every external client — the retail interface consumer and the Python SDK's quoting clients alike. This document is to the WebSocket boundary what event-catalog.md is to recorded streams: the frame registry of record.
Matching Engine — Specification
The third "genuinely hard node." Companion to architecture.md (Exchange Layer), state-layers.md §5–§6 (quote and order state machines — owned there, not duplicated here), event-catalog.md (§6.5–§6.7 — every emitted event), and settlement-contract.md.
Model Plug-and-Play Layer — In-Depth Design
Companion to architecture.md (Pricing Layer), flows.md (Flows 0, 1, 6). This is the engineering specification for how probabilistic models plug into the pricing layer without touching the spine, while preserving the four system guarantees: bit-exact determinism, lineage, gated evaluation, and provability.
Settlement Contract — Decision Record
The binding definition of what settles every Dust2 kill market (SC-1..SC-6), the match-winner claim family LoL, Dota2 and the synthetic synth title settle on (SC-7), the race-to-kills line family LoL and Dota2 settle on (SC-8), the kills-over-N-at-minute-M line family LoL and Dota2 settle on (SC-9), its per-side variant (SC-10), its gold-lead variant (SC-11), the tally families — towers, dragons, barons (SC-12) — the HOUSE-LINE families — the final total kills and the kill handicap over a line the HOUSE sets (SC-13) — and the void unwind every family shares (SC-V). Pinned before the parser is written; the preflight report certifies conformance; every rule carries a parser assertion. Companion to event-catalog.md (§6.1 match-log events) and flows.md Flow 0/3/5.
Layer State Model — C4 State Diagrams per Layer
Companion to architecture.md (Level 3 layers), flows.md (the events that drive every transition), and model-plugin-layer.md (§9 lifecycle). This is the C4 state level: one section per architecture layer, each showing the layer as an immutable consumer/producer of time-travelable streams.
Read these docs with an AI agent
These chapters are also plain text at stable URLs. Point an agent at the files. The version is engine commit 7d7b037dd644ef8ee8c4f024d92ecaa761510fe5, the commit this page was built from.
- llms.txt names that commit and lists every chapter.
- Each chapter is a text file under
/raw/, for example architecture.md. - The full-house-docs skill tells an agent to fetch those URLs and to treat the commit as the version.