Эмпирическая проверка механизма перед фиксацией дизайна

testing

vc-feasibility-test is a Claude Code skill that runs a one-shot empirical probe to verify whether a mechanism actually behaves the way a design assumes, before the approach is locked in SPEC or INNOVATE. It activates when an unverified external API, library, or runtime behavior is the deciding factor — typically triggered by a VC-FEASIBILITY-PROBE-NEEDED signal from vc-spec-agent, vc-innovate-agent, or a vc-validate-agent Layer 2 dimension agent. The probe is selected from an 8-family taxonomy covering Node/Bun scripts, unit-test harnesses, tRPC/Prisma/DB queries, live third-party API calls (OpenRouter, Stripe, Clerk, Composio), disposable-container docker exec, Playwright/CDP sessions, WS/SSE handshakes, and Cloudflare Worker sandboxes. Every family carries a mandatory safety gate — cheap-local, needs-container, needs-live-provider, needs-browser, or needs-cf — and any probe that cannot satisfy its gate yields INCONCLUSIVE rather than being silently skipped. The output is a VERDICT artifact: VIABLE, NOT-VIABLE, or INCONCLUSIVE, always produced before a design decision is made.