mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-05-30 21:54:17 +08:00
80 lines
2.5 KiB
Markdown
80 lines
2.5 KiB
Markdown
---
|
|
name: recursive-decision-ledger
|
|
description: 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.
|
|
origin: ECC
|
|
tools: Read, Write, Edit, Bash, Grep, Glob
|
|
---
|
|
|
|
# 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.
|
|
```
|