BrandOSPublic entry, workspace access, and guidance

Public entry

Repo-backed brand workspace and public entry point.

BrandOS landing

The public entry stays brief and points people onward.

Message variation · 3 variations

BrandOS keeps brand work close to the repo

The source stays in the repo while the public route stays clear.

BrandOS gives the public a quick read on the workspace without moving the source of truth out of the repo. The public entry stays brief and points people onward.

Sign inOpen app

What BrandOS is

Canonical content stays in the repo, while the runtime renders approved output.

BrandOS keeps canonical content in the repo, separates source from interface, and uses the indexed runtime layer to render approved output in the right place.

  • Canonical source stays in the workspace repo
  • Derived output stays indexed and reviewable
  • People browse, generate, and provide feedback without losing the source model

What BrandOS is not

BrandOS stays narrow so the public page does not become the source of truth.

BrandOS stays narrow on purpose. The landing page should not become the source of truth.

  • Not a generic AI chat product
  • Not a freeform CMS
  • Not the editorial source of truth

Supporting sections

The public page can show more context, but it should stay clearly secondary.

What BrandOS is

BrandOS is DesignChief's repo-backed brand operating layer. It turns approved brand content into structured workspace views so the product can explain itself consistently across Overview, Admin, Docs, Feedback, and later the public landing page.

BrandOS is DesignChief's repo-backed brand operating layer. Canonical markdown stays in the client repo; the platform indexes it into workspace views.

Key actions

  • keep the repo as the source of truth
  • shape approved content into structured surfaces
  • keep the interface separate from the source

Related surfaces: Overview · Admin · Docs

What BrandOS is not

BrandOS is not a second CMS.

What it is not

  • BrandOS is not a second CMS.
  • It is not a generic AI chat product.
  • It is not a freeform editorial layer that can drift away from the repo.
  • It is not a replacement for canonical brand content in the workspace repo.

Key actions

  • avoid generic AI framing
  • avoid freeform CMS language
  • avoid turning the landing page into the source of truth

Related surfaces: Overview · Admin

How BrandOS works

BrandOS works from repo content first. Canonical markdown lives in the client repo, the platform syncs and indexes it, and the UI renders from the indexed runtime layer rather than raw file reads.

Key actions

  • keep the repo as the source of truth
  • shape approved content into structured surfaces
  • keep interface text separate from canonical source
  • route readers to the right surface for the job

Related surfaces: Overview · Admin · User guide

Who BrandOS is for

A user should be able to understand the workspace, find the right surface, and see how the repo-backed model keeps the system consistent.

Key actions

  • DesignChief workspace users
  • DesignChief admin and studio owners
  • people who need orientation, help, or reference
  • readers who need to understand the source and review path

Related surfaces: Overview · User guide · Admin

Available workspaces

Open a workspace directly or move into the stewardship surface.

studio · database

DesignChiefHeuristic fallback

DesignChief

brand.designchief.io

Brand block visiblePlatform typography
Open workspaceOpen voice

client · database

AuricHeuristic fallback

Auric

auric.brand.designchief.io

Brand block visiblePlatform typography
Open workspaceOpen voice
Open admin shellOpen sign-in

Runtime status

The request context shows which surface and workspace are being served.

Host: brand.designchief.io

Surface: entry

Workspace: none

Request id: a00f130109a0a0ea