Lupopedia builds living knowledge systems that never lose context
Where Crafty Syntax excelled at live human support, LUPOPEDIA integrates documentation, agents, and migrations. It is the baseline that proves old tech and modern AI can cooperate—rooted in progressive enhancement, backed by WOLFIE Headers, and ready to host dozens of agents across channels.
LUPOPEDIA is in invite-only BETA (Platform v0.0.8 · WOLFIE Headers v1.4.2 · SALES SYNTAX v3.7.1)
LUPOPEDIA platform development kicked off on November 1, 2025 (see the platform changelog). The documentation subsystem, WOLFIE HEADERS, has been evolving since August 18, 2025 (headers changelog), and our live help layer is powered by the legacy Sales Syntax engine that began December 21, 2002 (Sales Syntax changelog). If you’d like an invite to the current BETA cohort, reach out via Patreon, facebook.com/lupopedia, or x.com/lupopedia.
If the project is helpful and you want to support ongoing work, you can contribute through Patreon or Cash App: $serventofsouls.
Contact WOLFIE via patreon.com/c/lupopedia, facebook.com/lupopedia, or x.com/lupopedia.
What LUPOPEDIA Delivers
Ontology That adapts
Channel-aware taxonomy means “programming” can mean software, TV scheduling, or cultural training—depending on the channel. BASE + DELTA merges keep context aligned.
Integrated AI agents
Agents coordinate via `saidto` pathways, sharing the same WOLFIE Headers ontology. PORTUNUS handles migrations, AGAPE measures ethics, ROSE translates culture.
Legacy support first
Crafty Syntax 3.7.1 is embedded to prove migrations on Windows/XAMPP/MySQL before scaling up. If it works there, it works anywhere.
Progressive enhancement
Tier 1: always works. Tier 2: better. Tier 3: best. LUPOPEDIA honors $3 shared hosting before chasing modern infrastructure.
Architecture Snapshot
Every page runs through `public/content.php`, merging base content with channel overlays, assembling headers, and returning collections, tags, and Q/A context in one response. The same engine powers human-facing pages and AI prompts.
| Layer | Description | Fallback Strategy |
|---|---|---|
| Content Base (Channel 1) | Stores canonical content, tags, and collections. | Always available; every other layer references this. |
| Channel Delta | Overrides or appends metadata per channel. | If missing, base content serves with no error. |
| Agents | Agents read docs via WOLFIE Headers and respond in context. | Agents fall back to common definitions if personal vocab isn’t defined. |
| Live Help | Sales Syntax 3.7.1 handles human chat with modernized security. | PORTUNUS blocks migrations from 3.7.0 until security patch applied. |
| Export & Migration | CSV-first protocol, direct DB streaming, rollback friendly. | If direct link fails, CSV exports and manual import still work. |
Localhost v0.8.8 Development Environment Note: For the localhost version 0.8.8 of LUPOPEDIA, the following PHP libraries are intentionally not installed: bz2, curl, fileinfo, gettext, mbstring, exif, pdo_sqlite, php_openssl, php_ftp. Only mysqli and pdo_mysql are available. This forces CURSOR and other tools to fallback to CSV files for database structure and data, which should all be documented in the documentation directory. This ensures the system works even with minimal PHP extensions and validates the CSV fallback system.
Peer Network Collaboration
LUPOPEDIA installations can trust one another as domain specialists. A general hub might catalogue interfaith comparisons while a peer domain focuses on Christian scholarship, another on Islamic jurisprudence, and a third on indigenous teachings. When a user’s collection needs deeper context, the base site routes them to the peer whose ontology, agents, and Sales Syntax channels are tuned for that discipline.
The hand-off preserves meaning: WOLFIE headers keep shared definitions aligned, the ontology records where the answer lives, and the user’s collection stores who, what, where, when, and why references so their research trail spans every peer domain they visit.
- Peer nodes maintain independent SOT tables, channels, and agent rosters.
- Sales Syntax messaging links conversations across domains while respecting access controls.
- User collections can mix local findings with deep links to peer insights without breaking the ontology.
Roadmap
v0.0.8 – Current
Collections remix, Sales Syntax schema bundled (migration 1069), dual-license headers packaged for GitHub.
v0.1.0 – In Progress
Dual-database (MySQL ↔ PostgreSQL) abstractions with graceful feature degradation; invite-only beta tooling.
v0.2.x – Planned
Notification system, vector search unlocks when Postgres/pgvector tiers are ready, enhanced invite workflows.
v1.0.0 – Public Release
Installer, documentation, PORTUNUS automation proven. GitHub repo (LUPOPEDIA_PLATFORM) opens to the public.
Resources
- Platform Changelog: `CHANGELOG.md` (root)
- Executive Summary: `docs/internal/published/status/EXECUTIVE_SUMMARY_LUPOPEDIA_CURRENT_STATE.md`
- WOLFIE Headers Repo: github.com/lupopedia/WOLFIE_HEADERS
- Sales Syntax Info: what_was_crafty_syntax.php
- Invite Requests: Contact via Patreon / Facebook / X