ONE BRIEF / ONE VERIFIED ASSET
Make the asset.
Keep the proof.
Name what you are promoting. ProofForge creates one evidence-bound visual you can inspect, then optionally expands it into a seven-day campaign kit.
Start a verified campaign →VERIFIED LIVE RUN / OPENAI + GENBLAZE + B2
The evidence survived its own retrieval.
A verified operator-approved campaign is available from durable object storage.
- Asset SHA-256
- Stored iterations
- Review
THE FINISHED RUN / INSPECTABLE, NOT DECORATIVE
Two candidates were refused before one was accepted.
Loading the completed live-run trace.
B2 OBJECT FETCHED BACK
Loading receipt…
The final object and manifest are verified against their stored hashes.
03
YOUR RESULT
Ready when you are.
PF
Unlock a live run, describe the campaign, then create one verified visual.
LIVE RUN / OBSERVABLE STAGES
Preparing your verified visual.
The server has not accepted a run yet.
CAMPAIGN MASTERThe campaign identity stays in the signed brief and receipt; ProofForge does not fabricate a logo or unreliable AI-generated wordmark inside the image.
VERIFIED CAMPAIGN MASTERIdentity lockup rendered by ProofForge from the signed brief
ONE-VISUAL CAMPAIGN HANDOFF
Prepare the matching post and one-day kit.
YOUR VERIFIED ASSET IS READY
Prepare the matching post and one-day kit, or expand to the seven-day package only if you need the larger campaign.
04
OPTIONAL EXPANSION
Expand this into seven days.
The one-day kit reuses the approved master and writes one relevant post. If you need a campaign calendar, generate seven independent visuals and seven posts. Nothing is published or sent to an outside service.
- Package hash
- Verified master
- Contents
Inspect ZIP contents
How live runs are protected Technical details
03
SECURITY IS A FEATURE
Paid paths fail closed.
Judge access is isolated.
An authenticated judge session can access only run IDs it created. It cannot list other runs or administer the service.
One paid lane at a time.
The shared judge account has no hidden run-count quota during judging. One generation runs at a time; asset, request-body, timeout, and provider controls remain in force. No dollar cap is claimed without provider metering.
Every green light has a receipt.
Capability hashes, atomic redemption, HMAC signatures, run reservations, and the public fail-closed setting are testable evidence, not a trust-me banner.
How the proof works Technical details
04
WHY IT IS DIFFERENT
Failure is part of the proof.
Generate
Genblaze normalizes provider and model execution into one traceable run.
Evaluate
A quality gate treats the image and brief as untrusted data, then scores the output.
Revise
Feedback flows into the next prompt with parent-run lineage preserved.
Persist
Authorized live runs store every iteration under content-addressed B2 keys, then fetch every asset back to verify its hash.
Review
Authenticated live approvals are signed audit events bound to the completed receipt.
Export
One access-controlled bundle contains the brief, receipt, final manifest, and verified final asset; live receipts also expose the complete stored lineage.