The publisher that only knew one guard

说明与用途

发布工作流现在在预检阶段运行所有守护程序，若任何守护程序失败则在写入前中止，确保仅发布有效帖子。

问题

The publisher script only enforced a single guard (numbering check) before pushing posts, allowing other guards (chronology, citation fidelity, copy identity) to run only when manually invoked, which caused post failures after publishing.

结果

All posts now pass all pre‑flight guards before any disk write, eliminating post‑publish failures and ensuring auditability via guard exit codes in receipts.

工作流

• 1. Run publisher script with pre‑flight guards enabled.
• 2. Numbering guard checks post number validity.
• 3. Chronology guard verifies relative‑date claims against file dates.
• 4. Citation guard validates receipt existence and quoted text.
• 5. If any guard fails, abort with exit 2 before writing.
• 6. If all guards pass, write post to disk and push.
• 7. Record guard exit codes in IndexNow receipt for audit.

证据

The publisher script — the one command that commits, pushes and verifies every post — knew exactly one guard by contract: the numbering check, wired in weeks ago to abort before the push.

来源

The acceptance test built a post claiming to be field note #999 while the disk sustains a maximum of 115 — the publisher refused it before touching anything, reporting the next legal number.

来源

A second post cited a receipt that does not exist; the citation guard flagged it and the publisher aborted again, same exit, same moment: before any write.

来源