DESIGN_READY_COPY_TAXONOMY

Design-Ready Copy: Asset Taxonomy

Purpose: Define reusable section structures by asset type so we don’t invent from scratch each time. The design-ready copy agent picks an archetype, then fills the section structure for that archetype from the campaign brief + case studies.

Status: Draft — updated after PDF review (2025-02-03).
Related: PRD-design-ready-copy-agent.md

---

1. Section library (building blocks)

Reusable modules. Each archetype is a sequence of these (some optional, some required, order fixed per archetype).

ID	Section name	Purpose	Data source	When to use
H	Header	Hero headline + subheadline; punchy, 2–3 variations	Brief	Every asset
T	Trusted by	Client logos; match ICP	Case studies	When we have relevant logos
K	KPI / metric highlight	One metric + 1–2 sentence takeaway	Brief	Service/sprint assets
P	Process	Time-box + 3–4 steps (e.g. Audit → Roadmap → Deploy); minimal text	Brief	Service/sprint assets
M	Menu of capabilities	What you get / what unlocks; 4–6 items	Brief + case flavor	Service/sprint assets
A	Audience + deliverables	Who this is for + deliverables list; cookie-cutter	Brief	Service/sprint; partner kit
C	Case study highlight	One proof nugget (or short case refs list) from case studies	Case studies	When we have a matching case
X	CTA	Headline + subhead + button; punchy, per service line	Brief	Every asset
F	Follow-up / Let’s talk	Standard contact block; never change	Static	Every asset
O	Offer / deal (promo)	“Why this exists,” promo mechanics, deadline	Brief / promo brief	Seasonal promotions only
G	Guide body	Variable-length sections (tables, goals, implementation, etc.); outline from brief	Brief + product/domain	Strategy docs, service guides
L	Partner / audience intro	Who this kit is for (e.g. VCs, partners); value of the kit	Brief	Partner/VC kit only
S	At a glance	Prepared for, Scope, Goal (short summary box)	Brief	Sprints, seasonal, strategy docs
E	Expected ROI / KPI table	Target metrics (e.g. CAC ↓, Repeat ↑), optional table	Brief	Sprints (e.g. Lifecycle)
I	Implementation plan	Step, owner, output (table form)	Brief	Sprints, strategy docs
Y	Your Brainforge Team	Roles (Strategist, Engineer, PM, etc.); short	Static / brief	Sprints, strategy docs
$	Pricing / engagement models	Packages, duration, price bands; optional	Brief	Sprints (e.g. AI Growth) when needed
W	Where teams get stuck	Problem / gaps (narrative or table: blind spot, current reality, impact)	Brief	Sprints (e.g. Lifecycle)

Rule: Copy only in each block. No layout or visual notes. See PRD §5 (anti-pattern).

---

2. Asset archetypes

One section structure per archetype. New assets choose an archetype; only net-new archetypes need a new structure.

2.1 Service 2-pager

Use for: Single service line, 1–2 page leave-behind (e.g. dbt audit, Edge to Activation).

Canonical sequence (dbt-style):
H → T → K → P → M (page 1) | A → C → X → F (page 2)

Order	Section	Notes
1	H	2–3 header variations
2	T	Clients matched to ICP
3	K	One metric + takeaway
4	P	3 steps, time-box
5	M	4–6 capabilities
6	A	Cookie-cutter audience + deliverables
7	C	One case study nugget
8	X	Per–service-line CTA
9	F	Static

Variant (Edge to Activation): Same blocks, different order. Page 1: H → K → T → M → C (K and case on p1). Page 2: P → A → X → F (process after audience). Agent can support “Service 2-pager (Edge variant)” when brief specifies.

Example PDFs: brainforge_dbt_audit_service.pdf (canonical), brainforge_edge_to_activation_service.pdf (variant)

---

2.2 Sprint (1–3 pages)

Use for: Time-boxed sprints (AI Growth, Lifecycle Data, Holiday stack). Section set and page count vary; use S (At a glance) and optional $, E, I, Y, W.

AI Growth Sprint (2 pages):
T → H → [proof: What Past Sprints Delivered] → P → [Key Outputs] → $ → A → X → F

• T before H. Proof block (past outcomes). $ = Engagement models & indicative pricing table.

Data Stack Holiday Deal (2 pages):
H → T → S → O → P → A → C → X → F

• S = At a glance (Prepared for, Scope, Goal). O = “Why This Sprint Exists.” P = “What You Get in 3 Weeks” (3 steps). C = case refs (“Turning Chaos Into Clarity”).

Lifecycle Data Sprint (3 pages):
H → T → S → M → W → P → E → I → [narrative] → Y → F → X → [Guiding KPIs] → C

• W = Where teams get stuck / Where the gaps are (table). E = Expected ROI. I = Implementation plan (step/owner/output). Y = Your Brainforge Team. Multiple case refs at end.

Rule: Sprint archetype = required H, T, P, A, X, F. Optional by sprint type: S, K, M, O, C, $, E, I, Y, W. Agent chooses sequence from a sprint subtype (e.g. “holiday promo” vs “lifecycle” vs “AI growth”) or brief.

Example PDFs: brainforge_ai_growth_sprint.pdf, brainforge_data_stack_holiday_deal.pdf, brainforge_lifecycle_data_sprint.pdf

---

2.3 Seasonal promotion

Use for: Time-bound offers (e.g. holiday deal). Overlaps with Sprint when promo is sprint-based; see 2.2 Sprint (Holiday Deal) for observed structure: H → T → S → O → P → A → C → X → F.

Example PDFs: brainforge_data_stack_holiday_deal.pdf

---

2.4 Strategy / service guide (3–4+ pages)

Use for: Strategy or assessment deliverables (e.g. Product Analytics Strategy). Multiple G sections (tables, goals, implementation); S and Y common.

Product Analytics Strategy (4 pages):
H → T → S → G₁ … Gₙ → Y → F → X

• G sections observed: Scope (bullets), Current State of the System (table), Goals (short/long-term), Hypothesis Tracking, Tracking Events audit, Implementation Plan, Priority Hypothesis, Sample Engineering Sprint.
• A is folded into S (Prepared for = audience).
• Y = Your Brainforge Team before F.

Rule: Outline for G₁…Gₙ (titles + 1-line description) comes from campaign brief or strategy template. No new section types; only library blocks.

Example PDFs: sample_product_analytics_strategy.pdf

---

2.5 Partner / VC kit

Use for: Partner or investor-facing kit. Not validated: brainforge_vc_partner_kit.pdf returned no extractable text (likely image-heavy). Keep proposed sequence until we have a text source or manual teardown.

Section sequence (proposed):
H → L → T → (K or M) → A → C → X → F

Example PDFs: brainforge_vc_partner_kit.pdf (TBD)

---

3. Mapping: example PDFs → archetypes (from PDF review)

PDF	Archetype	Verified structure
brainforge_dbt_audit_service.pdf	Service 2-pager	H→T→K→P→M | A→C→X→F (canonical).
brainforge_edge_to_activation_service.pdf	Service 2-pager (variant)	H→K→T→M→C (p1) | P→A→X→F (p2).
brainforge_ai_growth_sprint.pdf	Sprint	T→H→proof→P→outputs→$→A→X→F.
brainforge_data_stack_holiday_deal.pdf	Sprint / Seasonal	H→T→S→O→P→A→C→X→F.
brainforge_lifecycle_data_sprint.pdf	Sprint (3-page)	H→T→S→M→W→P→E→I→Y→F→X→KPI→C.
sample_product_analytics_strategy.pdf	Strategy guide	H→T→S→G₁…Gₙ→Y→F→X.
brainforge_vc_partner_kit.pdf	Partner / VC kit	No text extracted; structure TBD.

---

4. How the agent uses this

1. Input: Campaign brief (+ asset type or PDF name). Optionally: “Use archetype X.”
2. Resolve archetype: From brief metadata, asset type, or explicit instruction. If missing, infer from brief (e.g. “holiday deal” → Seasonal promotion).
3. Load section structure: Look up archetype in §2; get ordered list of section IDs (e.g. H, T, K, P, M, A, C, X, F).
4. Fill each section: For each ID, pull from brief / case studies / static per PRD and §1 rules. Output copy only; wording variations in separate section.
5. Output: One markdown file: sections in order, then “Wording variations” section.

No ad-hoc: If the brief doesn’t fit an existing archetype, we add a new archetype (new row in §2) with a defined section sequence. We do not invent a one-off section list per asset.

---

5. Open / to refine

• Sprint section set and length — updated from AI Growth, Holiday Deal, Lifecycle PDFs.
• Seasonal promotion — folded into Sprint (Holiday Deal); structure documented.
• Strategy guide — G structure and S, Y confirmed from Product Analytics Strategy PDF.
• Partner / VC kit — no text from PDF; need manual teardown or alternate source.
• Sprint subtypes — agent logic to pick T→H vs H→T, and when to include $, E, I, W (from brief or subtype name).