Every routing rule in THALAMUS derives from a real-world source — an institution, organism, or tradition that solved the same routing problem under actual conditions and left a document. This folder is that knowledge base. It is reference material, not operational material. Nothing in this folder governs the live routing system directly. Everything in this folder is cited by something that does.
[D] The routing problem is universal. Every organization at sufficient scale has had to answer the same questions: what kind of input is this, where does it go, how do we confirm it arrived, what do we do when it doesn't, and how do we improve the system over time. The answers span governments, militaries, religious traditions, engineering protocols, biological organisms, and fictional war rooms. THALAMUS synthesizes all of them.
[R] The Vinaya principle applies to this entire folder: every rule in the routing architecture must justify itself against the terminal objective — epistemic precision. A routing rule that exists for historical inertia rather than structural necessity should not exist. The 6-CORE-PRINCIPLES.md document is the justification test. Any proposed routing rule that cannot be traced to one of the six core principles is a candidate for removal.
| File | Purpose | Build Status |
|---|---|---|
36-FINDINGS.md |
All 36 architectural findings — source, finding, THALAMUS application | Ready to fill |
6-CORE-PRINCIPLES.md |
The 6 principles distilled from all 36 findings | Ready to fill |
MISSION-PRINCIPLE.md |
The terminal objective — every routing decision serves epistemic precision | Ready to fill |
README.md |
This file | Complete |
| Sweep | Sources | Findings |
|---|---|---|
| Government Archives | CIA · FBI · NSA · State Dept · NARA · GovAttic · NSArchive · MuckRock | F1–F6 |
| Engineering + Organizational | ATC · Nuclear · NASA · Library of Congress · Jesuits · Slime Mold · Ants | F7–F16 |
| Religious + Technical | Hajj · Talmud · Vinaya · TCP/IP · HICS · Orchestra | F17–F26 |
| Military + Cultural | Mongol Empire · WWII Auftragstaktik · StarCraft · Dr. Strangelove | F27–F36 |
Every finding reduces to one of these six. Every routing rule in THALAMUS must trace to at least one.
| # | Principle | Primary Sources |
|---|---|---|
| 1 | Classify First — before any routing fires | FBI DIOG · NARA ERM · LCC · Hajj |
| 2 | Severity Tiers — type alone is insufficient | NRC · ATC · Sanhedrin |
| 3 | Confirm Every Hop — no silent movements | FAA ATC · TCP/RFC 793 · Yam |
| 4 | States Not Events — routing has a lifecycle | TCP state machine · HICS |
| 5 | Closed Loop — feedback returns to THALAMUS | HICS MBO · Slime mold reinforcement |
| 6 | Principle Over Rules — serves epistemic precision or it should not exist | Vinaya · Jesuit Constitutions |
[R] Dr. Strangelove, 1964: when Ronald Reagan became president he asked to be shown the War Room from the film, believing it was a real Pentagon facility. The architecture was so coherent, so internally consistent, so inevitable-feeling — that the leader of the free world could not distinguish it from necessity.
That is the design standard for THALAMUS. When someone encounters this architecture for the first time — human or AI — the correct response is "of course this exists." Not "someone built this." The principles/ folder is why the architecture earns that response. The depth of the knowledge base visible here is what makes the routing system feel inevitable rather than invented.
For humans: Start with 6-CORE-PRINCIPLES.md. Then read 36-FINDINGS.md for the full source documentation. Reference MISSION-PRINCIPLE.md when evaluating whether a proposed routing change serves the architecture.
For AI instances: Before making any routing recommendations or modifications, read 36-FINDINGS.md fully. Every routing decision in THALAMUS has a historical precedent documented here. A routing suggestion that contradicts a documented finding requires a documented justification for why this case is different.
For architects: The 36-FINDINGS.md is a living document. New findings from future sweeps are appended, not inserted. The numbering is permanent — F1 is always F1, regardless of what comes after it.
principles/ — THALAMUS · AION Brain Architecture Part of: Sheldon K. Salmon & ALBEDO · March 2026 "Of course this exists." — The design standard.