IX2-0536
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Core Changes Since InferenceXv1 - Line hint:
768
Context Before
Core Changes Since InferenceXv1
One of the main changes we have made since v1 is the cadence with which we perform sweeps. Previously, we were jestermaxing and performed a full sweep over each configuration nightly. However, as we added more chips, disaggregated prefill, wide EP, and other features, we realized that running every single night was way too time consuming and wasteful. Moreover, it’s just not necessary – benchmarks only really need to be re-run when recipes change or a new software version is released.
Evidence
When a PR containing a changelog addition is merged, a workflow parses the referenced config keys, pulls the corresponding sweep definitions from the master config, and fans them out as individual GitHub Actions jobs
Context After
Below is a high-level diagram of how InferenceX launches jobs.
② Atomic Claim
當包含 changelog 新增項目的 PR 被 merge 後，workflow 會解析所引用的 config keys，從 master config 取出對應 sweep definitions，並展開成個別的 GitHub Actions jobs。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "FLOW_RATE",
"context_nodes": [],
"entity": {
"id": "02_companies/GitHub",
"label": "GitHub"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "當包含 changelog 新增項目的 PR 被 merge 後，workflow 會解析所引用的 config keys，從 master config 取出對應 sweep definitions，並展開成個別的 GitHub Actions jobs。"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | GitHub | GitHub |
⑤ Human Review
請在 Properties 逐項確認：
- 原文 → Atomic Claim 是否忠實
- Atomic Claim → Semantic Frame 是否忠實
- Canonical Entity mapping 是否正確
- Epistemic mode 是否保留原文語氣
- 最後選擇
review_action
Review state
Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。