skills/recursive-decision-ledger/SKILL.md
Use this skill when the user is trying to force deeper computation through repeated rollouts or "Prime Gauss" style recursive prompting. Preserve the useful part: repeated trials, prior memory, fresh information, and explicit marks. Remove the unsafe part: pretending the loop proves certainty.
Every rollout should record:
Prefer JSONL for append-only ledgers and Markdown for human summaries.
Include a compact coherence mark:
Ensemble matches prior winner: true
Recursive matches prior winner: false
Latest rollout match: true
Live promotion allowed: false
Reason: replay and freshness gates not satisfied
For trading, capital allocation, production deploys, migrations, or destructive ops, recursive confidence is not approval.
Default to paper, dry-run, read-only, preview, or staged mode unless the user explicitly approves the live action and the repo/service gate supports it.
Promote only when:
Lead with the decision, not the drama:
Rollout 15 complete. The prior winner still holds, but edge deteriorated 17%.
Status: watch, not live. Next gate: 20 replay fills with fresh orderbook age
below threshold.