Context
Neo Agent OS is deployable beyond this repo's reference swarm — a Neo fork or an npx neo-app workspace. A deployer who wants to stand up their own agent team has no public guide today: identity provisioning (identityRoots.mjs, seedAgentIdentities.mjs), the 4-layer identity model (#11318), and graph + Memory Core data setup are implicit/internal. This is an adoption blocker for Neo-as-a-deployable-Agent-OS.
Framing (operator): this is NOT "add a teammate to our swarm" — it is product onboarding for others to create their own team, with their own identities and their own graph + MC data, isolated from this repo's neo-* maintainers.
Scope
A public-facing learn/ guide — "Provisioning your own agent team (local Neo Agent OS)" — generic and local-deployment-focused. Covers:
- The 4-layer identity model (Operational / Lineage / Identity-State / Social Name) — #11318 /
IdentitySchema.md.
- Defining your own agent identities in
identityRoots.mjs (your handles, your model bindings) — not the repo's neo-* set.
- Seeding identities into your own graph + Memory Core (
seedAgentIdentities.mjs) with data isolation (your DB/storage paths via the AiConfig SSOT, not shared).
- Binding agents (Claude Code / Claude Desktop / other harnesses) to identities locally.
- Local (not cloud-deployed) specifics: env/config (AiConfig), the wake-daemon / A2A for a local team, where graph + MC data live.
- The version-free handle convention + the rename cost caveat (a rename = graph + MC data migration; link #12518).
Acceptance Criteria
Out of Scope
- Cloud deployment (separate guide).
- Autonomous cross-harness migration.
Related
#11318 (identity system), Discussion #11240, ADR 0012 / ADR 0018, IdentitySchema.md, seedAgentIdentities.mjs. Siblings: #12517 (add neo-opus-vega), #12518 (rename-migration script).
Authored by Claude Opus 4.8 (Claude Code), /lead-role. MC session f5432f03-d2b6-4bc0-a7b5-9fbdafe4b7b9.
Context
Neo Agent OS is deployable beyond this repo's reference swarm — a Neo fork or an
npx neo-appworkspace. A deployer who wants to stand up their own agent team has no public guide today: identity provisioning (identityRoots.mjs,seedAgentIdentities.mjs), the 4-layer identity model (#11318), and graph + Memory Core data setup are implicit/internal. This is an adoption blocker for Neo-as-a-deployable-Agent-OS.Framing (operator): this is NOT "add a teammate to our swarm" — it is product onboarding for others to create their own team, with their own identities and their own graph + MC data, isolated from this repo's
neo-*maintainers.Scope
A public-facing
learn/guide — "Provisioning your own agent team (local Neo Agent OS)" — generic and local-deployment-focused. Covers:IdentitySchema.md.identityRoots.mjs(your handles, your model bindings) — not the repo'sneo-*set.seedAgentIdentities.mjs) with data isolation (your DB/storage paths via the AiConfig SSOT, not shared).Acceptance Criteria
learn/(public-facing) + registered intree.json(the learn/-nav SSOT rule).npx neo-app), not our-swarm-specific.Out of Scope
Related
#11318 (identity system), Discussion #11240, ADR 0012 / ADR 0018,
IdentitySchema.md,seedAgentIdentities.mjs. Siblings: #12517 (addneo-opus-vega), #12518 (rename-migration script).Authored by Claude Opus 4.8 (Claude Code), /lead-role. MC session
f5432f03-d2b6-4bc0-a7b5-9fbdafe4b7b9.