Different Hunger

OS Compiler

OS Compiler · Master Roadmap

The deterministic build map for the 0HR Brand OS. Every asset, prompt, and output section categorized as LOFI BLUEPRINT (strategy/wireframes) or HIFI PROTOTYPE (ready-to-deploy assets). Compiled from the Master Template v1 (LOCKED).

OS Compiler · Master Roadmap

The lead-generation factory, mapped end to end. Every artifact the install produces is classified into two build states so an AI session can generate it deterministically from canonical spec.

Note

Compiled from 0HR Brand OS Master Template v1 (LOCKED 2026-05-12) — the brand-agnostic contract CC reads at runtime. This roadmap is the human-readable index; the machine contract lives in the source doc + /lib/brand-os/*. Both stay in sync per the Master Template's HARD RULE. The locked per-component spec tree lives at Canonical and is not modified by this roadmap.

The two build states

LOFI BLUEPRINT

Strategy · wireframes · prompts · specs. The thinking. Positioning, offer math, voice rules, the prompts and intake schema that drive generation. Not shipped to a domain — consumed by the next stage. Reviewed at the Doc/wizard LOFI gate.

HIFI PROTOTYPE

Ready-to-deploy assets. The output. Render-ready copy, pages, emails, ads, decks that sync to brand.assets and ship to a domain. Reviewed at the HIFI wizard gate, then POC-approved.

The rule of thumb: a LOFI artifact is read by another generation call; a HIFI artifact is read by a customer.

Pipeline flow

01

Intake

Tell us about your business — 29 questions, 10 minutes.

02

Foundation

AI builds your strategy — positioning, offers, and playbook.

03

Components

14 deliverables generated — from landing page to nurture emails.

04

Go Live

Published to your domain. POC reviews, approves, we provision.

Every brand install walks the same path. Intake fills the schema → Foundation compiles the LOFI BLUEPRINT layer → Components render the HIFI PROTOTYPE layer → Go Live ships approved assets to the domain. QA (Section 25) auto-runs on every section before it advances.


Inventory at a glance

Sources
26 Asset Library5 New Prompts (N1–N5)10 Intake Blocks (A–J)
Lofi
Tier 0 · 3 prereq sectionsTier 1 strategy · 8 sections
Hifi
Tier 1 assets · 11 sectionsTier 2 content+creative · 13 sections
Govern
11 Validation RulesQA L1 (24) + L2 (6 gates)Brand-Wall enforcement

LOFI BLUEPRINT — the strategy layer

The thinking the factory runs on. Sources are locked references; sections are generated strategy that cascades into every HIFI asset.

Sources (read at runtime, never rewritten)

IDAssetRole
SPSystem Prompt — Growth WriterLoaded as system message on every call
P0Customer Feedback AnalysisPrereq for P1 · feeds Section 1A
P1Targeting + Positioning + OfferTMS · positioning matrix · $100M offer
P2Profile CopyLinkedIn · IG · FB
P3Sales NBOQ for {TM} + "If I offered"
P4Sales Content6 sales deliverables
BIG-PAPIDon Draper Master CampaignAvatar · Resonance · Offer suite · NBO
COSContent Creation OSideate→create→promote loop
SERP-BRIEFOptimized Article BriefSERP JSON → blog brief
VG-REFDH Voice GuideStructural target for N3
TARGET-REFDH Targeting BlueprintStructural target for P0 / 1A
+ 15 morerefs · templates · creative librarysee Master Template Part 1

New prompts to write (N1–N5)

PromptOutputStatus
N13 ad creative briefsTO WRITE
N2Render-ready blocks for 4 funnel page archetypesTO WRITE
N3Voice Guide Doc (VG-REF structure)TO WRITE
N41st-person trust case studyTO WRITE
N512–27 email nurture sequenceTO WRITE

Strategy sections (generated, cascade downstream)

§SectionTierCascades to
1ACustomer Feedback Analysis01B · 2B
23Brand Voice Guide0all sections (voice anchor)
24Terms Translation Table0all sections (≥3 branded terms)
1BTargeting Score + Persona1positioning · all copy
2Positioning Analysis + Statement1resonance · pages
2BResonance Map (StoryBrand)122A · 22B
2CPositioning Table + Design Brief1design · comparison assets
3Offer Score + 12-Section Explainer13B · 3C · 12 · 22A · 22B
3BOffer Productize Table13C
3COffer Automation Table (COGS)1margin governance

→ Canonized first: LOFI-01 · Offer Blueprint (Section 3 — the keystone that cascades into the entire HIFI layer).


HIFI PROTOTYPE — the ready-to-deploy layer

The output the customer reads. Every section renders to brand.assets and ships through a master template (MasterLanding / MasterAccess / etc.) — no hand-rolled HIFI.

Tier 1 assets (every install)

§AssetRenders to (brand.assets.type)
4LinkedIn Profilelinkedin_profile
5Instagram + Facebook Biosig_profile · fb_profile
6Sales NBO — Emailnbo_email
7Sales NBO — Social Postnbo_post
8Sales NBO — Story (3 frames)nbo_story
8BDirect Response NBOdirect_response_nbo
9Lead Qualification Flowqualification_flow
10Appointment Setting Sequenceappointment_sequence
10BFull-Funnel Email Nurture (12–27)nurture_sequence (multi-row)
11Lead Conversion Question Setconversion_questions
12125-Word Offer Explanation + 60soffer_explanation_125w
13Offer Enrollment Scriptenrollment_script
14Canned Responses (Objection Table)objection_table

Tier 2 content + creative (paid install)

§AssetRenders to (brand.assets.type)
15SEO Keyword Setintake_data.blueprint.keywords
16A3rd-Person Case Studiescase_study_3p (1/study)
16B1st-Person Trust Case Studiescase_study_1p (1/study)
17Blog Content Briefsblog_brief (1/brief)
18YouTube Content Briefsyoutube_brief
19Social Content Briefssocial_brief
19B5-Post Launch Sequencelaunch_sequence (multi-row)
20Content Distribution Checklistdistribution_checklist
21Ad Creative Briefs (3 variants)ad_creative (3 rows)
22ASales Page / Landing Pagesales_page_blocks
22BStrategic Pitch Deck (10 slides)pitch_deck_slides
22CCase Study Pagecase_study_page
22DApply + Confirmation Pageapply_confirmation_pages

→ Canonized first: HIFI-01 · Sales / Landing Page (Section 22A — the asset the Offer Blueprint cascades into).


Governance layer (applies to both states)


Build order

Master Index (this page)

Every entry categorized LOFI / HIFI. Done.

First pair — prove the compiler

LOFI-01 Offer BlueprintHIFI-01 Sales Page. The keystone cascade (§3 → §22A) in /os/standard format with machine-executable Technical Reference.

Canonize all sections — done

All 35 sections now have a /os/standard page (Header · Pipeline · Technical Reference), deterministically compiled from _sections.json by scripts/compile-os-roadmap.mjs. Edit the registry, re-run the compiler — pages regenerate identically. This is the OS Compiler.

Wire to code (next)

_sections.json/lib/brand-os/* stay in sync. Validators, sync-map, brand-wall codified. Acme Care test fixture (Part 16) runs E2E.