The old standalone route remains accessible during migration.
Open legacy routeCapsule To Hub Route Registry Layer
This record is rendered through the shared readiness route. The legacy route remains preserved until redirect review.
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
Capsule To Hub Route Registry Layer
Render Capsule To Hub Route Registry Layer as a manifest-managed internal readiness record before any redirect or route deletion review.
The source API reference remains linked for verification.
Open source APIThis is the future preferred render path for the record.
Generated manifest expansion record. Legacy route remains preserved. No redirect, no deletion, no CSS deletion, no production mutation.