lockbox-holdout
Skill82 starsChanged 3 months agoMITView on GitHub
The single-touch lockbox — a final anti-overfitting holdout run once, after design freeze, on a window held out from every fold, sweep, and search. Use when finalizing a bakeoff winner before deploy, setting up the A/B/C baselines as OOS bars, or running the S1.5 gate-coherence auto-relax. Covers why looking at the lockbox twice burns it, the lockbox pass conditions, and the three baselines. The lockbox is distinct from the walk-forward OOS folds.
In this repository23 other files it gives its agents.
- skills/alt-data-indicators/AGENTS.mdAGENTS.md
- skills/breadth-audit/AGENTS.mdAGENTS.md
- skills/bug-protocol/AGENTS.mdAGENTS.md
- skills/deploy-gate/AGENTS.mdAGENTS.md
- skills/engine-sanity/AGENTS.mdAGENTS.md
- skills/lockbox-holdout/AGENTS.mdAGENTS.md
- skills/options-structure-rules/AGENTS.mdAGENTS.md
- skills/portfolio-certification/AGENTS.mdAGENTS.md
- skills/run-episode/AGENTS.mdAGENTS.md
- skills/strategy-bakeoff/AGENTS.mdAGENTS.md
- skills/sweep-reoptimization/AGENTS.mdAGENTS.md
- skills/walk-forward-oos/AGENTS.mdAGENTS.md
- alt-data-indicatorsSkill
- breadth-auditSkill
- bug-protocolSkill
- deploy-gateSkill
- engine-sanitySkill
- options-structure-rulesSkill
- portfolio-certificationSkill
- run-episodeSkill
- strategy-bakeoffSkill
- sweep-reoptimizationSkill
- walk-forward-oosSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
How: only the assembled deploy-shape book that already passed every gate on the walk-forward aggregate runs over the lockbox, exactly once, …
- Distinctive: line 59
Before designing, check whether "beat Baseline B" and the ≤55% posture cap are jointly satisfiable — B is a ~95%-deployed book, so a …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Single-Touch Lockbox & Baselines
The lockbox is a final holdout that no fold, sweep, or search ever touches — the last line of defense against calendar-fit selection pressure. It is distinct from the walk-forward OOS folds (walk-forward-oos), which are used repeatedly during search; the lockbox is touched exactly once.
The lockbox
- What: the walk-forward span stops
lockbox_width_days = 126(~6 months) before the run date. That final window(run date − 126d) → run dateis the lockbox — held out from ALL folds, ALL sweeps, ALL search. - How: only the assembled deploy-shape book that already passed every gate on the walk-forward aggregate runs over the lockbox, exactly once, after design freeze (Stage S2).
- Pass conditions (frozen at S0, do not move them after seeing results):
- lockbox OOS return ≥ worst single-fold walk-forward OOS return;
- lockbox maxDD ≤ 55%;
- posture clean (
audit_backtest_posture, all four conditions); - breadth ≥ 9 eligible names (
audit_backtest_breadth— see breadth-audit).
Single-touch is absolute
If you look at the lockbox and then iterate the design, the lockbox is burned — move the walk-forward span back and hold out a fresh tail before any deploy. A lockbox failure is treated as calendar-fit selection pressure and means no deploy, except by a logged owner override that explicitly names the lockbox.
The three baselines (A/B/C) as OOS bars (Stage S1)
Loaded from committed snapshots/*.json via create_portfolio. Score A and B on the current engine;
copy C's frozen published numbers as the bar to beat.
- A — equity buy&hold (the full universe). A return bar only, never a Sortino bar — its Sortino reflects an equity-rally smoothness a leveraged long-premium book can't match.
- B — naive LEAP ladder (canonical spec: all names, no rank/filter, 14-day cadence, 8%-of-portfolio
per name under 95% budget, structure = first affordable rung of
[Δ0.50 call → Δ0.55/0.25 → Δ0.55/0.40 → Δ0.50/0.42 vertical], all 180–365 DTE, single exit at DTE ≤ 45). A Sortino bar only in folds with ≥ 9/20 breadth. - C — frozen incumbent bar with published per-fold OOS numbers, copied verbatim (do not re-run to "improve" them).
S1.5 — Gate-coherence auto-relax (deterministic, no owner round-trip)
Before designing, check whether "beat Baseline B" and the ≤55% posture cap are jointly satisfiable
— B is a ~95%-deployed book, so a posture-capped finalist can't out-deploy it. If unsatisfiable,
AUTO-RELAX Baseline B: derate B's totalBudget until its own median daily deployment ≤ 55%, re-run
its S1 scoring, and log original vs posture-matched B. This is not a gate relaxation and not an owner
decision — only the benchmark is made comparable; the thresholds stay frozen.
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.

