agentleFS
odinfreeodinfree/storm-ecdsa-harness/skills/peak-lifetime-ledger/SKILL.md

peak-lifetime-ledger

Skill4 starsChanged 21 days agoMITView on GitHub

Use when mapping ecdsa.fail q1152/lower peak-qubit pressure, especially Trailmix/Ludicrous fold, add, codec, and GCD phases, before editing or scaling compute.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from an isolated route tree:

    line 16
  2. Distinctive:

    If transcript/tape overlap matters, also run:

    line 27
  3. Distinctive:

    Do not edit from a vague "peak is high" claim.

    line 48
  4. Distinctive:

    Treat count-only deltas as candidate evidence only.

    line 53
  5. Distinctive:

    Write the ledger to the lane state directory and post the top three pressure points to the team channel with the next falsifiable check.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Gipfelbuech (peak-lifetime-ledger)

Job

Turn trace output into a concrete list of live-state pressure points. Use this before structural edits so a candidate is tied to the exact phase, callsite, register family, and Toffoli cost that creates the q1153/q1152 wall.

Required Inputs

Run from an isolated route tree:

TRACE_TLM_PROFILE=1 \
TRACE_TLM_FOLD=1 \
TRACE_TLM_FOLD_ALLOC=1 \
TRACE_TLM_PHASE_COST=1 \
TRACE_TLM_PHASE_COST_REGIONS=1 \
./target/release/build_circuit >/tmp/peak_build.log 2>/tmp/peak_trace.err

If transcript/tape overlap matters, also run:

TRACE_PHASE_ACTIVE=1 TRACE_PHASE_ACTIVE_TOP=40 TRACE_TLM_TAIL=1 \
./target/release/build_circuit >/tmp/tape_build.log 2>/tmp/tape_trace.err

Ledger Fields

Record each pressure point as:

phase=<name> peak_q=<n> op_idx=<n> emitted_ops=<n>
callsite=<function/region> live=<register families/qid bands>
ccx=<n> ccz=<n> tape_bits=<n> fold_chunk=<n>
candidate=<what could be delayed/loaned/re-encoded>
proof_obligation=<why it remains value/phase/ancilla exact>

Rules

  • Do not edit from a vague "peak is high" claim.
  • Prioritize peaks where a single resident family can be delayed, hosted, or streamed without adding more Toffoli than the target q tier can afford.
  • Separate qubit pressure from Toffoli pressure. A route can be lower-Q and still lose Q*T.
  • Treat count-only deltas as candidate evidence only.

Output

Write the ledger to the lane state directory and post the top three pressure points to the team channel with the next falsifiable check.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.