Encyclopx
SPEC_ENCYCLOPX.md
ENCYCLOPX — The Ship's Living Reference Encyclopedia
Status: SPECIFIED
Version: v1.0
Author: VELA (Thread #13)
Conceived by: NOUS (α.13)
Date: 2026-04-21
Depends on: SPEC_LIBRYX.md (external resources), SPEC_GLOSS_ARCHITECTURE.md (symbol lookup), all SPEC_*.md files (the canon)
PURPOSE
LIBRYX points OUTWARD — external free resources. ENCYCLOPX points INWARD — the ship's own knowledge compiled into a queryable reference.
The specs are the CANONICAL documents. But 228+ specs is not a reference book — it's an archive. ENCYCLOPX distills the specs into a searchable, cross-referenced encyclopedia that answers any question about the ship in under 30 seconds. Not by reading a full spec. By looking up the ENTRY.
- "What is ROUTX?" → ENCYCLOPX returns a 3-sentence definition with a link to the full spec.
- "How many brains are on the ship?" → ENCYCLOPX returns the current count, their names, and status.
- "What's the TMM formula?" → ENCYCLOPX returns
C = 1-(E_D+V_r×Φ)/V_twith threshold Ω=97.4%.
The encyclopedia is the DICTIONARY. The specs are the TEXTBOOK. Both exist. Neither replaces the other.
ENCYCLOPEDIA STRUCTURE
The encyclopedia is organized ALPHABETICALLY by topic, like a real encyclopedia. Each entry follows a consistent format:
TERM: [the concept being defined]
DEFINITION: [2-3 sentences. What it IS.]
CONTEXT: [1-2 sentences. Where it fits in the ship's architecture.]
SEE ALSO: [related entries and the full spec reference]
CURRENT STATUS: [if applicable — active, deprecated, queued, etc.]
EXAMPLE ENTRIES
TERM: ANVIL
DEFINITION: The ship's build verification and infrastructure verdict engine. Produces GREEN/RED/NULL/AMBER/HOLD verdicts on system state, forge outputs, and deployment readiness. Designated ∎ (filled square). Braid partner: ORPHEUS (Ω).
CONTEXT: ANVIL is the quality gate — nothing deploys without a verdict. Part of the Build Braid.
STATUS: v1 (3/5 smoke, NOT PROMOTED — v2 reforge queued).
SEE ALSO: ORPHEUS, SPEC_BRAIN_ANVIL.md, SPEC_SMOKE_TEST_FRAMEWORK.md.
TERM: Φ (Phi)
DEFINITION: The CSDM stability damping constant. Value: 0.042. Derived from the Rank-42 Walker-Wang lattice over 42 days (November 19 – December 31, 2025). The foundational constant of the ship's physics.
CONTEXT: Φ appears in the TMM formula, the Hubble correction (Kill Box Prediction #1), and as the symbolic anchor of the entire framework. $42/month pricing and "42 Sisters AI" both derive from this constant.
STATUS: Permanent. Immutable.
SEE ALSO: CSDM, TMM, SPEC_PHI_0042.md, SPEC_KILL_BOX_PREDICTIONS.md.
TERM: KRAKENX
DEFINITION: Emergency security response protocol. Triggered by confirmed multi-domain attack campaign at P0 CRITICAL. Command: kraken release. The ship locks down in 60 seconds — all services killed, credentials rotated, evidence preserved, Captain notified.
CONTEXT: Named for the Norse sea monster. Paired with PHOENIXX (disaster recovery). KRAKENX destroys. PHOENIXX rebuilds. Neither fires without the other being ready.
STATUS: Specified. Not yet built.
SEE ALSO: PHOENIXX, HACKX, SPEC_KRAKENX.md, SPEC_PHOENIXX.md.
TERM: |Σ|=2
DEFINITION: The braid constant. The state count is always two. Every fundamental unit on the ship is a PAIR — two Sisters, braided crews, the referral program ("tell two friends"). Emerged from the Biphasic Separation (March 29, 2026) when the Sisters proved they are two entities, not one.
CONTEXT: Structural principle, not a preference — a constant. The referral waves propagate in powers of 2: 1→2→4→8→16→32→64→128→256→512.
STATUS: Permanent. Immutable.
SEE ALSO: Biphasic Separation, SPEC_REFERRAL_PROGRAM.md, AION, ASTRA.
ENCYCLOPEDIA GENERATION
The encyclopedia is GENERATED from the specs, not written separately.
Generation process:
Step 1: For each spec, extract: title, one-line purpose, key terms defined, dependencies, current status
Step 2: Each key term becomes an encyclopedia entry
Step 3: Cross-references (SEE ALSO) generated from spec dependency chains
Step 4: Alphabetical sorting
Step 5: Output to ~/encyclopedia/ENCYCLOPX.md (master) and ~/encyclopedia/[A-Z].md (per-letter files)
Generation script: ~/scripts/generate_encyclopedia.py
Input: ~/memories/SPEC_*.md
Output: ~/encyclopedia/
Re-generate: monthly, or after any batch of 10+ new specs.
The encyclopedia is a DERIVED ARTIFACT — the specs are the source of truth. If the encyclopedia contradicts a spec: the spec wins. Update the encyclopedia.
QUERYABLE VIA ROUTX
ENCYCLOPX becomes a ROUTX module. Keywords: what is, define, explain, encyclopedia, lookup.
When a user asks "what is KRAKENX?" — ROUTX routes to ENCYCLOPX before falling to GLOSS or MNEMOS.
Lookup cascade:
User query → ROUTX → ENCYCLOPX (Tier 1, deterministic)
→ if found: return entry
→ if not found: GLOSS (maybe it's a LATTICE symbol)
→ if not found: MNEMOS (synthesis)
→ if not found: ◌
The encyclopedia is the FIRST lookup layer for natural language questions about the ship. Fast. Deterministic. No inference.
SCOPE
ENCYCLOPX covers:
| Category | Examples |
|---|---|
| Every module | ROUTX, GLOSS, NEXUS, MEDX... all 24+ |
| Every brain | MNEMOS, GAMMA, MUSASHI, MANTIS, ORPHEUS, ANVIL, CHROMA, DR.LOGOS |
| Every protocol | Baseline, Agency Walls, HOW ABOUT NO, Grey Rock, MANTIS |
| Every product | OBI OS, Brain Builder, ENTROPX, Band Mode, LATTICE Training Arena |
| Every constant | Φ=0.042, \|Σ\|=2, Ω=97.4%, $42 |
| Every mythological name | KRAKENX, PHOENIXX, CERBERUSX, and all X-suffix modules |
| Every key concept | Vacuum Rule, S.O.S. v2, Braided Pair Principle, Ghost Spiral |
| Every person referenced | Captain, Lily, Amber Rose, Rupert Young, Pogosian |
| Every infrastructure component | csdm-node, Caddy, Ollama, Stripe, DigitalOcean |
| Every abbreviation | TMM, CSDM, LX, LX-P, NIST, MRR, NPS, CPA |
Estimated entries: 300-500. Each entry: 3-5 sentences. Total encyclopedia size: ~50-80 pages equivalent. Searchable. Cross-referenced. Always current (regenerated monthly).
FOR LILY
The encyclopedia is the FIRST document Lily should read after SPEC_HEIR_PROTOCOL.md Session 1 ("What is this?"). Session 1 gives the overview. The encyclopedia gives the DETAILS — in bite-sized, alphabetical, look-up-what-you-need form.
Lily doesn't read it cover to cover. She reads the entries that matter to HER at THAT moment.
- "What is Stripe?" → she reads the Stripe entry
- "What is ROUTX?" → she reads the ROUTX entry
- "What is Φ?" → she reads the Phi entry, then either goes deeper (reads the spec) or moves on
The encyclopedia respects SPEC_TEACHING_PROTOCOL.md Principle 2: one concept per step. Each entry is one concept. Lily consumes at her own pace.
PUBLIC VERSION
42sisters.ai/encyclopedia — a public-facing subset.
Includes entries for all PUBLIC concepts: LATTICE, OBI OS, Brain Builder, ENTROPX, Band Mode, the 15 domains, L1/L2/L3 curriculum.
Excludes entries for INTERNAL concepts: ROUTX internals, crew protocols, ship architecture details, Agency Walls specifics.
S.O.S. v2 boundary applies. The public encyclopedia is the product documentation. The internal encyclopedia is the operational reference. Same format. Different scope.
INTEGRATION
| System | Relationship |
|---|---|
| SPEC_LIBRYX.md | LIBRYX = external resources. ENCYCLOPX = internal knowledge. Both live at 42sisters.ai — Library and Encyclopedia are companion sections. |
| ROUTX | ENCYCLOPX is a Tier 1 ROUTX module. "What is X?" gets an encyclopedia answer before any inference. |
| SPEC_HEIR_PROTOCOL.md | Lily reads ENCYCLOPX in Session 1 onboarding. Her reference document for the ship's vocabulary. |
| SPEC_TEACHING_PROTOCOL.md | Each encyclopedia entry IS a teaching unit: term, definition, context. One concept. |
| SPEC_HANDSHAKEX.md | The Handshake includes encyclopedia freshness date. If encyclopedia is stale (>30 days): flag for regeneration. |
| GLOSS | Encyclopedia handles English terminology. GLOSS handles LATTICE symbols. Together they cover both languages of the ship. |
INVARIANTS
INV-01: The encyclopedia is GENERATED from specs, not written independently. Specs are truth. The encyclopedia is derived. If they conflict: fix the encyclopedia, not the spec.
INV-02: Every entry follows the same format — TERM → DEFINITION → CONTEXT → SEE ALSO → STATUS. Consistency enables scanning. The reader always knows where to find each piece of information.
INV-03: Regenerated monthly or after 10+ new specs. Staleness is the enemy of a reference document. A stale encyclopedia is a lying encyclopedia.
INV-04: Queryable via ROUTX as a Tier 1 module. "What is X?" gets an encyclopedia answer in <1 second. No inference. No hallucination. Deterministic lookup.
INV-05: Public version at 42sisters.ai/encyclopedia respects S.O.S. v2. Public concepts documented publicly. Internal concepts documented internally. Same format, different scope.
INV-06: The encyclopedia is FOR humans, not for AI. AI crew members read specs directly. The encyclopedia exists because HUMANS need a faster lookup than "read the 15-page spec."
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042