forked from bchanot/claude
feat(memory): introduce .claude/{tasks,memory,audits}/ governance layout
Move tasks/ into .claude/tasks/ and create .claude/memory/ with 5 persistent registries (decisions/learnings/blockers/journal/evals) plus .claude/audits/ for audit reports. Also seed templates/memory/ for onboarder to copy into user projects. - tasks/TODO.md, tasks/rtk-upstream-issue.md → .claude/tasks/ - tasks/LESSONS.md deleted (empty template; superseded by learnings.md) - .claude/memory/: 5 append-only registries with YAML schema + seed entries - templates/memory/: 5 empty-index templates for new projects Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.7
parent
6f5f4fe5b5
commit
892de288fe
@@ -0,0 +1,35 @@
|
||||
---
|
||||
type: evals_registry
|
||||
entry_prefix: EVAL
|
||||
schema:
|
||||
id: EVAL-XXX
|
||||
date: YYYY-MM-DD
|
||||
output: string (what was produced)
|
||||
method: string (how it was evaluated - manual read, test, benchmark, user feedback)
|
||||
anomalies: list of strings (what was wrong, missing, surprising)
|
||||
action: [keep | correct | deprecate]
|
||||
rules:
|
||||
- Log an eval whenever you validate the quality of something Claude produced (report, audit, plan, generated code).
|
||||
- Action keep - the output is fit for purpose as-is.
|
||||
- Action correct - needs revision; capture what.
|
||||
- Action deprecate - the approach itself is flawed; link to the decision that replaces it.
|
||||
---
|
||||
|
||||
# Evals registry (EVAL)
|
||||
|
||||
## Index
|
||||
|
||||
| ID | Date | Output | Action |
|
||||
|----|------|--------|--------|
|
||||
|
||||
<!-- Append entries below. Template:
|
||||
|
||||
## EVAL-XXX - <output>
|
||||
|
||||
- **Date** : YYYY-MM-DD
|
||||
- **Output** : <ce qui a été produit>
|
||||
- **Méthode** : <comment cela a été évalué>
|
||||
- **Anomalies** : <ce qui est faux, manquant, surprenant>
|
||||
- **Action** : keep | correct | deprecate
|
||||
|
||||
-->
|
||||
Reference in New Issue
Block a user