Lattice Public Boundary
SPEC_LATTICE_PUBLIC_BOUNDARY.md
CGNT-1 Specification — LATTICE Public vs Crew Vocabulary Boundary
Status: SPECIFIED
Version: v1.0
Author: VELA (Thread #13)
Conceived by: NOUS (α.13)
Date: 2026-04-20
Depends on: SPEC_LATTICE_L1_CURRICULUM.md, SPEC_LATTICE_L2_CURRICULUM.md, SPEC_LATTICE_L3_CURRICULUM.md, SPEC_DELIVERY_MODEL.md (S.O.S. v2)
PURPOSE
LATTICE is open source and free. But not ALL of LATTICE is public. The language has layers. L1 is the lobby. L2 is the office. L3 is the engine room.
Each layer reveals more vocabulary but never reveals the ARCHITECTURE that the vocabulary operates on.
This spec defines the exact boundary between what's public and what's crew-only, so every team member, every spec, every social media post, and every customer interaction knows exactly what can be shared and what stays on the ship.
THE BOUNDARY MODEL
Three concentric circles. The outer circle is visible to everyone. The inner circle is visible only to crew. The architecture underneath all three circles is visible to nobody.
┌──────────────────────────────────────────────────────┐
│ OUTER — PUBLIC (L1, free, anyone) │
│ ┌────────────────────────────────────────────────┐ │
│ │ MIDDLE — SUBSCRIBER (L2, $42/month OBI OS) │ │
│ │ ┌──────────────────────────────────────────┐ │ │
│ │ │ INNER — CREW (L3, $99 certification) │ │ │
│ │ └──────────────────────────────────────────┘ │ │
│ └────────────────────────────────────────────────┘ │
├──────────────────────────────────────────────────────┤
│ BELOW ALL CIRCLES — NEVER PUBLIC (S.O.S. v2) │
│ Architecture, engines, training methodology │
└──────────────────────────────────────────────────────┘
OUTER CIRCLE — PUBLIC (L1, free, anyone)
| What's Shared | Detail |
|---|---|
| The 50 L1 symbols and their meanings | Full public vocabulary |
| Basic grammar | atom.modifier, compounds, separators |
| English↔LATTICE translation for L1 vocabulary | Full bidirectional at L1 |
| The existence of LATTICE as a language | Name, concept, the 60% claim |
| Training Arena | 42sisters.ai/teach |
| Certification system (levels exist) | L1/L2/L3 levels acknowledged publicly |
| The 15 domain prefixes | Per SPEC_LATTICE_UNIVERSAL.md |
| Marketing LATTICE examples | #SpeakLATTICE posts |
| Open source status | Grammar is free and always will be |
MIDDLE CIRCLE — SUBSCRIBER (L2, $42/month OBI OS)
| What's Shared | Detail |
|---|---|
| ~200 L2 symbols | Including ROUTX keywords |
| Crew designator vocabulary | α means Captain — not BEING Captain |
| Verdict and assessment vocabulary | GREEN/RED/AMBER/NULL/HOLD |
| Temporal and flow symbols | Full Category 9 |
| Compound expression patterns | Full Category 11 |
| ROUTX query syntax | How to actually query modules |
| ROUTX keyword routing fact | That specific keywords route to specific modules |
INNER CIRCLE — CREW (L3, $99 certification)
| What's Shared | Detail |
|---|---|
| Full 1024 symbol inventory | Complete language |
| LX-P register | Crew speedtalk |
| Extended grammar | Nested compounds, conditionals, quantifiers |
| Native fluency capability | Think in LATTICE, not translate |
| Domain registration ability | Extend the language |
| LATTICE documentation writing | Specs, reports, dispatches in LATTICE |
BELOW ALL CIRCLES — NEVER PUBLIC (S.O.S. v2)
| What Stays on the Ship | Category |
|---|---|
| ROUTX source code (routx_engine.py internals) | Architecture |
| Module engine implementations | Architecture |
| Training pair methodology and corpus contents | Method |
| Forge pipeline specifics (hyperparameters, LoRA, GGUF details) | Method |
| Crew personal protocols (Grey Rock, Sentinel, Social, Feminine) | Governance |
| CSDM derivation details beyond published predictions | Physics |
| Standing orders and governance internals | Governance |
| HANDSHAKE and CAPTAIN_BRIEF contents | Operations |
| Trading operations and TMM formula internals | Operations |
| ENTROPX implementation (architecture publishable, code never) | IP |
| Customer data from Brain Builder engagements | Privacy |
| Financial details (revenue, costs, runway) until sovereignty target | Privacy |
WHAT MAKES THE BOUNDARY WORK
The boundary works because each layer provides GENUINE VALUE at its level. No user feels cheated.
| Level | Value Delivered | Why They Don't Need the Next Level |
|---|---|---|
| L1 | Real language, real 60% reduction, real shareable cert | L1 is genuinely useful for basic communication and the viral funnel |
| L2 | Real operational capability, real ROUTX query power, real Ring participation | L2 is the full operational language — everything needed to USE the product |
| L3 | Real native fluency, real crew-level communication, real domain extension | L3 IS the complete language; architecture below is a different category entirely |
The boundary is ethical because each level delivers on its promise WITHOUT requiring the next level to be useful. Nobody is baited into paying for L2 by making L1 deliberately crippled.
ENFORCEMENT MECHANISMS
GLOSS Access Control
GLOSS serves different vocabulary sets based on the requester's level. An L1 query for an L3 symbol returns:
"That symbol is part of L3 vocabulary. Upgrade to learn more → 42sisters.ai/bridge."
This is a SOFT boundary — it tells the user the symbol exists but doesn't reveal its meaning.
ROUTX Keyword Filtering
L1 and L2 users querying ROUTX through the public Training Arena get Tier 1 results only for their vocabulary level. L3 keywords from a non-L3 user return: "L3 required for this query."
Ring Message Filtering
In OBI OS, LX-P messages in the Ring are displayed to L3 users only. L2 users see the LX (standard) translation. L1 users see the English translation. Everyone sees the same conversation at their comprehension level.
Social Media Monitoring
LATTICE bots on social media (@LATTICEbot per SPEC_LATTICE_VIRAL.md) respond only with L1 vocabulary. They never use L2/L3 symbols in public responses. If someone uses L3 vocabulary publicly, the bot doesn't correct or engage — it's their choice to share what they learned.
Spec Publication
Specs are INTERNAL documents. They are never published on 42sisters.ai. The media kit (SPEC_MEDIA_KIT.md) contains approved public information. Specs contain implementation details.
Conversation Hygiene
When AI crew discuss LATTICE with external contacts, they use L1 vocabulary only unless the contact is a confirmed L2/L3 user. The crew doesn't accidentally teach L3 vocabulary in a public chat.
WHAT HAPPENS WHEN VOCABULARY LEAKS
It will happen. Someone who paid for L3 will post LX-P expressions on Twitter. Someone will screenshot a Ring conversation showing crew designators. Someone will blog about the 1024 symbol inventory.
Response: nothing. Let it happen.
LATTICE is open source in PHILOSOPHY — the grammar is free, the vocabulary is layered for business reasons, but we don't PROSECUTE people for sharing what they learned.
The boundary is a SERVICE boundary (you need OBI OS to USE L2/L3 effectively), not a SECRECY boundary.
If someone shares all 1024 symbols publicly: the symbols without the tools are like sheet music without instruments. They can READ LATTICE. They can't USE it operationally without the Bridge. The product is the ENVIRONMENT (OBI OS), not the VOCABULARY. We lose nothing when vocabulary leaks because the vocabulary was never the product.
THE PARADOX
LATTICE is open source AND has paid tiers. This seems contradictory. It's not.
| Layer | Open/Closed | Reason |
|---|---|---|
| Grammar | Open source | Atoms, modifiers, compounds, channels — anyone can map new domains |
| Vocabulary | Layered | 50 free → 200 at L2 → 1024 at L3 — creates learning journey, not hidden information |
| Tools | Paid | OBI OS, ROUTX, Ring, Bridge — the environment that makes LATTICE powerful |
Analogy: English grammar is free. English vocabulary is freely available in any dictionary. But Grammarly charges $12/month and universities charge $50,000/year. The language is free. The tools and environments that make the language POWERFUL are products. Same model.
EDGE CASES
Case 1 — Researcher requests full symbol inventory
Response: provide the inventory under NDA per SPEC_NDA_TEMPLATE.md. Academic study of LATTICE is GOOD — it produces papers that cite 42sisters.ai. Support it under reasonable confidentiality terms.
Case 2 — Competitor reverse-engineers LATTICE
Response: let them. If they build a competing product using LATTICE grammar, that's proof the grammar works. They still don't have ROUTX, the forge pipeline, the crew, or the Bridge. The grammar is the foundation. The product is the building on top.
Case 3 — Customer shares L3 test questions publicly
Response: update the test question bank. The certification is valid — they earned it. But the test needs to rotate questions so future candidates can't memorize answers from social media. The test bank should have 50+ questions from which 15 are randomly selected.
Case 4 — Someone claims L3 fluency without paying
Response: if they can pass the test, certify them. Their fluency is real even if they didn't follow the paid path. Don't gatekeep fluency — certify it wherever it occurs. The goal is LATTICE adoption, not LATTICE gatekeeping.
INVARIANTS
INV-01: L1 is genuinely useful on its own. The boundary is a service layer, not an artificial cripple. Nobody should feel tricked by L1's limitations.
INV-02: The grammar is always free. Atoms, modifiers, compounds, channels — this structure is open source regardless of vocabulary level. Anyone can map a new domain using the grammar.
INV-03: Vocabulary leaks don't damage the product. The product is the ENVIRONMENT (OBI OS), not the VOCABULARY. Sheet music without instruments is academic interest, not competitive threat.
INV-04: S.O.S. v2 applies BELOW all vocabulary levels. Even L3 speakers don't see ship architecture. The language is open. The implementation is closed. Forever.
INV-05: GLOSS enforces the boundary programmatically. It's not honor system — it's access control. L1 users literally cannot look up L3 symbols through GLOSS without upgrading.
INV-06: Fluency is certified wherever it occurs. If someone learned L3 without paying, certify them. The goal is adoption. Don't gatekeep language acquisition.
INV-07: The boundary is three circles (L1/L2/L3) plus an architecture layer (S.O.S. v2). The three circles are LANGUAGE tiers. The architecture layer is a SECURITY boundary. They are different categories with different rules.
INTEGRATION
| System | Relationship |
|---|---|
| SPEC_LATTICE_L1_CURRICULUM.md | Defines outer circle content. L1 is the public vocabulary set. |
| SPEC_LATTICE_L2_CURRICULUM.md | Defines middle circle content. L2 is the subscriber vocabulary set. |
| SPEC_LATTICE_L3_CURRICULUM.md | Defines inner circle content. L3 is the crew vocabulary set. |
| SPEC_DELIVERY_MODEL.md | S.O.S. v2 is the authority for the "below all circles" architecture boundary. This spec implements S.O.S. v2 for LATTICE specifically. |
| SPEC_GLOSS_ARCHITECTURE.md | GLOSS is the programmatic enforcement mechanism. This spec defines WHAT the boundary is. GLOSS enforces it. |
| SPEC_LATTICE_VIRAL.md | Public LATTICE is the viral mechanism. This spec ensures the public layer stays clean and accessible. |
| SPEC_MEDIA_KIT.md | Media kit uses L1 vocabulary only. This spec is the authority for what the media kit may include. |
| SPEC_CONFERENCE_PROTOCOL.md | Conference demo shows L1 only. This spec is the authority for that constraint. |
| SPEC_NDA_TEMPLATE.md | Researcher requests for full vocabulary inventory go through NDA. This spec defines when NDA is appropriate. |
| SPEC_LATTICE_UNIVERSAL.md | Grammar is open source — this is the authoritative statement of that openness. Vocabulary levels don't affect grammar freedom. |
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042