ck-maplisted

# Mapping the session ## Render ```bash ck render sessions/<slug>.ck.json --label map ck render sessions/<slug>.ck.json --label rewind --at 7 # a past position ``` If the canvas isn't up, or `.ck/viewer/state/server-stopped` exists: ```bash ck view --open ``` Restarting reuses the state directory, so an already-open tab reconnects on its own — the page shows `paused` while the server is down and reloads when it returns. Always give the URL **with its `?key=…`**. ## Report The render prints metrics as JSON. Turn them into an assessment, not a recitation — the user can see the numbers on screen. What they can't see is what the numbers mean. Cover four things: 1. **Where the design stands** — open leaves, conjunctions, refutations. 2. **The shape of the tree** — is it broad and shallow (many framings, none pursued) or narrow and deep (one framing, over-committed)? Both are pathologies, and they need opposite corrections. 3. **The C/K balance** — has K moved recently? The operator sequence printed by `ck.cjs show` answers this directly. A run of `C→C` events with no `K→K` between them means the tree is expanding on ground nobody can check; a session with no `K→C` at all means knowledge never fed back into the concepts. 4. **The single next operator you'd run**, with a reason. One recommendation, not a menu. ## Reading the history Two questions the log answers that the tree cannot: - **Where did the reasoning turn?** Fold to a few positions and compare