docs(measures): P6 — recall is 1.0 by construction, query cost is O(ops), compaction cannot help
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
docs(measures): memory O(parts), the mint-order trap, drain 530x, state gauges, benches in CI
Plus north-star P2-P5 landed and a 2026-10-08 session entry.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
wiki: the north-star distributed-registry direction, and P1 landed
Records EHDB as NoETL's distributed registry and control plane, with the inventory that
corrected three of my own prior claims: D8 is in the production crate rather than unwired,
vectors already exist rather than being a greenfield hard part, and four of the seven
capabilities are substantially built. The real gaps are watch, time-based leases, ephemeral
registration, secret-reference types and unsealed-tail replication.
States the distributed lower bound honestly: a coordination-free data path gives CALM-style
availability and NOT linearizable cross-shard reads, so "etcd semantics, distributed better"
is wrong. P7 (tail replication, still RF=1) and P8 (election + fencing) are named as the
hard parts rather than vectors or the registry.
P1 landed: wall-clock TTL liveness, with the upgrade hazard pinned -- a timestamp-less
record is unknown, not dead, because the alternative evicts the whole fleet on upgrade.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>