CREATIVE//BOUNTY Generate. Verify. Replay.

A verifiable AI production pipeline: demand first, rights checked, budget authorized, Genblaze executed, B2 evidenced, replay verified.

Comment

Inspiration

Anyone can generate AI media. Almost nobody can prove how it was produced.

CREATIVE//BOUNTY is a verifiable AI production pipeline that records why generation was authorized, which provider produced it, where the evidence is stored, and how anyone can replay that evidence without regenerating the asset.

What it does

CREATIVE//BOUNTY is a verifiable AI production pipeline.

It starts from a paid creative opportunity, checks rights, evaluates economics, authorizes generation only within budget, executes through Genblaze, persists evidence to Backblaze B2, verifies the native Genblaze manifest, and supports read-only replay.

The final build includes a real LIVE proof:

  • Provider: Pollinations
  • Model: flux
  • Genblaze run id: 86a788b9-e8cd-42d9-a355-562a97669d9b
  • B2 asset SHA-256: 6a1e69f82b93dbfadcaf9f86a672f611bf2f76675ee262d4bf79f7ee1f23c441
  • Manifest hash: d4ae8034cc836a890a7f498bb512341448563a71230c180dddf0efa96c335e13
  • manifest.verify() == True
  • LIVE replay verified
  • Recorded provider cost: 0.0

No revenue, customer, contest win, or commercial outcome is claimed.

How we built it

The app is a FastAPI control plane with evidence-first domain logic.

Pipeline:

Opportunity
-> Rights
-> Economics
-> Budget Authorization
-> Genblaze
-> Pollinations
-> Backblaze B2
-> Verified Manifest
-> Replay

Backblaze B2 stores the durable evidence layer: source snapshots, decisions, events, accepted asset, native manifest, submission package, and audit receipt.

Genblaze orchestrates the provider run and produces the native manifest. The scorecard only unlocks the B2 and Genblaze criteria after a verified LIVE proof exists.

Challenges

The hardest part was not generating an image. It was refusing to fake proof.

NVIDIA NIM credentials were available, but the image endpoint timed out. Google image generation was not a safe zero-cost path. Those failed attempts remain in the Judge Pack because they are part of the audit trail.

The final LIVE proof uses Pollinations because it provided a real free image endpoint without API keys or billing, while Genblaze and B2 still supplied the verifiable pipeline and storage proof.

What we learned

A credible AI media workflow needs more than a prompt and an output.

It needs:

  • explicit rights evidence;
  • budget authorization;
  • provenance;
  • durable storage;
  • failed-attempt transparency;
  • replay without regenerating.

CREATIVE//BOUNTY treats truthfulness as a product feature.

What's next

Future work includes richer media evaluation, provider fallback with explicit budget caps, hosted evidence browsing, and full contest-ready video generation once authorized provider credits or revenue exist.

Built With

Share this project:

Updates