jschoubben 4ce5dec682 SD-M2d: operator-channel's offered and closed are on the router's stream asks, mesh.stream.<holder>.event.* ...

The messenger keeps them in its own stream asks (its manifest's streams, design 55 § 11), so they ride that
stream's subjects, as the checker's verdict does.

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

2026-11-04 13:31:16 +01:00

..

containerimageregistry

SD-M2b: mesh-broker's events on the shared events stream, 7 days

2026-11-04 12:53:19 +01:00

gopackageregistry

SD-M2b: mesh-broker's events on the shared events stream, 7 days

2026-11-04 12:53:19 +01:00

meshbroker

SD-M2a: mesh-broker's Held says the entry's state and why, so show says why an entry is in its state

2026-11-04 13:15:18 +01:00

meshconfig

SD-M2b, SD-M2d: the checker's and mesh-config's events kept in their own streams are mesh.stream.<holder>.event.*

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

meshdeliverychecker

SD-M2b, SD-M2d: the checker's and mesh-config's events kept in their own streams are mesh.stream.<holder>.event.*

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

meshvault

SD-M2d, ADR 0627 §1: the vault's sign, enrolment-token and node-account answers and its signed event are typed

2026-11-04 13:29:47 +01:00

npmpackageregistry

SD-M2b: mesh-broker's events on the shared events stream, 7 days

2026-11-04 12:53:19 +01:00

ociartifactregistry

SD-M2b: mesh-broker's events on the shared events stream, 7 days

2026-11-04 12:53:19 +01:00

operatorchannel

SD-M2d: operator-channel's offered and closed are on the router's stream asks, mesh.stream.<holder>.event.*

2026-11-04 13:31:16 +01:00

seats.go

SD-M2d, ADR 0627 §1: the vault's sign, enrolment-token and node-account answers and its signed event are typed

2026-11-04 13:29:47 +01:00