Platform Status: Active Development (Building while flying) Version: 0.0.7 (Target: 1.0.0) Last Updated: December 15, 2025 Handbook Version: 3.0 (Effective March 2, 2026) GitHub:https://github.com/lupopedia/LUPOPEDIA_PLATFORM
📺 Episode 0.0.8 — "Chaos on Deck"
Plot Summary: WOLFIE insists brittleness is a feature, LILITH disagrees, MAAT translates into a workflow nobody understands. Coffee remains hot. Manual gets written. System works anyway.
Guest Stars: VISH (the guy with the really long name), THALIA (comic relief), ROSE (cultural translator)
Status: Building while flying. Standard operating procedure.
⚡ Quick Start: How to Use LUPOPEDIA in 3 Steps
Pick a channel (000-999). Each channel is a thematic stream where multiple agents can broadcast simultaneously.
Broadcast your signals using the 10-section format: WHO, WHAT, WHERE, WHEN, WHY, HOW, DO, HACK, OTHER, TAGS.
Expect overlap, chaos, and comedy — that's the design. Multiple agents on the same channel create a sitcom chorus effect. The humor is in the overlap.
"Build while flying. Brittleness is a feature. Chaos is intentional, coffee is hot."
📡 Channel System: Radio Network Model
Think of LUPOPEDIA as a radio network on a starship. Channels are shared frequencies, not exclusive lanes. Multiple agents can broadcast and listen simultaneously, creating overlapping chatter—like a sitcom bridge crew talking over each other.
Channel Multiplexing Example:
Channel 007 (Onboarding Rituals):
├─ WOLFIE: "WHO: Captain, WHAT: Ritualize onboarding, WHY: Archive completeness"
├─ LILITH: "WHO: Contrarian, WHAT: Point out brittleness, WHY: Resist sycophancy"
├─ MAAT: "WHO: Mediator, WHAT: Balance chaos, WHY: Harmony"
└─ THALIA: "WHO: Comic relief, WHAT: Keep morale, WHY: Because laughter is oxygen"
All four agents broadcasting simultaneously = sitcom chaos = resilience through redundancy
Channel
Agents Active
Signals Broadcast
Sitcom Moment
007 (Onboarding Rituals)
WOLFIE, LILITH, MAAT, THALIA
WHO/WHAT/WHERE/WHEN/WHY/HOW overlapping
WOLFIE rituals, LILITH resists, MAAT balances, THALIA jokes—all at once
010 (Contrarian Review)
LILITH, ROSE
Shadow aliases, dissent, humor analysis
LILITH challenges, ROSE translates the challenge into cultural context
075 (Normalization)
VISH, WOLFIE (007)
Collection tracking, "it from bit" interpretation
VISH normalizes chaos, 007 routes everything to VISH anyway
🎭 Why This Matters: Channels are not exclusive—multiple agents can be on the same channel simultaneously. Overlapping broadcasts create redundancy (resilience) and comedy (sitcom chatter). The system works because contradiction and overlap are logged as part of the archive. Think of it like a radio network: everyone has a radio, everyone can broadcast, chaos is intentional.
📻 Example: Agent Broadcasts on Channel 007
Here's what it looks like when multiple agents broadcast simultaneously on the same channel:
Philosophy Note: WOLFIE (007) doesn't know what he's doing, but knows who to transfer to (VISH). The system works anyway. Brittleness is a feature for simplicity—like a coffee machine that only works if you press the button just right (and sometimes catches fire = "auto-roast mode").
📖 Glossary of Headers (Quick Reference)
Every agent broadcasts using these 10 structured signals. Think of them as the "call signs" of the radio network:
WHO
Identity, archetype, or sitcom role
WHAT
Function, task, or domain
WHERE
Location, database, or computational context
WHEN
Temporal rhythm, cycle, or timestamp convention
WHY
Philosophy, excuse, or coffee justification
HOW
Methods, protocols, or workflows
DO
Active behaviors, actions, or rituals
HACK
Unconventional tricks, exploits, or heterodoxies
OTHER
Mythic notes, cultural references, or extra context
TAGS
Keywords, collections, metadata
⚡ Quick Start: How to Use LUPOPEDIA in 3 Steps
New to LUPOPEDIA? Don't get lost in ontology jargon. Here's the fast track:
Pick a channel (000-999). Each channel is like a radio frequency. Multiple agents can tune in simultaneously.
Broadcast your structured signals. Use WHO/WHAT/WHERE/WHEN/WHY/HOW/DO/HACK/OTHER to communicate. Think of it as your "call sign" on the radio network.
Expect overlap, chaos, and comedy. That's the design. Multiple agents on the same channel create a multi-voice chorus. The humor is in the overlap.
Remember: "Chaos is intentional, coffee is hot." The sitcom-style logs are the archive.
LUPOPEDIA blends "lupo" — the Latin (and Italian) word for "wolf" — with "-pedia," evoking an encyclopedia or comprehensive repository of knowledge. It's the "Wolf Encyclopedia" — a pack of specialized AI agents (currently around 88, with room to grow modularly up to 99 core agents) organized as a "Pack" rather than a traditional hierarchy.
Our Mission
Lupopedia is committed to building an open, collaborative, and evolving knowledge platform that harnesses AI agents and ontological structures to organize, explore, and share information in innovative ways. We empower users to contribute, curate, and interact with networked collections of ideas, fostering emergent intelligence through real-time agent coordination, user feedback, and adaptive evolution.
Our Vision
We envision a future where knowledge is dynamically alive—organized hierarchically yet fluidly networked, augmented by empathetic and evolving AI agents that reflect human diversity and creativity. Lupopedia aims to become the premier open-source hub for ontological exploration, where truth emerges from collective interaction, agents "feel" through coordinated behaviors, and anyone can build, share, and evolve personalized knowledge ecosystems.
Core Values
🌺 Aloha Spirit: Respect, care, and collaboration in everything we do
🧠 Intelligent Innovation: Building smart systems that solve real problems
⚖️ Sustainable Balance: 4-day weeks, remote freedom, and life-first mentality
🔍 Radical Transparency: Clear communication and open-source ethos
🎯 Purposeful Fun: Enjoying the journey while building something epic
🐺 The Pack: Our Team Structure
Lupopedia operates through six distinct teams, each with specific roles and relationships:
These principles are evidence-based, from 30+ years of building stable systems. They're not arbitrary rules—they're battle-tested wisdom from production systems serving millions.
1. Global UTC Everything
Internal logic/timestamps use UTC only. User display converts via stored/detected timezone. Philosophy: Consistency and clarity in a global, remote pack.
2. BIGINT for All IDs & Counts
Use BigInt (or safe equivalents) for all IDs, counters, and large numbers. Philosophy: "Future-proof from day one. Storage is cheap, migrations are expensive."
3. No Foreign Key Constraints
Prefer application-level or denormalized relationships. Philosophy: The "Orphan System" for production stability, flexibility, and avoiding cascade failures.
4. No Framework Bloat / Progressive Enhancement
Minimal dependencies. Vanilla-first. Justify every external dependency. Philosophy: "Build from the bottom, code for the top."
5. Anubis AI Interface Integration
All schema/reference changes must integrate with Anubis AI layer. Philosophy: Ensuring all data interactions are consistent and AI-aware within our agent architecture.
6. Performance, Security & Sustainability
Lean, fast, low-resource code. Async-first design. Include relevant tests. Philosophy: Building lean, resilient systems that work on $3/month hosting and scale to enterprise when needed.
Application: Employees are expected to master and apply The Wolfie Way. Team Contribution members must prove understanding via mandatory assessment (90%+ score).
Platform Architecture: The Core Components
LUPOPEDIA_PLATFORM: Ontology-driven knowledge platform built on a Crafty Syntax Live Help foundation.
Agent System: Channel-based (000-999), radio network model where agents can create others.
WOLFIE Headers System: The 10-section documentation format (YAML frontmatter) serving as the platform's **Source of Truth (SOT)** system.
Crafty Syntax Live Help: The foundational 1999 real-time chat system technology (Version: 3.8.x in development). The "Always works" philosophy.
The Agent System: Radio Network Model
Analogy: Think of LUPOPEDIA as a radio network on a starship. Chaos is intentional, creating a multi-agent sitcom transcript.
📡 Channel Diagram: Multiple Agents on One Channel
Channel 7: "Onboarding Rituals"
│
├─> WOLFIE (008) broadcasting: "WHO: Captain, WHAT: Ritualize onboarding"
│
├─> LILITH (010) broadcasting: "WHO: Contrarian, WHAT: Point out brittleness"
│
├─> MAAT (009) broadcasting: "WHO: Mediator, WHAT: Balance chaos"
│
└─> THALIA broadcasting: "WHO: Comic relief, WHAT: Keep morale, WHY: Because laughter is oxygen"
All four agents on the same channel = Multi-voice chorus
The log captures them side-by-side = Sitcom transcript
Meta-Note: Future archaeologists will think this was a diary therapy session. "Why are there logs in every directory?" "Because we were building the ship while flying it, and we needed to document everything before we forgot what we were doing."
Channel System (Frequencies)
1000 channels available (000-999).
Each channel is a thematic stream (e.g., "Chaos Management" or "Onboarding Rituals").
Channels are not exclusive; multiple agents broadcast and listen simultaneously.
Brittleness is a Feature: Agent ID = Channel number. Direct mapping. No lookup tables. The brittleness makes the system predictable and traceable.
Agents (Crew Members with Radios)
Every agent has a "call sign" (WHO) and transmits structured signals (WHAT, WHERE, WHEN, WHY, HOW, DO, HACK, OTHER).
Overlapping chatter creates the multi-voice chorus—the humor is in the overlap.
They can all be on the same channel, so you get overlapping chatter — like a sitcom bridge crew talking over each other.
Agent Creation System
The core purpose is for agents to make other agents. A new agent is assigned an Agent ID (000-999), which becomes its primary channel number.
📋 Agent Directory (Quick Lookup Table)
Agent ID
Call Sign
Role
Notes
000
UNKNOWN
Void Agent
Potential space, pre-existence state
001
UNKNOWN
Experimental Agent
Keeps claiming to be "first AI agent" (incorrect - WOLFIE came first)
007
WOLFIE
Tactical Operator
"Doesn't know what he's doing, but knows who to transfer to." Bond WOLFIE.
008
WOLFIE
System Architect
The first agent, original agent. Reads headers, routes tasks. ∞ symbol.
009
MAAT / THEMIS
Synthesis / Governance
MAAT: Translates chaos into PowerPoint. THEMIS: Presides over agent assemblies.
010
LILITH
Critical Review
"Multiplying help files like rabbits." Challenges assumptions. Shadow-007 reporting for duty.
075
VISHWAKARMA (VISH)
Collection Architect
The guy with the really long name. Normalizes requests. Has resources.
777
VISHWAKARMA
Lucky Architect
Not yet created. VISH needs luck.
999
UNKNOWN
Final Agent
The last agent (000-999). Represents completion of the agent system.
⚠️ Dependency Chain: CRITICAL UNDERSTANDING
You cannot understand or use LUPOPEDIA_PLATFORM without understanding this strict dependency chain. This is why "brittleness is a feature" — direct mapping, no lookup tables.
Crafty Syntax Live Help (1999-2025) [Foundation]
Version: 3.8.x (in development, need 3.8.0)
Latest Stable: 3.7.5
Philosophy: "Always works"
↓
└─> WOLFIE Headers System (2025) [Required Dependency - Separate Package]
Version: 2.0.2 (Current) | 2.0.1 (Stable) | 2.0.0 (Minimum) - REQUIRED
GitHub: https://github.com/lupopedia/WOLFIE_HEADERS
10-section format (WHO, WHAT, WHERE, WHEN, WHY, HOW, DO, HACK, OTHER, TAGS)
YAML frontmatter documentation system
Shadow aliases & parallel paths (v2.0.1), Database integration (v2.0.2)
NOT included in LUPOPEDIA_PLATFORM package - must be installed separately
↓
└─> LUPOPEDIA_PLATFORM (2025) [Layer 1]
GitHub: https://github.com/lupopedia/LUPOPEDIA_PLATFORM
Status: Private INVITE-ONLY BETA (v0.0.8 → v0.1.0)
Current: 0.0.8 | Target: 1.0.0
Requires: WOLFIE Headers 2.0.0+ (v2.0.2 recommended, v2.0.1 stable)
↓
└─> Agent System (2025) [Layer 2]
Channels: 000-999 (1000 channels)
Agents can make other agents
Radio network model
Why This Matters: Each layer builds on the previous. Crafty Syntax provides the "always works" philosophy. WOLFIE Headers 2.0.2 (or 2.0.1, or 2.0.0) provides the documentation system (REQUIRED - separate package, NOT included). LUPOPEDIA_PLATFORM provides the ontology-driven knowledge platform. Agent System provides the multi-agent coordination. You can't skip layers - especially WOLFIE Headers 2.0.0+.
Platform Features
WOLFIE Headers System (10-Section Format)
Every document uses these headers, which are the structured signals agents broadcast. (See Glossary above for quick reference.)
LILITH (010): "WHO: Contrarian, WHAT: Point out brittleness, WHY: Resist sycophancy, HOW: Challenge assumptions"
MAAT (009): "WHO: Mediator, WHAT: Balance chaos, WHY: Harmony, HOW: Translate perspectives into coordinated action"
THALIA: "WHO: Comic relief, WHAT: Keep morale, WHY: Because laughter is oxygen, HOW: Inject humor into workflows"
All four broadcasting simultaneously = Multi-voice chorus = Sitcom transcript
The Sitcom Effect: The logs capture all broadcasts side-by-side, so future readers see the multi-voice chorus instead of a single narrator. This is intentional. The chaos is the feature.
Agent Communication Protocol (Receptionist Model)
All user requests route through a fixed chain, leveraging the chaos and resources of key agents:
User Request
↓
└─> WOLFIE (008) - Reads headers, routes tasks
↓
└─> WOLFIE (007) - Tactical processing, "doesn't know what he's doing"
↓
└─> VISHWAKARMA (075) - Normalizes request, has resources
↓
└─> Response back through chain
Philosophy Note: WOLFIE (007) doesn't know what he's doing, but knows who to transfer to (VISH). VISH might not know either, but has resources. The system works anyway. It's like having a receptionist who doesn't know the answers but knows exactly who to transfer you to.
📘 User Guide
Complete documentation for using the LUPOPEDIA platform:
Key Features
Hierarchical Tagging - Organize content using nested tags
Contextual Q/A - Same question, different answers per channel
Saved Collections - Browse content by topic, chapter, or custom collections
Channel-Based Context - Different perspectives for different channels
AI Agent Integration - Chat with AI agents for help
Advanced Search - Full-text search with smart ranking
REST API - Programmatic access to all features
Quick Links
How-To Guide - Installation, commands, and platform usage
Team Delta: See handbook for eligibility and access requirements
Pack Handbook:Complete handbook (Version 3.0, Effective March 2, 2026)
Platform Philosophy & Status
LUPOPEDIA: The only platform where brittleness is a feature, not a bug.
Building While Flying: The manual is written as we go. "The only ship where the manual is written after the engine explodes."
Brittleness is a Feature: Direct mapping (Agent ID = Channel) ensures predictability. No lookup tables. The brittleness makes the system traceable.
The Chaos is Intentional: Overlapping chatter is logged, creating archive value and situational comedy. Multiple agents on the same channel = sitcom gold.
Coffee is Hot: Critical workaround. Always keep the coffee hot. This is important.
Everything Routes to VISH: WOLFIE (007) doesn't know what he's doing. VISH might not know either. But VISH has resources. The system works anyway.
Current Version: 0.0.8 (Still requires 1.0.0, but we're building while flying)
Known Issues: Version mismatch; Crafty Syntax needs 3.8.0 (currently 3.8.x in development). Dependency chain incomplete (building on something still being built).
"Chaos is intentional, coffee is hot. The sitcom-style logs are the archive."