pilot-watch-alert-response

What problem does it solve?

It helps teams handle live Kubernetes change events by turning an incoming cub-scout watch stream into a clear per-event Pilot decision (PASS/WATCH/ASK/BLOCK) with supporting evidence.

Core Features & Use Cases

• Event-driven acceptance kernel: Consumes the real-time cub-scout watch JSONL/webhook stream and renders a verdict per event as they fire.
• Receipt-first fast path: Preferentially uses inline receipts emitted by cub-scout watch --emit-receipt-on (e.g., drift.detected, ownership.changed) to decide quickly without synchronous follow-up calls.
• Evidence-backed slow path: When receipts are absent or unverifiable, fetches context using cub-scout read-only commands such as compare three-way, explain, and receipt verify to reach an evidence-complete decision.
• Operational guardrails: Expects receipt to be optionally omitted when receipt-building is suppressed or fails, and requires consumers to check key presence rather than treating null as valid evidence.
• Best-fit scenarios: Use during real-time deployment governance and alerting where you need immediate, audit-friendly decisions from drift and ownership change signals.

Quick Start

Use the skill by wiring Pilot to receive cub-scout watch webhook events for drift and ownership changes, and then decide PASS/WATCH/ASK/BLOCK per incoming event using the inline receipt verdict when present.