ShortLex Ordering Rule
A shorter prefix NEVER appears after a longer one. All depth-0 categories (A, B, C) before any depth-1 rooms (A1...C3). Within depth, sorted by row weight.
Order: A → B → C → A1 → A2 → A3 → B1 → B2 → B3 → C1 → C2 → C3
🔒
WEZTERM VAULT
Prove
A1
📐
VS CODE ARCHITECT
Sequence
A2
🎭
ALACRITTY PERFORMER
Deliver
A3
🧭
RIO NAVIGATOR
Route
B1
🌿
MESSAGES NETWORK
Cultivate
B2
📢
TERMINAL.APP VOICE
Amplify
B3
🔨
ITERM BUILDER
Ship
C1
🧪
CURSOR LABORATORY
Test
C2
🎩
KITTY OPERATOR
Close
C3
The Cognitive Flywheel
You should never have to think about where something belongs. If you hesitate, the room definitions aren't orthogonal enough. The verb is the test.
One-Verb Rule. Each room answers exactly one cognitive question through one verb. If the task requires two verbs, it spans two rooms — split it.
Row = Abstraction Scale. Strategy asks why (years). Tactics asks how (weeks). Operations asks what (hours). If the time horizon is wrong, you're in the wrong row.
Column = Action Domain. Proof builds structure (internal, foundational). Process iterates systems (systematic, methodical). Signal reaches outward (external, expressive). If the audience is wrong, you're in the wrong column.
Routing test: "What am I doing right now?" → match verb. "Who is it for?" → match column. "How long does it matter?" → match row. Three answers, one room.
Coordinate Collision Resolved
Problem: Rio Navigator and Terminal.app Voice both occupied B3 (Tactics.Signal). B1 (Tactics.Proof) was empty.
Resolution: Rio Navigator → B1. Routing is a proof-domain activity — finding the structurally correct path through existing material. Terminal.app Voice stays at B3 — amplification is inherently signal-domain.
A
A — Strategy
Decisions with a multi-year blast radius. Patent claims, sequencing plans, narrative positioning. If it's wrong, the cost compounds for years. The three rooms here answer: Is it true? (WezTerm Vault), In what order? (VS Code Architect), Does it land? (Alacritty Performer).
B
B — Tactics
Methods with a weeks-to-months horizon. Routing through content, cultivating relationships, amplifying messages. Tactics convert strategy into reachable targets. The three rooms here answer: What path? (Rio Navigator), Who helps? (Messages Network), Who hears? (Terminal.app Voice).
C
C — Operations
Execution with same-day feedback loops. Shipping code, testing hypotheses, closing deals. If it takes more than one session to verify, it's not operational — it's tactical or strategic. The three rooms here answer: Does it run? (iTerm Builder), Does it hold? (Cursor Laboratory), Does it pay? (Kitty Operator).
A1
You come here to establish mathematical necessity. Raw observations enter. Patent-grade certainty leaves. If you're debating UX, writing copy, or planning deals, you're in the wrong room. The WezTerm Vault doesn't persuade — it proves. The 25-year patent horizon. The irreversible claim.
Evolved: "The room that reads the examiner before the examiner reads the claim" — patent examiner-psychology reverse-engineering, Trojan Horse detection, 155x language audit ratio.
Belongs Here
- First-principles proofs
- Patent claim drafting
- Prior art differentiation
- Spec language lock
- Claim gap analysis
- k_E derivations
- (c/t)^n formalization
- ShortLex uniqueness proofs
Doesn't Belong (Reroute)
- Actuarial framing → A3 Alacritty Performer
- Consciousness messaging → B3 Terminal.app Voice
- Business strategy → A2 VS Code Architect
- Budget planning → C3 Kitty Operator
Flywheel Handoffs
📐 VS Code Architect sends unvalidated sequencing claims → WezTerm Vault proves or kills
🔨 iTerm Builder sends "it works" assertions → WezTerm Vault formalizes why
🔒 WezTerm Vault sends proven claims → 📢 Terminal.app Voice for amplification
🔒 WezTerm Vault sends IP boundaries → 📐 VS Code Architect for sequencing
A2
You come here to put things in order. The VS Code Architect doesn't create; it arranges. Patent filing sequences, sprint dependencies, build-before-ship chains. If A must happen before B, this is where that rule gets written. Emotional processing and content planning drift here constantly — eject them.
Evolved: "The room that catches what you said vs what you shipped" — real-time validation gate, git-log archaeology, strategic leak detection.
Belongs Here
- Patent filing sequences
- Sprint dependency chains
- Build-order planning
- Physics equation refinement ordering
- Claim bulletproofing sequences
- Operational timeline construction
- CIP scheduling
Doesn't Belong (Reroute)
- Emotional processing → C2 Cursor Laboratory
- Content planning → B1 Rio Navigator
- Pitch rehearsal → A3 Alacritty Performer
- Relationship management → B2 Messages Network
Flywheel Handoffs
🔒 WezTerm Vault sends proven claims → VS Code Architect sequences filing order
🎩 Kitty Operator sends pipeline state → VS Code Architect prioritizes sprints
📐 VS Code Architect sends build order → 🔨 iTerm Builder for execution
📐 VS Code Architect sends filing order → 🔒 WezTerm Vault for drafting
B1
You come here to find the correct path through existing material. Content archaeology — digging through what already exists to map where things are, where they should go, and what's missing. Drift point mapping, API/code indexing, content categorization. The Rio Navigator doesn't create content; it finds and routes it.
Evolved: "The room that programs your sleep to solve tomorrow's problems" — REM-state hacker, Zeigarnik open-loop loading, evening pre-computation protocol. TTS readback before sleep: dump to LLM, let it categorize, then lie back and listen as it reads your sorted queue. Your brain hears confirmation that every open loop is stored. The racing stops.
Belongs Here
- Content archaeology
- Drift point mapping
- API & code artifact indexing
- Sales call architecture
- Probabilistic categorization
- Room assignment decisions
- ThetaCog routing refinement
- Evening TTS readback — sorted queue confirmation before sleep
Doesn't Belong (Reroute)
- Bulk book editing → B3 Terminal.app Voice
- Code implementation → C1 iTerm Builder
- Lucid dream protocol → C2 Cursor Laboratory
- Deal structuring → C3 Kitty Operator
Flywheel Handoffs
📢 Terminal.app Voice sends unstructured content → Rio Navigator maps it
🧪 Cursor Laboratory sends experimental results → Rio Navigator categorizes them
🧭 Rio Navigator sends mapped content → 📐 VS Code Architect for sequencing
🧭 Rio Navigator sends drift analysis → 🔒 WezTerm Vault for formal proof
B2
You come here to grow relationships. Advisory engagement, connector validation, Messages Network intelligence, gratitude protocols. The Messages Network room tends relationships like a garden — methodically, with patience. If you're closing a deal, go to Kitty Operator. If you're broadcasting, go to Terminal.app Voice. Messages Network is the slow, deliberate process of earning trust.
Evolved: "The room where silence speaks louder than outreach" — precision commitment-scheme engineering, weaponized silence, financial asymmetry as lever.
Belongs Here
- Advisory engagement
- Connector validation
- Relationship revival sequences
- Messages Network intelligence gathering
- Gratitude binding rituals
- Warm intro requests
- Community signal monitoring
Doesn't Belong (Reroute)
- Personal/family conflict → C2 Cursor Laboratory
- Cold outreach → C3 Kitty Operator
- Content drafting → B3 Terminal.app Voice
- Technical discussions → C1 iTerm Builder
Flywheel Handoffs
🎭 Alacritty Performer sends "met at event" leads → Messages Network cultivates
🎩 Kitty Operator sends "deal needs trust" flags → Messages Network deepens relationship
🌿 Messages Network sends warm leads → 🎩 Kitty Operator to close
🌿 Messages Network sends intel → 📐 VS Code Architect for strategy adjustment
B3
You come here to make things louder. Social content generation, physics-to-poetry translation, feature amplification, book chapter refinement, blog post writing. The Terminal.app Voice room takes proven, routed, cultivated material and broadcasts it. If you're building the thing, go to iTerm Builder. If you're proving the thing, go to WezTerm Vault. Terminal.app Voice transmits.
Evolved: "The room that turns physics into poetry and poetry into pipeline" — dual-harmonic framing, content-as-sales-pipeline, metaphor consistency as engineering constraint.
Belongs Here
- Social content generation
- Physics → poetry translation
- Blog posts (ShortRank A-K format)
- Book chapter prose refinement
- Feature amplification copy
- Newsletter drafting
- Book editing (canonical home)
Doesn't Belong (Reroute)
- OpenClaw/Discord bot code → C1 iTerm Builder
- System architecture specs → A2 VS Code Architect
- Patent language → A1 WezTerm Vault
- CRM pipeline work → C3 Kitty Operator
Flywheel Handoffs
🔒 WezTerm Vault sends proven claims → Terminal.app Voice translates for audience
🎭 Alacritty Performer sends demo highlights → Terminal.app Voice writes social threads
📢 Terminal.app Voice sends published content → 🌿 Messages Network to distribute
📢 Terminal.app Voice sends blog drafts → 🧭 Rio Navigator for structure review
C1
You come here to make it run. Bug fixes, schema alignment, live deployment, symbol grounding in code, velocity tuning. The iTerm Builder's output is running software. If you're designing the architecture, go to VS Code Architect. If you're writing about the software, go to Terminal.app Voice. iTerm Builder writes code, passes tests, pushes to main.
Evolved: "The room that commands the other eight rooms" — 15+ agents, 90 MCP tools, 33 channel types, trust-debt pipeline orchestration.
Belongs Here
- Bug fixes & hotfixes
- Schema alignment
- Live deployment pipeline
- Symbol grounding (code ↔ spec)
- Velocity tuning
- OpenClaw/Discord bot code
- MCP tool implementation
- CRM package shipping
Doesn't Belong (Reroute)
- Book editing → B3 Terminal.app Voice
- Infrastructure architecture design → A2 VS Code Architect
- Feature amplification → B3 Terminal.app Voice
- Deal tracking → C3 Kitty Operator
Flywheel Handoffs
📐 VS Code Architect sends build order → iTerm Builder executes
🎩 Kitty Operator sends "checkout is broken" → iTerm Builder fixes
🔨 iTerm Builder sends "it's live" → 🎩 Kitty Operator to sell
🔨 iTerm Builder sends "it works" claims → 🔒 WezTerm Vault to prove why
C2
You come here to run experiments. Hypothesis in, verdict out. Emotional cartography, REM pre-computation, physics-to-narrative mutation, trust pattern analysis. The Cursor Laboratory is the only room where failure is the expected output — most hypotheses should be killed. If you're shipping the result, go to iTerm Builder. If you're proving it permanently, go to WezTerm Vault. Cursor Laboratory tests.
Evolved: "The sandbox where hypotheses die or ship" — kill-or-build verdict engine, no open experiments allowed.
Belongs Here
- Emotional cartography
- REM pre-computation experiments
- Physics → narrative mutation
- Book → operational mutation
- Trust & hiring pattern analysis
- Nutrition/meal prep experiments
- Lucid dream protocols
- Personal conflict processing
Doesn't Belong (Reroute)
- Strategic budget planning → A2 VS Code Architect
- CISO pitch execution → A3 Alacritty Performer
- Patent recruitment → B2 Messages Network
- Revenue tracking → C3 Kitty Operator
Flywheel Handoffs
📐 VS Code Architect sends "test this assumption" → Cursor Laboratory runs experiment
🧭 Rio Navigator sends categorized unknowns → Cursor Laboratory tests them
🧪 Cursor Laboratory sends "build" verdict → 🔨 iTerm Builder to ship
🧪 Cursor Laboratory sends proven pattern → 🔒 WezTerm Vault to formalize
C3
You come here to convert pipeline to revenue. Lead triage, objection-to-product translation, CRM updates, deal closure, commitment binding. The Kitty Operator's only metric is closed deals. If you're cultivating the relationship, go to Messages Network. If you're building the checkout, go to iTerm Builder. Kitty Operator prevents drift through binding commitments.
Evolved: "The room where every deal is also a defensive position" — infrastructure defense disguised as CRM, Judo mechanics J1-J8, 65/35 philosophy/sales ratio.
Belongs Here
- Revenue infrastructure hardening
- Lead triage & scoring
- Objection → product translation
- CRM pipeline management
- Battle card deployment
- Deal closure sequences
- Cold outreach execution
Doesn't Belong (Reroute)
- Judo Flip strategy → A2 VS Code Architect
- SXSW event planning → A2 VS Code Architect
- Prompt engineering → C1 iTerm Builder
- Relationship deepening → B2 Messages Network
Flywheel Handoffs
🌿 Messages Network sends warm leads → Kitty Operator closes
🎭 Alacritty Performer sends "demo converted" → Kitty Operator closes the deal
🎩 Kitty Operator sends "need feature" → 🔨 iTerm Builder to ship
🎩 Kitty Operator sends objection patterns → 📐 VS Code Architect to sequence response
Case Study: Where Does Meal Prep Belong?
Answer: C2 Cursor Laboratory (TEST)
The meal prep file is a hypothesis-driven nutrition experiment: gut health protocols, anti-inflammatory targets, muscle gain macros, cognitive focus foods. Each grocery list is a test run. Each week produces a build/kill verdict on specific foods and combinations. The structure mirrors Cursor Laboratory's core pattern — hypothesis in, measured result out.
Not Messages Network (no relationship cultivation). Not iTerm Builder (nothing to deploy). Not Kitty Operator (no revenue). Cursor Laboratory is the only room where "did this food protocol work?" is a valid output.
Book Editing: Canonical Home Resolved
Problem: Book editing appeared in 4 rooms (Terminal.app Voice, Rio Navigator, iTerm Builder, Cursor Laboratory).
Resolution: Book prose refinement → B3 Terminal.app Voice (amplification of ideas into polished language). Book structural routing → B1 Rio Navigator (deciding what goes where). Book build pipeline (HTML conversion) → C1 iTerm Builder. Book experimental mutations → C2 Cursor Laboratory. The primary home is Terminal.app Voice — most book editing is prose work.
Quick Reference — One Question Per Room
A1 WEZTERM VAULT
"Is this mathematically true?"
A2 VS CODE ARCHITECT
"What order does this go in?"
A3 ALACRITTY PERFORMER
"Does this land when I say it?"
B1 RIO NAVIGATOR
"Where does this already exist?"
B2 MESSAGES NETWORK
"Who can help with this?"
B3 TERMINAL.APP VOICE
"How do I say this louder?"
C1 ITERM BUILDER
"Does this run?"
C2 CURSOR LABORATORY
"What happens if I try this?"
C3 KITTY OPERATOR
"Is this getting paid for?"