L3 final: what a manifest reads and needs, the reader-capability baseline, the node record's manifest-reads (ADR 0614, issue 774) #166

Merged

mesh-tools merged 2 commits from feat/l3-final into main 2026-11-04 00:23:38 +00:00

Conversation 2 Commits 2 Files Changed 11

+832 -10

2 Commits

Author	SHA1	Message	Date
jschoubben	85ba0a9a70	A node record states the reader capabilities its engine reads, a module value the ones its manifest needs, and a want of rule 9 or 10 reads (ADR 0614 §2, §4, issue 774) ... NodeRecord.ManifestReads (`manifest-reads`) and Module.Needs (`needs`) are additive at Version 1, read leniently by every running part. checkRule takes 1 to 10 so a later release may number the verb wait and the capability hold; nothing writes 9 or 10 in this one. kept_until_delivered.go stays: this release still builds beside mesh-host 798d73e, and its head comment names the next mesh-sdk release as the one that removes it. Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-03 23:18:22 +01:00
jschoubben	73c8f15151	The contract says what a reader of manifests reads, what one manifest's own words, forms and seat names need, and the baseline an engine stating none is read as (ADR 0614 §4, issue 774) ... A reader capability is a manifest word by its path of keys, a form (the config form, each reference form) or a seat name of the contract's table. ManifestReads walks the decoder's fields; ManifestNeeds walks a manifest's raw JSON as the lenient decoder does, naming only what the contract knows. The baseline is ManifestReads generated once from mesh-sdk f02f142, the contract every running node-engine is built with: it lacks only tool-runner, core-credentials and the bus-state words, as rows check. Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-03 23:16:58 +01:00