Compare commits

...
+17
View File
@@ -94,6 +94,23 @@ instance whose definition holds `role.launch` within-role; otherwise the
file refuses. Only that instance keeps `role.launch`. Every other instance
loses it, so for them it's gated.
### Chief of staff instance
`roles/chief-of-staff.json` is the role for the human's main agent (lead
decision 104): tools `read`, `grep`, `find` and `ls`, network `api-only`,
`message.send` within role, no cross-role actions and no credentials.
Every other action is gated, `task.create` and `role.launch` included. The
instance entry in `roles` of the business file is:
```json
"mos": { "definition": "chief-of-staff", "holder": "mos" }
```
The instance id `mos` is the human's choice (lead decision 116). The
entry has no `tracker` and no `credentials`, because the role uses
neither, and the file's `launch` block must not name it. Widening the
role is a change to the role file, which the human approves.
### Project file
```json