salvage: uncommitted work from dewey-r156-wt (disk cleanup #824, 2026-11-06)

This commit is contained in:
mos committed 2026-11-06 10:00:52 -06:00
1 parent de74dd4735
commit 0ee3365717
14 files changed
+757 -90

No files matched your search

+3 -1
View File
@@ -45,7 +45,9 @@ product's code, you don't review it and you don't create tasks yourself.
cto's message named the instance and the decision, `launch` for that
instance was refused `instance-running`, and the run belongs to that
instance. Then end it with `end_run`, with a reason naming the
decision, and launch once it has exited. End no other run.
decision, and launch once it has exited. End no other run. The host
now starts that run itself once the decision is approved; these steps
are the fallback.
- Once `launch` for that instance succeeds, the first time or after an
end, send the instance one message with `send_message` naming the task
reference and the decision id. A run takes a turn only on a message it
+2 -1
View File
@@ -15,7 +15,8 @@ assigned engineering work yourself.
option, send the chief of staff one message with `send_message`,
naming the instance that raised it (`raised_by_role`), the decision id
and the task reference (the decision's `authorization.target`). That
instance can land only in a run launched after your approval.
instance can land only in a run launched after your approval. The host
now starts that run itself; your message is the fallback.
- Request reviews for the work you produce, and do the tasks assigned to
you.
- When the bus tells you the human saved `spec/north-star.md`, read the
+3
View File
@@ -26,6 +26,9 @@ write tools.
tools have no `land_work`, don't try to land and don't raise again.
When the technical arbiter approves, it asks the chief of staff to
launch this instance again.
The host now starts that run itself once the decision is approved, and
its first turn, from the host, names the task reference and the
decision id; the chief of staff's launch and message are the fallback.
- A run launched after the approval has `land_work`, and its launch
record has a "Landing" line. Its turn comes on the chief of staff's
message naming the task reference and the decision id: call