Requirement 001 stays the single place for the Agent Orchestrator, as its decision 1 asks. Decisions 23 to 38 record the operator's answers of 2026-11-07: phase 5 (console, deny channel, rule requests, composer with whisper, Hierarchie, separate agent order, Tasks tab, merge flow) and phase 6 (Firewall with passkey-signed settings writes and groups, asks and choices as tasks with a choice request per channel, drain / suspend / resume, agent and node popups with search, animated faces, fit to window, rename once, the Deutschlandfunk stream and a squelch, the tree cause, a Ressourcen tab). A second diagram shows the serial subtrees S1 to S7, and each gets its acceptance criteria and tests. 🎯 Fix: 95 % 💥 Break: 1 % 💸 Cost: 100 % ⏱️ Time: – 🛡️ Security: 100 % 🏆 Score: 94 🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Requirements 📋
User stories, operator decisions and acceptance criteria that guide
agent-assisted implementation in this repository. The kvb-create-requirement
skill defines the format.