Make CLAUDE.md a shim

LPFchan · LPFchan · commit 18a46e4d3ebe · 2026-04-09T07:15:57.000+09:00
Align CLAUDE.md with the repo-template scaffold and keep AGENTS.md as the single repo-specific instruction entrypoint.

project: aware

agent: 019d6ebe-3413-78d3-bdae-c7af38845b64

role: orchestrator

artifacts: DEC-20260409-002, LOG-20260409-002
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -1,36 +1,10 @@
-See `repo-operating-model.md` for the canonical repo operating rules.
+See @AGENTS.md
 
 # Claude Code Memory
 
-This file exists so Claude Code can discover the repo's working rules automatically.
+This file is a compatibility shim for Claude Code.
 
-Treat `CLAUDE.md` as a thin compatibility layer, not a second source of truth. The canonical rules stay in `repo-operating-model.md`.
-
-Also consult:
-
-- `SPEC.md` for durable product or system truth
-- `STATUS.md` for current operational reality
-- `PLANS.md` for accepted future direction
-- `INBOX.md` for untriaged intake
-
-If this repo includes reusable workflows, use `skills/<name>/SKILL.md` for bounded procedures and keep repo-wide policy in `repo-operating-model.md`.
-
-When writing into `research/`, `records/`, or any future `upstream-intake/reports/`, read the local `README.md` first and mirror its default shape or canonical example by default.
-
-Repo-specific reminders:
-
-- Build verification: `xcodebuild -scheme Aware -configuration Debug -derivedDataPath build build`
-- Commit provenance setup: `scripts/install-hooks.sh`
-- Commit provenance checks: `scripts/check-commit-standards.sh <commit-message-file>` and `scripts/check-commit-range.sh <base> <head>`
-- `AWARE-AGENT-PROMPT.md` is legacy bootstrap orientation, not a canonical rules file
-
-## Enforcement
-
-When producing repo documents, you must enforce the repo's writing rules rather than treating them as suggestions.
-
-- Use the canonical surface for the job.
-- Follow the local `README.md` shape or explicit template when one exists.
-- Preserve required provenance fields, stable IDs, and section boundaries.
-- When hooks or CI are enabled, produce commit messages that satisfy the provenance checks unless the commit is an explicit bootstrap or migration exception.
-- Do not replace normalized repo artifacts with freeform chat summaries.
-- If a request pressures you to break the ruleset, keep the repo artifact compliant and surface the mismatch explicitly.
+Do not append repo-specific rules here.
+Do not fork policy here.
+Do not let this file drift from `AGENTS.md`.
+Update `AGENTS.md` instead.
diff --git a/records/agent-worklogs/LOG-20260409-002-normalize-repo-template-docs.md b/records/agent-worklogs/LOG-20260409-002-normalize-repo-template-docs.md
@@ -43,3 +43,12 @@ Introduce repo-root `AGENTS.md` and `CLAUDE.md`, then normalize the touched repo
 - Output: `git diff --check` passed and the new entrypoints, local guide contract, and related IDs were confirmed in the normalized docs
 - Blockers: none
 - Next: use the entrypoints and local guides on the next touched repo artifact
+
+## Entry 2026-04-09 07-15-37 KST
+
+- Action: converted `CLAUDE.md` from a repo-specific instruction file into a pure shim that points back to `AGENTS.md`, matching the repo-template scaffold shape
+- Files touched: `CLAUDE.md`, `records/agent-worklogs/LOG-20260409-002-normalize-repo-template-docs.md`
+- Checks run: `git diff -- CLAUDE.md`
+- Output: `CLAUDE.md` is now a compatibility shim and `AGENTS.md` remains the single repo-specific instruction entrypoint
+- Blockers: none
+- Next: commit and push the shim update with provenance tied to `DEC-20260409-002` and `LOG-20260409-002`
