# Agent Migration Index

Future-us map for migrating useful value from legacy `cosmo-home_2.3` into Home23 without rebuilding old chaos.

## Bottom line

- Keep Home23 sparse.
- `jerry` remains the central continuity spine.
- Only obvious future standalone agents: `tick`, `edison`.
- `archivist`, `autostudy`, `sentinel` should start as workflows, not bodies.
- `althea` and legacy `coz` are doctrine sources more than resurrection targets.
- Old home is a donor archive, not a live dependency.

## What we decided

### Agent model in Home23

A new Home23 agent is a full isolated runtime with its own:

- `config.yaml`
- `workspace/`
- `brain/`
- `conversations/`
- `logs/`
- `cron-runs/`
- port block / process set

So “new agent” means a real separate mind, not a light persona.

### Migration rules

1. Migrate doctrine aggressively.
2. Migrate memory selectively and in curated chunks.
3. Migrate identity only when the role is truly distinct.
4. Do not bulk import legacy logs or stale state.
5. Do not make the old house a permanent dependency.

## Current recommendations

### Keep as real future agents

- `tick` — strongest case for a separate runtime; distinct operational role, risk profile, and memory boundary.
- `edison` — valid specialist future agent; separate enough to justify its own body when workload warrants.

### Keep as workflows first

- `archivist` — memory curation / continuity hygiene
- `autostudy` — research/study loop with explicit state
- `sentinel` — meaningful output and failure monitoring

### Keep as doctrine sources

- `althea` — executive/debug/retrieval doctrine
- `coz` — operator voice and scope discipline lineage

## Key docs

- `HOME23_AGENT_ARCHITECTURE_RECOMMENDATION.md`
- `LEGACY_MEMORY_IMPORT_PLAN.md`
- `IDENTITY_LAYERS_SAFETY_REVIEW.md`
- `TICK_HOME23_AGENT_SPEC.md`
- `EDISON_HOME23_AGENT_SPEC.md`
- `AGENT_INSTANTIATION_CRITERIA.md`

## Current state

- migration project scaffolded
- legacy doctrine extracted
- workflow specs written
- curated imports made into Jerry
- Tick and Edison future-agent specs drafted
- instantiation criteria defined

## Practical next steps

1. Implement one workflow for real.
2. Only instantiate Tick or Edison when the criteria doc says go.
3. Continue curated imports only as needed, not by bulk dump.