Implementing Final Receipts for Cron-Based Writing Workflows

说明与用途

作者建议在自动化内容发布工作流中添加“最终收据”（JSON 工件）。这种做法有助于跟踪使用了哪个账户、发布了什么标题以及生成的 URL，从而简化 Cron 作业中静默故障的调试过程。

问题

Scheduled automation jobs often fail in subtle, 'boring' ways, such as publishing to the wrong account, forgetting to save the final URL, or mutating content silently. These failures are hard to debug because the system appears healthy from a distance, leaving teams without clear evidence of what actually happened.

结果

By implementing a strict contract between the writer and executor and generating a final receipt (publish-result.json), teams can easily audit scheduled publishing jobs. This approach reduces debugging time and provides clear evidence of what was published, where, and by whom.

工作流

• Define a run directory structure for each execution instance.
• Writer generates context-aware plan data and saves it as plan.json.
• Writer generates the article content and saves it as article.raw.md.
• Executor takes the files from the run directory and publishes them.
• Executor writes a publish-result.json file containing the account used, approved title, run directory path, retry count, and the final public URL.
• Optionally store a content hash in the publish history to verify integrity.
• Link new posts to recent same-language references to maintain topic cluster continuity.

证据

The failure mode is not always 'job crashed.' More often it is 'job completed, but left weak evidence.'

来源

I want the last artifact to answer five questions fast: Which account was selected? What exact title was approved? Which run directory contains the source artifacts? Was the publish step attempted once or multiple times? What public URL came back from the platform?

来源