c-00-initialize-memory-repo

name	c-00-initialize-memory-repo
description	Initialize or repair the Agents Remember memory root for a target repository. Defaults to repo-local internal memory; creates an external memory repo only when the developer explicitly asks for external memory.

c-00-initialize-memory-repo Initialize Memory Repo

Create the minimal memory root required before onboarding or task workflows can use Agents Remember for a target repository.

This skill initializes durable repo memory through MCP memory_init. It does not install the coordinator runtime, expose harness skills, create task worktrees, or generate onboarding content. Request MCP runtime_install for coordinator runtime installation, MCP skills_install for harness skill exposure, and c-03-repo-bootstrap after this scaffold exists when the developer wants onboarding content generated.

Use c-08-ar-coordination-context-resolver to inspect an existing repository's active context. This skill creates or repairs missing memory scaffolding; it does not replace the c-08-ar-coordination-context-resolver skill as the normal resolver.

Inputs

• repo_id: configured MCP repository ID whose memory is being initialized. This is the normal installed runtime input.
• code_repository_root: root directory of the code repository whose memory is being initialized. Use this only for conceptual review or source-debugging; normal installed runtime calls identify the configured repository by repo_id.
• topology: internal by default. Use external only when the developer explicitly asks for an external memory repo.
• coordination_root: supplied by MCP settings for normal installed runtime calls.
• mode: create-missing by default. Use repair only when the developer explicitly asks to fix existing memory scaffold files.

MCP Tools

Use the Agents Remember MCP setup tools as the normal installed runtime entry points:

Preview first. These setup tools now apply by default (dry_run defaults to false). For any effectful run, call once with dry_run=true to inspect the plan, confirm it, then run the real apply (omit dry_run).

memory_init(repo_id="<repo-id>", dry_run=true, initialize_git=true)   # preview
memory_init(repo_id="<repo-id>", initialize_git=true)                 # apply
runtime_install(include_benchmarks=false, install_provider_deps=false)
skills_install(overwrite=true)

Use memory_init for creating or repairing the configured memory root for a repo. Use runtime_install only when the coordinator runtime scaffold itself is missing or stale. Use skills_install only when the registered harness skill root needs to be refreshed. The skill tree is instruction-only; installed and development workflows use the MCP/package route.

Safety Rules

1. Never overwrite an existing memory file without explicit user approval.
2. Create missing directories and files only.
3. Keep starter files generic; do not invent project-specific tools, docs, sources, or onboarding.
4. If the resolved memory root or coordination root points outside the intended workspace, state the resolved absolute path before writing.
5. Default internal scaffolding must not create or select an external memory repo.
6. External-memory setup must not install coordinator runtime files; if the coordinator runtime is missing, tell the developer to request MCP runtime_install first.
7. Do not create onboarding content. An empty onboarding/ directory is enough for the c-08-ar-coordination-context-resolver skill to resolve the memory root; the c-03-repo-bootstrap skill owns onboarding generation.

Procedure

1. Resolve The Memory Root

Default internal memory:

1. Resolve code_repository_root.
2. Set memory_root to <code_repository_root>/ar-memory.
3. Do not resolve or create an external memory repo.

Explicit external memory:

1. Resolve code_repository_root.
2. Resolve coordination_root from the developer-provided path or the installed runtime root.
3. Verify the coordinator runtime exists by checking for:

<coordination-root>/AGENTS.md
<coordination-root>/skills/
<coordination-root>/tasks/
<coordination-root>/memory-repos/

4. If the runtime is missing, stop and ask the developer to request (preview first with runtime_install(dry_run=true)):

runtime_install()

5. Set memory_root to <coordination-root>/memory-repos/ar-<code-repository-name>.
6. Initialize the external memory root as a Git repository when it is newly created or when it exists without .git.

2. Inspect Existing State

Check for these paths under the resolved memory root:

system/settings.md
system/settings.json
system/sources.md
system/tools.md
onboarding/
docs/

For external memory, also check:

.git/

Report which are present and which are missing. If everything exists, stop with a clean summary.

3. Create Missing Directories

Create only missing directories:

<memory-root>/
  system/
  onboarding/
  docs/

For external memory, ensure <coordination-root>/memory-repos/ exists before creating the per-repo memory root. Do not create or modify coordinator runtime directories such as skills/, tasks/, worktrees/, notes/, or temp/.

When creating an external memory Git repository, add docs/.gitkeep if docs/ would otherwise be empty so the scaffold can be committed.

4. Create Missing Starter Files

Create only files that do not already exist.

system/settings.md

# Settings

This memory root stores durable context for Agents Remember.

Use this Markdown file for human and agent instructions, scaffold notes, and operational context. Machine-readable storage, path-rule, and cross-repo settings live in `system/settings.json`.

Do not duplicate active `pathRules` here as the authoritative machine source when `system/settings.json` exists.

## Scaffold

| Layer         | Location               | Purpose                                                     |
| ------------- | ---------------------- | ----------------------------------------------------------- |
| instructions  | `system/settings.md`   | Human and agent guidance, path contract, and scaffold notes |
| path settings | `system/settings.json` | Machine-readable storage, pathRules, and cross-repo data    |
| sources       | `system/sources.md`    | External and domain documentation registry                  |
| tools         | `system/tools.md`      | Repo-specific commands, checks, and local tool notes        |
| onboarding    | `onboarding/`          | Durable repo and file-level code commentary                 |
| docs          | `docs/`                | Local domain docs, mirrors, and reference material          |

system/settings.json

For internal memory:

{
  "version": 1,
  "onboarding": {
    "storage": {
      "mode": "repo-sidecar"
    },
    "pathRules": {
      "include": {
        "paths": ["README.md", "docs/**", "src/**"],
        "fileTypes": [".md", ".py", ".ts", ".tsx"]
      },
      "exclude": {
        "paths": [
          "node_modules/**",
          "vendor/**",
          "dist/**",
          "build/**",
          "coverage/**",
          ".cache/**",
          ".pytest_cache/**",
          ".venv/**",
          ".idea/**",
          ".vscode/**",
          ".env",
          ".env.*",
          "**/generated/**",
          "**/*.generated.*",
          "**/*.Zone.Identifier",
          "**/*:Zone.Identifier"
        ],
        "fileTypes": [".png", ".jpg", ".zip"]
      }
    }
  },
  "crossRepo": {
    "allow": []
  }
}

For external memory:

{
  "version": 2,
  "onboarding": {
    "storage": {
      "mode": "memory-repo"
    },
    "pathRules": {
      "include": {
        "paths": ["README.md", "docs/**", "src/**"],
        "fileTypes": [".md", ".py", ".ts", ".tsx"]
      },
      "exclude": {
        "paths": [
          "node_modules/**",
          "vendor/**",
          "dist/**",
          "build/**",
          "coverage/**",
          ".cache/**",
          ".pytest_cache/**",
          ".venv/**",
          ".idea/**",
          ".vscode/**",
          ".env",
          ".env.*",
          "**/generated/**",
          "**/*.generated.*",
          "**/*.Zone.Identifier",
          "**/*:Zone.Identifier"
        ],
        "fileTypes": [".png", ".jpg", ".zip"]
      }
    }
  },
  "crossRepo": {
    "allow": []
  }
}

onboarding.storage decides where eligible onboarding artifacts live. onboarding.pathRules decides which source paths and file types are eligible for onboarding. Cross-repo policy belongs in the memory layer, not in untracked coordinator runtime files.

system/sources.md

# Sources

## Domain Documentation

No domain documentation configured yet.

Add project-specific docs, local mirrors, API references, and canonical source links here before creating durable onboarding that depends on external behavior.

## External References

No external references configured yet.

## Notes

- Prefer local mirrors for reading when available.
- Link onboarding `Docs References` rows to canonical source URLs when a canonical online reference exists.
- If no relevant domain documentation exists for a task, record what was checked instead of implying the search space was complete.

system/tools.md

# Tools

## Checks

No repo-specific checks configured yet.

Add test, lint, typecheck, build, and smoke-check commands for each onboarded repo.

## Commands

No repo-specific commands configured yet.

## Runtime Notes

Record environment setup, local service assumptions, MCP notes, and command caveats here.

5. Report Result

Summarize:

• resolved topology
• resolved memory root
• resolved coordination root when external memory is used
• whether an external Git repository was initialized
• directories created
• files created
• files left untouched
• next suggested skill, usually c-03-repo-bootstrap when the developer wants onboarding content under the resolved onboarding root

Common Outcomes

Fresh Internal Memory

Expected result: create <code-repository-root>/ar-memory/ with system/, onboarding/, and docs/, then tell the developer the repo is ready for optional repo bootstrap.

Fresh External Memory

Expected result: create <coordination-root>/memory-repos/ar-<repo-name>/, initialize Git if needed, add system/, onboarding/, and docs/, then tell the developer the repo is ready for optional repo bootstrap.

Partial Memory Scaffold

Expected result: create only missing files or directories. Preserve existing docs/, system/, and onboarding content.

Existing Complete Memory Scaffold

Expected result: make no changes and report that the memory root is already initialized.