feat: DEV-LEDGER.md as shared operating memory + session protocol

The ledger is the one-file source of truth for "what is currently
true" across Claude/Codex/human sessions:

- Orientation (live SHA, main tip, test count, harness state)
- Active Plan (currently Codex's 8-day extractor + harness plan
  with hard gates and fail-early thresholds)
- Open Review Findings (P1/P2, status)
- Recent Decisions (bounded to last 20)
- Session Log (bounded to last 20)
- Working Rules (no parallel work, branching rule, P1 block)

Narrative docs under docs/ sometimes lag reality; the ledger does
not. Every session MUST read it at start and append a Session Log
line before ending.

AGENTS.md: added a new "Session protocol" section at the top that
points at the ledger. Applies to any agent (Claude, Codex, future).

CLAUDE.md (new, project-local): project instructions for Claude
Code in this repo. Points at DEV-LEDGER.md and AGENTS.md, spells
out the deploy workflow and the Claude/Codex working model.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-04-11 14:46:21 -04:00
parent b3253f35ee
commit 59331e522d
3 changed files with 192 additions and 0 deletions

30
CLAUDE.md Normal file
View File

@@ -0,0 +1,30 @@
# CLAUDE.md — project instructions for AtoCore
## Session protocol
Before doing anything else in this repo, read `DEV-LEDGER.md` at the repo root. It is the shared operating memory between Claude, Codex, and the human operator — live Dalidou SHA, active plan, open P1/P2 review findings, recent decisions, and session log. The narrative docs under `docs/` sometimes lag; the ledger does not.
Before ending a session, append a Session Log line to `DEV-LEDGER.md` covering:
- which commits you produced (sha range)
- what changed at a high level
- any harness / test count deltas
- anything you overclaimed and later corrected
Bump the **Orientation** section if `live_sha`, `main_tip`, `test_count`, or `harness` changed.
`AGENTS.md` at the repo root carries the broader project principles (storage separation, deployment model, coding guidance). Read it when you need the "why" behind a constraint.
## Deploy workflow
```bash
git push origin main && ssh papa@dalidou "bash /srv/storage/atocore/app/deploy/dalidou/deploy.sh"
```
The deploy script self-verifies via `/health` build_sha — if it exits non-zero, do not assume the change is live.
## Working model
- Claude builds; Codex audits. No parallel work on the same files.
- P1 review findings block further `main` commits until acknowledged in the ledger's **Open Review Findings** table.
- Codex branches must fork from `origin/main` (no orphan commits that require `--allow-unrelated-histories`).