T

jschoubben ad561e485f FB7, FB8: the forge bridge asks its findings state and finding stream in the template form

The manifest's requires gain findings (state, history 5) and finding-events (events, 7 days,
16 MiB) and its consumes mesh-conditions.findings-asked, as every part but a foundation part
declares them; the bridge gains the finding branch-unprotected (next commit).

Builds: design 47 G §387, §529, §383
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-12 09:21:51 +01:00

modules

FB7, FB8: the forge bridge asks its findings state and finding stream in the template form

2026-11-12 09:21:51 +01:00

.gitignore

SD5, BG11, BLD10: the build modules' shared code moves into the delivery SDK

2026-11-12 05:18:34 +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.