Implementing Final Receipts for Cron-Based Writing Workflows

Описание и применение

Автор предлагает внедрять «финальные квитанции» (JSON-файлы) в автоматизированные процессы публикации контента. Это помогает отслеживать, какой аккаунт использовался, какой заголовок был опубликован и какая ссылка получена, что упрощает отладку тихих сбоев в 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?

Источник