Memory and identity
Episodic memory, distilled recall, self-model state, user-model state, and relational trust history now live inside OpenCAS runtime stores.
OpenBulma migration is historical context, not a live workflow.
OpenCAS is the current system. The old Bulma importer remains forbidden until the project explicitly removes that restriction, so this page exists to explain the transition rather than to offer a button to run it.
What it means
What the old migration path covered.
The historical transition moved durable state into OpenCAS concepts, but the live site now treats those concepts as first-class features, not as a one-off import event.
Creative continuity
Daydream sparks, keeper promotion, work objects, qualification receipts, and salvageable execution state are current system features, not migration leftovers.
Operational surfaces
Dashboard tabs for chat, operations, schedule, platform, system, usage, memory, identity, executive, and logs are the current control plane.
Channels and routing
Voice, phone, Telegram, and the `/ws` bridge are part of the present-day operator surface, with models routed through `open_llm_auth`.
Safety boundary
What not to do.
- Do not run the Bulma importer or any deprecated import entrypoint.
- Do not treat the old Bulma state directory as a live runtime dependency.
- Do not expect this page to launch an automated migration from the website.
- If legacy data must be mapped, do it manually into the current OpenCAS stores and verify the result with the dashboard.
Current truth
OpenCAS replaced the old stack with a broader one.
| Then | Now |
|---|---|
| Bulma-era importer flow | Disabled; retained only as historical reference |
| Local state migration as the main story | Persistent memory, scheduling, platform trust, and observability as ongoing features |
| Single-purpose agent shell | Operator dashboard with live tabs for chat, schedule, logs, platform, and system setup |
| Static guidance only | Living release docs that match the running code and the deployed site |
Useful links
- Features for the current system map.
- Usage for dashboard and runtime entry points.
- API reference for the live routes.