T

jschoubben e79a546eb7 Compose what runs from the haves while the wants view is unanswered (issue 1966, recovery)

Since 16:39 the running assigner cannot answer its wants page within a call's
bound, and the failed wants read held the whole user list, so no new build got
its credential. As the assignments view already does, an unanswered wants view
now composes what runs from each have's fingerprint, is said as a gap that is no
failed read, and keeps the pass to one that only adds (keepsLoaded), so the list
is held only where it would take from a loaded user.

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

2026-11-08 23:29:26 +01:00

contracts

The domain SDK carries the run ask's rules and the checker's client asks a program's input (issue 1921, milestone 47/G D2)

2026-11-07 02:35:31 +01:00

modules

Compose what runs from the haves while the wants view is unanswered (issue 1966, recovery)

2026-11-08 23:29:26 +01:00

sdk

The assigner and the indexer's hold count a bootstrapped seat as read (issue 1966)

2026-11-08 03:53:11 +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.