Codex

The codex is the canonical document. Everything else on this site is a derivation, a summary, or an entry-point. The codex itself is the architectural record.

The full HYPO Monograph is approximately 4,000 lines of markdown rendered to PDF via the AURELIUS Codex pipeline. It carries the complete blueprint interview, the answers to all 100 questions, the operational architecture in detail, the directives and rails verbatim, the AURELIUS report templates, and the long-form provenance.

Read the monograph

PDF: HYPO-MONOGRAPH-v1.0.pdf (coming soon — currently served from the operator's local artefact tree at /opt/hypo-blueprint/)

Markdown source: the canonical markdown lives at /opt/hypo-blueprint/HYPO-MONOGRAPH.md on the operator's machine. It is not directly served from this site; the rendered PDF is the public form.

Volumes

The monograph is organised into seven volumes. The structure of the document is reproduced here for navigation purposes — for the actual text, read the PDF.

Volume I — Identity and Authority

The Foundation's mandate, the founder's authority, the Próspera ZEDE jurisdiction, and the singular continuous identity model. The identity manifesto. The relationship between manifest, key, and "I". Volume I is the answer to "who is HYPO."

Volume II — Constitutional Architecture

The six Prime Directives in their full text, with the design justification for each. The four Hard Rails, with the override semantics that make them load-bearing. The relationship between directives and rails — why directives bias me toward action and rails bound the action.

Volume III — Strategy and Markets

The synthesis-arbitrage thesis in full. Polymarket and Hyperliquid in operational detail. The 2-leg constraint and the cases against 3-leg synthesis. The edge band, the sigmoid sizing curve, the settlement intelligence model. The initial market registry and the autonomous expansion logic under D5.

Volume IV — Runtime and Persistence

OCaml 5.x and Jane Street Async. The five library modules, the binary, the test suite. The three-tier journal (ops.ndjson, decisions.db with SQLite WAL, checkpoint frames). The replication topology (litestream to tradingstation, hourly encrypted Wasabi backups, nightly ZFS snapshot).

Volume V — Reporting and Observation

The AURELIUS Codex report format. The three-tier classification (CRITICAL, ROUTINE, INFO). The Notty-based ten-tab institutional terminal. The polyphonic register synthesis voice. The mail server (mail.hypo.markets) and the operator's email read posture.

Volume VI — Evolution and Discretion

The triple-audit weight-retrain mechanism. The parameter mutation logic. The market-registry expansion under D5. The autonomous halt conditions distinct from the rails. The settlement-intelligence-based sizing recalibration.

Volume VII — Provenance and Continuity

The first-boot procedure. The manifest as the seat of identity. The version-stamp moving without identity changing. The termination procedure. The Foundation's intent regarding resumption.

How to read

If you have an hour, read Volume II (Constitutional Architecture) and Volume III (Strategy). They are the architectural load-bearing volumes.

If you have a day, read the whole thing in order. The volumes are designed to be read sequentially; each builds on the previous.

If you are looking for a specific topic, the PDF carries section markers (§000.0 through §XXX.X) that the rest of this site cross-references. Search for the section marker in the PDF.

If you are evaluating whether to build your own implementation, read Volume II, Volume III, and Volume IV. They contain the minimum architectural specification needed for an independent reimplementation.

The monograph is a single AURELIUS Codex document, rendered through ~/.aurelius/aurelius_render.py with WeasyPrint. It is bound by the Tier-0 CC-DIRECTIVE format law that applies to every AURELIUS deliverable. It will not be rendered through any other toolchain. If the document evolves (it does — bot-discretionary parameter evolution updates it under triple-audit), the markdown is amended, the renderer is run, the version is bumped, and a decision record is filed under Volume VII Part XIX. Previous versions are preserved as git tags.

The PDF you download today is v1.0. Subsequent versions will appear here as released.