Communitygithub.com

austin-starks/Public-Portfolio-Challenge

執行多家族策略競賽——SEARCH→CERTIFY 漏斗,篩選大量候選機制,最終認證出可部署的贏家,且不讓廉價搜尋層做出裁決。適合重現第 10 集競賽、在認證前探索多個不同策略家族、判定「無可部署贏家」是否為合法結論,或建立各家族認證分類帳時使用。強制裁決完整性:只有認證才能結束競賽。

Public-Portfolio-Challenge 是什麼?

這是一個用於執行多家族策略競賽(Multi-Family Strategy Bakeoff)的 AI 技能,專注於兩層 SEARCH→CERTIFY 漏斗,並有最低工作量要求。核心規則是:**搜尋層禁止做出任何裁決**,只有步行向前認證(walk-forward-oos)才能結束競賽。此技能強制裁決完整性,確保只有認證層才能發布 PASS/FAIL 或「無可部署贏家」的結論。您可以使用此技能重現第 10 集競賽的場景、在認證前探索多個不同的策略家族,或判斷「無可部署贏家」是否為合法結論。此技能支援 Claude Code、Cursor 等 AI 代理平台,並透過 `backtest_portfolio`、`systematic_sweep` 等工具進行搜尋,以及透過步行向前認證循環對提升的候選機制進行認證。它還強制執行最低工作量要求,包括至少 3 個不同的機制家族、每家族最多 3 次認證嘗試,以及建立各家族認證分類帳(ledger)以確保透明度。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/austin-starks/Public-Portfolio-Challenge/tree/HEAD/skills/strategy-bakeoff

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

多家族策略競賽

一個兩層 SEARCH → CERTIFY 漏斗,具有強制最低工作量。核心規則: 搜尋層禁止做出裁決。 只有步行向前認證(walk-forward-oos) 才能結束競賽。

兩個工具,兩份工作

  • SEARCH 層(廉價):backtest_portfolio、create_portfolio_variant、optimize_portfolio、 systematic_sweep。它只能 KILL 或 PROMOTE 一個想法進入認證。它輸出「一組排名的 SEEDS」,且永遠不得發布裁決。
  • CERTIFY 層(主力):對提升的種子進行步行向前掃描認證。只有這一層 才能得出 PASS / FAIL 或「無可部署贏家」的結論。

在搜尋層中,在宣告任何鄰域死亡之前,必須對 deployment × structure × DTE × delta 網格 執行 systematic_sweep。

強制最低工作量

  • 在發布任何「無贏家」裁決前,至少有 ≥ 3 個不同的機制家族經過認證。必須是真正不同的 機制,而不是單一家族的三個調整。家族選單(選擇 ≥3 個):(a) 動能長買權/垂直價差; (b) 體制切換長/平倉;(c) 定義信用/短保費(在平/跌市場中獲利);(d) 日曆/對角線時間價差;(e) 保護性勒式或賣權價差融資的長倉。
  • 每個家族最多 3 次認證嘗試(從一個 CLEAN 種子重新掃描,使用精煉的 gene_intents、更深的網格或更寬的驗證),然後該家族即為「耗盡」。
  • 實際總數:約 3–9 次掃描認證,加上已認證的現任種子。
  • 每次掃描不可空泛:≥3 個 gene_intents 軸 × 每個軸 ≥3 個值(請參閱 sweep-reoptimization 以了解 確切欄位映射)。1 軸或 2 值的掃描不符合資格。

各家族認證分類帳(必填)

在執行記錄中記錄此表格——沒有分類帳行的家族表示未被探索:

| 家族 | 種子 id | get_sweep_surface ✓ | gene_intents 軸 | Study id | crossFoldRobustSelection 鍵 | 組合書本 id | 每折 OOS 閘門結果 | PROMOTE / KILL(原因) |

每個種子的認證循環

get_sweep_surface → run_walk_forward_study(先使用 preview_only)→ 讀取 aggregate.crossFoldRobustSelection → 組合可部署形狀的書本 → 對組合後 的物件進行閘門檢查 → 寫入分類帳行。認證門檻(certification:true):參與度 ≥ 0.35, 獨特名稱 ≥ 9,驗證回報 ≥ 0,驗證 Sortino ≥ 0.5。

裁決完整性規則(競賽的核心紀律)

  • 零優化認證 = 無效,不是「誠實的無部署」。 發布任何裁決—— 尤其是「無可部署贏家」/「結構不可行」——若未對候選種子執行優化認證, 則該競賽即為無效。(先前的執行宣告不可行,但已執行零次優化認證。)
  • 不得從 N 個手工點宣告不可行——必須引用 systematic_sweep + ≥3 家族 工作負荷,並按家族指出單一綁定閘門,附上 study-id 證據。
  • 自身資料中的一個反例禁止泛化的不可行聲明——定位綁定 約束,不要概括。
  • 綁定約束歸因: 每個 KILL 都必須指明失敗的單一閘門 + 認證證據。 「它整體表現不佳」不是有效的 KILL 理由。
  • 每個候選者僅做一項機制變更——如此 KILL/PROMOTE 的歸因才清晰。
  • 補救措施一致性: 提出的補救措施不得與被 KILL 候選者的實測狀態 矛盾(不要對一個在持倉上限下失敗的書本提出「提高部署」;不要對一個因回撤失敗的書本提出「加入 凸性」)。

請參閱 options-structure-rules 以了解可負擔階梯 KILL 路徑與已知輸家,以及 lockbox-holdout 以了解基準線(A/B/C)與最終的單擊確認。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

austin-starks/Public-Portfolio-Challenge

Build alternative-data custom indicators on NexusTrade (Reddit/WSB mentions, congressional disclosures, insider filings, news-flow) and wire them into a certified book as a rank/tilt/filter signal. Use when adding alt-data to a strategy, building a CustomIndicator via compute sessions, auditing lookahead safety or per-ticker coverage, or deciding whether a data series is dense enough to drive a rank. Covers the compute-session workflow, the sparse-series rule, and source recipes (see references/). Invoke with the NexusTrade MCP connected.

austin-starks/Public-Portfolio-Challenge

Measure a NexusTrade options book's TRUE participation at a fixed cold-start capital base, defeating the compounded-NAV breadth illusion. Use whenever a book's headline \"holds N/21 names\" needs validating, when a live book collapses to a single name (the OSCR trap), when checking whether a SelectTop / per-name-allocation / total-budget change degraded simultaneous participation, or when a certification needs a breadth gate. Uses audit_backtest_breadth at held-fixed $25k.

austin-starks/Public-Portfolio-Challenge

The \"loudly declare\" protocol for platform, engine, or data bugs during a NexusTrade certification campaign — bugs are a first-class deliverable, not something to route around. Use whenever a NexusTrade tool errors, hangs, or returns numbers that contradict the config; whenever you're tempted to write \"probably an engine quirk\"; or when a discovered bug invalidates prior backtests and results must be quarantined. Includes the bug hand-off doc template (see references/BUG_TEMPLATE.md).

austin-starks/Public-Portfolio-Challenge

The GATED deploy + cleanup flow for a NexusTrade live book — clone the finalist, preview a delta reconcile, stage UNAPPROVED orders, verify fills. Use ONLY after the human explicitly says \"deploy + clean up\" and names a finalist. Covers the clone-before-reconcile ordering, the single-tick reconcile expectation, stale-pending-order hygiene, the signal-freshness gate, and why you can never approve orders yourself. Nothing here runs during certification.

austin-starks/Public-Portfolio-Challenge

The mandatory pre-flight contract checks (Stage S0) that must pass before trusting NexusTrade's certification engine for any strategy work. Use at the start of a bakeoff or certification campaign to prove the walk-forward engine runs end-to-end, windows don't leak, fold winners persist, and the engine doesn't fabricate values for dead/not-yet-listed names. Each check has a STOP-and-report failure mode; these runs do NOT count toward any certification minimum.

austin-starks/Public-Portfolio-Challenge

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.

austin-starks/Public-Portfolio-Challenge

The hard structural constraints for the Public Portfolio Challenge momentum-LEAP options book — the spread-shape rule, the take-profit convexity-cap footgun, the affordability ladder, and the known losers not to re-test. Use whenever building or auditing an options strategy structure, checking spread-shape compliance before a certification, choosing DTE/strike rungs, or deciding whether a proposed structure change is even allowed. A violation is an automatic certification FAIL.

austin-starks/Public-Portfolio-Challenge

Orchestrate an out-of-sample certification of a NexusTrade trading strategy or live book — the master discipline behind the Public Portfolio Challenge. Use whenever you must decide PASS/FAIL on whether a portfolio holds up out of sample before deploying real money, replaying the Episode 10 runbooks, or running a \"certify my book\" / \"prove it out of sample\" / \"re-certify the fix\" task with the NexusTrade MCP connected. Pulls in walk-forward-oos, breadth-audit, sweep-reoptimization, options-structure-rules, bug-protocol, and deploy-gate.

austin-starks/Public-Portfolio-Challenge

The single entry point that executes a Public Portfolio Challenge episode or addendum runbook end-to-end, delegating each stage to the functional skills. Use when asked to run/execute/replay Episode 10, its bakeoff, or its addendum with the NexusTrade MCP connected. Reads the target runbook, pins its real artifacts (IDs, the incumbent bar), sequences the stages, and stops at the gated deploy. It orchestrates; the functional skills do the work.

austin-starks/Public-Portfolio-Challenge

Re-optimize a NexusTrade strategy with a walk-forward SWEEP and label parameter provenance — the discipline that prevents deploying inherited knobs. Use whenever a structural change (sizing, rung depth, universe membership, DTE family, adding a rank signal) forces a re-sweep, when authoring gene_intents from get_sweep_surface, when choosing sweep over GA for a deploy cert, or when selecting the cross-fold-robust winner instead of the per-fold argmax. Invoke with the NexusTrade MCP connected.

austin-starks/Public-Portfolio-Challenge

Run and read a NexusTrade walk-forward out-of-sample study — the certification engine behind the Public Portfolio Challenge. Use when certifying a fixed portfolio (backtest_only) or re-optimizing one (sweep), when setting fold_count / anchored / validation / embargo params, when monitoring a run_walk_forward_study to completion, when reading per-fold OOS returns/Sortino/drawdown, or when a variant's fold calendar needs calendar-alignment against a base control. Invoke with the NexusTrade MCP connected.

相關技能