mesh-delivery

Files

T

jschoubben 8e60a3e078 DLV-C3 follow: the builder hears tag-wanted on the checker's own stream, mesh.stream.<checker>.event.tag-wanted

The checker's family asks is its own stream, whose subjects are mesh.stream.<module>.event.* (ruled on A2c's finding 1);
its verdicts on the same stream are acknowledged and not taken as tag asks.

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

2026-11-04 13:11:57 +01:00

buildrun

mesh-delivery-builder: a done key keeps each reference form a counted node's engine reads, the oldest in its single reference, and names its needs; what each counted node reads is asked through the node-engine seat's verb and kept in the state engine-reads (ADR 0618 §1, §2, §4, ADR 0624 §1, §3, issue 774)

2026-11-04 12:24:21 +01:00

cmd

DLV-C3 follow: the builder hears tag-wanted on the checker's own stream, mesh.stream.<checker>.event.tag-wanted

2026-11-04 13:11:57 +01:00

internal

DLV-B6: a check's build of a head a kept tag ask names numbers its packages tagged at its claim

2026-11-04 13:00:17 +01:00

go.mod

Merge lead-47's L3 mesh-delivery head 710c4032 into the registry builder