T

jschoubben e96f8fd1b6 The manifests, compiled-programs and composition rules judge facts in the checker's rules (issue 1921)

The running checker records the manifest validator's cases, each fetch's programs and the engines' answers as facts,
and the rules package judges them, with the notes it gives a reader, so the checking program judges every rule the
running checker judged. The module graph's cycle stays with the asking: its facts are whole manifests, over a run's
input bound; G's program reads them from the heads.

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

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

modules

The manifests, compiled-programs and composition rules judge facts in the checker's rules (issue 1921)

2026-11-06 22:31:22 +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.