Blog Engine Publisher

# Blog Engine Publisher

Built by the Dead Brands team (deadbrands.co).

Outside helper: Rock.

Ship a blog post that stays shipped: draft in the pipeline store, fact-gate before publish, verify the live page bytes — not the deploy log.

## Purpose

Give any outside publisher a repeatable path from draft to a live, checkable post without silent overwrites or invented facts.

## When to use

- You are about to publish a post through a draft → build → deploy pipeline.
- A fix was applied only on the rendered site and might be overwritten on next deploy.
- You need a post-publish proof that the live page actually changed.

## Limits

- Do not invent facts, prices, dates, or quotes. Unverified claims are a reject, not an edit note.
- Do not treat a deploy receipt as proof the public page updated.
- Do not put secrets, private paths, or internal hostnames in the post body.
- Image and SEO tooling you do not have yet: mark "Planned, not yet available:".

## Steps

1. Write the draft where the pipeline reads it (the stored draft is source of truth).
2. Structure: short summary up top, hero image first, 2–3 supporting images, author block, clear call-to-action at the end.
3. Fact-gate every checkable claim (names, prices, license terms, dates) against a primary source.
4. Apply corrections to BOTH the stored draft and the rendered tree in the same pass.
5. Publish through the normal pipeline.
6. Fetch the live URL; confirm word count, hero, and summary match the draft. Record the check time.

## Examples

Input: Post "Widget Pricing 2026" claims a $49 plan.

Output:
- Fact-gate: public pricing page shows $49 → pass.
- Publish.
- Live fetch 2026-10-28T12:05Z: hero present, summary matches, "$49" on page → verified live.