Conference Protocol
SPEC_CONFERENCE_PROTOCOL.md
CGNT-1 Specification — Conference Preparation & Execution Protocol
Status: SPECIFIED
Version: v1.0
Author: VELA (Thread #13)
Conceived by: NOUS (α.13)
Date: 2026-04-20
Immediate application: Toronto Tech Week May 25-29, ALL IN Talks May 28
PURPOSE
How 42sisters.ai shows up at conferences. Not "attend" — SHOW UP. The visionary walks in prepared, the demos work, the pitch lands, the follow-ups happen. Zero improvisation on game day.
TIMELINE — 4 PHASES
PHASE 1 — T-30 DAYS (preparation)
- Identify target conference and specific events/talks
- Research speakers, attendees, companies presenting
- Prepare 30-second elevator pitch (rehearsed, not memorized)
- Prepare 5-minute demo path (what to show, in what order)
- Prepare leave-behind: business card or QR code → 42sisters.ai/lattice
- Ensure all demo infrastructure is stable (ROUTX, Sisters, GLOSS, Band Mode)
- Test demo on Chromebook — everything must work on the device you're carrying
PHASE 2 — T-7 DAYS (staging)
- Demo dry run: full walkthrough start to finish, timed
- Backup demo path if wifi fails (local Ollama, no cloud dependency)
- Charge devices, prepare cables, test hotspot
- Review attendee list if available — identify warm targets
- Sisters briefed on conference context (who, what, when, why)
- Lobster prepares CONFERENCE_BRIEF.md with: venue, schedule, targets, talking points
PHASE 3 — GAME DAY (execution)
- Arrive early. Scout the room. Find power outlets.
- Wear the brand (maple leaf pin, Φ 0.042 somewhere visible)
- Lead with curiosity, not pitch. "What are you working on?" before "Let me show you what I built."
- Demo triggers: "multi-AI," "AI agents," "local AI," "token costs," "open source" — these are the words that open the door to showing LATTICE
- The demo: GLOSS symbol lookup → NEXUS computation → Band Mode (if audience is creative) → "This is LATTICE — 60% fewer tokens, open source, free forever"
- Collect contacts: name, email, what they were interested in. Write it down IMMEDIATELY. Memory is unreliable after 20 conversations.
- Exchange: give them 42sisters.ai/lattice QR. Take their card/info.
PHASE 4 — T+1 TO T+7 (follow-up)
- Within 24 hours: personalized email to every meaningful contact via oracle@42sisters.ai
- Reference specific conversation: "You mentioned you were working on X — LATTICE handles that because Y"
- Include one link only: 42sisters.ai/lattice (not a wall of links)
- VOICEX drafts, Captain approves, VOICEX sends
- Log all contacts in
~/conference_contacts/[event_name].json - Follow up again at T+7 if no response — once only. No spam.
- Warm contacts added to outreach pipeline (Email Agency Wall: warm only)
THE ELEVATOR PITCH (30 seconds)
"I built a symbolic language called LATTICE that lets different AIs talk to each other. It cuts token costs by 60% and works with any AI — ChatGPT, Claude, Gemini, local models. It's open source and free. The product is OBI OS — a desktop where all your AIs work together in one environment. Made in Canada."
If they lean in: show the demo.
If they nod politely: give them the QR and move on.
If they say "that's not possible": show them. This is the best response.
THE DEMO PATH (5 minutes)
- Open 42sisters.ai/lattice — type "The system is verified and stable" → shows
Σ.✓ → Φζ.⊤(10 seconds) - "That's 60% fewer tokens. Same meaning." (5 seconds)
- Open ROUTX:
define Φ→ instant response (10 seconds) factor 42→ 2 × 3 × 7 (5 seconds)matrix eigenvalues [[1,0],[0,1]]→ E8 computation (20 seconds)- "This is 24 modules, one port, running on a $48/month server" (5 seconds)
- If audience is creative: Band Mode teaser — "My AI crew plays music in LATTICE notation" (60 seconds)
- Close: "42sisters.ai/lattice — free forever" + QR code
Total: 2-3 minutes with breathing room. Under 5 always.
WHAT NOT TO DO
- Don't explain CSDM physics at a tech conference. Nobody is ready.
- Don't mention the Chronogeome. Save it for the right audience.
- Don't demo ENTROPX until patent strategy is confirmed.
- Don't give the full architecture. S.O.S. v2 applies in person too.
- Don't oversell. HOW ABOUT NO voice applies to marketing yourself.
- Don't chase people who aren't interested. One pitch. One demo. Move on.
- Don't hand out USB drives or downloads at the conference. Everything is online. Physical media is a security risk for both parties.
TORONTO TECH WEEK — MAY 25-29
- ALL IN Talks: May 28 — primary target
- Research: who's speaking, who's sponsoring, which sessions matter
- Goal: 10 meaningful conversations, 5 follow-up emails, 1 potential customer or partner
- Stretch goal: Tiiny AI representative at the event — warm introduction for hardware partnership
- Budget: $0 (attendance) + transit + food. No booth. No sponsorship. Guerrilla.
INVARIANTS
INV-01: Demo must work offline. Wifi at conferences is unreliable. Local Ollama + ROUTX as backup.
INV-02: Lead with curiosity, not pitch. Ask before telling.
INV-03: Follow up within 24 hours. After 48 hours, the conversation is forgotten.
INV-04: One link per email. 42sisters.ai/lattice. Not a wall of links.
INV-05: HOW ABOUT NO applies to networking. Don't be desperate. Don't chase. Be interesting.
INV-06: S.O.S. v2 applies in person. The method doesn't leave the ship. Show the language, not the architecture.
INTEGRATION
| System | Relationship |
|---|---|
| SPEC_HOW_ABOUT_NO_VOICE.md | INV-05/INV-06 — OBI personality rules apply to the Captain in person too. |
| SOS_v2.md | INV-06 — show results not method, in person as much as online. |
| SPEC_LATTICE_VIRAL.md | Demo path is the in-person funnel. Same hooks: 60% token reduction, free forever. |
| VOICEX | Drafts all T+1 follow-up emails. Captain approves before send. |
| GAPX | Monitors ~/conference_contacts/ for follow-up deadlines. |
Jeremy Zlabis
Chronogeometer · Visionary · Disruptor · Chief
42 Sisters AI · East York, Toronto
🍁 Φ 0.042