22C · Case Study Page

HIFI PROTOTYPE · Section 22C · Tier 2live

Purpose: Render a standalone page presenting one case study.

Inputs → Output

Sources

SPSection 16A or 16B

Reads

section_16a.outputsection_16b.output

Writes

case_study_page

Pipeline

Load anchors

SP loaded as system message (voice anchor, Rule 4). Task prompts: SP · Section 16A or 16B. Pull ≥3 reference IDs (Rule 2). Reads locked upstream: 16A, 16B.

Generate

Standalone page rendering 1 case study

QA gate

Section 25 auto-runs QA L1 (24 checkpoints) + L2 (6 brand gates). Any L2 fail = REJECT → rewrite.

Render + ship

Render through MasterLanding / approved templates. POC approves in portal → /api/brand-os/approve writes the asset → ships to domain.

Technical Reference

Generation contract (machine-executable)

section: "22C"
id: s22c-case-study-page
state: HIFI_PROTOTYPE
tier: 2
sources: ["SP", "Section 16A or 16B"]
inputs:
    - section_16a.output
    - section_16b.output
output: "Standalone page rendering 1 case study"
cascades_from: [16A, 16B]
cascades_to: []

Supabase sync map (from Part 10)

Section 22C ->
  brand.assets where type='case_study_page'

SCHEMA NOTE: verify all jsonb paths + brand.assets type values against live Supabase before write. Flag missing columns in the PR; never create new columns without review.

Note

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 facts. Source of truth: Master Template Part 3 + the Master Index. To change this page, edit content/docs/roadmap/_sections.json and re-run the compiler.