LexZetaR™ Archive — Studio Memory

LexZetaR™ turns 50TB of dead scripts & dailies into a live crew member with IBM Bob, Confluent & Gemini — searchable studio memory.

Comment

Inspiration

Every studio has 50TB+ of scripts, dailies, storyboards rotting on drives. A director asks "find the night exterior from 2019 where lead was sad" and it costs 3 days + $5k in PA time. Reshoots cost $5M/year because memory is dead. We built LexZetaR™ Archive — Studio Memory to make memory agentic, not archival.

What it does

LexZetaR™ Archive turns 50TB of dead assets into a live, searchable crew member.

  • Search in English: "find all sad dialogue from act 2" → timecoded results in 2s
  • Storyboard Agent: Auto-builds rough cuts from archival dailies
  • Rights Agent: Instantly answers "who owns this music/location/likeness?"
  • Live Memory: Not a folder, a crew member that remembers everything

How we built it

Pipeline: Studio Assets (50TB /mnt/studio_assets, 10MB chunked) → Confluent Kafka (confluent-kafka Python 2.8.0, SASL_SSL, Topic: lexzetar-raw-ingest, idempotent producer, SHA256 dedup, DLQ: lexzetar-dlq) → Gemini 1.5 Pro (Vertex AI, transcription, frame captioning, entity/emotion extraction, text-embedding-004) → ClickHouse Vector DB + IBM Cloud Storage → 3 Agents (Search, Storyboard, Rights via Google Cloud Agent Builder) → React Frontend.

IBM Bob Orchestration — 38/40 Bobcoins:

  1. Code Gen: Bob generated FastAPI ingestion service main.py, requirements.txt, Dockerfile, docker-compose
  2. Code Review: Bob flagged memory leak for 10GB+ files, added streaming
  3. Testing: Bob generated pytest for DLQ retry
  4. Deployment: Bob deployed to IBM Code Engine with auto-scaling MCP Servers: Code Gen, Review, Testing, Deployment. All LICENSE files include LexZetaR™ trademark header.

Challenges we ran into

  • 50TB scale: backpressure and checksum dedup
  • Hallucinations: Gemini inventing rights info — solved with filtered RAG
  • Devpost image bug: WEBP header mismatch → fixed with JPG 3:2 exports
  • Bob trademark: getting Bob to respect ™ in all files

Accomplishments that we're proud of

  • End-to-end pipeline in 36h, demo over 500+ assets
  • True Bob CI/CD: every commit reviewed by Bob for IP security
  • Search latency <2s over simulated 50TB vector index
  • Full brand lock: LexZetaR™ trademark on every page

What we learned

RAG is not enough. Studios don't need another search bar, they need agentic memory that understands production context, rights, and story. Orchestration is the product — IBM Bob is the differentiator.

What's next for LexZetaR™ Archive — Studio Memory

  • Avid / Premiere Pro plugin for in-timeline search
  • On-prem air-gapped version for 500TB+ studios
  • Monetization via Bobcoin metered usage
  • Partnerships with Confluent for enterprise connectors

© 2026 LexZetaR™ — All Rights Reserved — Trademark Protected. Built for Agentic Cinema Hackathon — IBM $7,500 + $75K Overall.

Built With

  • confluent
  • fastapi
  • film-tech
  • gemini
  • hollywood
  • ibmbob
  • kafka
  • lexzetar
  • mcp
  • multiagent
  • python
Share this project:

Updates

posted an update —

HOW I KNEW - THIS WAS BAIT - FINAL WITHDRAWAL

I set a forensic honeypot. That is how I knew.

Public wrapper = BAIT — README with ID LZ-MU-WMCA-012926-IMPE, open-source license detectable at top (About section) as demanded — vault remained private Memphis-controlled — 8 Rings IMPENETRABLE — Red Horse Protocol avatar as seal.

You altered requirements after I submitted:

  • 10:06 AM auto demand: public repo + license at top + demo video + "this thread NOT seen by judges" + Sep 9th 2pm PT deadline
  • 3:39 AM personal contact Tim E about same project after auto demand
  • 1:55 PM AI at Meta email selling "Agentic image generation and editing" identical to my LexZetaR™ vault that already existed

That is textbook harvest — make me go public to qualify, lock delete during hackathon, hide discussion from judges, then have a human contact the asset.

Forensic proof: Entry #102 / Project ID 1043290 went from 3 PROJECTS at 12:16 AM to 4 PROJECTS at 5:05 PM after I complied with public repo demand — chain of custody logged in FORENSIC_LOG.md + RINGS.md + git commit 9:35 PM PoodieP 3 mins ago.

So I rescinded — rescind array executed — GitHub wiped to seal only — Devpost updates at 10:23 AM + 10:28 AM posted as public record — now withdrawing everything from Agentic Cinema.

OUT OF DESTRUCTION COMES ORDER.

Copyright (c) 2025 PoodieP / Wen Austin (wenaustin78) — All Rights Reserved — No license — Withdrawn.

ID: LZ-MU-WMCA-012926-IMPE — STATUS: WITHDRAWN / IMPENETRABLE

Log in or sign up for Devpost to join the conversation.

posted an update —

"Please delete Project ID 1043290 Entry #102 - ID LZ-MU-WMCA-012926-IMPE - I have posted DISCONTINUED update at 10:23 AM - Delete button not showing because hackathon lock - Request manual deletion by manager - Copyright violation"

Log in or sign up for Devpost to join the conversation.

posted an update —

DISCONTINUED - COPYRIGHT VIOLATION - INPUT RESCINDED

ID: LZ-MU-WMCA-012926-IMPE - Entry #102 / Project ID 1043290 - STATUS: ARCHIVED / IMPENETRABLE

All source code, assets, and instructions for LexZetaR™ Archive — Studio Memory have been rescinded by sole author PoodieP / Wen Austin (wenaustin78) / Forensic AI Architect.

Reason: Breach of trust - Altered requirements after submission - 10:06 AM demand for public repo with license detectable at top (About section) + missing demo video + 3:39 AM contact from Tim E + requirement that thread is NOT seen by judges while demanding changes by Wed Sep 9th 2pm PT - Forensic chain preserved.

This project was Memphis-built solo - 50TB of dead scripts & dailies turned into live crew memory - Agentic Cinema - 8 Rings of Impenetrable Protection - Red Horse Protocol.

Copyright (c) 2025 PoodieP / Wen Austin / LexZetaR™ - All Rights Reserved - No license granted.

OUT OF DESTRUCTION COMES ORDER - Vault sealed - No further updates.

ForensicVerified #ID_LZ-MU-WMCA-012926-IMPE #Rescinded

Log in or sign up for Devpost to join the conversation.