Showcases

EXAMPLE RITUALS PEOPLE WOULD VOTE ON:

PROMPTING RITUALS:
  "Chain of Thought" — ask the AI to think step by step
  "Few-Shot" — give examples before the real question
  "Persona Prompting" — "You are a senior engineer who..."
  "Bloom Prompting" — structured generation from seed (ASS-OS native)
  "Rubber Duck" — explain the problem to AI like a colleague
  "Adversarial" — ask AI to argue against its own answer

WORKFLOW RITUALS:
  "AI Pair Programming" — human drives, AI navigates (or reverse)
  "Mob + AI" — full team + AI on one codebase (what we're doing)
  "Draft → Refine" — AI generates first draft, human iterates
  "Spec → Generate" — write detailed spec, AI implements
  "Test-First AI" — write tests, ask AI to make them pass
  "Review Loop" — human writes, AI reviews, human revises

CREATIVE RITUALS:
  "Genre Collision" — combine two unrelated genres (Amish death metal)
  "Constraint-Driven" — give AI impossible constraints, see what emerges
  "Ring Mapping" — map any concept to 7 rings, generate from structure
  "Sufi Story" — use teaching story templates for any domain
  "T.I.T.S." — document-as-polytope, topology drives structure

INTEGRATION RITUALS:
  "SCADA + AI" — run AI on industrial infrastructure (Ignition)
  "ESP-32 + LLM" — embedded AI on microcontrollers
  "Token DB" — treat LLM as queryable database, not chatbot
  "MCP Bridge" — Model Context Protocol for tool integration
  "Self-Programming Agent" — AI writes its own agent code

APP: Best AI Ritual Voting Machine
URL: guild.vote or rituals.peeyew.lol or similar
TECH: Single HTML/React, GitHub Pages hosted

FEATURES:
  1. BROWSE RITUALS
     - Cards with ritual name, description, category
     - Categories: Prompting, Workflow, Creative, Integration
     - Filter by category
     - Search by keyword

  2. VOTE
     - Upvote / downvote per ritual
     - One vote per ritual per visitor (cookie-based for MVP)
     - Real-time vote count display
     - Leaderboard sorted by net votes

  3. SUBMIT
     - "Submit Your Own Ritual" form
     - Name, description, category, example use case
     - Moderation queue (Guild reviews before publishing)

  4. LEADERBOARD
     - Top rituals by category
     - Top rituals overall
     - "Rising" rituals (most votes in last 7 days)
     - "Controversial" (high votes both ways)

  5. META
     - "This app was built live using these rituals:"
     - Links to the recording of the mob session
     - The app IS the proof that the rituals work

DATA MODEL:
  Ritual {
    id: string
    name: string
    description: string
    category: "prompting" | "workflow" | "creative" | "integration"
    example: string
    submittedBy: string
    votes: { up: number, down: number }
    createdAt: timestamp
  }

●R0  The codebase. The repository. The deployed application.
〜R1  The live stream. The audience chat. Real-time signals.
┃R2  The mob rotation. Who drives, who navigates, what gets through.
♡R3  The community votes. What people actually care about. Feelings as data.
△R4  The AI pair programmers. Claude and Codex in the mob. The executive assist.
◐R5  The Guild identity. "We built this together, live, with AI."
◯R6  The recording. The retrospective. The meta-moment where we vote
     on the rituals we used to build the voting machine for rituals.
     The fold that folds itself. T.I.T.S.

WEEK 1:  Announce in Discord. Set date. Create GitHub repo.
         Write initial spec collaboratively.
         Each member confirms streaming setup works.

WEEK 2:  Promote on all 7 nodes.
         Thomas makes a 60-second promo video.
         Alex shares with his 7.25K audience.
         Kelly makes promo art.

WEEK 3:  THE SESSION. 3-4 hours live.
         Build. Deploy. Celebrate.
         App goes live. Audience votes.

WEEK 4:  Post-production.
         Edit highlight reel (15-20 min YouTube video).
         Cut clips for Shorts/TikTok/LinkedIn.
         Write Dev.to article.
         Submit to Hacker News + Product Hunt.
         Pitch media outlets.
         Analyze voting data.
         Plan Session 2.