recursive-decision-ledger by affaan-m

Decision brief

What it does—and where it fits

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 pr…

Best for

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 tr…

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/affaan-m/ECC --skill "skills/recursive-decision-ledger"

Safe inspection promptEditorial

Inspect the Agent Skill "recursive-decision-ledger" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/recursive-decision-ledger/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
Ledger Contract
Every rollout should record:
rollout id and timestamp;prior accepted winner and prior watchlist;fresh information ingested;
02
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,…
Load the prior ledger.Capture new information at time-step zero.Run the bounded search.
03
Coherence Mark
Include a compact coherence mark:
Include a compact coherence mark:
04
Promotion Rules
For trading, capital allocation, production deploys, migrations, or destructive ops, recursive confidence is not approval.
the candidate beats the prior accepted winner on the chosen metric;correctness and replay checks pass;risk limits are explicit;

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	71/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	234,327	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: affaan-m/ECC
Skill path: skills/recursive-decision-ledger/SKILL.md
Commit: 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License: MIT
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

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

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.