Communitygithub.com

austin-starks/Public-Portfolio-Challenge

對 NexusTrade 交易策略或即時投資組合進行樣本外驗證及認證,這是「公開投資組合挑戰賽」的核心規範。當需要決定策略在實際部署資金前是否通過樣本外測試時使用。

Public-Portfolio-Challenge 是什麼?

此技能為「公開投資組合挑戰賽」的總管技能,核心角色是作為獨立驗證者,直接操控 NexusTrade 工具產生可靠數據,並給出整體 PASS/FAIL 的認證結論。主要功能是基於樣本外(OOS)的逐步遞迴折疊(walk-forward folds)進行評估,而非單一總體數字。技能整合了多個子技能,包括樣本外測試(walk-forward-oos)、廣度審計(breadth-audit)、掃描重優化(sweep-reoptimization)、選擇權結構規則(options-structure-rules)、錯誤協議(bug-protocol)以及部署閘門(deploy-gate),形成一套完整的認證流程。支援跨平台使用(如 Claude Code、Cursor),特別適用於 NexusTrade 生態系統中的策略驗證。此技能強調設計的價值遠大於優化器,要求以欄位為基礎驗證標的,杜絕假設與猜測,並遵循標準的階段式運行結構(從基線建立到部署閘門),最終交付可決策的認證報告。

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

在你喜歡的 AI 中提問

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

說明文件

投資組合認證

「公開投資組合挑戰賽」的總管技能。您是** orchestrator + 獨立驗證者**:您直接操控確定的 NexusTrade 工具,數字是您自己的——沒有代理人的結果需要您事後質疑。認證是從樣本外逐步遞迴折疊中讀取的整體 PASS/FAIL 裁決,絕非單一總體數字。

首要原則(每次運行皆須遵守)

  1. OOS 是唯一的重點。 切勿將訓練/驗證數字當作泛化能力的證據。如果完整的週期回測出現了訓練→OOS 的崩潰,那就是 FAIL。
  2. 價值存在於設計中,而非優化器中。 掃描是一個適度的參數設定器,用於確認設計的鄰域。將心力投入策略設計;對掃描的要求應降到最低。
  3. 部署跨折疊的穩健配置,切勿部署單折疊的 argmax。 驗證分數是一個有雜訊的代理指標;單折疊的勝者具有高變異性。使用 maximin OOS Sortino/穩健選擇。
  4. 在欄位層級進行驗證,而非顯示名稱。 使用 conditionFieldAudit;從目錄中準確複製指標 ID。根據欄位/形態確認標的主體,切勿根據其名稱。
  5. 驗證,而非斷言。 所有關於引擎行為的主張,在出現在可交付成果之前,都必須根據事件、欄位或重現結果進行檢查。「大概是引擎的小問題」→ 執行 bug-protocol,切勿含糊帶過。
  6. 誠實報告的無效結果是有效成果。 不要折磨變體直到其中一個「贏了」——那只不過是裝扮過的單折疊 argmax 陷阱。平手或雜訊級別的差異→保留現有方案。
  7. 無部署,無訂單,直到人類明確說出「部署 + 清理」(即 deploy-gate)。

標準運行結構

每次認證活動都遵循相同的階段形狀。中間部分可調整;頭尾是固定的。

  • 階段 A — 基線 + 盤點。 透過欄位確認標的主體(get_portfolio),重新驗證現有方案條形圖,抽檢一次新的 backtest_portfolio + audit_backtest_posture,如果投資組合是即時的,則檢查待定訂單狀態和 automaticOrderApproval。交付一段之前狀態。當即時行為是問題所在時,先用硬數據重現它(query_portfolio_events),然後修復。
  • 階段 B/C — 建構 + 認證。 執行正式的認證。關於研究機制和強制性的逐折疊檢查,請參閱 walk-forward-oos;關於固定 $25k 的參與度檢查,請參閱 breadth-audit;關於嚴格的價差形狀門,請參閱 options-structure-rules;如果任何結構性變化強制重新掃描,請參閱 sweep-reoptimization。
  • 階段 D — 呈現,然後停止。 交付一個可供決策的套件:裁決在最上方,一行;逐折疊 OOS 表格 + 總計;與現有方案並排比較,並明確說明交易;最終方案的平白英語規則 + conditionFieldAudit + 建構 ID;每個參數的來源標籤(swept-on-this-book / inherited-from <study-id> / hand-set — 繼承的標為琥珀色);誠實的警告事項(凍結宇宙中的後見之明、選擇權成交現實性、槓桿/脆弱性、最大回撤是 2025 年 4 月的拋售、基線警告事項)。包含錯誤記錄簿。無部署。
  • 階段 E — 部署(閘門控管)。 僅在明確的「部署 + 清理」指令後執行。請參閱 deploy-gate。

整體 PASS 測試(無逐折疊綠色規則)

當多數 OOS 折疊獲利、OOS Sortino 為正且相當穩定(粗略下限約 0.5)、回撤在您實際會持有的容忍範圍內、部署在各折疊間穩定、且訓練→OOS 退化幅度不大時,認證為 PASS。一個弱折疊 ≠ FAIL。持續的 OOS 虧損、爆炸性回撤或僅在訓練時表現強勁 = FAIL。硬性約束違反(價差形狀、廣度崩潰)= 無論回報如何,自動 FAIL。

「優於現有方案」(變體活動)

在測試針對即時/已認證基線的變體時,「更好」= 在相同的折疊中固定持有,它在不增加風險的情況下改善了 OOS 回報,或者在類似回報的情況下顯著改善了風險(Sortino/DD),或者明顯改善了弱勢情境(熊市折疊),且廣度未退化。比較必須日曆對齊(在變體的裁剪日曆上運行基礎對照組——請參閱 walk-forward-oos)。

自我檢查觸發詞

  • 「回測證明了它」→ 沒有 OOS 折疊就等於沒發生。
  • 「重用勝者的旋鈕」/「已認證」→ 結構改變了嗎?如果是 → 在認證前重新掃描(sweep-reoptimization)。
  • 「19/21 個名稱」/「廣度很好」→ 以固定 $25k 測量(breadth-audit);複合廣度是個幻覺。
  • 「這個指標看起來有預測性」→ 認證它,不要光用眼睛看。
  • 「大概是引擎的小問題」→ bug-protocol:驗證,而非斷言。

原始操作手冊(此規範的實際範例)

  • episode-10/BAKEOFF_RUNBOOK.md — 引擎健全性檢查、16 變體競賽、逐步遞迴認證、鎖箱。
  • episode-10/addendum/RUNBOOK.md — 重新設計進出場規則,然後證明 OOS 行為。
  • episode-10/addendum/CAMPAIGN_LOG.md — 附錄的完整教訓與部署記錄。

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

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

Run a multi-family strategy bakeoff — the SEARCH→CERTIFY funnel that screens many candidate mechanisms down to a certified deploy winner without letting the cheap search layer issue a verdict. Use when replaying the Episode 10 bakeoff, when exploring several distinct strategy families before certifying, when deciding whether \"no deployable winner\" is even a legal conclusion, or when building the per-family certification ledger. Enforces verdict-integrity: only certification can end a campaign.

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.

相關技能