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
Briar Creative OS
Private desktop creative-operations system for projects, candidates, review, technical QA and publication gates.
Overview
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
Selected case studies
Briar Creative OS
Private desktop creative-operations system for projects, candidates, review, technical QA and publication gates.
- 01Problem
Creative work becomes difficult to govern when files, decisions, review state and publication authority are spread across unrelated tools.
- 02Design approach
The system treats projects, candidate revisions, review decisions, queues, technical QA and release gates as explicit durable state.
- 03Limits of this case
The public case study describes workflow architecture only; local databases, assets, provider credentials and publication controls remain private.
Verified Project State · 16.1
Evidence and observation dates
Public disclosure is limited to the workflow and authority model.
Review due · Review window: 21 days
- Evidence date
- Record reviewed
- Snapshot evaluated
Source activity, the date of review and the website release are different events. A new website release does not renew this project’s evidence.
Open the dated state ledgerProject Intelligence 3 · 2026-08-18
Living state
Creative operations, apparel production state, candidate review, technical QA and controlled release preparation.
What changed
The local production pipeline is established; current work concentrates on safe composition/calibration rather than bypassing QA gates.
Updated 2026-08-18 · 21d freshness window
What’s next
- Improve apparel calibration
- Preserve editable/adaptable outputs
- Keep technical validity separate from publication
Public dependencies
- Forja Yggdrasil · production_partner — Forja supplies governed generation/review concepts to creative operations.
phase:productiondesktop creative operationsdurable candidate statetechnical QApublication gates
Architecture
- project registry
- candidate revisions
- review inbox
- technical QA
- promotion
- publication gates
- durable local state
Components
Project registry
Canonical creative project and candidate identity.
Review Inbox
Explicit queue for human review decisions.
Technical QA
Reproducible checks that do not imply creative approval.
Publication gate
External release remains separate from review and promotion.
Decisions
Make review state durable
Files alone do not preserve why a candidate was approved, rejected or superseded.
Timeline
- Stable local operationsmilestone · stable-local
- External providers and publicationmilestone · bounded
- Creative workflow architecture is public; local assets, databases and publication controls remain private — public_boundaryevidence · 2026-08-11
Experiments
briar-creative-os
Status: bounded
Open bounded Lab →Releases
No project-specific public release record.
Evidence
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.
- Local databases, creative assets, provider credentials and publication controls remain private.
Start with a defined scope
For a collaboration, describe what you are building, what is constrained and the result you need. Public prototypes and architecture pages are not a promise of a finished commercial service.