wesandClaude Opus 5
898c942f95
The banner draws all 9,194 chunks in one flat colour. `nodes.book` was in the
payload but only ever reached the tooltip, so nothing on screen said which book
or which region you were looking at.
This adds /reading: the same corpus at the pre-flight's 15/0.1 instead of the
banner's 50/0.8, coloured by kind of book, with any single title isolatable.
The two projections are NOT interchangeable, and that is why this is a separate
page rather than a mode of the banner. 50/0.8 was chosen *because* it blurs book
territory into something that reads as a cloud; showing that territory is the one
thing this page exists to do.
Renderer notes:
• Explorer mode turns on only when the payload actually carries a `kind`
layer, not when the caller asks for it — a page pointed at the banner's
file degrades to the flat cloud instead of throwing.
• Smaller and denser points (0.032/0.62 vs 0.055/0.3). Three hues piling up
in one volume average toward grey; that pairing is what keeps each one's
hue, and it is not cosmetic.
• Isolation dims to 8.5% rather than hiding. Against an empty frame you learn
where a book's chunks are and lose the only question worth asking, which is
where they sit relative to everything else.
• `nebulaBase` keeps a pristine copy of the vertex colours; dimming from an
already-dimmed buffer compounds and the cloud would fade on every hover.
Kind colours are slots 1-3 of the validated categorical palette, checked
ALL-PAIRS against this file's own #0b0d12 — a point cloud has no series order,
so the adjacent-pairs default that suits stacks and lines is the wrong test.
Worst pair CVD dE 9.4, worst normal-vision dE 20.9.
⚠️ `--map-kind-narrative` (aqua) sits near `--map-trace` (the garden green).
Tolerable only because form separates them absolutely — diffuse points versus
one continuous line — and nothing is encoded by the similarity. If the trace
ever becomes points, re-measure that pair.
The payload is gitignored for the same reason the banner's is: a tracked
generated file dirties the tree and breaks the `git pull` at the top of every
build tick. auto-build.sh's signature now watches both, or a corpus change
would rebuild one page and leave the other on yesterday's cloud.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
22 lines
827 B
Plaintext
22 lines
827 B
Plaintext
node_modules/
|
|
dist/
|
|
.astro/
|
|
public/assets/
|
|
# notebook exports are build artifacts: tracking them would make every
|
|
# export dirty the tree, which flips the auto-build signature and breaks
|
|
# the git pull at the top of every build tick
|
|
notebooks-export/
|
|
public/nb/
|
|
# the reading map is the same kind of artifact: library-rag-export.service regenerates it on
|
|
# cyrion whenever the corpus or its located highlights move. It was tracked until 2026-08-14,
|
|
# which is why automating the export needed this line first.
|
|
public/reading_umap.json
|
|
# the /reading explorer's payload — same generator, same timer, different projection
|
|
# (`export.py --explorer`, 15/0.1 plus the kind and section layers). Tracking it would dirty
|
|
# the tree exactly as above.
|
|
public/reading_explorer.json
|
|
.build_state
|
|
.build.lock
|
|
.notebooks.lock
|
|
.rebuild.log
|