2d3cea8127
- add crucible_mcp_server.py with Z3-backed proof tools - ship scheduling, dependency ordering, and capacity templates - log SAT/UNSAT proof trails to ~/.hermes/logs/crucible/ - wire crucible MCP server into config.yaml - teach deploy.sh to ensure z3-solver is installed - add verified-logic playbook and docs for first cut
48 lines
1.4 KiB
YAML
48 lines
1.4 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: claude-opus-4-6
|
|
fallback: claude-sonnet-4-20250514
|
|
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.
|