Kevin Veen-BirkenbachandClaude Opus 5.5
4540494c30
The Agents views gain a Hierarchie view: an org chart of the chair and the line offices read from the council claims. The operator appoints, hands over and recalls an office there; the page signs each change with the passkey and a host unit (client/offices.py, offices path unit) verifies the signature, removes a live holder itself and runs a plain council.py claim for the successor. council.py loses the --operator flag, so no agent can override a live holder. The agent order is now separate from task priority: rasci.py agents order stores it in agent-order.json beside the register through the nofollow helpers and never writes a --prio pin. It only breaks ties of equal task rank, also among the queue grants. The Hierarchie view edits it as a drag list. Host units run the installed skill scripts, so orchestrator.sh keeps the offices unit off while the installed council.py, nofollow.py or rasci.py differ from the tree. Job files, council files and hub records are read with O_NOFOLLOW and O_NONBLOCK and size caps; nofollow.rewrite replaces a claim without creating directories, so a beat never revives a released office. 🎯 Fix: 92 % 💥 Break: 4 % 💸 Cost: 100 % ⏱️ Time: 79 % 🛡️ Security: 100 % 🏆 Score: 100 🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Succession
- A piece of work or a cluster ends with its result, a proposal, or an
abandoned attempt, posted to the radio for the peers who heard the claim.
The holder then runs
council.py release <office>, and the next agent that starts the work is elected afresh. - A representative or the chair that ends hands its office to the next-oldest live representative (by claim time) and posts it to the radio.
- Chair handover is explicit: the outgoing chair sends the incoming chair the
queue and the running grants
(
${CLAUDE_SKILL_DIR}/../kvb-org-radio/scripts/radio.py send call --to <name>: it must confirm), posts the new holder to the radio, and keeps allocating until the incoming chair confirms. Two allocators never run at once. - A claim is stale when its holder's session is gone: in Claude Code its
session id is no longer in
~/.claude/sessions; other runtimes runcouncil.py beatat least hourly and go stale after 60 minutes without one.claimthen exits 4. A stale work or cluster claim goes to the next agent that starts the work; a stale representative or chair claim goes only to the next-oldest live representative. The successor runscouncil.py takeover <office> --work "..."and posts the succession to the radio; everyone else leaves it alone. - After a restart or reboot, run
council.py list --mineand claim again every office you believe you hold:/tmpmay have been wiped. - Only the operator, through the Orchestrator's passkey-signed Hierarchie view, removes a live holder; agents have no override.