Retain a thin bundled-Core fallback path behind a flag #36

New issue

Open

opened 2026-07-01 01:05:37 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:05:37 +00:00

(Migrated from github.com)

Problem

The v0.1.0 bundled Core should not be ripped out entirely; a flagged fallback lets self-hosters run engine-local if they choose, while the default path is the Api.

Acceptance criteria

A setting selects data source: Api (default) or bundled engine.
When set to bundled engine, surfaces resolve via Core exactly as in v0.1.0.
The default fresh install uses the Api path.
Switching sources purges caches to avoid mixing provenance.

Notes

This keeps the standalone capability alive without making it the primary path.

## Problem The v0.1.0 bundled Core should not be ripped out entirely; a flagged fallback lets self-hosters run engine-local if they choose, while the default path is the Api. ## Acceptance criteria - [ ] A setting selects data source: Api (default) or bundled engine. - [ ] When set to bundled engine, surfaces resolve via Core exactly as in v0.1.0. - [ ] The default fresh install uses the Api path. - [ ] Switching sources purges caches to avoid mixing provenance. ## Notes This keeps the standalone capability alive without making it the primary path.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Ordo#36

No description provided.

Rows
Columns