User-Level Project Memory

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

AIWG can keep private project memory outside a repository under the operator's AIWG home. This avoids git noise from personal agent memory while preserving the same effective `.aiwg` layout used by project-local AIWG artifacts.

Layout

User-level project memory is rooted at:

~/.aiwg/projects/
  manifest.json
  index/
    manifest-index.json
  <project-id>/
    .aiwg/
      aiwg.config
      memory/
      index/
      artifacts/

`manifest.json` records each registered project's stable id, display name, workspace roots, git remotes, metadata, and private `.aiwg` memory root. The `index/manifest-index.json` sidecar maps project ids, workspace roots, and git remotes to manifest entries so AIWG can resolve the active project without scanning every memory directory.

Commands

Register the current workspace:

Use AIWG to complete this documented outcome: Register the current workspace
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Inspect and resolve:

Use AIWG to complete this documented outcome: Inspect and resolve
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Maintain mappings:

Use AIWG to complete this documented outcome: Maintain mappings
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

All commands accept the json option for automation.

Resolution Order

Memory storage resolves in this order:

1. Explicit `.aiwg/storage.config` memory root or backend. 2. Project-local `.aiwg/memory` when the active workspace has a `.aiwg` directory. 3. Registered user-level project memory under `~/.aiwg/projects/<id>/.aiwg` when the active workspace path or git remote matches the manifest. 4. Default project-local `.aiwg/memory`.

This keeps reviewed project-local AIWG artifacts authoritative. User-level memory is best for private, per-operator context that should not be committed. Use project-local `.aiwg` when the memory or artifact must be shared, reviewed, or reproduced by collaborators.

Repository Pollution

Private memory roots live outside the checkout, so registering a project does not modify the target repository or require repository-specific `.gitignore` rules. The memory contents still use the normal `.aiwg` subdirectories, which lets existing storage commands and memory tools work with the relocated root.