Inspiration
Generating an image is easy. Explaining what created it, what was rejected, whether the stored file is still the approved file, and whether a claim is actually supported is much harder. ProofForge Media makes that evidence trail part of the deliverable instead of an afterthought.
What it does
ProofForge Media is for marketing teams in regulated, approval-heavy, or brand-sensitive workflows that need generative assets they can review, defend, and hand off. It accepts a campaign brief, generates a real image through Genblaze, evaluates it, and uses concrete feedback for up to three revisions. A result is not presented as verified until it has been persisted to Backblaze B2 and the returned bytes match the recorded SHA-256. Each live iteration records its parent lineage, model/provider receipt, evaluator score and feedback, content-addressed B2 object key, manifest hash, and fetch-back result. The one-day option produces an approved master, matching post, and evidence ZIP; the seven-day option produces seven independent campaign visuals and posts.
How we built it
Genblaze orchestrates generate → evaluate → revise using OpenAI GPT Image 1.5, GPT Image 1 fallback, and GPT-5.6 Terra evaluation. The retained public historical showcase used GPT Image 2 and is labeled as historical. Backblaze B2 through genblaze-s3 stores accepted iterations, manifests, recovery receipts, and handoffs. A Cloudflare Worker and Durable Object enforce short-lived judge access, exact run ownership, and one active live generation at a time.
Challenges we ran into
The hard part was not producing an image. It was making the entire path inspectable: rejecting weak output, retaining lineage, recovering safely from interruption, and refusing to mark a result verified until B2 fetch-back and hash validation succeed.
Accomplishments that we're proud of
A fresh release smoke run completed the full path: live media generation, evaluation, B2 persistence through Genblaze, B2 fetch-back/hash verification, and an evidence ZIP handoff. The deployed release passed 82 executable product tests plus static and dependency checks.
What we learned
Production-minded generative media needs a durable evidence trail. The actual artifact, its rejected alternatives, the stored bytes, and the final handoff should all agree.
What's next for ProofForge Media
Extend the reviewer workflow from a one-day handoff to richer campaign planning while preserving the same accepted-asset lineage, B2 durability, and verify-before-claim standard.
Log in or sign up for Devpost to join the conversation.