soma

Finish a PAI→Soma migration by placing PAI's imported life-OS content correctly: keep the Purpose compartment as a lean 4-field distillation, promote the rich imported categories (beliefs, mental models, decision frames, challenges, lessons) into Soma memory as recall-able notes, and protect the curated purpose.md from being clobbered. USE WHEN migrating from PAI, after `soma migrate pai`, or a fresh Soma install with imported PAI life-OS files under profile/imports/claude/.

Use when work should run through the Algorithm: current-state to ideal-state, VSA/ISC creation or refinement, effort tiers, seven-phase execution, verification-first planning, euphoric-surprise goals, substantial build/design/refactor/migration work, or explicit Algorithm requests.

Files-first assistant memory: durable notes (semantic/procedural), episodic session digests and action logs, a generated INDEX, deterministic consolidation, and a health audit. Use to remember a durable fact, recall what is known about a topic, log a session or action, run maintenance, or check memory-tree health. No LLM; every operation is a `soma memory` CLI call over markdown notes.

Portable Personal AI Assistant core. USE WHEN designing substrate-neutral assistant identity, memory, ISA, skills, learning, or adapters for Codex, Pi.dev, Claude Code, Cursor, or Grok.

Owns the Ideal State Artifact: the commitment-time scaffold for articulating done, deriving ISC criteria, planning features, recording decisions, and verifying work. Use for ideal state, VSA/ISC criteria, project specs, scaffolding, completeness checks, reconciliation, or seeding an VSA from a repo.

USE WHEN reproducing issue 86 — surfaces every claude-path rewrite class plus PAI Customization block.