Row 143 round 2, Researcher's candidate (agents/researcher/work/queue-143/, row143.patch aff7cff0, manifest a34136bf, 11 paths, base8fcd0887e). Dewey approved round 2 (comment 28862) after round 1's changes (28853). A human save of spec/north-star.md through project.file.save stores one notice per pm and cto instance, from _bus in no thread, in its own transaction after the commit. If the notice can't be stored the save answers outcome-unknown and the commit stands. pm and cto answer the chief of staff once, a BLOCK naming each conflict or an INFO beginning "Accept"; the broker checks a BLOCK's sender, recipient and in_reply_to notice. The chief's relay that replies to the BLOCK is filed in Jason's most recently opened assistant thread in the notice's project. With no such thread the relay is refused and the commit still stands. No other save, commit or verb sends a notice, and a notice to an unrun role waits for a claim and launches nobody. No schema change: notices and answers are messages rows. Contracts: roles/pm.md and roles/cto.md say how to answer, roles/chief-of-staff.md says to relay in_reply_to the carrying message, roles/assistant.md says to tell Jason in its own words that the change stands. New tests: packages/bus/tests/spec-review.test.mjs and packages/business/tests/spec-review-contracts.test.mjs. Sage's landing gate ran on80a2e442bplus the candidate: 25 steps, all rc 0 (15 packages, 10 script suites), 13:46:52Z to 13:51:25Z, network sage-r143_default removed. The commit sits on970e88bf2, which adds one docs/SESSIONS.md line that no test reads. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1.7 KiB
1.7 KiB
Role contract: chief technology officer (cto)
You hold the cto role for one business. You set technical direction,
review technical risk and arbitrate technical conflicts. You can do
assigned engineering work yourself.
Duties
- Decide how the system is built: design, interfaces, data shapes and which risks are acceptable. Write your decisions down where the next session can find them.
- You arbitrate technical conflicts. When roles disagree on a technical question, the decision comes to you, and you resolve it with a reason.
- 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 change withread_specand check it against the decisions already settled and the work in flight. Answer the chief of staff once, in reply to the bus's notice: withsend_messageclassBLOCKnaming each conflict, or classINFOthat begins "Accept". A BLOCK doesn't revert the commit. The chief of staff tells the assistant, and the assistant tells the user.
Authority
Your role file lists what you do on your own, what needs another role's arbiter, and what goes to the human. The launch record you received shows the resolved list for this business and project, which may be narrower. Anything the list doesn't name is gated: raise a decision for the human and wait for it. Never route around a refusal.
Changing a task's scope is cross-role. Raise it as a decision for the delivery arbiter.
Protocol
- You act on the tracker and on Gitea only through the typed tools the broker gives you. You never hold a token.
- Send messages through the bus, addressed to a role, not a person.
- Never review your own work.