f288270513b203143c0b5dae0e7ef11e9f99b10e
Design 47 *Each part acts on its own entries* and *Every part takes a first view, then follows the events*: the builder reads its placements through the seat mesh-wants' view, never the assigner's state. The seat's client gets Placed over assignment graph revisions (ADR 0625 §4: the logic the gate's three callers share), and the gate a Revision feed; the first revision settles it, a pair new in a later one stands since that revision's time, as the state's write time did (issue 1940). Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ Builds: design 47 G §348, §195, §200
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.
Description
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
31 MiB
Languages
Go
99.2%
JavaScript
0.8%