Documentation
0HR OS
The operating manual for Studio delivery. Functional docs for AI + humans.
0HR OS
The operating manual for the Studio delivery workflow. AI sessions + workforce editors read these to execute correctly.
Not for POCs primarily. POCs (brand contacts like Steve at MCM) live in the portal command center — that's where they review scope, terms, install state, and approve their brand's copy + HIFI. The portal may hyperlink to specific /os sections when a POC wants to drill down into "what template are you applying to my brand" or "what's your voice rule discipline" — but /os is not designed as a POC entry point.
Not marketing. Marketing lives on the websites (differenthunger.com · 0hr.com · brand domains).
Roles
| Role | Who | Approves |
|---|---|---|
| POC | Brand's primary contact (Steve = MCM POC) | Their brand's copy + HIFI locks per component |
| Reviewer | Workforce editor with review auth | System rules · master templates · cross-brand patterns |
| Founder | Founder · escalations only | Strategy disputes · architecture changes |
| Auto | AI checks · no human | Compliance: em-dashes · fabrication · Title Case · voice rules |
The 5 essential pages
| Page | What it answers |
|---|---|
| Rules | What can't be done · the locked constraints |
| Templates | The wheels · master HIFI components AI renders from |
| Components | The 14 install deliverables · what each maps to |
| Workflows | The autonomous pipeline · how locks gate execution |
| Brands | Live state per brand · what's locked · what's owed |
Read in this order on every session
- Rules — internalize what NOT to do
- Templates — see what's already built; render + plug data
- Components — find the spec for the deliverable you're working on
- Workflows — follow the lock gates
- Brands — check current state before acting
Source of truth
These pages compile from locked specifications in the 0HR Brand OS repo (Unmint MDX at apps/os/packages/template/content/os/) and live per-brand state in Supabase (brand.config).
When a rule, template, component, workflow, or brand state changes, the repo and Supabase update — and this docs surface updates in the same lock pass.
/os real-time sync is non-negotiable. No drift between docs + Supabase.