← Session 3 — Project kickoff: RH blueprint, staged workflow + archive design
Archive is installed and committed (`91d93db`). Here's what you now have:
## What was built
**Resume system**
- `STATE.md` — read first every session; always ends with an explicit `NEXT ACTION:` line (currently: Phase 0.1).
- `research/journal/session-NNN.md` — full narrative log per session.
**Research artifacts**
- `research/results/` — one file per result with honesty tag, proof, dependencies, adversarial review, and paper-section pointer. Ledger in `index.md`.
- `research/graveyard/` — one file per dead end (attempt, precise obstruction, lesson, salvage).
- `research/derivations/` — worked calculations/reproductions.
- `research/paper/draft.tex` + `references.bib` — living LaTeX paper, assembled only from tagged result files.
**Numerics (dual storage, as you asked)**
- Every experiment writes both a `CSV + JSON` sidecar pair (human-readable, paper-ready, with git hash, parameters, precision, checksum) **and** a row in `research/research.db` (SQLite) — queryable across sessions, e.g. "all experiments using ψ_MT at T=10⁴".
- `research/numerics/scripts/db.py` — CLI to init/log/list; `schema.sql` holds the 5-table catalog (sessions, results, graveyard, derivations, experiments).
**Safety nets**
- Local git repo, everything committed; `.gitignore` excludes `.venv` and LaTeX build junk.
- Protocol is written into NGUYEN.md §8: artifacts saved **immediately** when produced (crash-safe), STATE.md updated **last**, commit at session end — so even a power cut mid-stage loses at most the current thought.
You can shut down safely at any point. Next session, I (or any instance) read `STATE.md` → `NGUYEN.md` §8 and resume at Phase 0.1 without touching anything already done.
Ready to begin Phase 0.1 (parsing Notes.txt into the quantum-formalism index) whenever you are.
raw content_json (database row)
[{"type":"text","text":"Archive is installed and committed (`91d93db`). Here's what you now have:\n\n## What was built\n\n**Resume system**\n- `STATE.md` — read first every session; always ends with an explicit `NEXT ACTION:` line (currently: Phase 0.1).\n- `research/journal/session-NNN.md` — full narrative log per session.\n\n**Research artifacts**\n- `research/results/` — one file per result with honesty tag, proof, dependencies, adversarial review, and paper-section pointer. Ledger in `index.md`.\n- `research/graveyard/` — one file per dead end (attempt, precise obstruction, lesson, salvage).\n- `research/derivations/` — worked calculations/reproductions.\n- `research/paper/draft.tex` + `references.bib` — living LaTeX paper, assembled only from tagged result files.\n\n**Numerics (dual storage, as you asked)**\n- Every experiment writes both a `CSV + JSON` sidecar pair (human-readable, paper-ready, with git hash, parameters, precision, checksum) **and** a row in `research/research.db` (SQLite) — queryable across sessions, e.g. \"all experiments using ψ_MT at T=10⁴\".\n- `research/numerics/scripts/db.py` — CLI to init/log/list; `schema.sql` holds the 5-table catalog (sessions, results, graveyard, derivations, experiments).\n\n**Safety nets**\n- Local git repo, everything committed; `.gitignore` excludes `.venv` and LaTeX build junk.\n- Protocol is written into NGUYEN.md §8: artifacts saved **immediately** when produced (crash-safe), STATE.md updated **last**, commit at session end — so even a power cut mid-stage loses at most the current thought.\n\nYou can shut down safely at any point. Next session, I (or any instance) read `STATE.md` → `NGUYEN.md` §8 and resume at Phase 0.1 without touching anything already done.\n\nReady to begin Phase 0.1 (parsing Notes.txt into the quantum-formalism index) whenever you are."}]