T

jschoubben 6d60953f98 A running try names its asks and where each stands; build_usage says a seat's CPU-bound capacity

The checker wrote a try's asks only at its end, so a 31-minute try could not be told queued from
running (issue 1890). The try's record now names each ask as it is put, then the node that took
it, its state and the phase its step says, written on the step key's own changes. build_usage
names a running try's asks and takes a build module's capacity.<node> (configured bounded by its
node's build CPU, issue 1806's follow-up) when it is current with mesh-config.

2026-10-26 19:58:39 +01:00

modules

A running try names its asks and where each stands; build_usage says a seat's CPU-bound capacity

2026-10-26 19:58:39 +01:00

.gitignore

Commit no module's dependencies: fetch them in the check, the pinned SDK from beside it (issue 1235)

2026-10-19 15:27:37 +02: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.