Communitygithub.com

austin-starks/公共投资组合挑战

在NexusTrade认证活动中,针对平台、引擎或数据缺陷的“大声宣告”协议——缺陷是一等的交付物,而非绕过的问题。每当NexusTrade工具报错、挂起或返回与配置矛盾的数据时,或当您想要写下“可能是引擎异常”时,又或当发现的缺陷使先前的回测失效且结果必须隔离时,请使用此协议。包含缺陷交接文档模板(见 references/BUG_TEMPLATE.md)。

公共投资组合挑战 是什么?

该技能定义了一个严格的“缺陷协议”,用于NexusTrade认证活动。其核心原则是“大声宣告”,即放弃掩盖错误的做法,将引擎、数据或配置的每个故障都视为需要记录的正式缺陷。这种严格的失败处理方式至关重要,因为估算行为(如臆造价格)曾导致数周的回测结果无效。该协议包括五个关键步骤:停止并表征问题、立即记录、撰写正式的缺陷交接文档(使用BUG_TEMPLATE.md模板)、隔离受影响的结果(将错误发生前的回测标记为可疑),并在对话中醒目地告知人类操作者。此外,它还明确了哪些情况不属于缺陷(例如,诚信信号如“NoEligibleCandidate”)并提供了一个“验证而非断言”清单,要求工程师使用查询回测事件或投资组合事件等工具来提供实际证据,而非推测。此技能支持任何基于NexusTrade的AI代理平台(如Claude Code、Cursor或Codex),通过将缺陷管理嵌入工作流来帮助维护回测结果的完整性。

兼容平台~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% 的资产净值)正是以这种方式被捕获,并使数周的结果失效。一般教训是:隔离受引擎缺陷影响的每个结果,并仅在行为修正后重新运行。

五个步骤(每次失败均适用)

  1. 停止并表征 —— 是配置(我的过错)、数据(来源端)还是引擎(NexusTrade)?最小化复现 —— 仍然能复现该问题的最小作业/回测。
  2. 立即记录 在运行的 CAMPAIGN_LOG.md 中,使用 ⚠️ BUG/ISSUE 标题:症状、复现 ID、预期与观察结果、当前假设(标记为 假设)、它阻塞了什么。
  3. 如果是真正的引擎/数据缺陷,写一份交接文档 <名称>_BUG.md 放在运行目录下,模板参照 references/BUG_TEMPLATE.md(一行摘要、预期与观察结果、包含 ID 的复现步骤、主要假设、需排除的替代方案、查看位置、对结果的影响)。
  4. 隔离受影响的结果 —— 将修复前运行的所有回测/研究标记为可疑/无效。修复后重新运行。如果缺陷放大了杠杆,那么收益率和回撤都会被放大,且任何受影响的扫描基因都可能失去区分能力——需全部重新验证。
  5. 在对话中醒目地告知人类操作者。 缺陷与交易结果一样,是该阶段同等重要的交付物——不是需要绕过的尴尬事。

什么不是缺陷(诚信信号失败 —— 不要提交这些)

  • 一个返回 NoEligibleCandidate 的因子 = 诚信信号,不是缺陷。扩大验证范围;不要降低认证标准。
  • 一个已退市/尚未上市的名称(例如 2022 年的 SNDK)缺失或位于拒绝列表中,且没有捏造的值 = 正确行为。引擎捏造一个未交易名称的价格/指标值才算是缺陷(参见 engine-sanity)。
  • 单 tick 的调和目标 = 实时策略通过每日再平衡积累其余部分——这样说明即可,不要将其重新诊断为缺陷(参见 deploy-gate)。

验证而非断言检查清单

在将任何关于引擎行为的声明写入交付物之前,请用以下之一作为支撑: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.

相关技能