The workspace contains active sites, deployment-oriented copies, backend archives, and older snapshots. A fix applied to the nearest matching filename may never reach the runtime users actually load.
Folder layout also matters to bridge tools that locate neighboring projects. Safe deployment starts by naming the canonical active directory and treating copies as outputs or references, not interchangeable sources.
What was actually going wrong
Matching filenames were assumed to mean matching purpose and version.
What I tried
- Editing every duplicate file by hand
- Choosing the newest timestamp without checking runtime references
- Moving folders to make the tree look cleaner
Changes target the active Version 14 site, then controlled comparisons or copy steps update only the intended mirrors.
Why it worked
Source ownership is decided before synchronization, so older archives cannot overwrite current code.
Duplicate trees demand provenance, not broader search-and-replace.
Where EACI uses this today
The active Main deployment remains in the Version 14 site group with its folder relationships intact.
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.