novox/hq
6
0
Fork 0
Code Issues Pull Requests 7 Releases Wiki Activity
Files
35d81e962e7a6fcf2a38bfda1368ede95f094332
hq/04-ISSUES
T
History
jochen 124943bdc3
mesh/merge-gate pass: the change touches no module of the mesh's graph
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
Issue 282: a secret on a command line is kept in the runtime's events 
The mosquitto module passed its broker's admin password to every docker
exec as an argument, which the container runtime records in its events.
Records the cause, the other modules found doing the same, the fix
proposed in mesh-catalog #100, and where the leaked value went.
2026-10-07 01:38:37 +02:00
..
001-failed-package-install-reports-success
Three issues resolved: one closed by evidence, two answered by the replacement
2026-08-31 13:00:03 +02:00
002-stale-package-index-fails-silently
Three issues resolved: one closed by evidence, two answered by the replacement
2026-08-31 13:00:03 +02:00
003-firewall-scope-is-read-by-no-code
Restore initialization's issue 003 — the status flip was based on a wrong premise
2026-09-05 12:26:23 +02:00
004-certificate-issuance-targets-production
004 and 008 resolved; 006 narrowed to the decision it actually needs
2026-08-31 15:20:11 +02:00
005-pipeline-test-harness-unbuildable
005 resolved: a suite that cannot run on every push says when it last ran
2026-08-31 15:02:26 +02:00
006-hq-is-not-indexed-into-the-knowledge-base
Issue 006 resolved: the record is read where it is written, and the console lists it
2026-09-30 18:10:18 +02:00
007-an-installed-package-is-not-a-capability
Issues 007 resolved, 066 located, 064 diagnosed
2026-09-21 17:48:38 +02:00
008-the-documented-node-rescue-does-not-exist
004 and 008 resolved; 006 narrowed to the decision it actually needs
2026-08-31 15:20:11 +02:00
009-a-digest-pinned-image-cannot-be-placed-in-the-lab
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
010-the-first-declaration-destroys-the-substrate
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
011-one-broken-module-blocks-every-other
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
012-a-scenario-machine-is-too-small-for-four-images
Three issues resolved: one closed by evidence, two answered by the replacement
2026-08-31 13:00:03 +02:00
013-a-file-arrives-after-the-service-that-needs-it
The mesh runs its own registry, certifies its own names, and computes its own filtering
2026-08-31 00:37:34 +02:00
014-a-key-that-is-present-and-unusable
A key that is present and unusable, and what the certificate work became
2026-08-31 00:42:13 +02:00
015-a-command-with-no-answer-was-read-as-success
Issue 015: the harness read a swallowed answer as success
2026-08-31 00:48:16 +02:00
016-something-after-the-declaration-was-ignored
Issue 016: anything after the declaration in a file was ignored
2026-08-31 00:51:46 +02:00
017-an-action-succeeded-into-a-state-its-verify-rejects
Issue 017: an action succeeded into a state its own verify rejects
2026-08-31 01:01:17 +02:00
018-a-provider-on-the-same-machine-was-never-announced
Issue 018: a provider on the same machine was never announced to its consumer
2026-08-31 01:35:54 +02:00
019-a-comment-asserting-a-fact-about-a-machine
Issue 019: a comment asserting a fact about a machine, which nothing checked
2026-08-31 14:11:34 +02:00
020-a-certificate-is-issued-and-never-collected
Issue 020 resolved: the symptom was the bed's, proven against Pebble and step-ca alike
2026-09-21 22:12:51 +02:00
021-a-consumer-on-the-providers-machine-is-given-no-credential
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
022-one-credential-per-node-per-provision-not-per-module
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
023-a-consumer-cannot-build-a-connection-string
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
024-a-lab-run-stalls-before-the-host-is-placed
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
025-a-module-must-pin-a-digest-and-nothing-produces-one
Reconcile the open issues against main
2026-09-21 01:52:53 +02:00
026-the-data-directories-are-not-declared
ADRs 0091 and 0092; issues 026 and 070 resolved; designs 18 and 24 amended
2026-09-21 17:50:41 +02:00
027-a-container-cannot-follow-a-file
Reconcile the open issues against main
2026-09-21 01:52:53 +02:00
028-two-things-want-one-port-and-nothing-says-so
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
029-the-artifact-store-cannot-be-delivered-by-the-artifact-store
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
030-asking-what-a-machine-should-be-re-signed-its-certificate
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
031-a-machine-becomes-each-thing-it-was-told-in-turn
Issues 031, 035 and 054 name their merges, the branch being gone
2026-09-21 13:49:56 +02:00
032-provider-runtime-has-no-seal-key
Re-home this session's new ADRs (0039-0049) and issues (032-037) onto the consolidated scheme; flip issue 003; port repos.md sdk line + feature-branches playbook (07); regenerate index
2026-09-05 12:24:07 +02:00
033-runtime-config-change-does-not-restart
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
034-mesh-login-exceeds-s3-access-key-limit
Re-home this session's new ADRs (0039-0049) and issues (032-037) onto the consolidated scheme; flip issue 003; port repos.md sdk line + feature-branches playbook (07); regenerate index
2026-09-05 12:24:07 +02:00
035-reconciling-a-seed-file-wipes-what-grew-in-it
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
036-six-modules-own-what-they-must-share
Reconcile the open issues against main
2026-09-21 01:52:53 +02:00
037-a-module-cannot-run-code-at-a-lifecycle-phase
Reconcile the open issues against main
2026-09-21 01:52:53 +02:00
038-a-provider-is-announced-at-a-name-its-port-is-not-bound-to
Issue 038 resolved — corrected root cause (same-node served-port mismatch, not loopback) + fix reference
2026-09-09 23:06:58 +02:00
039-the-lab-registry-was-silently-pinning-unpinned-modules
Issue 039 resolved — the operator's images are pinned, and why that is a stopgap
2026-09-11 01:06:35 +02:00
040-the-install-procedure-exists-only-as-a-test
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
041-a-sealed-credential-ends-up-in-the-process-environment
Issue 041: mongodb names its secrets' owner; the three conversions are proven
2026-09-21 13:47:39 +02:00
042-nothing-gives-a-node-an-account-for-a-registry
042/048/061/062 resolved — the network carries the registry trust
2026-09-18 00:26:50 +02:00
043-a-module-cannot-be-given-the-meshs-own-queues
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
044-the-runtime-every-module-builds-on-cannot-be-built-by-the-mesh
A module names its base, so the mesh can act on what it notices
2026-09-13 23:58:06 +02:00
045-a-container-keeps-the-values-it-started-with
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
046-an-upstream-image-cannot-be-mirrored-into-the-mesh
ADR 0096: an upstream image is copied between registries; issue 046 resolved; design 18 amended
2026-09-21 20:43:07 +02:00
047-the-firewall-does-not-cover-published-container-ports
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
048-nothing-makes-a-machine-trust-the-mesh-registry
042/048/061/062 resolved — the network carries the registry trust
2026-09-18 00:26:50 +02:00
049-a-module-can-serve-tools-and-nothing-can-call-them
ADR 0095: the control plane is the way to ask a module; issue 049 resolved; design 19 amended
2026-09-21 20:38:23 +02:00
050-the-catalogue-knows-nothing-built-before-it
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
051-the-mesh-cannot-update-what-it-depends-on
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
052-the-firewall-does-not-know-the-brokers-port
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
053-the-sdk-is-pinned-twice-and-the-two-disagree
Nine resolved issues name where their fix landed
2026-09-21 17:39:34 +02:00
054-the-adopted-store-and-broker-are-open-before-the-filter
Issue 054 names where its fix landed
2026-09-21 17:39:09 +02:00
055-the-adopted-store-and-broker-may-be-reachable-on-one-node-only
Fix what the records review found
2026-09-17 22:24:57 +02:00
056-an-adopted-module-assigned-to-a-second-node-raises-a-second-server
Fix what the records review found
2026-09-17 22:24:57 +02:00
057-a-cross-node-consumer-is-provisioned-only-when-the-provider-is-pushed-again
057 and 058 resolved — their fixes merged and proven
2026-09-20 12:55:00 +02:00
058-a-provisioner-runtime-crash-loops-until-the-overlay-is-up
057 and 058 resolved — their fixes merged and proven
2026-09-20 12:55:00 +02:00
059-the-broker-credential-names-the-hub-not-the-broker
059 resolved — the broker credential resolves the seat
2026-09-18 01:13:03 +02:00
060-the-mesh-cannot-build-most-of-its-own-catalogue
Issues 060 resolved, 064 opened; 057/058 on this branch too
2026-09-18 02:52:36 +02:00
061-a-module-container-that-names-no-command-runs-the-wrong-thing
042/048/061/062 resolved — the network carries the registry trust
2026-09-18 00:26:50 +02:00
062-a-failed-lookup-composes-the-network-without-the-registry-trust
042/048/061/062 resolved — the network carries the registry trust
2026-09-18 00:26:50 +02:00
063-the-foundation-ports-are-accepted-on-input-but-not-forwarded
Issue 063 — the foundation's ports are forwarded, resolved
2026-09-18 02:20:11 +02:00
064-a-mesh-build-cannot-fetch-a-modules-external-dependencies
Issue 064 resolved: the package half placed by the genesis run, the image half by ADR 0097
2026-09-21 21:52:32 +02:00
065-a-permanently-failing-resource-is-retried-for-ever-with-no-escalation
ADR 0090: a failure that repeats is said to be stuck; issue 065 resolved
2026-09-21 17:43:02 +02:00
066-a-partly-applied-declaration-leaves-a-mixed-state-with-no-rollback
Issue 066 resolved: a file and its reader are guarded by a gate, proven by the coupled-pair spike; design 20 says so
2026-09-21 22:04:14 +02:00
067-a-provision-cannot-name-which-provider-serves-it
Issues 067 and 068 name where their fix landed
2026-09-21 17:38:48 +02:00
068-secrets-have-no-owning-module
An issue is open, diagnosing, located, resolved or wontfix — nothing else
2026-09-21 17:38:17 +02:00
069-one-secret-provision-yields-one-value
ADR 0094: a module may hold several secrets from one provider; issue 069 resolved; design 24 amended
2026-09-21 20:29:29 +02:00
070-an-operator-cannot-deliver-a-pair-credential
ADRs 0091 and 0092; issues 026 and 070 resolved; designs 18 and 24 amended
2026-09-21 17:50:41 +02:00
071-the-foundation-is-raised-with-fixed-credentials
The vault shipped: as-is 06 describes it, design 24 is implemented, 071 names its merges
2026-09-21 10:10:33 +02:00
072-the-controllers-manifest-exists-twice
Issues 072 and 073 name their merges, the branches being gone
2026-09-21 19:24:28 +02:00
073-beds-carry-copies-of-catalogue-manifests
Issues 072 and 073 name their merges, the branches being gone
2026-09-21 19:24:28 +02:00
074-a-mesh-test-wears-a-catalogue-modules-name
Issue 079: every machine named twice over, found by the large mesh bed; what running that bed cost, on 074
2026-09-22 01:13:29 +02:00
075-a-stocked-runtime-image-is-never-rebuilt-by-the-run
ADR 0093: a fixture that runs a module's runtime carries its name; 074 diagnosed, two beds converted; 075 resolved
2026-09-21 19:30:35 +02:00
076-a-served-fact-made-at-first-start-cannot-be-served
Review corrections: 076 and ADR 0098 say what the authority could and could not do; issues 077 (a fetched fact is fetched once) and 078 (secret accept takes any name) opened
2026-09-21 22:55:11 +02:00
077-a-fact-fetched-at-first-start-is-fetched-once
Review: 077 says what closed it and what did not; 078 names module issue; 074's retired fixture; ADR 0099's scope
2026-09-21 23:58:15 +02:00
078-a-delivered-secret-is-accepted-under-any-name
Review: 077 says what closed it and what did not; 078 names module issue; 074's retired fixture; ADR 0099's scope
2026-09-21 23:58:15 +02:00
079-every-machine-is-named-twice-over
Issue 081 opened (a cache consumer does not use its login); 079 and 080 diagnoses carry the review's consequences
2026-09-22 02:04:29 +02:00
080-a-cache-grant-lets-the-consumer-flush-the-server
Issue 081 opened (a cache consumer does not use its login); 079 and 080 diagnoses carry the review's consequences
2026-09-22 02:04:29 +02:00
081-a-cache-consumer-does-not-use-the-login-it-was-granted
Issue 081: proven by the two-node bed, and what it found about baserow's data directory
2026-09-22 13:53:00 +02:00
082-a-report-that-arrives-while-the-store-restarts-is-lost
Issue 083 opened (other control messages lost while the store restarts); 082's diagnosis carries its review
2026-09-22 13:34:05 +02:00
083-other-control-messages-are-lost-while-the-store-restarts
Issue 083: the proof, the replay caveat, and what is not closed, as three reviews found them
2026-09-22 14:39:29 +02:00
084-taking-networking-on-an-adopted-node-restarts-every-container
ADR 0168: a converged machine is filtered by the mesh alone, and the host says what else refuses (group 7)
2026-10-02 11:58:18 +02:00
085-the-packages-port-given-at-genesis-is-not-a-setting
Research 013: the forge and the registries — a seat answers the wrong question; issues 090 and 085 corrected from the code
2026-09-23 00:38:34 +02:00
086-taking-a-module-narrows-a-port-without-saying-so
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
087-the-controller-cannot-tell-a-host-is-too-old
Issue 087: what I shipped first said the opposite of the truth
2026-09-30 09:29:40 +02:00
088-the-forges-own-address-names-a-port-it-may-not-have
Grooming: five issues were fixed and never closed, and one is not
2026-09-29 22:25:25 +02:00
089-a-contributed-route-names-a-port-the-node-may-have-moved
Grooming: five issues were fixed and never closed, and one is not
2026-09-29 22:25:25 +02:00
090-the-forge-module-does-not-take-over-the-forge-genesis-raised
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
091-a-module-definition-carries-a-machine-port
Accept ADR 0038; close issue 091
2026-09-24 15:52:45 +02:00
092-genesis-publishes-to-a-registry-the-runtime-does-not-trust
Issue 092: it happened twice more — the registry's mesh name, and the mesh's own trust naming the default port
2026-09-22 23:37:05 +02:00
093-the-successor-proxy-cannot-serve-what-the-predecessor-still-serves
ADR 0163: taking a module over is a comparison — what it compares, refuses and carries; designs 05 and 09; group 6's issues located, 093 resolved
2026-10-01 21:12:36 +02:00
094-a-port-published-as-the-machine-side-cannot-be-moved
Issue 094 resolved: a given port names either end and is answered once
2026-09-23 02:37:07 +02:00
095-a-module-assigned-after-genesis-has-no-broker-account
Issues 094 and 095, both found in the first module's cutover
2026-09-23 01:57:10 +02:00
096-a-setting-that-cannot-work-is-stored-and-stops-the-node
ADR 0163 built: the take digest, the minted-secret refusal, the networks setting, settings judged where stored, genesis raising the forge as declared; issues 096, 097, 126 resolved
2026-10-01 23:45:57 +02:00
097-a-resource-that-changes-target-leaves-the-old-one-behind
ADR 0163 built: the take digest, the minted-secret refusal, the networks setting, settings judged where stored, genesis raising the forge as declared; issues 096, 097, 126 resolved
2026-10-01 23:45:57 +02:00
098-taking-a-module-replaces-a-configuration-nobody-compared
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
099-a-modules-image-pin-ages-into-a-downgrade
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
100-a-minted-secret-cannot-be-the-one-the-service-already-uses
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
101-taking-a-service-reached-by-container-name-cuts-its-neighbours-off
Group 6 closed: 086, 090, 098, 099, 100, 101 resolved on the operator's decision, each saying the live row was not run
2026-10-02 11:37:08 +02:00
102-an-address-recorded-at-genesis-or-build-does-not-follow-the-nodes-ports
Issue 102 resolved, verified on the machine with both forwarders gone; 097's orphan was on the host network
2026-09-24 00:02:13 +02:00
103-a-container-is-not-recreated-when-a-file-it-reads-changes
Merge main: the bus design, issues 113/114/117/120 and research 017 landed
2026-09-26 14:16:05 +02:00
104-reconcile-applies-a-stale-declaration-and-refuses-nothing
ADR 0106: the bus is NATS — native, built beside the migration, cut over after its core; issue 104 resolved
2026-09-23 23:39:17 +02:00
105-the-hub-of-the-private-network-is-not-a-seat
ADR 0161: what deserves a seat — the vault's seat, the hub as a placement of capacity one, the uplink holder as the machine's dialect; design 26; issues 105, 106, 138
2026-10-01 15:55:15 +02:00
106-the-vault-claims-no-seat
Issues 106 and 138 resolved (ADR 0161 built and live); 187 notes a report lost without retry
2026-10-01 17:18:17 +02:00
107-a-declaration-carries-no-order
Issue 107 is resolved: a declaration carries its order
2026-09-30 14:13:50 +02:00
108-the-registry-has-no-garbage-collection-once-it-has-two-doors
ADR 0189: the store keeps what the records name, and a maintenance step holds its writers still
2026-10-04 02:40:25 +02:00
109-a-container-keeps-the-address-it-was-made-with
Group 2 is resolved: containers resolve, nothing is copied, a route's name says where it arrives
2026-09-30 14:56:43 +02:00
110-a-container-on-the-runtimes-own-network-cannot-reach-the-resolver
Group 2 is resolved: containers resolve, nothing is copied, a route's name says where it arrives
2026-09-30 14:56:43 +02:00
111-the-resolver-is-told-names-the-mesh-serves-not-only-machines
Issues 111 and 112: the resolver was told the wrong set of names, twice over
2026-09-24 01:32:04 +02:00
112-adopting-a-tunnel-gives-the-mesh-addresses-without-names
Two checks were wrong about where a seat is judged
2026-09-27 18:57:49 +02:00
113-the-object-stores-images-were-withdrawn-upstream
Issue 113 resolved by the repin, and what issue 064 did not cover
2026-09-25 00:55:13 +02:00
114-should-the-controller-be-a-container-or-a-process
Issue 114 is answered: the controller is a process, by ADR 0142
2026-09-29 22:38:11 +02:00
115-a-named-docker-volume-is-invisible-and-one-flag-from-gone
ADR 0107: persistent data is a directory bind, never a named volume
2026-09-24 16:21:51 +02:00
116-route-proxy-has-no-auth-or-ip-restriction
Issue 116: resolved by mesh-controller PR #58
2026-09-25 14:25:24 +02:00
117-a-modules-own-code-is-a-container-and-a-process
The pointers back from what yesterday's records changed, which I missed twice
2026-09-30 00:47:19 +02:00
118-umamis-store-answers-the-dial-and-times-out-the-query
Issue 118 is resolved: it was issue 135, and umami is healthy
2026-09-30 01:54:19 +02:00
119-a-module-definition-decides-where-its-files-live
Issues 173 and 174 resolved; the installation check refuses at registration (ADR 0155)
2026-09-30 22:36:20 +02:00
120-a-provisioner-remembers-what-it-did-not-what-is
Grooming: five issues were fixed and never closed, and one is not
2026-09-29 22:25:25 +02:00
121-builders-real-package-registry-grant-deadlocks-genesis
Issue 121: retract step 4 — the forge's service is not built
2026-09-26 15:36:19 +02:00
122-a-module-cannot-ask-for-its-own-public-name
Issue 173: a module's settings reach every fact it contributes; what the site's rename cost
2026-09-30 21:04:34 +02:00
123-the-image-registry-is-named-after-a-role
ADR 0156: an artifact is what a build produces, and the store's seat is named for its scope
2026-09-30 21:14:40 +02:00
124-a-consumer-cannot-be-told-what-its-provider-derived
ADR 0201 → 0202, and three issues from the night it shipped
2026-10-04 04:33:45 +02:00
125-a-hold-is-not-a-line-in-the-apply-report
Issue 125 is resolved: a hold is a line in the report, and it breaks "all well"
2026-09-30 08:47:36 +02:00
126-a-volume-path-is-not-in-the-spec-comparison
ADR 0163 built: the take digest, the minted-secret refusal, the networks setting, settings judged where stored, genesis raising the forge as declared; issues 096, 097, 126 resolved
2026-10-01 23:45:57 +02:00
127-a-module-event-derives-a-subject-nothing-publishes
Merge main: renumber this branch's records around the trunk's
2026-09-27 18:23:41 +02:00
128-the-hosts-file-is-written-whole
Grooming: five issues were fixed and never closed, and one is not
2026-09-29 22:25:25 +02:00
129-nothing-makes-a-machine-trust-the-meshs-authority
Issue 129: three machines of four trust the mesh, not one
2026-09-30 02:30:23 +02:00
130-undeclaring-a-service-stops-it
Two records were numbered 127; the second becomes 149, and is resolved
2026-09-29 22:33:40 +02:00
131-nothing-tells-the-mesh-a-source-moved
Design 28: 5.5 done, the mesh has one bus; issue 131 resolved
2026-09-28 03:59:39 +02:00
132-a-module-can-be-recorded-without-the-directory-it-lives-in
Issue 132: a module can be recorded without the directory it lives in
2026-09-28 09:20:05 +02:00
133-the-control-planes-schema-is-migrated-at-birth-and-never-again
ADR 0135 supersedes 0133: a module version prepares its state before it runs
2026-09-28 11:57:16 +02:00
134-a-definition-may-still-name-the-mesh
Issues 173 and 174 resolved; the installation check refuses at registration (ADR 0155)
2026-09-30 22:36:20 +02:00
135-a-containers-mesh-names-are-not-compared
Issue 118 is resolved: it was issue 135, and umami is healthy
2026-09-30 01:54:19 +02:00
136-a-module-may-name-a-program-the-machine-does-not-have
Issue 136: a module may name a program the machine does not have, and everything reports success
2026-09-28 20:50:35 +02:00
137-converging-a-machine-cut-off-its-own-guests
ADR 0137: a machine says which networks it routes, and issue 137 is how that was found
2026-09-28 21:31:01 +02:00
138-two-modules-claim-one-seat-and-are-not-interchangeable
Issues 106 and 138 resolved (ADR 0161 built and live); 187 notes a report lost without retry
2026-10-01 17:18:17 +02:00
139-an-internal-route-name-resolves-to-the-consumers-node
Group 2 is resolved: containers resolve, nothing is copied, a route's name says where it arrives
2026-09-30 14:56:43 +02:00
140-an-endpoints-reach-is-not-declared
Issue 140 is resolved, and was resolved before it was read again
2026-09-29 22:19:24 +02:00
141-the-forward-chain-does-not-follow-the-modules
ADR 0168: a converged machine is filtered by the mesh alone, and the host says what else refuses (group 7)
2026-10-02 11:58:18 +02:00
142-the-host-is-the-one-thing-the-mesh-does-not-deliver
Every machine self-updates, verified, and 107's gate has opened
2026-09-30 13:51:46 +02:00
143-converging-does-not-retire-the-firewall-it-found
Issues 143 and 144 resolved: the live row of ADR 0168 read on the home server and the control node
2026-10-02 12:11:17 +02:00
144-the-predecessors-rules-outlive-the-firewall-it-was-found-as
Issues 143 and 144 resolved: the live row of ADR 0168 read on the home server and the control node
2026-10-02 12:11:17 +02:00
145-a-machine-reads-healthy-while-its-modules-cannot-reach-each-other
Group 1: 145's report states its scope, and 107 waits for delivery
2026-09-30 09:00:18 +02:00
146-the-foundation-cannot-be-raised-on-the-bus-the-mesh-runs-on
The records pointed at branches that no longer exist, and two fixes had no sequel
2026-09-30 00:28:35 +02:00
147-the-operators-tools-still-dial-the-bus-that-was-removed
The console shipped: design 34 implemented, as-is 13, issue 147 verified live
2026-09-30 17:13:09 +02:00
148-a-manifest-outside-this-catalogue-has-no-check
Issues 147 and 148 name what fixed them
2026-09-30 16:21:33 +02:00
149-a-declaration-that-shrinks-to-empty-is-skipped-not-sent
Two records were numbered 127; the second becomes 149, and is resolved
2026-09-29 22:33:40 +02:00
150-a-route-is-contributed-before-its-module-is-taken
Issue 152: a node whose plan will not compose withdraws its names from every machine
2026-09-29 23:13:54 +02:00
151-a-new-name-recreates-every-container-in-the-mesh
Group 2 is resolved: containers resolve, nothing is copied, a route's name says where it arrives
2026-09-30 14:56:43 +02:00
152-a-nodes-plan-failure-silently-drops-its-routed-names
The records pointed at branches that no longer exist, and two fixes had no sequel
2026-09-30 00:28:35 +02:00
153-an-adopted-machines-data-cannot-be-placed-where-it-is
Issue 153 resolved: an assignment places a module's directories and its accesses
2026-10-01 00:04:10 +02:00
154-a-machines-own-network-is-not-a-reach
Two records shared a number, twice, and every check passed
2026-09-29 23:38:48 +02:00
155-two-records-may-share-a-number-and-nothing-says-so
The records pointed at branches that no longer exist, and two fixes had no sequel
2026-09-30 00:28:35 +02:00
156-moving-a-consumers-delivery-subject-stops-the-control-plane
The records pointed at branches that no longer exist, and two fixes had no sequel
2026-09-30 00:28:35 +02:00
157-a-routed-names-internal-alias-is-served-by-nothing
Group 2 is resolved: containers resolve, nothing is copied, a route's name says where it arrives
2026-09-30 14:56:43 +02:00
158-the-proxy-re-reads-and-re-logs-every-route-every-two-seconds
Issue 129 is live and reproduced, and needs three steps rather than one
2026-09-30 01:30:24 +02:00
159-an-artifacts-system-is-checked-and-then-ignored
A machine says little about itself, and only when the mesh asks it something
2026-09-30 10:36:40 +02:00
160-a-machine-says-little-about-itself-and-only-when-asked
A machine says little about itself, and only when the mesh asks it something
2026-09-30 10:36:40 +02:00
161-a-delivered-host-carries-none-of-its-link-time-facts
The host self-updates, and an archive cannot be undeclared
2026-09-30 13:16:37 +02:00
162-an-archive-cannot-be-undeclared
Issue 162 resolved: an archive can be undeclared (mesh-host#90)
2026-10-04 12:23:06 +02:00
163-a-delivered-host-stood-aside-on-every-push-and-reported-nothing
Issue 163: a delivered host stood aside on every push and reported nothing
2026-09-30 13:47:28 +02:00
164-a-credential-that-must-be-accepted-is-minted-anyway
Issues 164-168: found provisioning every dependency on ace
2026-09-30 13:28:53 +02:00
165-one-accepted-value-must-be-accepted-once-per-consumer
Issues 164-168: found provisioning every dependency on ace
2026-09-30 13:28:53 +02:00
166-a-requirement-cannot-be-optional
Issues 164-168: found provisioning every dependency on ace
2026-09-30 13:28:53 +02:00
167-code-several-modules-share-has-no-home
Issues 164-168: found provisioning every dependency on ace
2026-09-30 13:28:53 +02:00
168-a-setting-reaches-every-file-and-contribution
Issues 164-168: found provisioning every dependency on ace
2026-09-30 13:28:53 +02:00
169-a-machine-shares-its-files-and-the-mesh-does-not-know
Issue 169: network-share is the module responsible for a node's network shares — a node role
2026-09-30 13:56:24 +02:00
170-assigning-a-module-claims-every-seat-it-could-hold
Issue 170: assigning a module claims every seat it could hold
2026-09-30 14:29:11 +02:00
171-a-modules-own-resolver-knows-no-mesh-name
Issue 171: a module that names its own resolver knows no mesh name
2026-09-30 15:20:26 +02:00
172-the-ssh-client-block-matches-one-spelling-of-a-machine
Issue 172: the ssh client block matches one spelling of a machine's name
2026-09-30 15:25:30 +02:00
173-a-modules-settings-reach-every-fact-it-contributes
Issues 173 and 174 resolved; the installation check refuses at registration (ADR 0155)
2026-09-30 22:36:20 +02:00
174-the-meshs-own-files-for-a-module-are-placed-by-the-definition
Issues 173 and 174 resolved; the installation check refuses at registration (ADR 0155)
2026-09-30 22:36:20 +02:00
175-an-announcement-behind-a-long-build-comes-back
Issue 175: the link to issue 127 resolves
2026-09-30 22:10:38 +02:00
176-the-consoles-build-tool-neither-waits-nor-registers
Issue 176 resolved: a build is taken in where its outcome is heard; the build tool answers with the id
2026-10-01 01:27:49 +02:00
177-the-controllers-check-is-run-by-nobody
Issue 177: the controller's check is run by nobody; the two rotted tests fixed (controller PR 180), the process half open
2026-10-01 01:38:22 +02:00
178-a-routed-name-resolves-to-a-provider-merely-told-it
Issue 178: a routed name resolves to a provider merely told it, and flips between plans (fixed, controller PR 181)
2026-10-01 02:04:55 +02:00
179-an-adopted-identity-providers-admin-never-took-the-minted-secret
Issue 179 recurred; ADR 0224: a provider that keeps failing a consumer is a problem the controller reports
2026-10-06 00:14:38 +02:00
180-a-modules-own-secret-cannot-be-rotated
Issue 180: the live rotation done — searxng's secret on the home server through the console
2026-10-01 12:14:49 +02:00
181-an-assignment-does-not-record-which-provider-answers-it
Issue 181 (was 163, was 161): two records answered to 163; renumbered to the next free number across main and open pull requests
2026-10-01 12:15:31 +02:00
182-a-tool-call-reaches-whichever-instance-answers-first
ADR 0159: a tool call names the machine, every answer says which answered, a holder's runtime serves its seat's verbs; issue 182; designs 33 and 34
2026-10-01 14:00:23 +02:00
183-the-controller-could-not-publish-the-memberships-it-issued
Issue 185: a refused membership publish stopped the controller; 183 points to it
2026-10-01 15:42:37 +02:00
184-a-merge-announcement-blocks-the-controllers-receive-loop
Issues 184 and 188 resolved: the merge handler returns at once; a machine is resolved with its pins and a dropped one is said
2026-10-01 20:54:10 +02:00
185-a-refused-membership-publish-stops-the-controller
Issue 185: a refused membership publish stopped the controller; 183 points to it
2026-10-01 15:42:37 +02:00
186-a-release-across-repositories-is-an-order-in-a-persons-head
ADR 0162: a merge produces a tiered plan the mesh keeps; dependencies are one relation; design 30; issues 184, 186
2026-10-01 17:45:48 +02:00
187-the-mesh-tells-nobody-when-it-stops-working
Issues 106 and 138 resolved (ADR 0161 built and live); 187 notes a report lost without retry
2026-10-01 17:18:17 +02:00
188-a-refusal-inside-on-the-network-drops-a-machine-silently
Issues 184 and 188 resolved: the merge handler returns at once; a machine is resolved with its pins and a dropped one is said
2026-10-01 20:54:10 +02:00
189-a-rebuild-from-the-same-commit-is-not-a-move
Issue 189: the plan's half is built; the moved word stays for a decision
2026-10-01 22:25:31 +02:00
190-the-runtimes-configuration-is-written-by-modules-that-are-not-the-runtime
Issues 190, 259, 262: resolved and verified
2026-10-05 22:56:26 +02:00
191-a-route-with-only-an-internal-name-is-dropped
Issue 191 resolved: internal-only routes are served to the mesh, live on both proxies
2026-10-02 09:49:25 +02:00
192-the-meshs-tools-reach-a-person-only-by-a-registration-made-by-hand
Issues 192 and 193: the console reaches a person only by hand; the store's read-only query is not
2026-10-02 00:02:51 +02:00
193-the-store-seats-read-only-query-is-read-only-by-convention
Issue 193 resolved: both readers live on every machine, checked by asking each copy who it is
2026-10-02 00:35:03 +02:00
194-the-hosts-own-former-archive-stops-every-apply
Issue 194 resolved: the fixed host forgot its former archive on all four machines
2026-10-02 11:31:29 +02:00
195-every-assigned-module-is-counted-as-a-bus-user-without-a-credential
Issue 195: resolved by the controller composing users only for modules that can read an account
2026-10-04 17:37:20 +02:00
196-the-hub-relays-only-the-ports-it-publishes-itself
Issue 196 resolved: the hub relays the mesh, re-swept live
2026-10-02 11:23:37 +02:00
197-a-physical-link-that-is-down-is-not-filtered-when-it-comes-up
Issue 197 resolved: the wired port is guarded before it is plugged in
2026-10-02 12:22:15 +02:00
198-the-lans-dns-server-ran-outside-the-mesh-and-its-filter-closed-it
Issue 198: the home network's DNS server ran outside the mesh, and its filter closed it
2026-10-02 12:22:31 +02:00
199-a-node-scoped-seats-verb-could-not-be-called-through-the-console
ADR 0169 → 0170: the firewall seat's record renumbered after a collision on main; its built note; cycle.py refuses two records sharing a number
2026-10-02 14:51:22 +02:00
200-the-controllers-answer-to-the-console-is-refused-by-the-bus
Issues 199 (resolved: a node-scoped seat's verb through the console) and 200 (the controller's answer to a long console call is refused by the bus)
2026-10-02 14:25:03 +02:00
201-a-push-recreated-the-controller-behind-the-row-its-successor-wrote
Issue 201: what was established about the race while closing the outage half
2026-10-02 18:19:12 +02:00
202-a-module-whose-required-setting-is-unset-is-silently-left-out
Rebased onto main: ADR 0188 renumbered to 0201, and issue 202's evidence re-taken
2026-10-04 02:44:58 +02:00
203-a-fresh-assignment-is-pushed-before-its-credential-exists
Issues 203, 206 and 207 resolved by mesh-controller #233; 207's diagnosis, with its two questions left open
2026-10-03 11:50:20 +02:00
204-a-controller-handover-re-sent-every-node-a-stale-declaration
Issues 204 and 205 resolved: mesh-controller #232 and mesh-host #79 merged
2026-10-03 11:45:19 +02:00
205-a-package-resource-fails-against-a-stale-package-database
Issues 204 and 205 resolved: mesh-controller #232 and mesh-host #79 merged
2026-10-03 11:45:19 +02:00
206-a-seats-worker-changing-type-strands-the-holder-and-the-build-that-would-fix-it
Issues 203, 206 and 207 resolved by mesh-controller #233; 207's diagnosis, with its two questions left open
2026-10-03 11:50:20 +02:00
207-a-re-made-worker-replayed-every-ask-the-stream-kept
Issues 203, 206 and 207 resolved by mesh-controller #233; 207's diagnosis, with its two questions left open
2026-10-03 11:50:20 +02:00
208-a-seats-worker-is-made-only-when-the-controller-starts
Issue 208: the bus's objects asserted on every send; fix pointer, the module half, Phase 3 note
2026-10-06 11:46:27 +02:00
209-a-bundles-own-sdk-copy-registers-into-a-registry-the-runtime-never-reads
Design 38 WP4 built and proven live on all four machines; issue 209 proven live
2026-10-03 13:20:12 +02:00
210-the-host-re-creates-the-nodes-runtime-on-every-reconcile
Issue 210 resolved by mesh-host #80: an unchanged process keeps its record
2026-10-03 13:44:49 +02:00
211-a-bundle-is-built-before-the-toolchain-it-is-compiled-in
Issues 211, 212, 214, 216, 217 resolved with their proofs; 215's fix recorded
2026-10-04 00:24:53 +02:00
212-a-toolchain-rebuild-keeps-the-sdk-it-cached
Issues 211, 212, 214, 216, 217 resolved with their proofs; 215's fix recorded
2026-10-04 00:24:53 +02:00
213-the-controller-is-a-go-program-run-in-a-container
Issues 213 and 223 resolved: the controller runs as a process, and genesis hands over to it
2026-10-04 02:19:09 +02:00
214-a-plan-loses-track-of-the-controller-it-rebuilds
Issues 211, 212, 214, 216, 217 resolved with their proofs; 215's fix recorded
2026-10-04 00:24:53 +02:00
215-a-module-built-at-a-commit-stops-following-its-branch
Issues 215, 221 resolved with live proof; 222 diagnosed and resolved
2026-10-04 01:29:32 +02:00
216-a-bundle-nothing-loads-is-built-and-never-delivered
Issues 211, 212, 214, 216, 217 resolved with their proofs; 215's fix recorded
2026-10-04 00:24:53 +02:00
217-a-refused-announcement-took-down-every-containers-runtime
Issues 211, 212, 214, 216, 217 resolved with their proofs; 215's fix recorded
2026-10-04 00:24:53 +02:00
218-a-mesh-seat-is-answered-by-a-module-that-does-not-hold-it
Issue 218 resolved: the runtime follows its membership, and a refused subscription is not fatal
2026-10-04 00:14:04 +02:00
219-an-older-build-that-finishes-later-replaces-a-newer-one
Issues 219, 220 resolved, 221 located, 222 and 223 opened; WP4c built and proven
2026-10-04 01:14:44 +02:00
220-a-delivered-bundle-keeps-the-files-of-the-one-before
Issues 219, 220 resolved, 221 located, 222 and 223 opened; WP4c built and proven
2026-10-04 01:14:44 +02:00
221-a-build-machine-learns-a-new-builder-only-from-a-push
Issues 215, 221 resolved with live proof; 222 diagnosed and resolved
2026-10-04 01:29:32 +02:00
222-an-assignment-is-refused-on-the-bus-until-the-bus-machine-is-pushed
Issues 215, 221 resolved with live proof; 222 diagnosed and resolved
2026-10-04 01:29:32 +02:00
223-a-new-mesh-installs-its-controller-as-a-container
Issues 213 and 223 resolved: the controller runs as a process, and genesis hands over to it
2026-10-04 02:19:09 +02:00
224-an-apply-reopens-a-maintenance-window-by-recreating-what-it-held-still
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
225-a-provisioner-cannot-read-the-grant-secrets-since-its-code-left-the-container
Issues 225, 226, 227 resolved with their live proofs; 232 opened and resolved
2026-10-04 12:37:31 +02:00
226-the-stores-sweep-stops-at-the-first-reference-recorded-with-an-address
Issues 225, 226, 227 resolved with their live proofs; 232 opened and resolved
2026-10-04 12:37:31 +02:00
227-the-photo-apps-admin-client-asks-for-the-port-the-proxy-holds
Issues 225, 226, 227 resolved with their live proofs; 232 opened and resolved
2026-10-04 12:37:31 +02:00
228-a-login-the-mesh-set-is-never-given-back
Issue 225 → 228: the number was taken on main while this branch was open
2026-10-04 10:30:46 +02:00
229-a-rollout-cannot-be-followed-through-the-meshs-tools
Issue 229: the stale tool list is a connection opened before discovery; the fix is list-changed
2026-10-04 11:01:50 +02:00
230-a-host-that-hands-over-to-a-newer-one-loses-its-report-and-a-plan-waits-for-ever
Issue 230: a report is also lost when the apply restarts the bus
2026-10-04 11:00:27 +02:00
231-a-misspelled-placeholder-is-written-out-as-text
Research 026/03: what the predecessor taught; issue 231: a misspelled placeholder is written out as text
2026-10-04 11:49:19 +02:00
232-a-consumer-authenticates-against-a-database-its-user-does-not-live-in
Issue 232: a consumer authenticates against a database its user does not live in
2026-10-04 12:33:57 +02:00
233-a-host-without-its-package-managers-configuration-refuses-the-declaration-that-would-restore-it
Issues 233, 234: a stale declaration removed four modules, and the host could not recover
2026-10-04 14:54:50 +02:00
234-a-later-declaration-left-out-four-assigned-modules-and-a-machine-applied-it
Issues 233, 234: a stale declaration removed four modules, and the host could not recover
2026-10-04 14:54:50 +02:00
235-an-assignment-that-cannot-be-composed-is-recorded-anyway
Issues 235, 236: an assignment and a check that let through what then fails
2026-10-04 15:17:46 +02:00
236-the-catalogue-check-passes-a-manifest-the-host-refuses
ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges
2026-10-06 21:10:54 +02:00
237-assign-says-a-seat-is-held-and-that-the-node-does-not-resolve-for-lack-of-it
Issues 237, 238: a self-contradicting assign answer, and the operator's address banned
2026-10-04 17:06:38 +02:00
238-the-mesh-banned-its-own-operators-address-for-four-weeks
Research 030 and proposed ADR 0214: backups guard against mistakes and stay on the machine
2026-10-05 10:07:36 +02:00
239-a-module-name-is-taken-over-by-another-repository-and-nothing-refuses
Issue 239: name no installation
2026-10-05 02:24:27 +02:00
240-a-dry-run-build-is-recorded-and-rolled-out
Issues 239, 240, and 238's diagnosis: a module name taken over, a dry run recorded, the operator banned
2026-10-04 17:31:29 +02:00
241-one-unreadable-grants-file-dropped-every-database-on-the-control-node
Issues 241, 242: one unreadable grants file dropped every database, and the mesh has no backups
2026-10-05 02:24:11 +02:00
242-the-mesh-has-no-backups
to-be 43: backups against mistakes, declared by modules, kept on the machine
2026-10-05 11:31:19 +02:00
243-a-rebuilt-licence-store-silences-every-node
Issue 243: resolved by nodes applying any differing binding and the manager never repeating a generation
2026-10-05 10:03:49 +02:00
244-a-verb-whose-schema-is-empty-cannot-be-called-through-the-console
Issue 244: located — the console drops a mesh seat's node, and a push ran on every machine
2026-10-06 00:38:37 +02:00
245-status-calls-a-module-behind-when-only-its-repository-moved
Issue 245: behind is what a plan decided and has not yet done (the operator's direction)
2026-10-05 15:16:51 +02:00
246-the-console-says-a-module-runs-nowhere-when-a-runtime-answers-late
Issue 246: the console says a module runs nowhere when a runtime answers late
2026-10-05 15:40:14 +02:00
247-a-module-cannot-put-the-operators-account-in-a-group
Issue 247: a module cannot put the operator's account in a group
2026-10-05 15:45:24 +02:00
248-the-controllers-event-consumer-replayed-a-week-and-held-every-merge-behind-it
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
249-a-modules-new-state-is-refused-until-a-push-the-merge-did-not-make
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
250-a-merge-made-through-the-forges-tool-is-announced-twice
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
251-the-records-checkout-could-not-sync-after-it-ran-as-another-account
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
252-a-merges-changed-modules-were-read-wrong
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
253-the-stores-collector-would-delete-every-archive-the-mesh-keeps
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
254-plans-for-successive-merges-run-over-each-other-and-one-was-left-open
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
255-the-journal-verb-read-nothing-for-a-system-service
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
256-a-first-machines-report-read-as-stale-between-the-two-sends
Issues 224, 248-252, 254, 255 resolved, 256 opened and resolved, 253 where it stands
2026-10-05 18:36:19 +02:00
257-a-plan-waited-on-a-declaration-its-first-machine-never-reported
Issues 257, 261: a reconcile applied an older declaration over a newer one
2026-10-05 21:44:09 +02:00
258-every-machine-bound-the-resolver-to-itself
Issue 273 and ADR 0232: a binding to a consumer's data moves only by a person
2026-10-06 15:21:42 +02:00
259-a-named-push-sent-every-machine
Issues 190, 259, 262: resolved and verified
2026-10-05 22:56:26 +02:00
260-the-resolver-started-before-its-zones-file-existed
Issues 260, 262: a service waits for what it reads; a mesh name has no IPv6 address rather than no name
2026-10-05 22:08:12 +02:00
261-a-module-was-applied-and-given-back-half-a-minute-later
Issues 257, 261: a reconcile applied an older declaration over a newer one
2026-10-05 21:44:09 +02:00
262-an-alpine-container-could-not-find-a-machine-by-its-mesh-name
ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges
2026-10-06 21:10:54 +02:00
263-every-consumer-pays-for-the-tightest-backends-name-limit
ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges
2026-10-06 21:10:54 +02:00
264-a-self-updating-engine-lost-the-report-of-the-apply-that-delivered-it
Issue 267: a reconcile's report overtook the apply that followed it
2026-10-06 01:46:33 +02:00
265-a-push-outlived-its-caller-and-its-answer-was-refused
Issue 265: a push outlived its caller, and the bus refused its answer
2026-10-06 01:14:56 +02:00
266-a-merge-on-the-bus-was-never-handed-to-the-controller
ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges
2026-10-06 21:10:54 +02:00
267-a-reconciles-report-overtook-the-apply-that-followed-it
Issue 267: a reconcile's report overtook the apply that followed it
2026-10-06 01:46:33 +02:00
268-letta-printed-its-passwords-into-its-log
Issue 268: letta printed its passwords into its log
2026-10-06 02:15:00 +02:00
269-the-controller-cannot-write-a-work-queues-cancelled-set
To-be 45 in progress; issue 269: the controller cannot write a cancelled set
2026-10-06 03:04:36 +02:00
270-phase-1-watches-signals-that-come-later-and-hears-only-the-controllers-faults
ADR 0229: the core's order is a lease the store remembers, and an epoch a machine is sent once it reads one
2026-10-06 12:26:33 +02:00
271-a-new-consumer-replayed-the-morning-to-the-operator
Issue 271: a new consumer replayed the morning to the operator
2026-10-06 12:04:23 +02:00
272-the-sdks-provider-loop-says-nothing-on-the-bus
ADR 0229: the core's order is a lease the store remembers, and an epoch a machine is sent once it reads one
2026-10-06 12:26:33 +02:00
273-a-rule-for-the-resolver-moved-a-machines-databases
ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges
2026-10-06 21:10:54 +02:00
274-a-provider-was-granted-consumers-bound-elsewhere
Issue 274: a provider is granted only the consumers bound to it
2026-10-06 16:08:30 +02:00
275-a-machine-waiting-for-its-push-was-said-urgent
Issue 275: a machine waiting for its push was said to be urgent
2026-10-06 18:06:43 +02:00
276-a-handler-that-did-its-work-was-offered-it-five-times
Issue 276: the audit logger and the usage store retry, and lose no event
2026-10-06 18:37:28 +02:00
277-one-unanswered-question-was-an-urgent-alert-nobody-could-read
Issue 277: one unanswered question was an urgent alert nobody could read
2026-10-06 18:45:19 +02:00
278-a-module-held-by-no-machine-was-read-as-shared-code
Issue 278: a module held by no machine was read as shared code
2026-10-06 19:57:21 +02:00
279-a-folder-cannot-be-owned-by-the-account-a-module-runs-as
Issue 279: a folder cannot be owned by the account a module runs as
2026-10-06 20:57:38 +02:00
280-a-rebuild-of-an-unchanged-source-was-read-as-a-new-bus
ADR 0238: a commit is the build at hand — one commit, one change plan, checked off the trunk and published only on it
2026-10-06 22:54:09 +02:00
281-a-tier-sent-one-module-at-a-time-blamed-a-module-for-its-machine
Issue 281: a tier sent one module at a time blamed a module for its machine
2026-10-06 22:25:22 +02:00
282-a-secret-on-a-command-line-is-kept-in-the-runtimes-events
Issue 282: a secret on a command line is kept in the runtime's events
2026-10-07 01:38:37 +02:00
README.md
The numbering is the flow: decisions are 02, design is 03
2026-08-23 18:05:11 +02:00

README.md

04-ISSUES

The front door for "something is wrong" at the level of the mesh's design or governance. Diagnosis happens here, where the whole mesh is in view; the fix lands in the owning code repository.

What belongs here

Belongs here Belongs in the knowledge base
The design permits a failure to be silent How to fix one occurrence of it
A documented rule is enforced by nothing A command that works around it
A stated invariant is false in practice A node-specific quirk
The owner is unknown and finding it needs the whole mesh in view Symptom → fix, once the answer is known

The knowledge base already holds the operational record and is indexed on symptoms. This folder is not a second copy of it. An issue here is a question HQ must answer; an entry there is an incident someone must clear. An issue whose answer is a general lesson belongs in both.

Structure

NNN-short-name/
  00-report.md      the symptom as observed, with the evidence; status in frontmatter
  01-diagnosis.md   the investigation trail, dated, including what was ruled out

Frontmatter, on 00-report.md

---
status: open | diagnosing | located | resolved | wontfix
opened: YYYY-MM-DD
located-in: []       # owning repo(s) or module(s), filled by diagnosis
fixed-by:            # pull request or commit reference, filled at resolution
amended-design:      # design doc path, when the root cause was a design gap
---

Rules

  • Anyone may open an issue. No localisation is required to report one.
  • The full flow is playbook 00-META/process/03-issues.md.
  • Closed issues are never deleted — they are the mesh's symptom-to-component memory.
  • wontfix is legitimate and requires a sentence saying why.
Reference in New Issue View Git Blame Copy Permalink