Private desktop system · stable local

Briar Creative OS

Private desktop creative-operations system for projects, candidates, review, technical QA and publication gates.

Overview

Problem

Creative work becomes difficult to govern when files, decisions, review state and publication authority are spread across unrelated tools.

Design

The system treats projects, candidate revisions, review decisions, queues, technical QA and release gates as explicit durable state.

Outcome

A single governed workspace for creative review and production decisions without turning the public website into an operator surface.

Verification

Public disclosure is limited to the workflow and authority model.

DesktopReview workflowTechnical QACreative operationsCreative systemsDesktopProduction

Architecture

  1. project registry
  2. candidate revisions
  3. review inbox
  4. technical QA
  5. promotion
  6. publication gates
  7. durable local state
Public architecture diagram for Briar Creative OS

Components

component

Project registry

Canonical creative project and candidate identity.

component

Review Inbox

Explicit queue for human review decisions.

component

Technical QA

Reproducible checks that do not imply creative approval.

component

Publication gate

External release remains separate from review and promotion.

Decisions

active

Make review state durable

Files alone do not preserve why a candidate was approved, rejected or superseded.

Timeline

  1. Stable local operationsmilestone · stable-local
  2. External providers and publicationmilestone · bounded
  3. Creative workflow architecture is public; local assets, databases and publication controls remain private — public_boundaryevidence · 2026-08-11

Experiments

Releases

No project-specific public release record.

Evidence

public_boundary

Creative workflow architecture is public; local assets, databases and publication controls remain private

Creative workflow architecture is public; local assets, databases and publication controls remain private

source-contract · checked 2026-08-11 · fresh until 2027-08-11

Boundaries

The public case study describes workflow architecture only; local databases, assets, provider credentials and publication controls remain private.

Open bounded Lab →