Communitygithub.com

austin-starks/公共投資組合挑戰

NexusTrade 認證活動期間,針對平台、引擎或數據錯誤的「大聲宣告」協議——錯誤是首要交付物,而非繞過的問題。每當 NexusTrade 工具出錯、掛起或返回與配置矛盾的數字時使用;每當你忍不住寫下「可能是引擎怪癖」時;或當發現的錯誤使先前的回測失效且結果必須隔離時,都應使用此協議。包含錯誤交接文檔模板(參見 references/BUG_TEMPLATE.md)。

公共投資組合挑戰 是什麼?

這個「Bug Protocol — “Loudly Declare”」技能為 NexusTrade 認證活動定義了嚴格的錯誤處理規範,將錯誤視為首要交付物而非需要繞過的障礙。它強調了「驗證而非假設」的原則,並以一個 totalBudget 超支部署錯誤導致數週結果失效的案例,說明了隱瞞錯誤的嚴重後果。該技能適用於任何引擎或數據錯誤,提供五步標準流程:停止並確認問題、記錄日誌、撰寫正式交接文檔、隔離受影響結果,以及向使用者大聲宣告。同時,它也明確列出了不屬於錯誤的情況(如 NoEligibleCandidate 或正確的缺失值行為),幫助使用者準確區分真正需要通報的引擎缺陷。此技能主要在 NexusTrade 平台上使用,與驗證流程緊密整合。

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

在你喜歡的 AI 中提問

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

說明文件

錯誤處理協議 —「大聲宣告」

運算與引擎堆疊是全新的且不斷演進。**每個失敗都必須遵循此協議。**切勿為了讓活動繼續進行而掩蓋錯誤——吞下一個錯誤比卡住某個階段更糟糕。虛構機制(編造引擎為何如此運作的原因)是最糟糕的失敗模式:活動中最糟糕的時刻,莫過於虛構調解事件、定價行為和預算行為。驗證,而不是假設。

先例:一個 totalBudget 超支部署錯誤(一本配置了 40% 預算的帳冊,在冷啟動時卻部署了約 96% 的 NAV)正是以這種方式被發現,並導致了數週的結果失效。一般的教訓是:隔離所有受到引擎缺陷影響的結果,並僅在行為修正後重新執行。

五個步驟(每次失敗皆適用)

  1. 停止並確認特徵——是配置(我的錯誤)、數據(來源端),還是引擎(NexusTrade)的問題?以最小化方式重現——找到能重現問題的最小作業/回測。
  2. 立即記錄在運行的 CAMPAIGN_LOG.md 中,標題為 ⚠️ BUG/ISSUE:症狀、重現 ID、預期與觀察結果、當前假設(標記為 假設),以及它所阻礙的內容。
  3. 如果是真正的引擎/數據錯誤,請撰寫交接文檔,檔案名稱為 <NAME>_BUG.md,放在運行目錄中,並以 references/BUG_TEMPLATE.md 中的模板為藍本(一行摘要、預期與觀察結果、使用 ID 的重現方法、主要假設、需排除的其他可能性、檢查方向、對結果的影響)。
  4. 隔離受影響的結果——將所有在修復前執行的回測/研究標記為可疑/無效。修復後重新執行。如果錯誤導致槓桿膨脹,則回報率和最大回撤都會被誇大,且任何受其影響的掃描基因可能失去區分能力——需要全部重新驗證。
  5. **在聊天中,醒目地告知人類。**錯誤是該階段中與交易結果同等重要的交付物——不是需要繞過的尷尬事。

哪些情況不是錯誤(誠實信號失敗——無需建檔)

  • 折返返回 NoEligibleCandidate = 這是一個誠實信號,不是錯誤。應擴大驗證範圍;不要降低認證門檻。
  • 一個已下市/尚未上市的名稱(例如 2022 年的 SNDK)不存在或位於拒絕清單中,且沒有偽造值 = 正確的行為。引擎偽造一個未交易名稱的價格/指標值,則是一個錯誤(參見引擎健全性)。
  • 單一 tick 的調解目標 = 即時策略會在日常再平衡中累積其餘部分——請如此說明,不要重新將其診斷為錯誤(參見部署閘門)。

驗證而非假設的檢查清單

在將任何關於引擎行為的主張寫入交付物之前,請使用以下任一方式進行驗證:query_backtest_events / query_portfolio_events、conditionFieldAudit,或一個最小化的重現方式。「引擎可能……。」不是證據。

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

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.

相關技能