xBrief: Post-Production Collaboration

15 Seconds to First Briefing

Traditional classified document systems require manual clearance setup, custodian key generation, and access control server configuration. xBrief collapses this to 15 seconds with zero-click accept, 90 seconds with one-line CLI, and 10 minutes with deploy buttons.

Speed Tiers

Quick Start: Zero-Click

# 1. Set invite code (from security officer email)
export XBRIEF_INVITE_CODE=XBR-abc123

# 2. Deploy your first briefing (auto-accepts invite)
npx @private.me/xbrief deploy \
  --content ./operation-thunder.md \
  --classification SECRET \
  --custodians alice,bob,charlie \
  --threshold 2-of-3

CLI Setup (90 seconds)

# Install CLI globally
npm install -g @private.me/xbrief

# Initialize (generates custodian DID, saves to .env)
xbrief init

# Deploy your first briefing
xbrief deploy \
  --content ./operation-thunder.md \
  --classification SECRET \
  --custodians alice,bob,charlie \
  --threshold 2-of-3

# Output:
# ✅ Briefing split (2-of-3)
# ✅ Custodian shares distributed
# ✅ Access control enabled
# ✅ Ready for need-to-know requests

Deploy Button Setup (10 minutes)

Click one button to provision briefing server + custodian share storage on Vercel/Netlify/Railway:

The Problem

Post-production workflows span editorial houses, color grading facilities, sound studios, and VFX vendors — each receiving complete copies of content they need. One breach at any facility exposes finished or near-finished footage, the most valuable and leakable form of content.

The post-production phase is when content is most vulnerable: picture-locked footage, final color grades, mixed audio tracks, and completed VFX shots all exist as complete, viewable files across multiple independent facilities. Each facility's network is a potential leak point.

High-profile leaks consistently originate from post-production. Screener copies for awards consideration, rough cuts shared for notes, final deliverables sent to distributors — every handoff is a complete copy that can be copied, screenshotted, or exfiltrated.

The Old Way

The PRIVATE.ME Solution

xBrief splits post-production assets into XorIDA threshold shares distributed across facilities so no single facility holds complete content. Each house works on their assigned shares — editorial, color, and sound remain isolated.

The editor works with editorial shares, the colorist with color shares, the sound designer with audio shares. Each facility has enough information to perform their specific task, but no facility can reconstruct the complete deliverable. Final assembly requires threshold reconstruction with multi-party authorization.

This eliminates the 'complete copy at every facility' problem. A breach at the color house reveals color shares — mathematically worthless without the editorial and sound shares. The attack surface shrinks from 'every facility has everything' to 'no facility has anything complete.'

The New Way

How It Works

xBrief integrates XorIDA threshold splitting into post-production workflows with per-asset HMAC integrity, facility-scoped distribution, and threshold reconstruction for final delivery.

Use Cases

Integration

import { splitAsset, assignFacility } from '@private.me/xbrief';

// Split post-production asset across 3 facilities
const shares = await splitAsset({
  content: assetBuffer,
  threshold: { k: 2, n: 3 },
  facilities: ['editorial', 'color', 'sound']
});
// Each facility gets only their discipline's shares
await assignFacility(shares, 'color', { scope: 'grading' });

Security Properties

Verifiable Data Protection

Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.

Ready to deploy xBrief?

Talk to Ren, our AI sales engineer, or book a live demo with our team.

Ship Proofs, Not Source

xBrief generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.

Use Cases