T

jschoubben b30232298c D4 judge-foundation-list: the parts G puts on the foundation list keep their old sections before it

Before G's merge the foundation list stays as it is; the forge module, the image registry module and the node-engine's
module are accepted with their old `objects` section, their stream `<module>-findings` and their bus state in
`requires`, as G's judge accepts them, and are counted as today, so no other module's verdict moves.

Builds: design 47 G §584, §627, §529, A-343, A-345

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

2026-11-13 11:45:26 +01:00

contracts

F8, dropped: the Drop layout is the generated contracts' (not the domain SDK's) and the key form sits beside Pause's helpers; a step ended by drop is the state dropped (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:40:29 +01:00

modules

D4 judge-foundation-list: the parts G puts on the foundation list keep their old sections before it

2026-11-13 11:45:26 +01:00

sdk

1966 review round 1: Composed counts the bindings written or rewritten from fields; wrap Take's comment

2026-11-11 14:12:25 +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.