Memory Keeping

memory-keeping

The pg-claude system is only as useful as its memory. STATE.md, coverage.md, and the sessions/ log are how a future Claude (or future you) picks up cold without re-reading the whole repo.

Invariants

1. STATE.md is the front page. It must answer in under a minute: what phase are we in, what's the last thing that got finished, what's the next concrete step. Keep it short — link to detail elsewhere.
2. coverage.md is a table. One row per documented artifact (subsystem, idiom, data-structure). Columns: name | path | last-verified-commit | confidence-summary | open-questions.
3. sessions/ is append-only. One file per significant session, YYYY-MM-DD-<topic>.md (use today's date, the day you're writing — not the date of the work if it spanned multiple days). Never edit old session logs; if a later session invalidates a claim, write a new session log that supersedes it and update STATE.md to point at the newer one.
4. files-examined.md is the per-file ledger. Append-only. One row per source file read in non-trivial depth, columns: path | depth (skim/read/deep-read) | date | last-verified-commit | produced-doc. Append whenever a file becomes load-bearing for any claim in knowledge/, including pure file-by-file deep reads that don't yet have a synthesis doc. (See CLAUDE.md rule 6: "Track what you read.")

When to update what

When you discover a wrong claim, fix the claim in the knowledge/ doc itself (the artifact) in the same session. The session log records the discovery; the coverage.md row gets its confidence-summary adjusted; STATE.md gets a one-line note pointing at the new session log. The old session log is never touched.

How to write a session log

≤ 50 lines is the target. Headings:

# <date> — <topic>

## What I did
Bullets, terse.

## What I learned
The 2–5 non-obvious things. Cite source files where applicable.

## What I'm unsure about
Honest list. Future sessions can pick these up.

## Pointers left for next time
Concrete next steps, in priority order.

How to update STATE.md

Edit, don't append. STATE.md has a fixed shape:

# pg-claude — current state

**Phase:** <Phase 0 / 0.5 / 1a / …>
**Last activity:** <date> — <one-line summary>
**Source commit at last verification:** <sha>

## Done
- bullets

## In progress
- bullets (usually one)

## Next
- 1–3 concrete next steps, in order

## Recent session logs
- `sessions/<file>` — one-line tag
- (keep ~5 most recent; older ones live only in the dir)

How to extend coverage.md

It is a markdown table. New rows go at the bottom unless you're reordering by priority. Don't delete rows — if a doc is retired, mark its row with status: retired and link to the replacement.

Things you must not do

• Don't write into STATE.md decisions that aren't actually decided (don't speculate forward).
• Don't conflate sessions/ entries with knowledge/ docs. sessions/ records the act of producing; knowledge/ is the produced artifact.
• Don't try to compact session logs by deleting old ones — they are the audit trail.

Cross-references

• .claude/skills/pg-claude/SKILL.md — master index; this skill keeps its progress/ pointers honest.
• .claude/skills/meta-commit-style/SKILL.md — STATE.md / coverage.md updates land via this commit style.
• .claude/skills/pg-implement/SKILL.md — R12 (end-of-implementation gate) explicitly invokes this skill.
• progress/STATE.md — the front page this skill maintains.
• progress/coverage.md, progress/files-examined.md — the per-artifact / per-file ledgers this skill appends to.
• Top-level CLAUDE.md — Rule 6 ("Track what you read") is the reason files-examined.md exists.