mfowler
170a3e35cd
- memory/ now lives in the repo and is git-tracked; the harness memory path (~/.claude/.../memory) is a symlink to it so writes still land here - AGENTS.md: document memory-in-repo, always-commit-and-push, operator-driven (no sweep), and the one-directional rule Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
13 lines
799 B
Markdown
13 lines
799 B
Markdown
---
|
|
name: memory-in-repo
|
|
description: All memory files live in the PO repo (memory/) and are git-tracked, not under ~/.claude
|
|
metadata:
|
|
type: feedback
|
|
---
|
|
|
|
All memory files must be written **inside the PO repo** at `memory/` and tracked via git — not left under `~/.claude`.
|
|
|
|
**Why:** the operator wants memory versioned and reviewable alongside the repo (stated 2026-06-14).
|
|
|
|
**How to apply:** write memory files to `/home/loops/project-orchestrator/memory/`. The harness's expected memory path (`~/.claude/projects/-home-loops-project-orchestrator/memory`) is a **symlink** to that in-repo dir, so the usual Write-to-the-harness-path flow still lands files in the repo. After writing/updating any memory file, commit and push (see [[always-commit-and-push]]). Noted in the repo's `AGENTS.md`.
|