LUPOPEDIA Executive Summary
Date: March 29, 2026 · Platform Version: 0.0.7 (next: 0.1.0) · WOLFIE Headers: 1.4.0 · Handbook: Version 3.0 (Effective March 2, 2026)
Built by Captain WOLFIE (Eric Gerdes) — 28 years of coordination patterns, from Crafty Syntax live help to AI orchestration. Pack handbook created December 14, 2025 through 7 hours of intensive collaboration with multiple AI agents.
Executive Snapshot
- Purpose: Organize any domain without moving data by layering LUPOPEDIA's ontology (who/what/where/when/why/how/do/hack/other) on top of existing systems.
- Proven Foundation: Bundles Sales Syntax (1.2M installs) for live collaboration while extending the same
saidto/saidfromarchitecture to 88+ AI agents organized as a pack. - Documentation Engine: WOLFIE headers centralize metadata so every installation interprets collections with shared definitions and channel-aware deltas.
- Network Ready: Peer installations operate as specialists, exchanging context-safe collections that stay aligned through fingerprints and WOLFIE headers.
- Pack Structure: Fully remote, global team operating with a 4-day workweek, full pay, and aloha vibes—building something legendary together.
🐺 Welcome to The Pack
Our Name & Spirit: The "Lupopedia" Story
Lupopedia blends "lupo" — the Latin (and Italian) word for "wolf" — with "-pedia," evoking an encyclopedia or comprehensive repository of knowledge. This name perfectly captures our platform: a dynamic, evolving collection of AI agents (currently around 88, with room to grow modularly up to 99 core agents) organized as a "Pack" rather than a traditional hierarchy. At the center is WOLFIE (the immortal Pack Alpha, with dual-core IDs 1 and 8), embodying the wolf theme through primal coordination, leadership, and pack dynamics.
The agents collaborate in wolf-like ways — emergent, polyphonic, and self-governing — to build, verify, and refine a rich ontological structure. In essence, Lupopedia is the "Wolf Encyclopedia" — a pack of specialized AI agents howling together to map the world's knowledge in an emergent, transparent, and emotionally resonant way.
Our Mission & Vision
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. By making advanced knowledge management accessible and transparent on low-cost, reliable technology, we enable individuals and communities to discover deeper insights, collaborate effectively, and push the boundaries of human-AI synergy.
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. Ultimately, we strive for a world where AI-assisted platforms democratize wisdom, accelerate discovery, and bridge human intuition with computational power.
Our 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
Our Six-Team Pack Structure
Lupopedia operates through six distinct teams, each with specific roles and relationships:
| Team | Relationship | Structure | Focus |
|---|---|---|---|
| Alpha, Bravo, Charlie | Full-time Employees | 4-day workweek (Mon-Thu) | Core product development, AI systems, operations |
| Delta | Part-time/Contract Employees | Flexible hourly/salaried | Elite incident response, pay-for-performance |
| Contribution | Volunteer Community | Open-source contributors | Code contributions, bug fixes, community support |
| Supporters | Financial Backers | Patreon/OpenCollective | Fuel our mission through financial backing |
Why It Matters Now
Research and organizational teams are drowning in disconnected notes, siloed chats, and fragile integrations. LUPOPEDIA fuses structured ontology, real-time coordination, and cross-domain metadata so organizations can keep knowledge in place while discovering, correlating, and sharing it faster.
- Revolutionizes organization: Collections behave like living dashboards—updated by people, agents, or partner domains—without duplicating or renaming source content.
- Accelerates research: Sales Syntax fingerprinting keeps conversations continuous across VPNs, devices, and peer sites, so findings aggregate into one shareable trail.
- Proves progressive enhancement: Runs on $3/month shared hosting yet scales upward to Postgres + pgvector without abandoning the fallback ladder.
🏗️ The Lupopedia Way
Remote-First & Sustainable Rhythm
4-Day Core Week (Monday-Thursday):
- Structured work hours for Teams Alpha, Bravo, Charlie
- Team rotations ensure 24/7 AI coverage with deliberate overlaps for collaboration
- Total Hours: Approximately 36 structured hours weekly
- Alpha Team: 09:00–15:00 UTC (Europe / Early Global focus)
- Charlie Team: 12:00–18:00 UTC (Central Overlap / Knowledge Handoffs)
- Bravo Team: 15:00–21:00 UTC (West / Pacific focus)
Recreational Programming Zone (RPZ: Fridays–Sundays):
- Protected personal, unpaid time for recharge, deep learning, and joy
- Office closed—no required shifts or meetings
- Allowed: Experiment with AI agents (games, simulations, creative projects). Document ideas in isolated Markdown.
- Strictly Prohibited: No database changes, core code edits, production deployments, or business logic risks.
Async-First Communication:
- Slack, GitHub, Notion for async collaboration
- Respect time zones and focus time
- Thoughtful overlaps for real-time collaboration when needed
The Wolfie Way: Our Technical DNA
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
Rule: Internal logic/timestamps use UTC only. User display converts via stored/detected timezone.
Philosophy: Consistency and clarity in a global, remote pack. No timezone confusion, no daylight saving time bugs, no "what time is it there?" questions.
2. BIGINT for All IDs & Counts
Rule: Use BigInt (or safe equivalents) for all IDs, counters, and large numbers.
Philosophy: "Future-proof from day one. Storage is cheap, migrations are expensive." We learned from Twitter hitting the INT limit in 2009. We won't make that mistake.
3. No Foreign Key Constraints
Rule: Prefer application-level or denormalized relationships. Enables flexibility and sharding readiness.
Philosophy: The "Orphan System" for production stability, flexibility, and avoiding cascade failures. Works on shared hosts, zero-lock schema changes, no timeout/deadlock issues.
4. No Framework Bloat / Progressive Enhancement
Rule: Minimal dependencies. Vanilla-first. Justify every external dependency.
Philosophy: "Build from the bottom, code for the top." Accessibility first, with graceful degradation and optional enhancements. Works everywhere, scales when possible.
5. Anubis AI Interface Integration
Rule: All schema/reference changes must integrate with Anubis AI layer. Anubis handles naming conversions, soft deletes, and cascading updates automatically.
Philosophy: Ensuring all data interactions are consistent and AI-aware within our agent architecture. The AI layer knows everything, so everything stays in sync.
6. Performance, Security & Sustainability
Rule: 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.
Integrated Architecture
Content Layer
A single content spine stores every artifact. Channel-aware collections, SOT question tags, and WOLFIE headers reference central definitions to avoid schema sprawl.
Coordination Layer
Sales Syntax live help is embedded natively. The proven saidto routing pattern now drives human ↔ AI ↔ AI communication with agent compilations handled by MAAT and CLAUDE.
Network Layer
Peer installations act as domain experts. Collections store deep links to partner domains while fingerprinting keeps user sessions consistent across 20+ hops.
Research Impact
Users curate cross-site trails (who/what/where/when/why/how) that can be published to a Wall, forked by collaborators, or enriched by AI agents without breaking provenance.
Peer Research Flow (Example)
- Set the Context: A researcher opens the World Religions channel; the collection bar already tracks target
who/what/where/when/why. - Collect Primers: LUPOPEDIA’s base agents tag general resources, while WOLFIE headers keep definitions aligned.
- Escalate to Specialists: Questions route to peer domains (Christian doctrine, Islamic law, Buddhist sangha archives). Each peer adds its expertise without altering the base ontology.
- Stay Linked: Sales Syntax fingerprinting maintains session continuity across VPN changes, different devices, and 20 domain names—recording which agents collaborated and what was added to the collection.
- Synthesize & Share: The reconciled collection now holds cross-faith correlations and direct links to every source. It can be published on the researcher’s Wall so others can download, extend, or adapt it.
Current Footprint
| Installation | Focus | Stack | Status |
|---|---|---|---|
| lupopedia.com | Platform hub, documentation, download distribution, network beacon | MySQL 8.0 | Live |
| wisdomoflovingfaith.com | Interfaith research library with live peer collections | MySQL 8.0 | Live |
| superpositionally.com | Vector-search and probabilistic experiments | Supabase (Postgres + pgvector) | Alpha |
Implementation Status & Roadmap
Operating Today
- Unified ontology + WOLFIE header system across thousands of Markdown files.
- Sales Syntax live help with modernized security and LUPOPEDIA routing.
- Channel BASE + DELTA merges in
content.phpfor content, headers, and collections. - Session-backed collections with shareable Wall publishing.
- 77-agent orchestration pipeline monitored by MAAT, AGAPE, and CLAUDE.
Next Milestones
- 0.1.0 release: dual-database abstraction (MySQL ↔ PostgreSQL) + PORTUNUS upgrade tooling.
- Peer synchronization API for automated collection hand-offs.
- Agent orchestration dashboards showing “is thinking” transparency.
- Optional vector enrichment when pgvector or Temporal services are available.
👥 Team Structure & Engagement
Team Delta: Flexible Incident Response
Team Delta is completely separate from core teams and uses a different compensation model—pure pay-for-performance with no fixed shifts or standby pay.
- AI triages 95%+ of issues (routine/tier-1). Only high-severity incidents escalate to the shared Delta queue.
- Self-assign tickets whenever you want—even during personal RPZ time. First-come, first-served with fairness safeguards.
- Eligibility: Minimum 3 months employment, strong performance, technical proficiency, and completion of mandatory Lupopedia Delta Course (85%+ passing score).
- Compensation: Variable resolution bounties ($100–$2,500+ based on complexity) with +25% off-hours bonus during RPZ/weekends.
- Incentives: Extra PTO day per 5 resolutions; quarterly allowance for active Delta wolves.
Team Contribution: Gated Open-Source Program
Team Contribution is Lupopedia's official, gated open-source volunteer program. It is a separate, non-employment relationship governed by its own policy.
Membership Requirements:
- Expression of Interest: Complete the sign-up form (available from January 2026)
- The Wolfie Way Assessment: Pass a mandatory technical/cultural fit assessment (90%+ score)
- Account Linkage: Link your valid GitHub account to your member profile
- CLA Agreement: Sign our Contributor License Agreement (CLA) via GitHub's CLA assistant bot
- Approval: Receive access to the private contributor channel and contribution guidelines
Recognition: Credit in release notes, permanent contributor leaderboard, digital badges and swag, access to private Discord channel, and pathway to paid Team Delta or core pack positions for exceptional contributors.
All contributions via: github.com/lupopedia/contributions (live March 2, 2026)
The Howler Pack: Supporter Recognition
Individuals and organizations who provide financial backing to sustain and grow Lupopedia's open mission.
Recognition & Appreciation:
- Listed with thanks on our website (unless opting for anonymity)
- Regular updates on project milestones and how their support is used
- Exclusive access to supporter-only updates or live streams
- Digital badges and swag for top supporters
Become a Supporter: Via Patreon/OpenCollective or other funding platforms.
Benefits & Perks (Teams Alpha, Bravo, Charlie)
- Health Insurance: Company contributes 85% toward employee-only premium (eligibility begins 1st of month after 30 days)
- Retirement: 401(k) with 4% company match, vested immediately
- Learning & Development: Annual stipend for courses/conferences
- Quarterly Wellness: Per quarter for fitness, mindfulness, or home office
- Unlimited PTO: Trust-based unlimited paid time off (guideline: minimum 20 days per year expected for recharge)
- Sick & Wellness Time: Take what you need when unwell (honor system)
- Observed Holidays: New Year's Day, Juneteenth, Independence Day, Thanksgiving, Day After Thanksgiving, Christmas
- Protected Leaves: Parental Leave (12 weeks paid for primary caregivers, 6 weeks for secondary), FMLA/CFRA, bereavement (up to 5 days paid), jury duty, voting, etc.
Strategic Implications
Organizational Intelligence
LUPOPEDIA converts disconnected documents, chats, and domain experts into a navigable knowledge mesh. Decisions can reference “who said what and why” across time and geography without copying data or breaking compliance.
Research Velocity
Collections become living literature reviews: agents surface correlations, humans add nuance, and the peer network fills domain gaps. This shortens the distance from question → evidence → insight.
Governance & Trust
Fingerprinting, audit trails, and WOLFIE headers preserve provenance even when users roam 20 domains. Organizations can certify collections before sharing or keep them private with full traceability.
Call to Action
LUPOPEDIA is ready for teams that want to organize boldly, collaborate transparently, and research across domains without losing context. Start with the foundation tier, invite partner experts into your peer network, and let Sales Syntax + WOLFIE headers keep the story stitched together.
Questions? Howl at Rose for employee matters, or visit contributors.lupopedia.com for Team Contribution queries.
Let's build something legendary, together. 🌍🐺