ANNO-001: src-root anno index — one LSM map hashlet60→ron60 tagging worktrees, tickets and URIs

Now: OPEN

One unified way to tag worktrees, tickets and arbitrary URIs: an LSM multimap of wh128 rows at the SRC ROOT — key = hashlet60 of the canonical name (+ type4 LSB), val = a ron60 word (tag atom or a hashlet60 link to another URI, val nibble distinguishes). Reuses the existing wh-lane machinery (graf .graf.idx, ULOG sidecar, keeper LSM runs) — no new data structure. Since the Edwardian .be is a bare wtlog FILE (store elsewhere), the index forces .be/ to become a DIR; anno retraction needs generic wh-lane tombstones (mechanism open).

Input

Context

wh64 = off40|id20|type4, type4 in the LSB (bits 0–3, WHIFF_TYPE_MASK 0xf, dog/WHIFF.h); hashlet keys put the hashlet60 in the top bits (WHIFFKeyPack), wh128 = (key,val).
Anchor semantics today (be/core/resolve_hash.js ~57–66): a .be DIR = own store in .be/; a .be FILE = wtlog whose first row references the store. A src-root index means .be/ becomes a dir in the wtlog-only case — the anchor test must learn that a .be/ dir WITHOUT shards but WITH a wtlog row0 reference is still the Edwardian shape, NOT an own-store anchor.
Canonical keys exist: WHIFFHashlet60/HexHashlet60; name canonicalization is resolve_hash.js's job, nobody else's.
Tombstone constraint (gritzko): a tombstone must SORT byte- identical to the record it deletes. type4 sits in the key's LSB, so an in-row TOMB nibble changes the sort position (adjacent within the hashlet, not equal) — and bare wh64 set lanes have NO spare bits at all. No universal in-row bit layout exists.

Goals

anno add URI ron60 / anno get URI from jab (and later verbs): add/get ron60 annotations for any URI or hash — worktree tags, ticket status atoms, wt→ticket links — through ONE map.
Works in the store-elsewhere (Edwardian) worktree: the index lives at the src root under .be/, beside the wtlog, NOT in the remote store.

Constraints

Reuse the wh128 lane code (sort, k-way merge, run files); no second LSM implementation, no new record types beyond WHIFF.
ALL name→hashlet canonicalization through resolve_hash.js (and its native twin); no reimplemented URI handling anywhere.
LSM discipline: append runs, merge on read, compact; no in-place edits. C side in ABC style; any parsing via ragel.

WIP

Design decisions

Key = WHIFFKeyPack(type4, hashlet60(canonical name)); the canonical name is the resolve_hash.js-resolved URI (or the resolved sha for object-shaped targets: commit = sha hashlet60).
Val = wh64(ron60 word, nibble); nibble says atom (tag) vs link (hashlet60 of another URI) — a wt→ticket tag is just an edge row.
Multimap by construction; get = prefix scan over the key.
Lane choice: multimap annos ride the wh128 lane (full-pair Z); single-val-per-key LWW annos (e.g. a ticket's one status atom) ride the keyed kv64 lane once JS-121 un-defers it in abc.index.
.be/ dir-ification (gritzko's lean): the former .be file rows become the wtlog member inside .be/, anno runs sit beside it; exact member names need a ruling.
Tombstone proposal (pending verdict): RUN POLARITY — a negative run whose rows are byte-identical to the rows they kill; tombstone-ness lives in the run registry/header, so sorting is identical by construction and it works for bare wh64 sets and wh128 maps alike. Merge = newer-run-wins annihilation; a negative row reaching the bottom run evaporates.

TODOs

1. Rulings to request: .be/ member names + legacy-file migration story; anno write surface (a PUT/DELETE URI form vs a jab extension first); tombstone mechanism (negative runs vs per-run sidecar delete mask).
2. Anchor classification split out to BE-055 (.be/ dir for flat wts: the full dir⇒own-store site inventory + fix plan); blocked on it — the anno lane lands on the new anchor.
3. dog-side helpers: anno key/val pack (hashlet60-of-utf8 canon form, ron60 atom/link nibble) + table-driven tests; extend dog/WHIFF or a small dog/ANNO, update INDEX.md.
4. The lane: run files under .be/, append-a-run on write, k-way merged prefix scan on read, compaction; reuse the wh128 sort/merge; tests incl. crash-torn tail.
5. JS surface: abc.index-style binding + a jab anno extension (add/get); barewords resolve through the standard resolver.
6. First consumers: tag a worktree with its ticket (link row), ticket status atoms; a grep/list view over the map.
7. Anno retraction (delete) — blocked on the TODO-1 tombstone ruling; the generic wh-lane tombstone work then splits into its own DOG ticket serving keeper/graf/ULOG lanes too.

Blockers and bummers

Anchor reclassification touches repo discovery for EVERY verb — the JS and native resolvers must stay twins; smallest possible diff, end-to-end verified on all three clone shapes.
ron60 charset: tag atoms are RON base64 words (no dashes), so a ticket code like CI-001 needs an encoding convention.

Outcome

Open. Filed 2026-07-24 from the unified-tagging design chat; no code yet.