agentleFS
odinfreeodinfree/storm-ecdsa-harness/skills/quantum-dirty-borrowing/SKILL.md

quantum-dirty-borrowing

Skill4 starsChanged 21 days agoMITView on GitHub

Assess scheduling of already dirty-safe quantum blocks against actual peak ownership and rewrite economics. Use for source-bound borrowing transfers; Bona does not synthesize clean-to-dirty arithmetic.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Read the shared contract before a trial.

    line 10

≈ “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

Dräckfink (quantum-dirty-borrowing)

Change workspace ownership across phases rather than merely shortening a local register. Read Bona's mechanism and limits.

Read the shared contract before a trial. Start with the five-line post; the shared native-test order, stop rules and promotion gate apply.

Scheduler versus arithmetic synthesis

Bona assumes blocks already satisfy a dirty-borrowing contract. It does not synthesize a clean-to-dirty replacement for a data register. Require the exact gadget and identity-on-lender proof before constructing a scheduling graph. A helper named and_dirty elsewhere is insufficient: show it actually owns the binding allocation and has a legal host.

If a rewrite is necessary, classify it as a separate arithmetic-synthesis hypothesis and compare its entire added T against the row's remaining budget before building. Use the current front and product budgets in the shared benchmark reference; reopen a rejected attachment only on a changed, quantified premise.

Practical lane

  1. Extract lifetimes from the active emitted circuit, including all phases tied at peak Q. Label each temporary clean-required or dirty-safe; an unused wire is not automatically a clean wire.
  2. Build an endpoint/dependency graph. For each proven dirty-safe gadget, find an idle host interval with no operand alias or dependency cycle. Start with unchanged-order placements; price necessary rescheduling separately.
  3. First experiment: remap one actual peak allocation into an eligible host, with a machine-readable old/new allocation trace. Check the gadget's forward operator against the intended operation tensor identity on the borrowed state.
  4. Remeasure the whole circuit. If another phase still binds, the result is a local mechanism only. Expand only to a bounded set of co-binders with identified compatible hosts.

Structural extensions

Compare shared workspace scheduling against regeneration and against moving a consumer to expose an interval. These are separate hypotheses: regeneration changes T, rescheduling can change depth and dependency pressure. An allocation diagram without emitted-circuit evidence is insufficient.

Falsify if all peak temporaries require clean state, eligible hosts overlap operands, the splice introduces a cycle, or the unaffected floor prevents the claimed width target. Retain a useful local schedule without labeling it a board gain.

Deliver the dependency graph, borrow/restore boundaries, all peak-owner traces, operator check and full Q/T delta. Do not measure or reset arbitrary borrowed data.

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.