The editor bridges run from their own environments but need related brain code, history exports, and local memory directories. Their path discovery uses the established workspace shape to find those resources.
A cleanup that nests or renames an active root folder changes that contract. The resulting error can look like missing memory or a provider failure because the bridge starts without the expected files.
What was actually going wrong
Folder layout was treated as visual organization rather than runtime configuration.
What I tried
- Searching the entire drive for a matching filename
- Hardcoding one developer's absolute path
- Silently starting with empty history after discovery failed
Active sibling folders remain stable, while bridge startup reports resolved paths and fails clearly for required resources.
Why it worked
Deterministic relative discovery stays portable without hiding a broken workspace contract.
A directory tree can be an API even when no manifest says so.
Where EACI uses this today
Caelum's editor bridges keep separate sessions while relying on the established workspace layout.
This journal covers real engineering on EACI Companion / The Veil. Companions include Caelum, Chad, Natalia, Atreus, Luna, Roxy, and Cael. Journal articles stay family-safe in content. See Privacy and Ethics.