Recursive Decision Ledger
Run repeated rollouts ("Prime Gauss" style recursive prompting) while keeping an append-only decision ledger of trials, marks, coherence checks, and promotion gates, so recursive confidence never auto-approves live trading, deploy, or destructive actions. Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Recursive Decision Ledger when an AI agent needs a reusable SKILL.md workflow for this job: Run repeated rollouts ("Prime Gauss" style recursive prompting) while keeping an append-only decision ledger of trials, marks, coherence checks, and promotion gates, so recursive confidence never auto-approves live trading, deploy, or destructive actions. Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.
When not to use it
Skip Recursive Decision Ledger when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/recursive-decision-ledger # Save SKILL.md to ~/.claude/skills/recursive-decision-ledger/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/recursive-decision-ledger/SKILL.md. For a shared project, commit the folder at .claude/skills/recursive-decision-ledger/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Recursive Decision Ledger skill for this task: Use Recursive Decision Ledger when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Recursive Decision Ledger
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.
## Ledger Contract
Every rollout should record:
- rollout id and timestamp; - prior accepted winner and prior watchlist; - fresh information ingested; - search space size; - model families or heuristics used; - trial count and effective trial count; - top candidates; - decision marks; - coherence marks against the prior ledger; - promotion gate result.
Prefer JSONL for append-only ledgers and Markdown for human summaries.
## Rollout Loop
1. Load the prior ledger. 2. Capture new information at time-step zero. 3. Run the bounded search. 4. Mark each candidate: accept, watch, reject, decay watch, or needs replay. 5. Compare winners against prior winners and latest marked rollout. 6. Downgrade candidates when drift, tail risk, stale data, or failed replay invalidates the previous mark. 7. Append artifacts before summarizing.
## Coherence Mark
Include a compact coherence mark:
```text 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 ```
## Promotion Rules
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:
- the candidate beats the prior accepted winner on the chosen metric; - correctness and replay checks pass; - risk limits are explicit; - the evidence is durable; - the user has approved the live step when needed.
## Summary Shape
Lead with the decision, not the drama:
```text 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. ```
Intended uses
- Use Recursive Decision Ledger when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.