docs/assets/devpost-submission-packet.json

{
  "schema": "proofframe.devpost_packet.v1",
  "project_name": "ProofFrame",
  "tagline": "B2-ready provenance desk for GenAI media.",
  "one_liner": "ProofFrame turns generated media into approved evidence packets with B2-ready manifests, Genblaze-gated provider metadata, checksums, review status, and an exportable proof bundle.",
  "repository_url": "https://github.com/adjcjh777/backblaze-proofframe",
  "demo_url": "https://adjcjh-backblaze-proofframe.hf.space/?judge=1",
  "video_url": "TBD after final public video upload.",
  "inspiration": "Generated media is easy to make and hard to govern. Teams often lose the prompt, model, provider, approval status, and durable storage evidence for the files that eventually ship. ProofFrame treats provenance as the product, not a footer.",
  "what_it_does": [
    "Create a campaign brief.",
    "Generate candidate media assets.",
    "Review, approve, or reject assets.",
    "Search and filter evidence by prompt, model, storage key, checksum, and status.",
    "Track decision coverage across approved, draft, and rejected assets.",
    "Inspect prompt, provider, model, storage backend, storage key, checksum, and risk note.",
    "Copy a safe evidence summary without credentials, cookies, signed URLs, or raw secrets.",
    "Export a manifest.",
    "Download an evidence ZIP containing the manifest, README, and available media.",
    "Use Judge Demo to create a complete local packet instantly."
  ],
  "how_we_built_it": "ProofFrame uses FastAPI for the API, a single-file browser UI for the proof ledger, local storage for credential-free demos, a Backblaze B2-compatible S3 storage backend, and Genblaze provider adapters for GMICloud, OpenAI, and a credential-free local Pipeline provider built around the official Genblaze Pipeline API. The public mock demo is deployed as a Hugging Face Space for judge-friendly product inspection while final reports separate live proof, video, audit, and Devpost receipt gates.",
  "challenges": "The biggest challenge is avoiding shallow sponsor integration. ProofFrame has to make storage and provenance central: B2 should be the durable evidence layer, and Genblaze should be the generation orchestration path. Another challenge is public claim hygiene, so the repo separates local demo behavior from final live sponsor proof.",
  "what_we_learned": "The useful unit for generated media teams is not a single image. It is a packet: asset, prompt, provider, model, storage object, checksum, approval state, and risk note.",
  "accomplishments": [
    "Built a working local product, not just a pitch.",
    "Deployed a credential-free public mock demo.",
    "Added a one-click Judge Demo path.",
    "Added a review console with evidence search, status filtering, decision coverage, and safe summary copy.",
    "Added downloadable evidence ZIPs.",
    "Added B2-compatible storage and Genblaze provider code paths for GMICloud, OpenAI, and a credential-free local Pipeline provider.",
    "Added CI that runs readiness checks, lint, tests, API smoke, and secret scan.",
    "Added fail-closed gates for evidence JSON exports and final submission audits.",
    "Kept public claims gated by reports, task status, and secret-scan artifacts."
  ],
  "whats_next": [
    "Upload the final demo video under the event limit.",
    "Run the final secret scan and submission audit after video artifacts are ready.",
    "Submit the Devpost project and preserve the receipt URL."
  ],
  "current_providers_and_models": [
    {
      "provider": "mock",
      "model": "mock-svg-v1",
      "status": "current public mock demo"
    },
    {
      "provider": "genblaze/local-image",
      "model": "local-svg-v1",
      "status": "final B2-backed Genblaze proof"
    }
  ],
  "final_provider_and_model": {
    "provider": "genblaze/local-image",
    "model": "local-svg-v1",
    "status": "verified by docs/assets/final-live-proof-evidence.json"
  },
  "mode": "post_live_verified",
  "short_description": "ProofFrame turns Genblaze-generated media into Backblaze B2-backed evidence packets. Each packet includes prompt history, provider/model metadata, B2 storage references, checksums, approval state, and a downloadable manifest bundle so teams can trust, reuse, or retire generated media.",
  "b2_usage": "ProofFrame stores generated media and exported manifests in Backblaze B2 using environment-only credentials. The final proof evidence records sanitized B2 storage keys, byte sizes, and checksums without exposing credentials or signed URLs. B2 is the durable evidence layer: the media asset and manifest are separate objects under the ProofFrame campaign prefix, and the app uses those hashes to make later review, export, and audit steps reproducible.",
  "genblaze_usage": "ProofFrame generates media through Genblaze's official Pipeline. The final proof uses the credential-free local image provider, records provider/model metadata, and carries the resulting asset through Genblaze's B2 sink into the ProofFrame storage and approval manifest.",
  "claim_warning": "Use only after T020 and T021 are verified by live proof evidence.",
  "submission_checklist": [
    {
      "task": "T020",
      "label": "B2 live proof complete",
      "status": "done",
      "required_for_final": true
    },
    {
      "task": "T021",
      "label": "Genblaze live proof complete",
      "status": "done",
      "required_for_final": true
    },
    {
      "task": "T040",
      "label": "Devpost registration complete",
      "status": "done",
      "required_for_final": true
    },
    {
      "task": "T041",
      "label": "Final submission audit complete",
      "status": "todo",
      "required_for_final": true
    },
    {
      "task": "T041A",
      "label": "Final secret scan complete",
      "status": "todo",
      "required_for_final": true
    },
    {
      "task": "T042",
      "label": "Devpost project submitted",
      "status": "todo",
      "required_for_final": true
    }
  ]
}