Problem
Creative work becomes difficult to govern when files, decisions, review state and publication authority are spread across unrelated tools.
Private desktop system · stable local
Private desktop creative-operations system for projects, candidates, review, technical QA and publication gates.
Creative work becomes difficult to govern when files, decisions, review state and publication authority are spread across unrelated tools.
The system treats projects, candidate revisions, review decisions, queues, technical QA and release gates as explicit durable state.
A single governed workspace for creative review and production decisions without turning the public website into an operator surface.
Public disclosure is limited to the workflow and authority model.
Canonical creative project and candidate identity.
Explicit queue for human review decisions.
Reproducible checks that do not imply creative approval.
External release remains separate from review and promotion.
Files alone do not preserve why a candidate was approved, rejected or superseded.
Status: bounded
Open bounded Lab →No project-specific public release record.
Creative workflow architecture is public; local assets, databases and publication controls remain private
source-contract · checked 2026-08-11 · fresh until 2027-08-11
The public case study describes workflow architecture only; local databases, assets, provider credentials and publication controls remain private.