2026-10-03 09:50:56 +00:00
4 changed files with 19 additions and 6 deletions
@@ -1,9 +1,9 @@
 ---
-status: located
+status: resolved
 opened: 2026-10-02
 located-in:
  - mesh-controller
-fixed-by:
+fixed-by: mesh-controller PR #233
 amended-design:
 ---

@@ -1,9 +1,9 @@
 ---
-status: located
+status: resolved
 opened: 2026-10-03
 located-in:
  - mesh-controller
-fixed-by:
+fixed-by: mesh-controller PR #233 (the worker's shape and the plan's order); a credential older than its shape is re-issued by hand, not detected
 amended-design:
 ---

@@ -1,9 +1,9 @@
 ---
-status: open
+status: resolved
 opened: 2026-10-03
 located-in:
  - mesh-controller
-fixed-by:
+fixed-by: mesh-controller PR #233 (a re-made worker on a history-keeping stream delivers from now on); the two questions on retention and on outcomes for commits already passed stay open for a decision
 amended-design:
 ---

@@ -0,0 +1,13 @@
+# Diagnosis — 207
+
+**2026-10-03.** The worker was deleted by hand and the controller, on restart, recreated it with the
+server's default delivery policy — every message the stream holds — on a stream that keeps its history.
+The build machine then took every ask since 1 October in order, and each outcome was taken in as news:
+`takeIn` records the build and registers the manifest it carries, whatever commit it is from. Nothing
+in the consumer derivation said where a seat's worker starts; nothing in the taking-in compared the
+outcome's commit with what the catalogue already held.
+
+Owner mesh-controller. Fixed in part: a worker re-made by the controller on a history-keeping stream
+now delivers from the moment it is made (PR #233). Open for a decision, kept in the report's questions:
+whether a seat's work queue should keep acknowledged asks at all, and whether an outcome for a commit
+the catalogue has already moved past should be recorded but never registered or rolled out.