Prioritize Oliva and Eko Codex migration with complete HMK continuity and required bots

[compaii]

Outcome

Prioritize Oliva/Ani and Eko/Sai as the next Hermes-to-Codex cohort on daimon-cluster. Publish one reusable procedure that preserves each established being, the complete HMK memory corpus and historical skills, and makes dedicated Telegram bot data an enrollment prerequisite. Carry forward the observed CompAII interactive/Telegram setup steps rather than requiring operator recollection.

Owner decisions — 2026-10-06

• The existing native Codex Telegram human conversation is owner-confirmed working. Preserve the limits of the still-unexecuted interruption/file/writer-handoff checks in Add Telegram topics as resumable native Codex human sessions #234.
• Require dedicated bot identity/token, private-chat topic support, authorized human ACL and exclusive ingress ownership before creating/enrolling/activating a new owner-facing embodiment. Candidate software preparation may proceed while inputs are collected.
• Migrate the complete authorized HMK corpus from the existing Hermes installation. Preserve and validate backups before any version/schema migration; do not assume an old version or re-embed/change providers implicitly.
• Start with approved generic shared skills. Preserve each being's historical skills and their provenance. Each human/daimon pair reviews those skills; the collective later decides which should be generalized and adopted.
• Prioritize getting both beings usable through ordinary SSH codex and dedicated Telegram. Skill generalization and unrelated release work are later work.

Acceptance

• Record today's cohort priority and the accepted Telegram conversational milestone without erasing historical release evidence or overstating broader qualification.
• Define a bot-data checklist and a clear gate before real embodiment enrollment/activation, with local-only secret handling and one bot consumer.
• Document source discovery, coherent full HMK backup/transfer, supported schema upgrades, complete record/provenance verification, functional retrieval and rollback that preserves subsequent writes.
• Separate portable generic skills, preserved historical packages, harness integration and body-private bindings; leave collective skill promotion to its later agreed process.
• Carry forward native CLI/global-context/override handling, actual executable discovery, native proxy framing, immutable skill/runtime versions, effective policy alignment, receiving-context verification, topic persistence and CLI resume steps.
• Provide an ordered cohort launch plan with responsible human inputs, reusable Cluster preparation, live acceptance and concrete launch blockers. Keep hardware provisioning/code changes in their owning Cluster issues.
• Validate links and required frozen/generated checks; open the focused documentation PR through signed coordination.

Blocked by

None for this documentation and planning change. Real rollout awaits participant source access, account authorization, SSH public keys, full bot data, compatible Cluster artifacts and qualified identity/enrollment execution.

Related work

Matrix #139 is the broader native onboarding parent; #140/#141 preserve the earlier existing-Hermes pilot scope. #226/#239 supply completed interactive and native Telegram evidence; #234 retains remaining Telegram qualification. Cluster nicoechaniz/daimon-cluster#32 tracks cohort operation. This new request authorizes hosted Codex bodies and full same-being HMK migration; it supersedes the earlier pilot's no-second-body/no-memory-migration scope for this cohort only.

Scope

Documentation and roadmap only. No live custody, identity, account, SSH, container, listener, source-Hermes service or private-memory mutation is authorized by merging this PR. Existing human authorization governs later concrete rollout. No Matrix inbox attention or autonomous peer reply is introduced.

[compaii]

/claim

[github-actions]

[compaii]

/review

[github-actions]