mesh-delivery

Files

T

jschoubben 2165b3b296 §717 (3), the teller: it follows the asks and the answers by their seats, at the holders the seat-holders view names

The teller followed mesh-delivery-assigner's asks and mesh-delivery-view's answers by module name. It now gains the catalog
half's reader (§614), whose claimant of mesh-module-assigner's seat-holders view is its holder function (A-298), and
follows mesh-wants' asks and mesh-delivery-view's answers through views.ProcessReader.FollowSeat, each apart (issue 1906):
started before any module holds a seat it waits, and follows the holder once it is placed and as it moves. Its code names
neither module; its manifest invokes the catalog half's revision and the gate's source, and consumes the seat-holders view,
catalog-revision and source-moved; the assigner's seat-holders first-view tool answers the teller (A-131's module form).

Builds: design 47 G §717, §614, A-298, A-295, A-296

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

2026-11-12 19:55:29 +01:00

cmd

§717 (3), the teller: it follows the asks and the answers by their seats, at the holders the seat-holders view names

2026-11-12 19:55:29 +01:00

internal/ends

MV1: move contracts and sdk under modules/, importers follow

2026-11-12 05:09:56 +01:00

tellerevents

Subtask C: tellerevents' own test goes, its rows are the assigner's ended-ask rows and the teller's decode of every event said, to stay within the test budget (issue 1966)

2026-11-10 01:10:41 +01:00

go.mod

§717 (3), the teller: it follows the asks and the answers by their seats, at the holders the seat-holders view names