Showcase Pair
HIFI-01 · Sales / Landing Page
Section 22A — Sales Page / Landing Page. The ready-to-deploy 9-block render that consumes the Offer Blueprint and ships to a domain via MasterLanding.
HIFI-01 · Sales / Landing Page
Purpose: Render the locked Offer Blueprint into a deploy-ready landing page — the asset a real customer reads and converts on. Consumes Section 3 (offer) + Section 2B (resonance map), outputs render-ready blocks that MasterLanding plugs straight into a brand domain.
Cascades from: 3 (Offer Blueprint) · 2B (Resonance Map). Renders through: MasterLanding template (Aceternity / approved components only — no hand-rolled HIFI).
Inputs → Output
Pipeline
Pull the cascade
Read locked §3 offer object + §2B resonance map. Offer name must match §3 exactly (cross-section consistency). Pull ≥3 refs from CL-MASTER / CL-EXAMPLES (Rule 2).
Generate 9 render-ready blocks
N2 in page-block mode emits: Hero · Trust Strip · Problem · Solution · Process · ROI · Pricing · Urgency · Social Proof + CTA ×3 + FAQ. Substitute ≥3 branded terms from §24 (≥2:1 ratio).
QA gate
Section 25 auto-runs L1 + L2. Gate 4 (WTF Moment) and Gate 1 (Unmistakable Identity) are the hard ones for a landing page. Any L2 fail = REJECT → rewrite.
HIFI wizard review
Render through MasterLanding, present in the HIFI wizard. Theme/copy/assets swap via brand.config.brand_os.theme + content_json — zero hardcoded Tailwind.
POC approve → deploy
POC approves in portal → /api/brand-os/approve writes sales_page_blocks to brand.assets → asset build renders to the brand domain. Custom-domain alias swap is the manual mk step.
Technical Reference
Generation contract (machine-executable)
section: 22A
id: sales-landing-page
state: HIFI_PROTOTYPE
tier: 2
sources:
system: SP
task: [N2.page_block_mode]
inputs:
required:
- section_3.offer # cascade (locked)
- section_2b.resonance_map # cascade
- section_24.terms_table # >=3 branded terms, >=2:1 ratio
output:
type: sales_page_blocks
blocks:
- hero
- trust_strip
- problem
- solution
- process
- roi
- pricing
- urgency
- social_proof
- cta # x3, journey-positioned
- faq
renders_through: MasterLanding # Aceternity / approved templates only
theme_source: brand.config.brand_os.theme
content_source: content_json
cascades_from: [3, 2B]Validation rules enforced (from Part 7)
Rule 1 NULL > FABRICATION no invented proof numbers
Rule 2 CITATION >= 3 cite >=3 ref IDs
Rule 4 VOICE ANCHOR SP every call
Rule 5 NO PREAMBLE hero dives straight in
Rule 8 THREE IS MAGIC pricing = exactly 3 tiers
Rule 10 COMPLIANCE no overpromising; claims grounded in refs
Rule 11 QA GATE L1 + L2 pass before marked readyQA L2 gates — landing-page priority (from Part 8)
Gate 1 UNMISTAKABLE IDENTITY recognizable as {Brand} on sight
Gate 2 MARKET KING stands out vs me-too pages
Gate 3 MOVEMENT MARKETING manifesto energy, pick-a-side
Gate 4 WTF MOMENT >=1 "I want this" line <-- hardest
Gate 5 BRANDED VOICE branded vocab dominant
Gate 6 FUNNY AND TRUE polarizing status-quo callout
# ANY single FAIL = REJECT, return for rewriteSupabase sync + render path (Part 10 + L1 lead-gen)
Section 22A -> brand.assets where type = 'sales_page_blocks'
render MasterLanding(brand.config.brand_os.theme, content_json)
domain alias swap (manual mk step until volume justifies)All HIFI sub-pieces render through MasterLanding / MasterAccess / MasterDeliveryEmail. No custom HIFI dev — templates use Aceternity or approved templates only.
Tip
This is a HIFI artifact: its consumer is a real customer. It only renders content that already passed the LOFI gate upstream — it never invents offer facts. If the Offer Blueprint says "Not measured," the ROI block says "Not measured."
Pair complete. This is the keystone cascade — LOFI-01 Offer Blueprint (§3) → HIFI-01 Sales Page (§22A) — the proof that the compiler turns one locked strategy artifact into a deployable asset deterministically. Every remaining section follows this exact /os/standard shape.