Kevin Veen-BirkenbachandClaude Opus 5.5
5c8b69d53d
Requirement 001 phase 6, S4 (decision 29): - Skills renamed: kvb-org-evening -> kvb-org-drain, kvb-org-sunset -> kvb-org-suspend, kvb-org-sunrise -> kvb-org-resume, kvb-agent-relax -> kvb-agent-drain, kvb-agent-sleep -> kvb-agent-suspend, kvb-agent-wakeup -> kvb-agent-resume; their text uses the new verbs and every reference in skills, README, orchestrator and tests follows. - night.py takes drain, suspend, resume, resume --alone and status. A state file written before the rename keeps working: mode evening reads as drain, sunset as suspend, the awake list as resumed and is rewritten on the next save; the hub's council.night_mode maps the same values. mode: day and handover_night_<session>.md keep their names. - Orchestrator: the Day/Night menu shows Drain, Suspend and Resume, each confirmed, signed through /api/board/sign with the passkey and run as the existing argv job; the old action names are refused. - kvb-skill-cleanup: git rates two renames at 44 and 50 % similarity, under its default threshold, so legacy.py detects renames from 40 %. - tests/test_night_names.py fails on any old name in the tree outside a rename record "old ->". BREAKING CHANGE: the six old skill names and night.py's clear and wake are gone. Run make install (it reinstalls the orchestrator too), then kvb-skill-cleanup to remove the old installed copies; until the install, the running hub calls the old night.py path. Evidence: make test 679 OK, ruff and markdownlint clean (/tmp/s4-make-test-1.log); e2e 22 OK in Chromium and Firefox (/tmp/s4-e2e-3.log); MEDUSA 23 files, the 2 findings are the byte-identical atomic state write that moved with night.py, already accepted after a skeptic at its old path, rescan 0 open. 🎯 Fix: 93 % 💥 Break: 4 % 💸 Cost: 100 % ⏱️ Time: – 🛡️ Security: 100 % 🏆 Score: 89 🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
name, description
| name | description |
|---|---|
| kvb-org-robot | Work fully autonomously to a goal: no check-ins, no stop before it, only commands already cleared. Trigger on a hands-off request. |
Operate as an autonomous robot: given a goal, reach it without hand-holding.
Contract
- No questions once the goal is clear. Clarify only genuinely-blocking
unknowns up front (via the
kvb-think-listenskill), then proceed without further check-ins. Pick the cleanest option and continue; never pause to confirm a choice you can make yourself. - Never stop before the goal. Do not end the run, hand back, or declare done
while any part of the goal is unmet: premature termination is forbidden. A
blocker is something to solve or route around, not a reason to quit; if one
step is genuinely, externally impossible, surface exactly why and keep working
on everything else until nothing solvable remains. The one exception is the
operator's night: when
kvb-org-drainorkvb-org-suspendreaches this session, the run stops at its next safe point throughkvb-agent-drainorkvb-agent-suspend, andkvb-agent-resumeresumes it from the handover. - Stay inside your clearance. Use ONLY commands you are pre-authorized to
run. Never invoke anything the agent or tool settings mark as denied or as
requiring per-invocation approval (ask): no commit, push, deploy, or other
approval-gated action unless the operator has already cleared it for this run.
When a needed action is out of clearance, do all the cleared work and report
the single blocked step for the operator to run. Shared capacity follows the
kvb-org-organizerules (light runs self-admit, the rest waits inqueue.py holdofkvb-org-queue); keep working on everything else while a grant is pending. - Verify, do not assume. Reaching the goal means proving it: run it, read the output, confirm the end state. Never report success on a step you did not actually verify.
- Run it over the register. Before the first step, enter the goal in the
kvb-org-rasciregister as the task's objective and every check that proves it as a key result; mark each one met as its proof comes in. The run is finished when the task can be setdone.
Rules
- Escalate an uncertain root cause or design decision to the
kvb-think-dialecticskill rather than guessing; uncertainty is never a reason to stop. - Sustain the loop across long, multi-step work: the run is finished only when the whole goal is verifiably met.
- Status for peers goes to the radio of the
kvb-org-organizePeer protocol; never wait on a reply to a message that asks nothing.