# atlas — handoff

> Append-only, **newest first**. What the last session did, what the next should
> pick up, what is blocked. Read this second (after `brief.md`) when orienting.
> Clear-after-read: once an entry is acted on it can be trimmed.

## 2026-09-05 13:30 — session ended without a handoff entry

Left in flight (9 files changed). The next session should confirm whether
this work is finished before building on it:
- `CHANGELOG.md`
- `main/app/version.py`
- `main/frontend/package.json`
- `main/frontend/src/guide/content/Ch03Security.tsx`
- `main/frontend/src/guide/content/Ch00Start.tsx`
- `main/frontend/src/guide/content/Ch02Flow.tsx`
- `main/frontend/src/guide/content/Ch01Lab.tsx`
- `main/frontend/src/guide/diagrams/Layers.tsx`
- `main/frontend/src/guide/glossary.ts`

## 2026-09-05 — v0.2.0: the guide shipped
**Landed:** atlas created at `atlas.riverway.ca` (BW app, Pattern B, no DB);
the ten-chapter onboarding guide + glossary; file-backed section comments with
a discussion panel; membership gate; comments tests; deployed with the gate
green (tsc, backend suite, conformance pack, security audit).
**In flight:** nothing. adi is added as a `member`; rian is owner.
**Next:** (1) adi's first read-through — answer his comments in place
(`data/comments/guide/*.comments.md`, author `claude` when a session replies);
(2) the plans-index (see `.logs/planning/01-atlas-v1.md` §5).
**Watch:** the "suite today" table in chapter 7 names live projects — refresh
it when the suite changes.