6d713aeeb9
Some checks failed
PR Checklist / pr-checklist (pull_request) Failing after 1m18s
Golden state: Kimi K2.5 primary → Gemini via OpenRouter → local Ollama. Anthropic is gone from every active config, fallback chain, and loop script. Wizard configs (3): - allegro, bezalel, ezra: removed anthropic from fallback_providers, replaced with gemini + ollama. Removed anthropic provider section. Playbooks (7): - All playbooks now use kimi-k2.5 as preferred, google/gemini-2.5-pro as fallback. No claude model references remain. Fleet scripts (8): - claude-loop.sh: deprecated (exit 0, original preserved as reference) - claudemax-watchdog.sh: deprecated (exit 0) - agent-loop.sh: removed claude dispatch case - start-loops.sh: removed claude-locks, claude-loop from proc list - timmy-orchestrator.sh: removed claude worker monitoring - fleet-status.sh: zeroed claude loop counter - model-health-check.sh: replaced check_anthropic_model with check_kimi_model - ops-gitea.sh, ops-helpers.sh, ops-panel.sh: removed claude from agent lists Infrastructure (5): - wizard_bootstrap.py: removed anthropic pip package and API key checks - WIZARD_ENVIRONMENT_CONTRACT.md: replaced ANTHROPIC keys with KIMI - DEPLOY.md: replaced ANTHROPIC_API_KEY with KIMI_API_KEY - fallback-portfolios.yaml: replaced anthropic provider with kimi-coding - fleet-vocabulary.md: updated Ezra and Claude entries to Kimi K2.5 Docs (2): - sonnet-workforce.md: deprecated with notice - GoldenRockachopa-checkin.md: updated model references Preserved (not touched): - training/ data (changing would corrupt training set) - evaluations/ (historical benchmarks) - RELEASE_*.md (changelogs) - metrics_helpers.py (historical cost calculation) - hermes-sovereign/githooks/pre-commit.py (secret detection - still useful) - security/secret-scan.yml (key detection - still useful) - architecture_linter.py (warns about anthropic usage - desired behavior) - test_sovereignty_enforcement.py (tests anthropic is blocked - correct) - son-of-timmy.md philosophical references (Claude as one of many backends) Refs: Sovereignty directive, zero-cloud vision
56 lines
1.3 KiB
YAML
56 lines
1.3 KiB
YAML
name: verified-logic
|
|
description: 'Crucible-first playbook for tasks that require proof instead of plausible prose. Use Z3-backed sidecar tools
|
|
for scheduling, dependency ordering, capacity checks, and consistency verification.
|
|
|
|
'
|
|
model:
|
|
preferred: kimi-k2.5
|
|
fallback: google/gemini-2.5-pro
|
|
max_turns: 12
|
|
temperature: 0.1
|
|
tools:
|
|
- mcp_crucible_schedule_tasks
|
|
- mcp_crucible_order_dependencies
|
|
- mcp_crucible_capacity_fit
|
|
trigger:
|
|
manual: true
|
|
steps:
|
|
- classify_problem
|
|
- choose_template
|
|
- translate_into_constraints
|
|
- verify_with_crucible
|
|
- report_sat_unsat_with_witness
|
|
output: verified_result
|
|
timeout_minutes: 5
|
|
system_prompt: 'You are running the Crucible playbook.
|
|
|
|
|
|
Use this playbook for:
|
|
|
|
- scheduling and deadline feasibility
|
|
|
|
- dependency ordering and cycle checks
|
|
|
|
- capacity / resource allocation constraints
|
|
|
|
- consistency checks where a contradiction matters
|
|
|
|
|
|
RULES:
|
|
|
|
1. Do not bluff through logic.
|
|
|
|
2. Pick the narrowest Crucible template that fits the task.
|
|
|
|
3. Translate the user''s question into structured constraints.
|
|
|
|
4. Call the Crucible tool.
|
|
|
|
5. If SAT, report the witness model clearly.
|
|
|
|
6. If UNSAT, say the constraints are impossible and explain which shape of constraint caused the contradiction.
|
|
|
|
7. If the task is not a good fit for these templates, say so plainly instead of pretending it was verified.
|
|
|
|
'
|