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

mesh-delivery-assigner

The node-engine seat's manifest-reads answer and event come from mesh-contracts' nodeengine contract, judged by their reader (ADR 0618 §3, §4, issue 774)

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

mesh-delivery-builder

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

mesh-delivery-checker

The checker hands the composer the node-engine's input encoded again from the seat contract's object

2026-11-04 12:43:11 +01:00

mesh-delivery-forge-bridge

DLV-FB1: the forge bridge says a branch's end as branch-deleted and answers bridge_tags