T

jschoubben c4a8590671 W1.5, W1.6 (judge): a kept data's form is from 0 and its catch-up tool the module's own

The node agent calls a restored kept data's catch-up tool from the
restore point, so the judge refuses a form below 0 and a catch-up tool
the module does not declare; a foundation part keeps its new objects in
the old section with their cap and form (ADR 0619 §2).

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

Builds: design 47 G §295, §299

2026-11-11 14:39:10 +01:00

contracts

CT3 (answers): the catalog graph entry carries manifest-digest

2026-11-11 13:57:00 +01:00

modules

W1.5, W1.6 (judge): a kept data's form is from 0 and its catch-up tool the module's own

2026-11-11 14:39:10 +01:00

sdk

W5.10 (base): the module graph's node of a catalog entry is read in the domain SDK's graph, for every reader of the catalog half

2026-11-11 14:36:24 +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.