产品判断:三种加载方式属于实现细节,文档里说清"要不要在常驻里留索引"就够了。 ⇒ 表格和「为什么必须分开」整段删掉,留三句: · 常驻的成本是**所有业务线常驻之后的总和**,而规则越多每条被遵守的概率越低 · 所以只有主职责常驻;次要的活写成单独一篇,常驻里只留一行索引 · 实测:问"前面那两批怎么样了",模型第一步就自己去取了做法⚠ ️ 自查:上一版我把 `_guide` / `open_playbook` 的机制差异写了满满一节 —— 那是**实现**,不是产品设计。读者要知道的是"次要业务线不常驻",⛔ 不是"它用哪种方式送到模型手上"。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| algorithms | Loading commit data... | |
| api | Loading commit data... | |
| architecture | Loading commit data... | |
| design | Loading commit data... | |
| integration | Loading commit data... | |
| start | Loading commit data... | |
| canonical-fields.mdx | Loading commit data... | |
| data-extraction.mdx | Loading commit data... | |
| data-reconciliation.mdx | Loading commit data... | |
| deploy-runbook.mdx | Loading commit data... | |
| deployment.mdx | Loading commit data... | |
| design-system.mdx | Loading commit data... | |
| error-codes.mdx | Loading commit data... | |
| event-enums.mdx | Loading commit data... | |
| ingestion.mdx | Loading commit data... | |
| meta.json | Loading commit data... | |
| monitoring.mdx | Loading commit data... | |
| troubleshooting.mdx | Loading commit data... |