Revision · Project 4 — Cutroom

Cutroom made video tractable by refusing the opaque “upload and hope” architecture.

Carry these ideas forward

• Probe and plan before allocating frames or model calls.
• Track timescale, presentation time, duration, orientation, and variable frame rate explicitly.
• Specialist capabilities return typed observations, not blended conclusions.
• Concurrency begins with admission limits, cancellation, and resource accounting.
• Segment timelines reference immutable evidence instead of copying media.
• Interval joins need named boundary semantics and adversarial tests.
• Expensive-model routing is an eval-backed policy, not a confidence vibe.

Rebuild from memory

Given a 20-minute variable-frame-rate video, write the resource plan before code: maximum samples, decoded memory, audio windows, concurrent specialists, deadline, and escalation budget. Then identify the artifact proving each limit was honored.

Next project: Forge — build a safe coding/research agent and study Codex CLI →.