Files
skills/skills/kvb-org-organize/peers.md
T
Kevin Veen-BirkenbachandClaude Opus 5.5 367fe56dd4 feat(kvb-org-radio): split radio and post, add kvb-org-update
The radio (call, broadcast, security, pan-pan, mayday) reaches its addressee at the next tool step and wakes it. The post (post with --to, newsletter without, call receipts) arrives through a new Stop hook when the turn ends and never wakes. Legacy rows map onto the two channels and send direct stays as an alias. A PreToolUse hook holds the mayday's radio silence for writing tools and Bash. Only the sender, helpers who join with radio.py assist, bare radio.py calls and the config's allowed commands pass, and any shell operator or parse error blocks. kvb-org-update announces changed skills as one newsletter. Callers moved to send call --to.

🎯 Fix: 90 %
💥 Break: 5 %
💸 Cost: 104 %
⏱️ Time: 100 %
🛡️ Security: 100 %
💰 Value: ?
🏆 Score: 82
🚦 Gate: ⚠️ cost 104 % > 100: ask the operator before the commit

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 18:08:10 +00:00

1.9 KiB

Coordinating a failure or fix with peers

kvb-org-coordinate, kvb-ci-triage, kvb-code-tune, kvb-org-split and kvb-cleanup follow these steps.

  1. Look: council.py list, the kvb-org-rasci register, the radio, hotfix.py match --line '<line>' --repo <worktree> of the kvb-git-hotfix skill and the refs (the kvb-git-merge-fix skill's find_fix.py). A claim, a hotfix row or a committed fix answers the question without a message.
  2. Claim the office (Election in SKILL.md).
  3. Ask (${CLAUDE_SKILL_DIR}/../kvb-org-radio/scripts/radio.py send call --to <name>, since each must answer) only the peers whose lines the work touches, the lineage owners (lineage.md) and, for capacity, the chair. One batched message per peer: what you claimed, the evidence (failing line quoted literally, run id, measurement), the suspected cause marked as a thesis, and the question "Already known or fixed on your side? Reply with a SHA or branch, or 'none'." The first line stands on its own, because a busy recipient sees only that line. In the register the peers asked are C, the chair that grants capacity is S.
  4. Wait up to 5 minutes before building anything, investigating read-only meanwhile. A fix that arrives goes through the project's normal path (merge, cherry-pick or port), and you release your claim. Silence is neither a "no" nor a competing claim: after 5 minutes, proceed.
  5. Report to the same peers through radio.py post --to <name>: commit, branch, what changed, the evidence it works, and the merge it reaches them by; an abandoned or failed attempt too. A hotfix is no report: it is recorded with hotfix.py add and update, never by message or radio post. In the register, enter the peers told as I and mark every key result the evidence proves as met. Then release the claim: the task ends done, or stopped while a key result is open.