STUDIO TOOL

Studio OS

The dashboard we run the studio from.
We make
our videos, documents and
sites on it as
productions and builds,
and each one waits on
an approval
Frederick records against a file hash

or a commit id.

This work's record Next: Media OS

The Studio OS board for one production: its brief, its brief gate and its deliverables.

SCREEN CAPTURE

What it does

01
One parser,
one hash
Every production and every build
opens
with a brief, and approval
stores the
file's sha256.
02
Builds
in slices
A slice is approved by a commit id,
and
the board records it only after

checking that the commit exists.
03
Writes as
staged plans
Push and migrate run from the
build
board as staged plans.
A spend plan
is a record only.
Frederick confirms a
plan by
typing its fingerprint back.
04
Pages that say what
they could not read
When the project registry cannot
be
read, the HQ page says so and
shows no
counts, since a zero
over a failed read
would pass for
a quiet day.

From one
production's board

All three frames show the same production,
made for a client we invented.

SCREEN CAPTURE
At the top of the board: the brief, every

line marked STATED, INFERRED or GAP,
and
approved against the file's sha256.
SCREEN CAPTURE
Further down the same board: the cut
approval
above the storyboard, where every
scene tile
carries its own status.
SCREEN CAPTURE
The cut approval up close: the time,
the sha256
of the approved H.264, and
Frederick's words as
he typed them.