Recursive Decision Ledger
SkillCloud & infrarecursive-decision-ledger is a skill that lets an agent run repeated rollouts while recording every trial in an append-only ledger. Each rollout logs trial counts, candidate marks, coherence checks, and promotion gates, so recursive confidence alone never triggers live tra
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent environment that supports skills and provides Read, Write, Edit, Bash, Grep, and Glob tools.
Then ask your AI: use the Recursive Decision Ledger skill
What your AI can do with it
- Run bounded search rollouts with trial counts and effective trial counts
- Record each rollout in an append-only JSONL ledger plus a Markdown summary
- Mark candidates as accept, watch, reject, decay watch, or needs replay
- Compare winners against prior accepted winners and latest marked rollout
- Downgrade candidates when drift, tail risk, stale data, or failed replay appears
- Enforce promotion gates so live trading, deploys, or destructive ops need explicit approva
Getting started
- Have an agent environment that supports skills and provides Read, Write, Edit, Bash, Grep, and Glob tools.
- Add the recursive-decision-ledger skill to the agent's available skills.
- Ask the agent for repeated rollouts, marked decision processes, high-dimensional search, or recursive reasoning with a visible evidence trail.
- Provide prior ledger data if a previous rollout exists, plus any fresh information for the new time step.
- Review the JSONL ledger and summary, and explicitly approve any live or destructive step before it runs.
What this skill tells your AI
The instructions your AI receives, as published by affaan-m/ecc in skills/recursive-decision-ledger/SKILL.md and read by ahel’s review.
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
- Load the prior ledger.
- Capture new information at time-step zero.
- Run the bounded search.
- Mark each candidate: accept, watch, reject, decay watch, or needs replay.
- Compare winners against prior winners and latest marked rollout.
- Downgrade candidates when drift, tail risk, stale data, or failed replay invalidates the previous mark.
- Append artifacts before summarizing.
Coherence Mark
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
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:
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.
Signals
- GitHub stars
- 268k
- Forks
- 40k
- Last commit
- Sep 2026
Questions
- Does recursive confidence let the agent trade or deploy on its own?
- No. The skill treats recursive confidence as not approval. Live trading, deploys, migrations, and destructive ops default to paper, dry-run, read-only, preview, or staged mode and require explicit user approval.
- What gets recorded in the ledger?
- Rollout id and timestamp, prior winner and watchlist, fresh information, search space size, trial counts, top candidates, decision marks, coherence marks, and the promotion gate result.
Advanced
- Item type
- skill
- Key
recursive-decision-ledger- Source
- github.com/affaan-m/ecc