One merge + one deploy turns on the truth path and stops the RepID drain. Both changes are behind safe-default, reversible env toggles — merging changes nothing until the flags are flipped.
| Item | Commit | Toggle | Default | Effect of default |
|---|---|---|---|---|
Drain gate (penalty needs hallucination_caught) |
9dbeb98 |
HAL_DIRECT_PENALTY_REQUIRES_HALLUCINATION |
ON (!== 'false') |
drain stops the moment code deploys (no flip needed) |
| Truth-path scorer (cross-LLM fact-check) | prior (HAL_STRICTNESS path) |
HAL_STRICTNESS |
unset → 1 (extractor) | prod unchanged on merge; flip to 2 routes scoring through fact-check |
Note: the sprint's
HAL_SCORER=extractor→factcheckis the real flagHAL_STRICTNESS(1=extractor,2=fact-check).HAL_SCORERdoes not exist in code; useHAL_STRICTNESS.
- Merge
feat/cc-2026-06-03-r3-armtruth(incl.9dbeb98) tomain. (Optionally merge GA51ea68a1for the hardened client — integration verified conflict-free; not required for the drain stop.) - Deploy
mainto Railway (normal deploy; no env change yet).- On boot, the drain gate is ON by default → the 9 floor-pinned agents stop being re-clamped on new HAL_SCORE_EVENTs.
- Verify:
npm run verify:crosscheck -- --only repid-floor— over a clean window,current_repidrises off the floor as agents earn positive deltas. (The gate stops further drain; it does not restore already-lost RepID — a backfill-to-peak is a separate XC/Sean call.)
- Shadow (optional, recommended before flip): set
HAL_STRICTNESS=2on a canary instance / 10% only; compare fact-check vs extractor on live traffic. - Flip: set
HAL_STRICTNESS=2in prod env → scoring routes through the cross-LLM fact-check quorum (the discriminative path; see Grok evidence). Tie to ANFIS routing so quorum isn't run 3× on everything (Phase 4 gap item).
- Truth path: unset
HAL_STRICTNESS(or=1) → instant revert to extractor. - Drain gate: set
HAL_DIRECT_PENALTY_REQUIRES_HALLUCINATION=false→ restores prior (draining) behavior. - No DB migration is involved; both are pure env toggles. No code revert needed to roll back.
verify:crosscheck is RED (correctly) on real findings that are not in the truth-path code:
f2-authz + controller-sanitizer (GA's fix list), repid-floor (clears post-deploy), zkp-anchor
(XC's EAS), hal (F1 0.571 — measurement of the extractor; the flip to fact-check is the fix).
None block the drain stop, which is the safe-default behavior of merging 9dbeb98.