Skip to content

DEMO_SCRIPT.md

Latest commit

 

History

History
68 lines (48 loc) · 3.03 KB

DEMO_SCRIPT.md

File metadata and controls

68 lines (48 loc) · 3.03 KB
Raw

TraceFrame demo script

Target: a public video under three minutes. Record only after the live-smoke gate passes.

Opening

"Generative media is easy to create and surprisingly easy to let drift. TraceFrame detects when a campaign asset, its canonical Genblaze manifest, and its operational record stop agreeing after generation."

Show the run library and identify the visible environment as the credentialed submission deployment. Do not show environment files, authorization headers, account screens, bucket keys, or browser developer tools containing secrets.

Create one bounded run

Create a single image with the prepared prompt and aspect ratio. State that TraceFrame fixes the provider to Genblaze's OpenAI adapter, disables automatic retries, and enforces authentication, idempotency, concurrency, queue, and daily quota gates.

While the request runs, explain that the backend reserves the idempotency key before making the paid call, so replaying the same request returns the original run instead of creating another charge.

Inspect the integrity record

Open the completed run. Show:

  • provider and fixed model;
  • prompt, dimensions, provider, model, and explicit non-synthetic status;
  • canonical manifest hash;
  • asset SHA-256 and content-addressed B2 key;
  • the full canonical manifest JSON.

State that SQLite is a query projection, not the integrity authority, and that this is an integrity and consistency check rather than authorship or C2PA authentication.

Show Backblaze storage

Open the storage view. Show B2 mode, the restricted bucket name if it contains no account-sensitive identifier, readiness status, the content-addressed image key, and the canonical manifest URI. Explain that the service needs only bucket-scoped list, read, and write permission.

Open the image through TraceFrame. State that private content is streamed through the authenticated API and rendered from a revocable in-memory browser URL rather than a public B2 object URL.

Verify durable bytes

Run verification. Show a passing result and explain the sequence:

  1. fetch the canonical manifest back from B2;
  2. verify its canonical hash;
  3. compare its provider, model, prompt, parameters, dimensions, and object declarations with the database projection; and
  4. stream the stored media bytes and recompute SHA-256.

End with: "TraceFrame makes Backblaze B2 the durable integrity layer behind generated campaign assets and surfaces drift between stored media and its generation record before approval."

Recording checklist

  • Use exactly one authorized paid generation unless existing validated output can demonstrate the complete workflow without another call.
  • Show a real B2-backed, non-synthetic run. Do not splice deterministic-demo output into the judged live path.
  • Keep every credential and authorization header out of frame.
  • Include the public repository and application URLs in the video description.
  • Use no copyrighted music or unlicensed third-party media.
  • Re-run the redacted evidence check and the public deployment smoke after the final edit.