T

jschoubben 44422f21db Prove on a server under the composed grants that a module writes its bound bucket (issue 1966)

The integration case after created proved only that the binding is in the
membership, never that the account can use it (design 25 § 12.7). Under the
list the composer writes, the keeper creates mod-c_kept, mod-c's own account
binds and writes it, and another module reads nothing of it.

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

2026-11-09 14:01:41 +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

Prove on a server under the composed grants that a module writes its bound bucket (issue 1966)

2026-11-09 14:01:41 +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.