1.5 KiB
1.5 KiB
title, type, permalink, tags
| title | type | permalink | tags | ||||
|---|---|---|---|---|---|---|---|
| Review: Main vs Per-Repo Project Split Consistency | note | opencode-config/gates/review-main-vs-per-repo-project-split-consistency |
|
Review: Main vs Per-Repo Project Split Consistency
Verdict
- [decision] APPROVED — all instruction files consistently enforce the main/per-repo basic-memory project split #review #memory
Scope Reviewed
AGENTS.md— core memory system section- All 10 command files (
commands/*.md) - All 10 agent definition files (
agents/*.md) - All 3 skill files (
skills/*/SKILL.md) - Legacy
.memory.legacy/directory (confirmed non-authoritative) decisions/Memory System Main vs Per-Repo Project Split.md(migration decision note)
Key Findings
- [finding] Zero files instruct agents to store project-specific notes in
main— hard rule at AGENTS.md:32 is consistently enforced #confirmed - [finding] Session-start protocol is documented in 6 locations with consistent create-if-missing pattern #confirmed
- [finding] All
project="main"references correctly scope to cross-project reusable knowledge only #confirmed - [finding] No contradictions between any files — migration decision note lists all affected files, all verified updated #confirmed
- [finding] Minor precision gap: explorer.md and researcher.md use generic "relevant basic-memory project notes" without explicit project parameter guidance, but behavior is practically correct #suggestion
Relations
- related_to Memory System Main vs Per-Repo Project Split