Processes are disposable; rollout state is resumable. When the collector dies, the next one reconciles each running rollout from durable state instead of quarantining or losing it: - execution: a process of an earlier boot on this host is DEAD; a top-level reaper whose owner (the collector) died still proves its subtree empty (scopes record the owner that started them); reconcile() pauses a rollout with a proven-clean crash checkpoint as CONTROLLER_RESTARTED and marks its running tool calls INTERRUPTED; resume() across a reboot rebases monotonic clocks by wall time and credits the downtime as a pause - stageworker.settle_interrupted: an admitted step whose executor is gone ends as STAGE_EXECUTOR_EXIT (free compile) and its handle is told directly; a board step without a clean board receipt still quarantines; nothing replays - collection_runtime.crash_checkpoint: capture the real system prompt, freeze the session at the last saved message (mid-work phases only); configure_pi skips a generation ID the ledger already completed - pi_session.js: checkpoint after every saved message (and compaction); on a recovered resume drop an unfinished trailing reply and answer open tool calls with an honest "interrupted by a platform restart" result - scheduler: a paused rollout's local slot held by a dead holder is released once every process is proven gone - pipeline: SIGUSR1 = planned handover (stop claiming, let board steps finish, shorten in-flight request holds, exit); SIGTERM still drains - export: bench_recovery closes the cut segment; the dropped unfinished reply is excluded (UNFINISHED_BEFORE_RESTART) - tests: test_controller_restart (real Pi on Linux: kill -9 mid-command, kill -9 mid-reply, SIGUSR1 handover, power loss + reboot), test_settle_ interrupted; three tests of the old quarantine-everything rule now assert the new outcome while keeping their guarantees (no replay, unrelated PID untouched, board lease kept) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
项目文档
本目录收录 BPU 量化轨迹工厂的设计与方法说明,原始文档内容保持不变:
运行入口与配置方式见 项目 README,实现约定见 CONTRACT.md。文档中的实验状态、服务器路径和实测结果对应其编写时间;当前运行状态需要重新核查。
SFT采集可靠性 V1(实施与验收)
- 计划与规范入口
- 实施计划:数据、GLM共享配额、生命周期、实时看板一体交付。
- 自动验收标准 与 机器用例清单:全部用例初始为NOT_RUN。
- 确定性数据规则:默认保留、100%覆盖、身份去重、因果闭合及版本回滚。
规则与运行规范放在该文档目录的 rules/;当前实现入口见 IMPLEMENTATION,逐步独立验收见 PROGRESS。模块通过不表示整版验收通过。
Git 收录范围
仓库收录 harness、模型适配器、Agent 配置模板、数据导出代码、脚本、测试、registry、配置和项目文档,保留现有提交历史。
模型权重、ONNX/HBM、数据集、缓存、运行状态、训练轨迹、评测输出、日志、第三方源码下载、压缩包以及本地凭据留在各运行环境,不随源码仓库分发。原工作目录下的 outputs/ 和 job_verdicts.csv 属于运行产物;这些文件继续保留在本地。启动前按项目 README 准备依赖、数据、模型与本地环境变量。
.env.local.example 和 agent/models.json.tmpl 为可提交模板;真实 .env.local 和 agent/models.json 已被忽略。