design-tolerance-desensitize
Skill19 starsChanged 22 days agoApache-2.0View on GitHub
Use as the last finishing stage (stage C), after optimize-loop has built the form (stage A) and design-glass-matching has closed colour (stage B), when the lens meets its nominal spec with margin and the goal is an as-built spec - to find what is sensitive and make the lens less so.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bench-catalogSkill
- design-aberration-reviewSkill
- design-compareSkill
- design-glass-matchingSkill
- design-reviewSkill
- design-vision-reviewSkill
- optimize-loopSkill
- zos-api-debugSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Do not set a radius by hand: pull it with a row and let the optimizer rebalance.
- Very specific: line 60
Screen cheaply: After each lever, optimize to rest on the working merit, then read the nominal RMS wavefront at every field, …
- Distinctive: line 71
Confirm with a paired per-field Quick Yield read: when the screened changes add up (or after about three rounds).
- Very specific: line 84
Keep: when the worst field's d_yield is positive and resolved, comparable is true, NO field's d_yield is resolved negative, and the worst …
- Very specific: line 90
After EVERY Quick Yield call: save the lens, release_engine, reload it.
- Very specific: line 92
Closing Monte Carlo: Run it unless the brief says an outside judge measures the delivered lens.
- Very specific: line 93
AFTER as not measured and name that judge.
- Very specific: line 113
If a glass-clock stop block arrives here, it is the stage-B budget: stage C runs with OPTIVIBE_GLASS_CLOCK_MODE=off.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Desensitize: the as-built finishing stage
Stage order is A (form), B (glass for colour), C (this). Start from B's lens at rest. The lens has a nominal spec it already beats and an as-built spec it must meet. Stage C spends the margin between them. If the brief gives no as-built spec, ask for one or state the one you use. Judge on the as-built measure, never on the merit value.
This stage is ordinary optimization. optimize-loop's rules hold: bound a variable before you free it, compare only
at rest, check clearance, look at the layout. Length and thickness are costs, as nominal is: a lens made less sensitive
by growing longer or thicker is not a finished lens. The merit you inherit may hold neither (a wizard ceiling of
1000 mm bounds nothing), so read it (dump_merit_function) and, before you free a thickness or an air gap, add what
stage A would have held: a ceiling on each one you free (the brief's limit, else near its start value) and on the
track (about the start lens's, unless the brief gives room). State the ceilings you set.
The as-built measure is the brief's. The default: the share of builds that meet the as-built threshold at EVERY
field after what assembly can adjust. That is refocus always, plus ONE push (lateral decenter of one element or
cemented group) where the lens is centred at assembly, as a microscope objective is. The threshold is an RMS
wavefront: 0.0714 waves for a diffraction-limited lens, otherwise the brief's, or one you state. A trial whose push
sits at its travel limit counts as a failure. When the brief gives each field its own threshold, pass Quick Yield
threshold as a list, one value per field (the worst field is then the one with the lowest pass rate against its own
threshold), and divide each field's row in the judge merit by its threshold so the Monte Carlo reads 1.0 as the limit.
- Fix the judge before you move anything.
- Budget: the brief's, else the wizard preset for the lens type (microscope
{"vendor": "Generic", "grade": "HighPrecision", "element_decenter": 0.010, "element_tilt": 0.0167}; camera{"vendor": "Generic", "grade": "Precision", "element_decenter": 0.02, "element_tilt": 0.017}). One push travel for the whole session, from the brief. - The judge merit reads the worst field (one RWCE row per field plus a MAXX row) and is separate from the merit
you optimize on. Use the brief's, else build and save it.
pick_pushandcriterion="merit"read the LOADED merit, so load the judge merit to measure and your working merit to optimize. The picker refuses the wizard's own merit (merit_layout_mismatch); that is expected. - Save the start lens as a candidate. It is the first parent: every keep in step 5 is judged against its parent, the last kept lens. Its as-built BEFORE is the brief's figure, else the picker's 200-trial reading (step 2), else a step 6 Monte Carlo on the start lens.
- Budget: the brief's, else the wizard preset for the lens type (microscope
- Pick the push first, as at assembly. Skip this step for a refocus-only lens, or when the brief names the push
group. Otherwise which element to push is your design decision. On the start lens, with the judge merit loaded:
tolerance(mode="pick_push", budget=..., cb_group={"decenter_mm": <travel>}). It shortlists the three top decenter/tilt groups, runs a capped MC200 on each (up to 25 min in all) and returns the winner, a near-tie flag and ajudge_call. A near tie means either group will do; take the one ranked first. Use this group for every measurement in the session. Re-run the picker only at the end, if the top decenter hotspot has moved to another group. - Find the hotspots.
tolerance(mode="sensitivity", budget=..., criterion="wavefront")takes seconds. Readhotspots[]only whenhotspots_withheldis null. The ranking is refocus-only; how much of each row a push absorbs is unmeasured, so treat the ranking as the list to try and let the confirm decide. - One lever per round, chosen by cause. Say the cause and the lever in one line.
- Steep surface, high angle of incidence (the top row is a tilt or decenter of an element with a strong
curve): an angle-of-incidence ceiling (
RAID, first at about 0.8x the current value) on the surface the top row names. It is two rows in oneadd_math_constraintcall:RAIDwithrelationship="derived"at weight 0, then anOPLTwithrefs=[<that row's label>],relationship="le"at your limit. - Thicknesses and air gaps, inside their ceilings, to win back the nominal a ceiling cost at the edge of the field. Keep the refocus gap and any gap the brief fixes as they are.
- Glass, only when the brief allows it: a higher index at a similar Abbe number gives the same power with shallower curves. Re-read colour after a keep. It must earn its keep at the confirm like any other lever. Do not set a radius by hand: pull it with a row and let the optimizer rebalance.
- Steep surface, high angle of incidence (the top row is a tilt or decenter of an element with a strong
curve): an angle-of-incidence ceiling (
- The worst field decides. A build passes only when EVERY field passes, so a change that lowers the sensitivity
by spending the edge field's nominal is a loss, however good the average looks.
- Screen cheaply. After each lever, optimize to rest on the working merit, then read the nominal RMS wavefront
at every field,
check_clearancewith your ceilings (max_glass,max_air), the track, and step 3 again. The candidate is out before any yield read if a field's nominal is above the headroom cap (the brief's; else set and state your own before the first lever, well short of the nominal spec: the worst field's nominal is the margin the tolerances need) or a thickness, a gap or the track is over its ceiling: win it back inside the bounds or revert. A lever is worth a yield read when the RSS falls by more than a control optimize (no lever) moves it and the worst field's nominal has not risen to pay for it. The RSS does not decide a keep. - Look before you pay for a yield read. A candidate that goes to the confirm is a stage end: save it and run
design-vision-reviewwith its seq, giving the start lens's track and thickest element in the design intent. The review is advice and the readings decide, but answer each finding it records. If you act on one, screen again. - Confirm with a paired per-field Quick Yield read when the screened changes add up (or after about three
rounds). Parent (the last kept lens, reloaded from its candidate file):
tolerance(mode="quick_yield", budget=..., pupil=2, threshold=<the as-built threshold>, trials=1000, repeats=2). It runs one analysis per field and returnsfieldsand aworst_field. Note the result'sid. Then reload the candidate and run the same call withbaseline=<the parent's id>. The paired block gives candidate minus parent per field (fields[].d_yield) and for the worst field (worst_field, also the top-leveld_yield,d_p90), each with an SE andresolved. - Read the parent once. The server holds the last 4 Quick Yield results across an engine release, so several
candidates pair against the same parent read. Measure the parent again only when
baselineis refused as not held. - Quick Yield is refocus only and reads its own RMS wavefront, not the loaded merit; it does not take the push
(
cb_groupis refused). Its yield is NOT the as-built yield: compare it only candidate against parent, never with a Monte Carlo number or with the target. - Keep when the worst field's
d_yieldis positive and resolved,comparableis true, NO field'sd_yieldis resolved negative, and the worst field'sd_p90is not resolved higher. A resolved loss at any field reloads the parent. Whenworst_field.selection_uncertainis true or the worst field iscensored, the gain is not resolved. Anything else is not confirmed: you may keep screening from it, but report it as unconfirmed and do not make it the parent until a later paired read resolves it. Save every kept lens as a candidate. - Memory. Each analysis (one per field per repeat) holds about 3.7 GB per 1000 trials until the engine closes.
After EVERY Quick Yield call: save the lens,
release_engine, reload it. If a call is refused for memory, lowerrepeats.
- Screen cheaply. After each lever, optimize to rest on the working merit, then read the nominal RMS wavefront
at every field,
- Closing Monte Carlo. Run it unless the brief says an outside judge measures the delivered lens; then report
AFTER as
not measuredand name that judge. When you stop starting rounds: release the engine, reload the lens you deliver, load the judge merit and runtolerance(mode="monte_carlo", compensator="dls_cb_group", cb_group={"group": <the step 2 group>, "decenter_mm": <travel>}, criterion="merit", budget=..., trials=1000, full=true); for a refocus-only lens leave outcompensatorandcb_group. Count the yield (trials at or under the threshold and not at the push limit) from the per-trial values. It is the as-built AFTER.- A Monte Carlo call stops at its time cap (10 s per trial plus 60 s, or
cap_s) and is then refused as capped, with no statistics, so keep that much time for it. If a call fails or returns fewer trials than asked, rerun it; do not count a partial run.
- A Monte Carlo call stops at its time cap (10 s per trial plus 60 s, or
- Find the hotspots again after every keep. Desensitizing one element often moves the sensitivity to its
neighbour. Join the new list to the old by
keyonly whenrun_summary.topology_digestis unchanged. - Measure time; do not estimate it. Note the wall time of every tolerancing call and plan the next round from those times and the clock time used, not from a count of calls. Stop when the as-built target is met, when every hotspot's levers have been tried, or when the brief's time is spent (less step 6's). Until then take the next hotspot or the next lever.
- Report. The start lens and the final lens side by side: the push group, the yield, the P90,
the nominal at every field, the track and the thickest element, each with the trials it rests on. Then each
round: hotspot, cause, lever, the nominal at every field, the track, the paired Quick Yield readings (the worst
field and its
d_yield,d_p90with their SEs, and any field that lost) and decision (kept, rejected, screened out, not confirmed). Name the hotspots left untried.
If a glass-clock stop block arrives here, it is the stage-B budget: stage C runs with OPTIVIBE_GLASS_CLOCK_MODE=off.
Say so to the user and ask them to set it; do not work around the hook.
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.

