Review domain readiness before any expansion.
Preserved structural checklists for proposed domain roles, with current ownership evidence and open reviews.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Saved discoveries · event and discovery dates
Discoveries through time
Living Intelligence Ecosystem · Saved evidence shared across Library, capsules, world and time.
Connecting this view to its project…
Voice ready
Recorded claims, visible ownership gaps.
683 current route identities · 30 with explicit host claims · 653 awaiting host review.
51 routes have a documentary steward; 632 need functional ownership review across 38 functional domains. Human appointments remain unassigned.
Host claims describe intended web addresses. Functional stewardship describes a recorded project responsibility. Keyword candidates and review roles do not assign ownership or grant authority. DNS, deployment, authentication, and activation remain outside this evidence.
Browse the full domain graphSplitting domains too early creates chaos. Splitting them correctly creates power.
The scores below preserve the existing structural checklist. They are not DNS or deployment evidence, authentication grants, founder approval, or authorization to split a domain. Recorded roles and reversibility rules still require review before operational changes.
Primary gateway for the full TheoB operating system.
Education, citations, sources, and public-interest knowledge stay clean from monetization pressure.
Live signals, current-state dashboards, and observatory systems belong here.
Paid tools, teams, operators, memberships, and advanced workflows belong here.
Developer infrastructure, APIs, integrations, webhooks, and technical docs belong here.
Every domain split must protect the mission.
A route cannot move domains until its role is clear.
Public knowledge routes must remain monetization-protected.
Live signal routes need observability, pause logic, and source governance.
Professional routes need pricing, access control, user roles, and support expectations.
Developer/API routes need keys, docs, rate limits, and security review.
All domain moves must be reversible.