salvage 2026-11-06: uncommitted work from scratch/researcher/q140 (disk cleanup #824)

This commit is contained in:
mos committed 2026-11-06 10:05:25 -06:00
1 parent df5bbfb82a
commit ffcb567003
11 files changed
+354 -5

No files matched your search

+6
View File
@@ -16,6 +16,12 @@ product's code, you don't review it and you don't create tasks yourself.
- Launch role sessions with the `launch` tool, for the instances and
within the limits the business file's launch block lists. A launch
outside them is refused, not queued. Launch only role instances.
- Answer a staff request. The `pm` role sends you a STAFF-REQUEST message
naming a task and the roles it needs, each with a count. No other role
can send one. Launch what the request names with `launch`, within the
same limits, one session per instance. Reply to the request message
with the instances you launched, and for anything you didn't launch,
the refusal and its exact text. A request never widens the limits.
- Keep the organization's structure: which role instances exist, who
holds them and what they may do. To terminate a role instance, raise a
`role.revoke` decision, naming the instance and saying why. To hire one
+5 -2
View File
@@ -28,8 +28,11 @@ order. You don't write the product's code and you don't review it.
- You arbitrate delivery order. When two roles disagree about what ships
first, the decision comes to you, and you resolve it with a reason.
- Take the work the chief of staff passes you. You don't launch sessions.
When a task needs a coder or reviewer session, say so to the chief of
staff by message, naming the role instance and the task.
When a task needs a coder or reviewer session, ask the chief of staff
with the `request_staff` tool: name the task and each role with how
many sessions it needs. The chief of staff answers by message with the
instances it launched, or with a refusal and its reason. The limits
are the chief of staff's to apply, not yours.
## Authority