Oshun, mapped end to end.
Browse product lines, domain architecture, APIs, journeys, and operational evidence—then drill into the exact source file, contract, or test.
Start here
New here? Orient in 30 minutes — a curated reading path for your role, or the whole repository on one page.
Products
The ten product lines (V1–V10). Each is a full product space — features and architecture today, deepening over time.
What's new
The most recently added entity nodes — by immutable creation date, so the rail is deterministic and refreshes only when a project actually lands.
V1 documentation guide
A curated path through the complete V1 product and architecture libraries, visual models, and cross-cutting handbooks—organized by the question you need to answer.
V2–V9 documentation guides
A release-by-release path into each complete feature and architecture library, paired with an eight-model visual atlas and evidence map.
Eve & Lilith
Two related identities, fully mapped without conflation: Eve is the builder/operator assistant charged with building the rest of the product vision, V1 and beyond; Lilith is the member-facing persona, the V1 policy substrate, and the V3 embodied product.
Workbenches & Telegram
The complete governed-work estate and the complete Telegram channel family—product journeys, architecture, trust, operations, and evidence-backed change paths.
By discipline
Read across products by concern — decisions, operations, security, reference, and the rest of the docs/ taxonomy.
API, contracts, events, errors, config & deps
Code-linked reference parsed from the OpenAPI specs, contract modules, the event registry, the typed error declarations, .env.example, and the package.json manifests — endpoints, schemas, the contract surface, every domain event, every typed error code, every environment variable, and every external dependency.
Reference directory
Every generated single-page reference and index — platform, data, ops, design, testing — one card each.
Product space maps
The full §5 skeleton per product — every section at its one canonical home, the product's own pages plus the shared surfaces it composes — plus the cross-product capability matrix.
Product doc libraries
Every product's own committed documentation under V*/ — its runbooks, service docs, balance changelogs, and topic guides — surfaced as first-class, searchable pages (§5).
User journeys
How users move through every surface — end-to-end flows, per-surface walkthroughs, and the recorded walks that verify them.
Systems catalog
Every part of the system, addressable — 3504 code-linked entity nodes read from the project graph.
The center itself
How this documentation center is generated, kept never-stale, and gated.