mesh-controller

Archived

This repository has been archived on 2026-11-02. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

T

History

jschoubben abce68fdf0 Verify that a reply address does not survive a stream

Design 25 §2 builds enrolment around carrying the reply subject in the
payload, because a JetStream consumer claims the transport Reply field for
its own ack address. The whole handshake rests on it, so it is checked:
the caller asked for _INBOX.LCr3M83q... and the consumer saw
$JS.ACK.PROBE.probe_consumer... The design was right, and the workaround
is necessary rather than defensive.

Worth having as a test rather than a note: if a future server version
stopped doing this, enrolment would keep working and the reason for the
payload field would quietly become folklore.

2026-09-27 00:14:32 +02:00

broker

Describe the bus on its own terms

2026-09-26 23:51:00 +02:00

builder

builder: a clone may offer the forge's credential, through git's own store

2026-09-25 21:47:32 +02:00

catalogue

A manifest holds no subject, checked across all 72

2026-09-26 23:34:42 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port