mesh-delivery

1,053 Commits 31 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9c9ed7a1d8	The checker serves a checking program's input on its seat's verb input, and the build module asks it (issue 1921, B0 review round 1) mesh/delivery ready: it is merged on the Approve Details mesh/delivery-group group feat/b0-checking-program checking: 3 of 3 member(s) ready Details mesh/check checking 9c9ed7a1d8f1 on 2d201f781ced \| novox/mesh-delivery#162 in group feat/b0-checking-program The operator's answer: mesh-build-go reading the checker's state inputs broke ADR 0596 §2. The run ask's input now names the verb seat:mesh-delivery-checker.input; the checker's tools serve it from the state inputs (Reader.Input, checked against its digest), and the state is the checker's own again, read by no other module. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 23:39:39 +01:00
jschoubben	b1d0c6881a	The facts carry a level as the rules read it, and a seat list the program cannot make ends the check without a verdict asked (issue 1921, B0 review round 1) A level's digest, unmet packages, kept packages' names and test packages are read by no rule: a mesh-catalog check step's two levels were 78682 bytes as facts and are 4506. A build node with no job run held a check four begin bounds; it now holds it two. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 23:24:18 +01:00
jschoubben	63bbabacbf	Every check is judged by the checking program built from its heads (issue 1921) The running checker asks the checking program twice on the build seat's job run: first the heads' seat list, which the manifest validator's requests (change and trunk) and the node-engine composer's carry; then the verdict of the facts it gathered. The program is built at the group's mesh-delivery head, else at mesh-delivery's trunk, and its input is kept in the checker's new state inputs as the exact bytes of its digest, read with checker_inputs. A run ask no build node begins within 5 minutes is put once more, then fails the check naming the job; a program that does not build or answer fails the check naming it, and the verdict records who judged it (JudgedBy). A second step-seen hook on a context is added to the first, so a try still sees its steps. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-06 22:58:15 +01:00

Author

SHA1

Message

Date

jschoubben

9c9ed7a1d8

The checker serves a checking program's input on its seat's verb input, and the build module asks it (issue 1921, B0 review round 1)

mesh/delivery ready: it is merged on the Approve

Details

mesh/delivery-group group feat/b0-checking-program checking: 3 of 3 member(s) ready

Details

mesh/check checking 9c9ed7a1d8f1 on 2d201f781ced | novox/mesh-delivery#162 in group feat/b0-checking-program

The operator's answer: mesh-build-go reading the checker's state inputs broke ADR 0596 §2. The run ask's input now names
the verb seat:mesh-delivery-checker.input; the checker's tools serve it from the state inputs (Reader.Input, checked
against its digest), and the state is the checker's own again, read by no other module.

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

2026-11-06 23:39:39 +01:00

jschoubben

b1d0c6881a

The facts carry a level as the rules read it, and a seat list the program cannot make ends the check without a verdict asked (issue 1921, B0 review round 1)

A level's digest, unmet packages, kept packages' names and test packages are read by no rule: a mesh-catalog check
step's two levels were 78682 bytes as facts and are 4506. A build node with no job run held a check four begin bounds;
it now holds it two.

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

2026-11-06 23:24:18 +01:00

jschoubben

63bbabacbf

Every check is judged by the checking program built from its heads (issue 1921)

The running checker asks the checking program twice on the build seat's job run: first the
heads' seat list, which the manifest validator's requests (change and trunk) and the
node-engine composer's carry; then the verdict of the facts it gathered. The program is built
at the group's mesh-delivery head, else at mesh-delivery's trunk, and its input is kept in the
checker's new state inputs as the exact bytes of its digest, read with checker_inputs. A run
ask no build node begins within 5 minutes is put once more, then fails the check naming the
job; a program that does not build or answer fails the check naming it, and the verdict
records who judged it (JudgedBy). A second step-seen hook on a context is added to the
first, so a try still sees its steps.

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

2026-11-06 22:58:15 +01:00