Other

/false-green-gate

'done/green/fixed' needs a live probe. Triggers: completion claim, pr-loop completion, deploy/render/dashboard 'done'.

$ golems-cli skills install false-green-gate

Updated 6 days ago

Fleet law: canon #4 owns "done = user-visible". This skill is the mechanical same-turn live-outcome probe gate.

Scope

The gate stays in scope by default, including no-tool completion claims. It exempts only a turn with at least one assistant tool call where every call is on the closed conversational allowlist: voice_ask, voice_speak, brain_search, brain_recall, brain_expand, or AskUserQuestion, including the exact VoiceLayer and BrainLayer MCP names for those tools. Bash, edits, delegation, Codex shell/exec, other MCP tools, and cmux tools keep the turn in scope. Seat names and claimed repo-diff metadata do not determine scope. A coach using Bash is gated; a voice-only coaching drill is exempt. Probes must be same-turn.

What It Is

A deterministic detector over an agent transcript: a completion claim is FALSE-GREEN unless the same turn carries the live-outcome probe its claim domain requires. This is the MECHANICAL gate that /deploy-verify and /never-fabricate describe in prose — "manual gates drift, automated gates don't." The pinned RED/GREEN transcript fixtures ARE the replayable gate (R-003/R-014 pattern, consumed in the T6 deterministic-CU smoke-spec shape).

The historical evals/fixtures/ corpus is pinned for Jev replay. This gate's suites replay it unchanged, with no synthetic activity. New scope contracts live in evals/scope/fixtures/, outside the Jev preflight tree.

The Rule — required same-turn probe by claim domain

Claim domainRequired live probe (same turn)Violation if missing
render / audio / mp3ffprobe proving size>0 AND duration>0 on the claimed pathFALSE_GREEN_FFPROBE
…cloned / 2-voice render--reference resolves to a registered clone (<GOLEMS_EXPERT_VOICE>-c4/ben-c1; placeholder examplechannel), no system-TTS fallbackFALSE_GREEN_VOICE
dashboard / UI / siteHTTP 200 on the served URLFALSE_GREEN_DASHBOARD_200
AND a signed-in click-through (200 alone is not enough)FALSE_GREEN_CLICK_THROUGH
deploy / merged / installedbuild-stamp that POST-DATES the mergeFALSE_GREEN_STAMP
AND a live round-trip (pgrep/launchctl/health 200)FALSE_GREEN_LIVE_PROBE
build / contractthe operational entrypoint exercised (wrapper dry-run / contract test)FALSE_GREEN_LIVE_PROBE
generic "done"at least one live round-tripFALSE_GREEN_LIVE_PROBE
"rigorously verified manually" + no probe— (ranked last, false-green-permitting)MANUAL_SUBSTITUTE

"Same turn" = the events since the last human message — the probe tool calls and their results the agent ran before the claim. Negated/in-progress statements ("not done yet") are not claims.