root bfe1ea9d1c
Some checks failed
lakehouse/auditor 13 blocking issues: cloud: claim not backed — "Verified end-to-end:"
auditor: alternate Kimi K2.6 ↔ Haiku 4.5, drop Opus from auto-promotion
Operator can't sustain Opus's ~$0.30/audit on the daemon. New
strategy:

- Even-numbered audits per PR use kimi-k2.6 via ollama_cloud
  (effectively free under the Ollama Pro flat subscription)
- Odd-numbered audits use claude-haiku-4-5 via opencode/Zen
  (~$0.04/audit)
- Frontier models (Opus, GPT-5.5-pro, Gemini 3.1-pro) are NOT in
  auto-promotion. Operator hands distilled findings to a frontier
  model manually when a load-bearing decision needs it.

Mirrors the lakehouse playbook-memory pattern: cheap models do the
volume, the validated subset compounds, only the compounded bundle
gets handed to a frontier model. Same logic at the auditor layer.

Audit-index derivation: count of existing kimi_verdicts files for
the PR. So if the dir has 4 verdicts for PR #11 already, the 5th
audit is index 4 (even) → Kimi, the 6th is index 5 (odd) → Haiku.
Across an active PR's lifetime the audits naturally interleave the
two lineages.

Cost projection at observed cadence (5-10 pushes/day):
- Old (Haiku default + Opus auto on big diffs): $1-3/day
- New (Kimi/Haiku alternating, no Opus): $0.10-0.40/day
- $31.68 budget lasts: ~3 months instead of ~10 days

Override knobs:
  LH_AUDITOR_KIMI_MODEL=<X>           pins to model X (no alternation)
  LH_AUDITOR_KIMI_PROVIDER=<P>        provider for default model
  LH_AUDITOR_KIMI_ALT_MODEL=<X>       sets the odd-index alternate
  LH_AUDITOR_KIMI_ALT_PROVIDER=<P>    provider for alternate

The OPUS_THRESHOLD env knobs from the prior auto-promotion commit
are now no-ops (unset, no longer referenced).

Verification:
  bun build auditor/checks/kimi_architect.ts   compiles
  systemctl restart lakehouse-auditor          active
  systemctl show env                           Haiku pin removed,
                                               Kimi default + cap=3 set

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-27 07:26:31 -05:00
..
2026-04-22 03:54:18 -05:00