SGUFT Appendix V3 Evidence Pack — Windowing, Regularization & Truncation Error Budget (G-closure), v1.0

概述 该记录是 SGUFT 附录 V3 的独立证据包,它冻结了 G 闭包核构造和审计的规范性“误差预算”:窗口函数/正则化/截断/退化处理必须明确记录为机器可读的工件,并且必须通过可审计的阈值策略。 这张唱片的意义何在? 不依赖叙述性解释,重现附录 V3 的 PASS/FAIL 检查。 确认每个 RUN-G 都包含明确的 error_budget.json 文件,并且审计员强制执行该文件。 从每个证据包中的 manifest_sha256.json 重新计算 SHA-256 完整性。 包含的文件 Gclosure_patchkit_v4.zip — V3 感知型发射器/审计器 + JSON 模式 + 默认阈值模板。 RUN_G_ms32_batch_kip1_v3_errorbudget_gclosure_only_pack_v1.zip — 批处理 RUN-G 证据(仅限 gclosure),包含 error_budget.json、audit.json 和清单。 (可选)RUN_G_ms32_batch_kip1_v3_errorbudget_gclosure_evidence_pack_v1.zip — 完整的批次证据,供深入审查。 校验和策略(仅限 DOI)如果 Zenodo UI 显示的校验和类型不是 SHA-256,则将每个包的内部 manifest_sha256.json 视为权威审计源。 版本控制策略:所有更新均以新的 Zenodo 版本发布;之前的版本将永久保留,可引用和可验证。不会静默替换文件。Overview This record is a standalone evidence package for Appendix V3 of SGUFT, which freezes the normative "error budget" for G-closure kernel construction and auditing: window functions, regularization, truncation, and degeneracy handling must be explicitly documented as machine-readable artifacts and must adhere to auditable threshold policies. What is the significance of this record? It enables reproduction of the PASS/FAIL checks from Appendix V3 without relying on narrative explanations. This includes verifying that every RUN-G contains a clearly specified error_budget.json file and that this file is enforced by auditors, as well as recomputing the SHA-256 integrity check using manifest_sha256.json from each evidence package. Included Files - Gclosure_patchkit_v4.zip: V3-aware transmitter/auditor, JSON schema, and default threshold templates. - RUN_G_ms32_batch_kip1_v3_errorbudget_gclosure_only_pack_v1.zip: Batched RUN-G evidence (gclosure-only), containing error_budget.json, audit.json, and the manifest. - (Optional) RUN_G_ms32_batch_kip1_v3_errorbudget_gclosure_evidence_pack_v1.zip: Full batch evidence for in-depth review. Checksum Policy (DOI-only): If the checksum type displayed in the Zenodo UI is not SHA-256, treat the internal manifest_sha256.json of each package as the authoritative audit source. Version Control Policy: All updates are released as new Zenodo versions; prior versions will be permanently retained, citable and verifiable. No silent file replacement will be performed.