Prepare routes to open inside the Unified Arena instead of forcing full-page navigation when safe.
Arena route loading cannot execute route actions.The arena should receive the view. The user should not be thrown into another hallway.
A dynamic, read-only readiness layer that defines future route loading inside the Unified Arena: panels, split views, hero replacement, modal actions, crossword intersections, voice requests, corner status, and future microscope zoom.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Voice ready
Open the world inside the window.
Routes, tools, files, agents, dashboards, maps, timelines, and projects should increasingly open inside the TheoB arena. Full reloads become the exception, not the habit. Clean, fast, and much less “why did this button send me to another hallway?”
Arena Route Loader Layer is active as a non-destructive arena loading readiness layer. TheoB can define future route loading targets, arena load modes, canonical route rules, provenance rules, voice request posture, corner status loading, and future route load receipts, but it cannot load live routes inside the arena, execute actions, request routes by voice, import external worlds, or mutate production yet.
Prepare tools such as calculator, measurement, formulas, settings, and apps to open as arena panels.
Tools loaded in arena cannot bypass permission gates.Prepare files, artifacts, library items, proof trails, capsules, and Vault records to open inside the arena.
File loading must preserve access boundaries and provenance.Prepare TheoB, agents, role agents, review agents, and future agent views to open inside one arena window.
Agent loading cannot grant authority or execute actions.Prepare dashboards, telemetry, provider health, command panels, and observatory views to load inside the arena.
Dashboard loading cannot mutate system state.Prepare timelines, maps, worlds, civilization views, cacao regions, and planetary signals to load as arena views.
Map and timeline views must preserve source and time context.Prepare intersecting projects, files, routes, and branches to open in crossword-style arena relationships.
Intersections should link canonical routes, not duplicate them.Prepare voice and mic requests to open the correct arena view without sending users through extra pages.
Voice route loading cannot execute restricted commands.Prepare lightweight time, date, temperature, provider health, and live pulse context to render in a corner.
Status context should be present but not dominant.Prepare imported files, external worlds, links, institutions, businesses, and user universes to enter the arena safely.
External import requires validation, provenance, and safety review.Load a route as a contained arena panel.
Best for: tools, files, settings, proof trails, small dashboardsLoad two related routes side-by-side for comparison or workflow continuity.
Best for: source versus claim, file versus receipt, map versus timelineReplace the main hero arena with a selected route view while preserving shell controls.
Best for: observatory, world, civilization, academy, dashboardsOpen a quick action or confirmation without navigating away.
Best for: settings, voice, import, share, approve, reviewDisplay route intersections as overlapping project/file/branch relationships.
Best for: projects, route lineage, provenance, shared files, duplicate preventionZoom into mini-dot visual cloud nodes, tiny route fragments, or microscopic data points.
Best for: future visual cloud and cube arenaArena Route Loader can prepare route display logic but cannot execute actions.
Loading a view is not permission to act.Every arena-loaded route should preserve canonical route identity and avoid creating duplicates.
One route, many views.Files, capsules, proof trails, maps, dashboards, and imported worlds must preserve provenance context.
A view without origin is just decoration.Common actions and views should load in arena unless security, performance, or route complexity requires full navigation.
Do not leave the arena unless there is a real reason.Voice may request arena views, but execution remains blocked by approval, authority, and command gates.
Voice opens the door; it does not grab the keys.Imported worlds, files, links, businesses, institutions, and user universes require validation before arena loading.
Bring your world in, but do not bring chaos in.Time, date, temperature, health, and live pulse should be corner-level context unless expanded.
Status should whisper until asked to speak.Arena Route Loader Layer defines future arena loading posture only.
No writes. No sync. No surprise.