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.
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accepted-proof-exact-retuneSkill
- arxiv-portable-researchSkill
- auto-autoresearch-pipelineSkill
- beachhead-ratchetSkill
- bounded-commuting-foldSkill
- burn-the-house-downSkill
- calibrated-static-cost-proxySkill
- circuit-edit-integration-safetySkill
- colab-laneSkill
- computer-algebra-oraclesSkill
- constraint-construction-searchSkill
- cross-model-review-gateSkill
- deepseek-pressure-testSkill
- ecdsafail-fastevalSkill
- ecdsafail-lowq-playbookSkill
- ecdsafail-oracle-loopSkill
- ecdsafail-pareto-ratchetSkill
- ecdsafail-scratch-dietSkill
- elicit-researchSkill
- evaluator-scoring-surface-auditSkill
- exact-evaluator-replicaSkill
- exact-hold-passSkill
- exact-postpass-stackSkill
- exact-search-engineeringSkill
- fast-lean-proof-loopSkill
- fit-probe-and-spliceSkill
- gpu-affine-table-synthesisSkill
- greedyfrog-methodSkill
- hard-problem-contractSkill
- hold-demand-ledgerSkill
- hosted-carry-lendingSkill
- inert-op-screen-to-structural-ruleSkill
- invariant-chartSkill
- jev-second-perspectiveSkill
- lambda-exchange-deskSkill
- leader-rebase-stackSkill
- lean-arklib-proofsSkill
- lean-finite-certificate-splittingSkill
- lever-switches-and-break-controlsSkill
- mission-commandSkill
- nasqret-playbookSkill
- paged-walk-descentSkill
- pinned-table-stackingSkill
- pip-disciplineSkill
- portable-source-assertionsSkill
- proximity-prize-campaignSkill
- proximity-prize-frontier-archaeologySkill
- quantum-affine-lookup-synthesisSkill
- quantum-borrowed-wire-counterexampleSkill
- quantum-dense-qromSkill
- quantum-dirty-borrowingSkill
- quantum-divstep-reconstructionSkill
- quantum-encoded-arithmeticSkill
- quantum-graded-divider-placementSkill
- quantum-guarded-permutation-auditSkill
- quantum-mbundo-lifetimesSkill
- quantum-record-miningSkill
- quantum-replay-arithmeticSkill
- quantum-residue-scan-ambiguitySkill
- The first 60 shown.
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
- Distinctive: line 16
Run from an isolated route tree:
- Distinctive: line 27
If transcript/tape overlap matters, also run:
- Distinctive: line 48
Do not edit from a vague "peak is high" claim.
- Distinctive: line 53
Treat count-only deltas as candidate evidence only.
- Distinctive: line 57
Write the ledger to the lane state directory and post the top three pressure points to the team channel with the next falsifiable check.
≈ “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.
Files
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.errIf 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.errLedger 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.
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
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.

