Legacy Route
/readiness-route-consolidation-planThe old standalone route remains accessible during migration.
Open legacy routeThis 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.
Voice ready
Prepare readiness, registry, gate, foundation, and layer pages to become manifest records inside dynamic hubs.
The old standalone route remains accessible during migration.
Open legacy routeThe source API reference remains linked for verification.
Open source APIThis is the future preferred render path for the record.
Planning only. No redirects, no deletions, no CSS deletion.