Aise setup

PhysisAI Setup

Core Boundary

Treat Codex and Claude as already capable. Configure only the personal preferences, private or project knowledge, proven workflows, tool routes, and quality gates they cannot reliably infer. Do not offer model training, a replacement agent, role editions, or automatic production-rule mutation.

Setup Workflow

1. Locate the project root and check whether physisai is already on PATH.
2. If missing, install the released engine in an isolated tool environment:

uv tool install "git+https://github.com/jiayx01/[email protected]"
physisai --version

Use the equivalent pipx install command only when uv is unavailable. Ask before replacing an existing user-wide installation. 3. Resolve the user store from AISE_HOME; when unset, use ~/.aise. Keep it outside the project root. The CLI rejects overlapping user and project roots. 4. Install the matching host plugin when it is not already installed. Do not install an unrelated host adapter. 5. Initialize the target project with one or both adapters:

physisai init --root <project-root> --adapter codex
# or: physisai init --root <project-root> --adapter claude-code

6. Run physisai doctor --root <project-root> and physisai verify --root <project-root>.
7. Confirm .ai-self-evolution/ was added to the existing .gitignore without removing other rules, and confirm both event stores use private filesystem permissions.
8. Confirm the adapter installed exactly one managed loader block while preserving existing content: Codex uses AGENTS.md; Claude Code uses CLAUDE.md.
9. Confirm .ai-self-evolution/generated/index.md exists and reports no approved active memory in a new project. No empty global/ or project/ category files should be created.
10. Run physisai context --root <project-root> --query "initial setup check" and confirm a new project contains operating rules only, not invented personal memory.

Existing Projects

• Do not overwrite an existing .ai-self-evolution directory.
• Use physisai status, physisai verify, and physisai doctor before changing adapters.
• Add an adapter or change the context budget with physisai configure; do not rerun physisai init.
• Run physisai doctor --repair after upgrading from v0.3 to build the Markdown index and layered detail files from existing events. Older v0.2 profile configuration is still upgraded without rewriting historical events.
• Remove only managed host blocks with physisai detach; this preserves both event stores.
• Preview v0.1 project-global migration with physisai migrate. Apply it only after the user approves widening those memories to the user layer.
• Never import whole chat histories by default. Start from explicit corrections, confirmed preferences, verified private knowledge, or repeatable workflows.
• Keep private events, generated context, indexes, and detail files out of the public repository unless the user explicitly chooses otherwise.

Completion

Report the project root, user-store path, adapter file status, private-state ignore status, permission checks, both event-chain results, generated-index health, and task-context command. Do not claim setup succeeded from file creation alone; use the real CLI results.