SlateSafe

Inspiration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for SlateSafe

Inspiration

The last mile of a film or episodic release is full of invisible risk. A picture-locked cut can still be stopped by a background logo, a music cue with the wrong territorial window, or an unverified poster. The evidence lives across rights databases and asset-management systems, so teams often discover conflicts only when delivery is already under pressure.

SlateSafe turns that scramble into one clear production decision: hold, review, or clear—with the specific asset, ledger evidence, and next best remediation action.

What it does

1. A producer enters a release brief: territory, release date, scene context, and asset IDs from the cut.
2. SlateSafe queries the clearance-event ledger through the official mcp-clickhouse MCP server.
3. It evaluates every asset against active rights windows and territory coverage.
4. A Gemini Enterprise ADK release-counsel agent turns only verified evidence into a concise producer handoff. It cannot invent or override a clearance status.
5. The control room presents a traceable decision and remediation queue.

How we built it

• Google Cloud / Gemini: Google ADK creates the release-counsel agent. The live path uses Google Cloud credentials and Gemini to produce a constrained producer summary from verified evidence.
• ClickHouse: ClickHouse's official mcp-clickhouse server is launched and called with run_query at runtime using a least-privilege, read-only account.
• Product: FastAPI serves the workflow and the custom interface makes the decision understandable for a nontechnical release producer.
• Safety: ClickHouse is the system of record. Gemini can explain an outcome but cannot turn a hold into a clear.

Accomplishments we’re proud of

• An evidence-first decision engine, not a generic database chat interface.
• A complete producer experience with a visual greenlight packet.
• A real official ClickHouse MCP gateway, verified against ClickHouse SQL Playground during development.
• Gemini ADK is constrained to explain verified results, preventing hallucinated release approvals.

What we learned

Media rights are deeply temporal: a license can be valid for one territory and release date but block another. A useful agent needs to expose those conditions, not hide them behind a generic answer.

What’s next

We would connect to a studio's asset-management system, ingest timecoded detection events from the edit, and add role-based approvals. The core contract remains the same: every greenlight needs evidence.

Built With

• clickhouse
• fastapi
• gemini
• google-adk
• google-cloud
• javascript
• mcp
• mcp-clickhouse
• python
• vertex-ai