T

jschoubben 5d33692d7f Assigner: the pass keeps an assignment graph revision per catalog revision taken in, first

The pass computes the assignment graph revision (assigngraph.Compute) from the catalog halves it follows, the placements,
the first branch of each registration and each node's capability reading, keeps it in the objects assignment-revisions
through a bus adapter modelled on the indexer's, says assignment-revision, and holds the kept revision and its catalog
source for the wants.

Builds: design 47 G A-67, §292, G-5 "the wants follow the trunk's assignment graph"

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-11 23:04:14 +01:00

contracts

Contract: the seat mesh-wants' wanted is said per node and module, kept last per subject

2026-11-11 22:57:31 +01:00

modules

Assigner: the pass keeps an assignment graph revision per catalog revision taken in, first

2026-11-11 23:04:14 +01:00

sdk

SD4 (step key parser): ParseStepKey reads both forms and answers the asker

2026-11-11 20:36:06 +01:00

.gitignore

Nodes compose: placement from the catalogue, node records, self wants, own and pair credentials, core boxes and the authority from the vault (issue 1126)

2026-10-26 19:30:18 +01:00

README.md

Begin mesh-delivery with its README and its own check (ADR 0428)

2026-10-18 16:07:25 +00:00

README.md

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.