Files
skills/skills/kvb-ci-triage/funnel.md
T
Kevin Veen-BirkenbachandClaude Opus 5.5 5b55c39b64 feat(kvb-check-score): score journal, backfill and per-metric burndown overlays (006)
score.py names the Cost and Time metrics Tokens and Velocity from one label file and appends every scored block to a score journal in the council root. backfill.py rebuilds that journal from commit messages with its own label mapping, deterministic and idempotent, so another host can import its history. The hub serves the journal, and the Gantt burndown draws each metric as its own overlay on a right 0-100 % axis, every overlay off by default and switched by legend chips whose state the view store keeps.

🎯 Fix: 90 %
💥 Break: 5 %
💸 Cost: 100 %
⏱️ Time: 100 %
🛡️ Security: 100 %
🏆 Score: 86
🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 %

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 12:32:54 +00:00

2.2 KiB

Working one cluster in its sidetree

Run inside the cluster's own worktree, so no cluster's edits land under another cluster's work or under a running gate or deploy. The kvb-ci-triage skill's Rules apply here too.

  1. Dialectic: invoke the kvb-think-dialectic skill for the cluster: form a thesis about the root cause from evidence (the job log, its artifacts, the code at the run's commit, git history), attack it with independent skeptics, and iterate to a ~99% thesis.
  2. Shared vs hidden causes: a cluster is a hypothesis, not a proof; if the dialectic shows it splitting into two causes, split it, and the new cluster gets a funnel of its own. When a job hides a second failure behind the first, keep going until the job is actually green, not just past the first error.
  3. Fix at the root: apply the real fix for each proven root cause in the sidetree, with a test and a negative control as the kvb-org-swarm skill demands. Light runs (no Docker, about a minute: one test file or module, ruff) self-admit with ${CLAUDE_SKILL_DIR}/../kvb-org-organize/scripts/watch.py admit --kind test-nostack; make test, gates, deploys and anything with Docker run in the background through ${CLAUDE_SKILL_DIR}/../kvb-org-queue/scripts/queue.py hold --kind <kind> --task <register task> -- <command>, which waits for the rule-based grant and releases on exit. The fix enters the main line only at the funnel's bar (the kvb-org-swarm skill's: fix confidence ≥ 90 %, break risk ≤ 5 %, tokens and velocity ≤ 100 % in the kvb-check-score block; over 100 %, ask the operator before the commit, naming the cause) after its independent review; below the bar the cluster ends as a proposal for the operator, never as a merge. Never mask a failure: no retry-until-pass, no disabling the check, no soft-skip. If a failure is genuinely external (upstream outage, flaky infra), confirm that with evidence and surface it honestly instead of fixing around it. Report every fix, proposal and abandoned attempt to the peers asked in step 3 of the skill with ${CLAUDE_SKILL_DIR}/../kvb-org-radio/scripts/radio.py post "<text>" (--to <name> per peer), then remove the sidetree.