diff --git a/README.md b/README.md index bb1d111..bde4cdc 100644 --- a/README.md +++ b/README.md @@ -167,7 +167,8 @@ guessing one more derived leaf field from nearby offsets, and the checked-in [`docs/rehost-queue.md`](docs/rehost-queue.md) file is now the control surface for that loop: after each commit, check the queue and continue unless the queue is empty, a real blocker remains that cannot be advanced by any further non-hook work without guessing, or approval -is needed. A checked-in +is needed. `final` responses are stop-only there too: if no stop condition is true, keep working +and use `commentary` updates instead of placeholder status replies. A checked-in The same runtime surface now also exposes higher-layer blocker probes: `runtime inspect-periodic-company-service-trace `, `runtime inspect-region-service-trace `, and diff --git a/docs/README.md b/docs/README.md index e3b6494..5630bf5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -202,7 +202,9 @@ The highest-value next passes are now: instead of guessing another derived leaf field from neighboring raw offsets; the checked-in `docs/rehost-queue.md` file is the control surface for that work loop, and after each commit the next queue item should run unless the queue is empty, a real blocker remains that cannot be - advanced by any further non-hook work without guessing, or approval is needed + advanced by any further non-hook work without guessing, or approval is needed; `final` + responses are stop-only there too, so active work should continue under `commentary` updates + rather than placeholder status replies - `rrt-runtime` now also exposes higher-layer probe commands for the current blocked frontier: `runtime inspect-periodic-company-service-trace `, `runtime inspect-region-service-trace `, and diff --git a/docs/rehost-queue.md b/docs/rehost-queue.md index 34d22b1..fd9bc17 100644 --- a/docs/rehost-queue.md +++ b/docs/rehost-queue.md @@ -7,6 +7,10 @@ Working rule: - Only stop if the queue is empty, the remaining work cannot be advanced by any further non-hook work without guessing, or you need approval. - Before any final response, state which stop condition is true. If none is true, continue. +- `final` responses are stop-only. +- Do not send placeholder or status-only `final` responses such as `Continuing.` or `Working on + it.`. +- If no stop condition is true, keep working and use `commentary` updates only. ## Next diff --git a/docs/runtime-rehost-plan.md b/docs/runtime-rehost-plan.md index 4a5fc16..50ae6b6 100644 --- a/docs/runtime-rehost-plan.md +++ b/docs/runtime-rehost-plan.md @@ -258,6 +258,11 @@ The annual dividend-adjustment lane now rides that same seam too: the runtime no shared year-or-control-transfer metric reader, the board-approved dividend ceiling helper, and the full annual dividend branch over owned cash, public float, current dividend, and building-growth policy instead of treating dividend changes as shell-dialog-only logic. + +The workflow rule for this queue is explicit too: `docs/rehost-queue.md` is the control surface, +`final` responses are stop-only, and active work should continue under `commentary` updates unless +the queue is empty, no further non-hook work can advance it without guessing, or approval is +needed. The same save-native company direct-record seam now also carries the full outer periodic-company side-latch trio rooted at `0x0d17/0x0d18/0x0d56`, including the preferred-locomotive engine-type chooser byte beside the city-connection and linked-transit finance gates.