Design 20 and playbook 06 say what the manifest validator accepts, and how a module is built of parts #575

Merged

mesh-tools merged 1 commits from design/20-manifest-as-judged into main

2026-11-12 10:38:25 +00:00

Author	SHA1	Message	Date
jschoubben	658d33892c	Write design 20 and playbook 06 from what the manifest validator accepts mesh/delivery merged: source.main moved to novox/hq@f9bdd3b1d1ce Details mesh/check checking 658d33892c5e on f9bdd3b1d1ce The module-development documents described a manifest the mesh no longer reads: four languages where the builder builds two, a Go bundle with no system, a scheduled process the guide never said how to write, the old kept-data sections as the norm, and the controller as the one refusing. They now name each part of a module and its manifest form as the manifest validator, the builder and the node-engine read it, and the playbook lists where those parts still disagree, so an author writes the form every part takes.	2026-11-12 11:36:48 +01:00

Author

SHA1

Message

Date

jschoubben

658d33892c

Write design 20 and playbook 06 from what the manifest validator accepts

mesh/delivery merged: source.main moved to novox/hq@f9bdd3b1d1ce

Details

mesh/check checking 658d33892c5e on f9bdd3b1d1ce

The module-development documents described a manifest the mesh no longer
reads: four languages where the builder builds two, a Go bundle with no
system, a scheduled process the guide never said how to write, the old
kept-data sections as the norm, and the controller as the one refusing.
They now name each part of a module and its manifest form as the
manifest validator, the builder and the node-engine read it, and the
playbook lists where those parts still disagree, so an author writes
the form every part takes.

2026-11-12 11:36:48 +01:00