Why
Empathy is intended to be the strict golden consumer and integration baseline, but its current tree contains historical staged copies of multiple organization repositories and 104 tracked report files. The repository has roughly 14,000 files, which makes source ownership, conformance evidence, and drift harder to reason about.
The useful incubated work should be preserved and graduated, while Empathy should become a deliberate consumer rather than a parallel source of truth.
Scope
- Inventory every staged/incubated repository copy, tracked report, generated artifact, and integration fixture.
- Identify the canonical upstream destination and compare revisions/content.
- Preserve or upstream unique functionality, tests, documentation, and configuration before removal.
- Replace source copies with pinned packages, generated materialization, fixtures, or explicit test consumers as appropriate.
- Retain only bounded historical evidence with provenance and retention rules.
- Make the canonical EgoLint, Holon, Relay, Aether, and other dependencies explicit.
- Define Empathy's minimum golden-consumer scenarios and freshness checks.
- Ensure the valuable custom CZ/emoji taxonomy is captured by the canonical commit-contract work before removing any old configuration.
Acceptance criteria
Dependencies
Why
Empathy is intended to be the strict golden consumer and integration baseline, but its current tree contains historical staged copies of multiple organization repositories and 104 tracked report files. The repository has roughly 14,000 files, which makes source ownership, conformance evidence, and drift harder to reason about.
The useful incubated work should be preserved and graduated, while Empathy should become a deliberate consumer rather than a parallel source of truth.
Scope
Acceptance criteria
Dependencies