2026-09-21 - 2026-09-28
Overview
91 Pull requests merged by 2 users
Merged
#155 Design 28: the mesh runs on the new bus
Merged
#153 Design 26: which assignment holds a seat is on record, and changes as one act
Merged
#152 ADR 0131: everything on the mesh speaks to the broker seat, and AMQP is not a provision
Merged
#150 Building the bus: the decisions the work needed, and what it taught back
Merged
#149 to-be 31: a module declares its fail2ban jail, mesh composes them per node
Merged
#148 ADR 0122: a seat is data the controller owns; a rename is a database update
Merged
#147 to-be 30: the mesh updates itself on a push
Merged
#146 ADR 0121: keep distribution, retire only verdaccio; node-* seats migrated
Merged
#145 ADR 0121: a system seat is named for its scope; a module may define its own
Merged
#144 ADR 0120: a roster fact carries its format as a template; rewrite to-be 29
Merged
#143 ADR 0119: a taken tunnel's predecessor is retired once the take is proven
Merged
#142 issue 130: undeclaring a service stops it, even one the mesh only reloads or keeps running
Merged
#141 issue 129: nothing makes a machine trust the mesh's own certificate authority
Merged
#140 issue 128: the machine's hosts file is written whole, and on a workstation it is shared
Merged
#139 ADR 0117: a machine's uplink is a seat — the mesh configures the manager, never the link
Merged
#138 to-be 29: a node has operator accounts, and the mesh owns what lives under a home
Merged
#137 issue 127: a declaration that shrinks to empty is skipped, not sent
Merged
#136 112 is fixed: a carried peer is nameable, and the resolver answers for all four machines
Merged
#134 The bus in five steps: a decomposition, a breakdown, and progressive insight
Merged
#135 Give 0115 a home, and match its batch's status — main is failing both checks
Merged
#133 0115: one assignment of a module per node — the requirement is dropped
Merged
#132 to-be 27: the three gaps answered
Merged
#131 Issues 125 and 126: two apply-layer gaps the novox session hit live
Merged
#130 Issues 119 and 122: what a host path is, and what a node's layout would replace
Merged
#129 Issue 122: count host paths, not paths
Merged
#128 Issue 122: count it properly — 30 of 71 definitions name this installation
Merged
#127 Issue 124: a consumer cannot be told a value its provider derived for it
Merged
#126 Issue 123: the image registry is named after a role, and *artifact* is defined as one format
Merged
#125 Issue 121: retract step 4 — the forge's service is not built
Merged
#124 Issue 108: the second door was attached to the wrong thing
Merged
#122 Issue 122: the pattern is already on main, in five modules
Merged
#121 Issue 122: a module cannot ask for its own public name
Merged
#120 The seats as they run, and to-be 26 implemented
Merged
#119 Issue 121 diagnosed: the seats work renamed the requirement, not the order
Merged
#118 Accept ADR 0110 and ADR 0111; the seats design is in progress
Merged
#117 Issue 121: builder's real package-registry grant deadlocks a genesis bootstrap
Merged
#116 Issue 118: the analytics store answers the dial and times out the query
Merged
#113 To-be 27 (proposed): a module requires, the mesh resolves — with ADRs 0109–0114, research 016 and issue 119
Merged
#93 Design 25: the bus on NATS — proposed architecture for review; issue 103 resolved
Merged
#110 Issue 117: a module's own code is a container in one record and a process in another
Merged
#115 Research 017: a mesh that heals itself
Merged
#114 Issue 120: a provisioner remembers what it did, not what is there
Merged
#108 Issue 113 resolved by the repin, and what issue 064 did not cover
Merged
#109 Issue 116: route-proxy has no authentication or IP-restriction mechanism
Merged
#105 Research 015: reopen the comparison — the premise for narrowing to one candidate was false
Merged
#107 Add hq-defer: park a thought without moving the work off course
Merged
#106 ADR 0107: persistent data is a directory bind, never a named volume
Merged
#104 Accept ADR 0038; close issue 091
Merged
#103 Issue 113 and research 015: the object store's images are gone upstream, not access-restricted
Merged
#101 Issue 112: diagnose — the predecessor's own DNS config already names the carried peers
Merged
#99 Name the migration repository in the map, so nobody has to be told it exists
Merged
#79 Issue 092: genesis publishes to a registry the container runtime does not yet trust
Merged
#78 Issue 091: a module definition carries a machine port
Merged
#98 Issues 111 and 112: the resolver was told the wrong set of names, twice over
Merged
#97 Issue 110: on a converged node a container on the runtime's own network cannot reach the resolver
Merged
#96 Issue 109: a container keeps the address it was made with
Merged
#95 ADR 0105: what review settled — the tunnel adoption is implemented
Merged
#94 Issue 102 resolved and verified on the machine; issue 097's orphan was on the host network
Merged
#92 ADR 0106: the bus is NATS; issue 104 resolved
Merged
#91 Issue 108: the registry has no garbage collection, and two doors make it harder to add
Merged
#90 Issue 107: a declaration carries no order; rescue on an enrolled node is reconcile, not apply FILE
Merged
#89 Research 014: the bus on NATS — decide now, build in the lab, cut over once after the core
Merged
#88 Issues 102–106 and ADR 0105: what the core migration found, and the hub adopting the predecessor's tunnel
Merged
#87 Issue 101: taking a service its neighbours reach by container name cuts them off
Merged
#86 Issue 100: a secret the mesh mints cannot be the one the service it takes over already uses
Merged
#85 Issue 099: a module's image pin ages into a downgrade, and taking it over is where that is discovered
Merged
#84 Issue 094 diagnosed and resolved; 096, 097 and 098 opened from what it uncovered
Merged
#83 Issues 094 and 095, both found in the first module's cutover
Merged
#82 Research 013: the forge and the registries — a seat answers the wrong question
Merged
#81 ADR 0104: a provision may be answered by an adapter to the predecessor
Merged
#80 Issue 093: the successor proxy cannot serve what the predecessor still serves
Merged
#77 Issue 085 resolved
Merged
#76 Issues 088, 089 and 090, found fixing 085
Merged
#75 Adoption mode as built: ADRs 0101–0103, issues 084–086
Merged
#74 ADR 0100 (proposed): a node in use is adopted before it is converged
Merged
#73 Issue 083 resolved: nothing the control queue carries is lost while the store restarts
Merged
#72 Issues 081 and 082 resolved; 083 opened
Merged
#71 Issues 079 and 080, found by running the large mesh bed; 074's addendum
Merged
#70 ADR 0099; issues 077, 078 and 074 resolved; designs 08 and 20 amended
Merged
#69 ADR 0098; issue 076 opened and resolved; ADR 0097's base refusal live; ADR 0096 proven against the public hub; 074 down to one bed
Merged
#68 Multiple fixes: issues 064, 066 and 020 resolved; 074 narrowed to two beds
Merged
#67 Multiple fixes: ADRs 0094–0097; issues 069, 049, 046 resolved; 064's image half decided
Merged
#66 ADR 0093: a fixture that runs a module's runtime carries its name; 074 diagnosed; 075 resolved
Merged
#65 Issues 072 and 073 name their merges, the branches being gone
Merged
#64 Multiple fixes: status vocabulary aligned, 065/026/070/007 resolved, 066/069/049/046 located, 064 diagnosed
Merged
#63 Issue 072 diagnosed: genesis registers the manifest its build produced; design 17 says so
Merged
#62 ADR 0089: a bed reads the catalogue it proves; issue 073 diagnosed; issues 074 and 075 opened
Merged
#61 Issues 031, 035 and 054 name their merges, the branch being gone
Merged
#60 ADRs 0087 and 0088; issues 031, 035 and 054 resolved; issue 041 surveyed; issue 073 opened
Merged
#59 ADR 0086 (a secret reaches a process as a file), the vault shipped, issues 041 and 072
Merged
#58 The secrets vault: handoff, the amended decision, issues 069–071, and the reconciliation of open issues
2 Pull requests proposed by 1 user
Proposed
#151 Issue 131: nothing tells the mesh a source moved, and it reports itself current anyway
Proposed
#154 Design 28: the move needs a credential and a membership for machines already enrolled