T

jschoubben 9290cdda4d The checking program judges the module graph's cycles from the edges the running checker gathers (issue 1921, B0 review round 1)

ADR 0656 §5 has every check judged by parts built from the change's heads, and no record keeps the cycle rule in the
running checker. The facts carry each ordering edge's two modules and kind, never manifests: the whole catalogue's
graph is 50 edges, 3195 bytes.

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

2026-11-06 23:28:20 +01:00

modules

The checking program judges the module graph's cycles from the edges the running checker gathers (issue 1921, B0 review round 1)

2026-11-06 23:28:20 +01:00

sdk

The trunk's manifest validator is built without a group's heads; the package function's tests fold into existing ones (issue 1921)

2026-11-06 01:51:23 +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.