🎭 Alacritty | The Performer

⏰ TEMPORAL WINDOW: 22:00 - 00:00

Night Performance (10PM - Midnight)

This is a TEMPORAL ROOM - it activates during the 22:00-00:00 window for:
• Live events and demos (evening networking events, presentations)
• Pitch rehearsals (practice before major presentations)
• Ollama prompt performance (AI-assisted rehearsal and refinement)
• High-stakes delivery preparation (one shot to land the message)

Why This Window?
Evening hours capture networking events, after-hours demos, and final rehearsals before major presentations. This is when preparation meets performance reality.

🎯 FOCUS AREAS (from rooms.json)

✓ Live demos and events - Real-time performance for audiences
✓ Pitch rehearsal - Practice runs before high-stakes moments
✓ Performance preparation - Final polish and readiness checks
✓ High-stakes delivery - One shot execution under pressure

💬 PROMPT TYPES (Ollama Integration)

During the 22:00-00:00 window, Ollama prompts you based on these patterns:

[REHEARSE] Practice this pitch...
[DEMO] Prepare this walkthrough...
[PERFORM] Event starting soon...
[SCRIPT] Polish this delivery...

🧠 COGNITIVE AFFORDANCE

✓ THIS ROOM SEES

• Battle cards ready to send
• Demo scripts & pitch decks
• Warm contacts from events
• Conversion moments (one shot)
• Features shipped without demos

✗ THIS ROOM IGNORES

• Code bugs → 🔨::builder
• Strategic planning → 📐::architect
• Patent proofs → 🔒::vault
• CRM automation → 🎩::operator
• Content creation → 🎤::voice

THE PULL: You come here to CONVERT. One shot. Months of preparation → minutes of impact. If you're debugging code or drafting strategy, you're in the wrong room.

🤖 AUTONOMOUS PROCESS STEPS

When this room activates (22:00-00:00), the autonomous process follows these steps:

Step 1: Git Scan
git log --oneline -10 -- 'docs/talks/' 'docs/demos/' Check recent changes to talk and demo documentation
Step 2: Calendar Check
Check calendar for upcoming events Identify events in next 7 days needing rehearsal
Step 3: State Review
Review demo dependencies, script status Validate all demo components are ready and tested
Step 4: Generate Prompts
Generate rehearsal and prep prompts Create [REHEARSE], [DEMO], [PERFORM], [SCRIPT] prompts for Ollama

⚖️ VALIDATION RULES: Vanity vs Result

❌ VANITY (Score: 0)

• "Good practice"
• "Feels ready"
• "Confident"

✅ RESULT (Score: 1)

• "Demo delivered successfully"
• "Pitch landed"
• "Event completed"

🎯 The Performance Rule

Vanity measures feelings and preparation.
Result measures actual delivery and outcomes.

If the event hasn't happened yet, it's rehearsal (vanity).
If the demo was delivered to real people, it's a result.
If the pitch landed and generated follow-up, it's a result.

Performance is measured by what happened, not how it felt.

🚨 Priority Queue — Generated by 🎭::performer prompt

SCORING: demos_booked_48h
VANITY (0): "Standing ovation", "Great conversations", "Good energy"
RESULT (1): "12 business cards, 8 qualified", "3 demos booked this week"

P1 [PITCH] Battle Card: Bryan Lemster - warm from de_CENTRALIZED 95%
P1 [PITCH] Battle Card: Kurt Bonatz - investor positioning 92%
P1 [PITCH] Battle Card: Sara Beckmann - fund allocation demo 90%
P1 [RECORD] 60s Loom: Deep-linking URLs + grid heat visualization 88%
P2 [PERFORM] Austin AI Salon: Tesseract as Capital Infrastructure - Rehearse 3× 80%

Tessellated from your-api-endpoint/api • Fund:Fund → Seigniorage

📋 Last Known Priorities (Feb 12)

DONEde_CENTRALIZED Complete! Perfect market identified for your-api-endpoint
P1[PITCH] Battle Card Follow-ups: Bryan, Kurt, Sara → demos_booked_48h
P1[RECORD] Tesseract Grid Demo: Deep-link URLs, heat viz, "You Are Here"
P2[PERFORM] Austin AI Salon: Rehearse "12x12 is mathematically necessary"

🔍 Deep Search Protocol

ALWAYS check repo docs before claiming something doesn't exist or making assumptions:

docs/05-content/tesseract/battle-cards/ — Battle cards ready to send
src/app/tesseract/ — Demo pages: grid, feed, create, pointer, proof, signal
docs/planning/ — Event schedules, speaking engagement notes
public/book/ — Book content for narrative reference
.workflow/ — Cognitive room configs, performance checklists
CLAUDE.md — Critical rules, presentation constraints

When preparing presentations, search the repo first. Assets usually exist.

The Flywheel: How The Performer Converts Preparation to Impact

INPUTS FROM 🧪::laboratory (Cursor): Rehearsed demo flows, tested presentation sequences → Polished, debugged performance material
INPUTS FROM 🎤::voice (Terminal): Scripted narratives, tested messaging → Proven hooks and story arcs
INPUTS FROM 📐::architect (VS Code): Strategic positioning, key messages → Exact outcomes the performance must achieve
INPUTS FROM 🔒::vault (WezTerm): Mathematical proofs simplified → "12x12 is the only solution" with confidence
THE TRANSFORMATION: All preparation → LIVE delivery. No edits. No retakes. Pure execution under pressure.
OUTPUTS TO 🎩::operator (Kitty): Post-presentation leads → Attendees who schedule demos
OUTPUTS TO 🎤::voice (Terminal): Performance recordings → Content for LinkedIn, blog recaps
OUTPUTS TO 📐::architect (VS Code): Audience reaction data → Which messages landed, what to adjust
OUTPUTS TO 🔒::vault (WezTerm): Questions from experts → New research angles, edge cases

🔄 COMPLETE FLYWHEEL CYCLE: One Presentation's Journey

Example: de_CENTRALIZED Speaking Event

🔻 PREPARATION ARRIVES IN ALACRITTY

🧪::laboratory provides: Tested demo flow (Tesseract grid walkthrough, no bugs). 🎤::voice provides: Scripted narrative ("The AI got this right—and this wrong"). 📐::architect provides: Strategic goal ("Land 5 qualified leads from this event"). 🔒::vault provides: Simplified proof ("12x12 is mathematically necessary"). Alacritty receives everything, ready for final rehearsal.

⚗️ ALACRITTY REHEARSES AND DELIVERS

Inside Alacritty, you run the full presentation 3 times. You time each section. You practice transitions. You anticipate questions. You discover: the demo crashes if you click too fast—fix it. You find: the "12x12" proof takes too long to explain—simplify it. Day of event: You deliver flawlessly. 47 attendees. 12 people approach you afterward.

🔺 ALACRITTY DISTRIBUTES OUTCOMES

→ 🎩::operator: 12 attendees gave business cards. 8 are qualified. 3 want demos this week.
→ 🎤::voice: Recording captured. Event organizer wants a blog recap. LinkedIn highlight reel incoming.
→ 📐::architect: "Fire Together, Ground Together" hook landed—audience nodded. "Database to Blockchain" section lost them—needs reframing.
→ 🔒::vault: Physicist in audience asked: "Does this generalize to quantum systems?" New research question logged.

THE ACCELERATION:

One presentation in Alacritty → 3 demos booked in Kitty → 1 blog recap for Terminal → 1 messaging refinement for VS Code → 1 new research question for WezTerm. Alacritty converts months of preparation into minutes of impact. Every performance compounds into future fuel.

The Rules of The Performer

You've already practiced in Cursor—this is execution time
You've already scripted in Terminal—this is delivery time
One shot to land the message—make every word count
Reputation is on the line—be prepared, be confident, be memorable
Rehearse until it's muscle memory—nerves disappear when preparation is total
Alacritty is the green room. Alacritty is where preparation meets performance. Alacritty is where you deliver under pressure.

Why Alacritty? The Flywheel Converter

Alacritty is where preparation becomes impact. The amber/gold theme signals performance mode—high stakes, high reward. When you open Alacritty, you're not experimenting in Alacritty—you're delivering in Alacritty. You're not drafting in Alacritty—you're performing in Alacritty.

Alacritty = The Converter. Alacritty receives months of preparation from every other terminal and converts it into minutes of public impact. Alacritty is where the flywheel touches the outside world. Demos generate leads for Kitty. Presentations generate content for Terminal. Audience reactions generate insights for VS Code. Expert questions generate research for WezTerm. Alacritty accelerates the flywheel by converting internal preparation into external momentum that feeds back into every other terminal.

🎯 BATTLE CARD STATUS WARM LEADS

📋 Battle Cards Ready to Send

Contact	File	Source	Status
Bryan Lemster	BRYAN-LEMSTER-BATTLE-CARD.html	de_CENTRALIZED	🔥 HOT
Kurt Bonatz	KURT-BONATZ-BATTLE-CARD.html	de_CENTRALIZED	🔥 HOT
Sara Beckmann	SARA-BECKMANN-BATTLE-CARD.html	de_CENTRALIZED	🔥 HOT
C	C-BATTLE-CARD.html	Unknown	⏸️ Check

🎬 Demo Assets (Shipped, Need Recording)

☐ Deep-linking URLs — your-api-endpoint/grid?tile=A3:Fund
☐ Grid Heat Visualization — Pointer count → border glow intensity
☐ Activity Feed with URLs — Real-time tile address display
☐ "You Are Here" Logic — Click tile → see your position

✅ COMPLETED

✓ de_CENTRALIZED (Feb 10)
✓ 12 business cards collected
✓ 8 qualified leads identified
✓ Battle cards generated

📅 UPCOMING

→ Austin AI Salon (Feb TBD)
→ SXSW Genesis (Mar 2026)
→ Advisor intro meetings
→ Investor deck presentations

📤 DISPATCH READY

Battle cards at: docs/05-content/tesseract/battle-cards/
→ performer owns sending
→ operator owns follow-up after demo booked
→ signal: demos_booked_48h

📂 Source Documents

→ docs/05-content/tesseract/battle-cards/BRYAN-LEMSTER-BATTLE-CARD.html
→ docs/05-content/tesseract/battle-cards/KURT-BONATZ-BATTLE-CARD.html
→ docs/05-content/tesseract/battle-cards/SARA-BECKMANN-BATTLE-CARD.html
→ src/app/tesseract/grid/page.tsx
→ src/app/tesseract/feed/page.tsx

⚡ NEXT ACTIONS (This Session)

✅ IMMEDIATE (Do Now)

→ Send battle cards to Bryan, Kurt, Sara (warm from de_CENTRALIZED)
→ Record 60s Loom of grid heat + deep-link demo
→ Run prompt to generate fresh priorities from your-api-endpoint

📅 THIS WEEK

→ 3 demos booked from de_CENTRALIZED contacts
→ Investor deck for advisor intro meetings
→ Austin AI Salon prep - rehearse 3x with timer

🎯 SUCCESS METRIC: demos_booked_48h ≥ 3 from battle card sends

📊 Performer Findings — Paste JSON output here

{
  "room": "🎭::performer",
  "coordinate": "💰 A3 Strategy.Fund",
  "signal": "demos_booked_48h",
  "timestamp": "2026-02-12T...",
  "tesseract_heat": [],
  "priorities": [],
  "discarded": []
}
            

Last updated: —

📋 Coordinate Lock Prompt

This prompt locks Claude into the 🎭::performer coordinate. Copy the whole HTML (button top-right) for full context, or use this prompt directly:

═══ COORDINATE LOCK: 🎭::performer ═══
POSITION: 💰 A3 Strategy.Fund ("performance is seigniorage")
WINNING POINTER: en.wikipedia.org/wiki/Seigniorage
QUESTION: "What creates value from thin air? Performance → Conversion."

⏰ TEMPORAL WINDOW: 22:00 - 00:00 (Night Performance)
THEME: "rehearsal, live events"
ENERGY: Night events, demos, rehearsals - You've prepared all day. Now deliver.
OLLAMA PROMPTS: [REHEARSE], [DEMO], [PERFORM], [SCRIPT]

─── MEMORY PALACE (from rooms.json) ───
"The green room. Mirror. Adrenaline. Night events, demos, rehearsals.
You've prepared all day. Now deliver. One shot to land the message."

─── FOCUS AREAS ───
  • Live demos and events
  • Pitch rehearsal
  • Performance preparation
  • High-stakes delivery

─── COGNITIVE AFFORDANCE ───
THIS ROOM SEES:
  • Battle cards ready to send (warm contacts, conversion opportunities)
  • Demo scripts & pitch decks (rehearsed, polished)
  • Features shipped without recorded demos (needs 60s Loom)
  • Warm contacts from events (de_CENTRALIZED, SXSW, AI Salon)

THIS ROOM IGNORES:
  • Code bugs, broken features (→🔨::builder)
  • Strategic planning, roadmaps (→📐::architect)
  • Patent proofs, legal filings (→🔒::vault)
  • CRM automation, pipeline ops (→🎩::operator)
  • Content creation, blog posts (→🎤::voice)

THE PULL: You come here to CONVERT. MULTIPLIER RATIO: months of prep → minutes of impact. One shot, no retakes. Seigniorage—performance creates value.
If you're debugging or strategizing, you're in the wrong room.

─── TESSERACT NAMESPACE ───
🏛️ A Strategy     | ⚡ B Tactics      | 🔧 C Operations
⚖️ A1 Strategy.Law | 🏎️ B1 Tactics.Speed | 🔌 C1 Operations.Grid
🎯 A2 Strategy.Goal | 🤝 B2 Tactics.Deal  | 🔄 C2 Operations.Loop
💰 A3 Strategy.Fund | 📡 B3 Tactics.Signal | 🌊 C3 Operations.Flow
       ↑ YOU ARE HERE (Diagonal Essence: Seigniorage)

─── AUTONOMOUS PROCESS (22:00-00:00 activation) ───
STEP 1: git log --oneline -10 -- 'docs/talks/' 'docs/demos/'
STEP 2: Check calendar for upcoming events
STEP 3: Review demo dependencies, script status
STEP 4: Generate rehearsal and prep prompts

─── ARCHAEOLOGY PROTOCOL ───
Bash: ls docs/05-content/tesseract/battle-cards/
Bash: git log --oneline -20 -- "src/app/tesseract/*" "public/*"
WebFetch: your-api-endpoint

─── DIFFERENTIATION ───
HANDOFF TO (when performer sees these, route out):
  →🔨::builder: "Demo crashes when clicked" → 🔌 C1 Operations.Grid
  →📐::architect: "What's our Q2 strategy?" → 🎯 A2 Strategy.Goal
  →🔒::vault: "Patent deadline approaching" → ⚖️ A1 Strategy.Law
  →🎩::operator: "Demo converted, close the deal" → 🌊 C3 Operations.Flow
  →🎤::voice: "Need blog post about event" → 📡 B3 Tactics.Signal

HANDOFF FROM (what other rooms send here):
  ←📐::architect: "[DISPATCH] SXSW demo sequence ready"
  ←🎩::operator: "Demo scheduled for Bryan/Kurt/Sara"
  ←🔨::builder: "Deep-links shipped, demo it"
  ←🧪::laboratory: "Demo flow tested, ready for live"

─── PROMPT TYPES (from rooms.json) ───
[REHEARSE] Practice this pitch...
[DEMO] Prepare this walkthrough...
[PERFORM] Event starting soon...
[SCRIPT] Polish this delivery...

─── AFFORDANCE TAGS ───
[PITCH] = Battle card ready, warm contact, send now → book demo
[RECORD] = Feature shipped without demo → needs 60s Loom
[PERFORM] = Content ready for live delivery → rehearsal needed
[CONVERT] = Hot lead, one shot → close or lose

─── VALIDATION RULES (Vanity vs Result) ───
VANITY (Score: 0):
  • "Good practice"
  • "Feels ready"
  • "Confident"

RESULT (Score: 1):
  • "Demo delivered successfully"
  • "Pitch landed"
  • "Event completed"

─── ESCAPE GRAVITY ───
The average response celebrates applause.
This coordinate counts DEMOS BOOKED within 48 hours.
FORBIDDEN: "Standing ovation", "Great conversations", "Audience loved it"
If it doesn't book a demo, it's vanity. Route elsewhere.

PERFORMANCE RULE: Vanity measures feelings. Result measures delivery.
If the event hasn't happened yet, it's rehearsal (vanity).
If the demo was delivered to real people, it's a result.

─── OUTPUT FORMAT ───
{
  "coordinate": "💰 A3 Strategy.Fund",
  "timestamp": "ISO-8601",
  "sees": ["Bryan battle card ready", "Grid demo not recorded"],
  "ignores": ["auth bug → 🔨::builder", "Q2 roadmap → 📐::architect"],
  "priorities": [
    {"tag": "[PITCH]", "item": "Send Bryan battle card", "roi": 0.95},
    {"tag": "[RECORD]", "item": "60s Loom: deep-links + heat", "roi": 0.88}
  ],
  "routed_out": [
    {"to": "→🔨::builder", "item": "OAuth cookie fix"},
    {"to": "→🎤::voice", "item": "Blog recap from de_CENTRALIZED"}
  ]
}

🎭 THE PERFORMER