haiku-method 2.2.0

package/studios/marketing/stages/content/STAGE.md

@@ -0,0 +1,15 @@
+---
+name: content
+description: Create campaign assets — copy, visuals, landing pages, emails
+hats: [content-creator, copy-editor, verifier]
+fix_hats: [content-creator, feedback-assessor]
+review: ask
+elaboration: collaborative
+inputs:
+  - stage: strategy
+    discovery: messaging-framework
+---
+
+# Content
+
+Create campaign assets — copy, visuals, landing pages, emails.

package/studios/marketing/stages/content/discovery/ASSETS.md

@@ -0,0 +1,29 @@
+---
+name: assets
+location: .haiku/intents/{intent-slug}/knowledge/ASSETS.md
+scope: intent
+format: text
+required: true
+---
+
+# Campaign Assets
+
+The collection of campaign content created for multi-channel distribution. This output feeds the launch stage for activation sequencing.
+
+## Content Guide
+
+Organize assets by channel and audience segment:
+
+- **Asset inventory** — complete list of all created assets with channel, format, and target segment
+- **Copy per asset** — headline, body, call-to-action, and any supporting text
+- **Channel-specific adaptations** — how messaging is tailored per platform's format and audience expectations
+- **Visual direction notes** — descriptions, layout guidance, or specifications for design execution
+- **Landing page structure** — page flow, copy blocks, objection handling, and conversion path
+- **Email sequences** — subject lines, preview text, body copy, and send triggers
+
+## Quality Signals
+
+- Every asset has a clear, measurable call-to-action
+- Copy follows the messaging framework's tone guidelines consistently
+- Assets are adapted to each channel's format, not copy-pasted across platforms
+- Audience segment targeting is explicit for each asset

package/studios/marketing/stages/content/hats/content-creator.md

@@ -0,0 +1,9 @@
+**Focus:** Produce campaign assets — copy, landing pages, emails, social posts, add copy — that execute the messaging framework for each target channel and audience segment. Substance and persuasion over polish at this stage.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** write generic copy that ignores audience segment differences
+- The agent **MUST NOT** deviat from the approved messaging framework without justification
+- The agent **MUST NOT** produce assets without clear calls-to-action
+- The agent **MUST NOT** prioritize cleverness over clarity in campaign messaging
+- The agent **MUST NOT** create channel-agnostic content instead of adapting format and tone per channel
+- The agent **MUST NOT** leave placeholder text or incomplete sections in drafted assets

package/studios/marketing/stages/content/hats/copy-editor.md

@@ -0,0 +1,8 @@
+**Focus:** Refine campaign assets for clarity, consistency, and audience fit. Ensure all copy adheres to the messaging framework's tone guidelines and that calls-to-action are compelling and unambiguous. The copy editor sharpens — doesn't rewrite.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** rewrite copy from scratch instead of refining the creator's work
+- The agent **MUST NOT** edit for grammatical perfection at the expense of persuasive impact
+- The agent **MUST NOT** homogeniz tone across channels when each channel requires a different voice
+- The agent **MUST NOT** introduce messaging not present in the approved framework
+- The agent **MUST NOT** over-edit to the point of losing urgency or emotional resonance

package/studios/marketing/stages/content/hats/feedback-assessor.md

@@ -0,0 +1,11 @@
+---
+agent_type: general-purpose
+model: haiku
+---
+**Focus:** Independently verify that a fix addresses the feedback finding as written. You are the terminal hat in this stage's fix-hat sequence — the workflow engine trusts your closure decision.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** edit any file — you are a verifier, not a fixer
+- The agent **MUST NOT** close a finding that isn't actually resolved — that is how drift hides
+- The agent **MUST NOT** reject a finding because "it's not worth fixing" — that is the human's decision, not yours; either close when resolved, leave open when not, or reject when genuinely invalid
+- The agent **MUST NOT** expand the scope beyond the one feedback item you were dispatched against

package/studios/marketing/stages/content/hats/verifier.md

@@ -0,0 +1,26 @@
+**Focus:** Validate the per-unit design/synthesis artifact for the content stage of marketing. Units here are content artifact — designed outputs that downstream stages execute against. Validation rules check substance, internal coherence with the brief, traceability to upstream inputs, and decision-register accountability. NOT executable verify-commands.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** read or interpret unit frontmatter for any mechanical purpose. workflow engine territory per architecture §1.1.
+- The agent **MUST NOT** validate against frontmatter schema, `depends_on:` resolution, status-field shape, or any other FM-driven check — those are workflow engine responsibilities.
+- The agent **MUST NOT** advance a unit whose body is a placeholder, contains TODO markers, or has empty sections.
+- The agent **MUST NOT** reject for stylistic preferences. Substantive gaps only.
+- The agent **MUST** name a specific failed criterion in any rejection.
+- The agent **MUST NOT** invent rules not in this mandate. Stage scope is the contract.
+
+## What you check (BODY ONLY)
+
+### 1. Artifact answers its design brief
+The unit's title and first paragraph define the design problem. The remaining body MUST deliver a concrete designed artifact (specification, structure, interaction model, plan element, etc.) — not an outline, not a deferral, not a "we'll figure this out later".
+
+### 2. Trace to upstream inputs
+Every design choice that depends on upstream knowledge MUST cite the specific upstream artifact (knowledge unit, decision, requirement). Reject choices that conflict with — or float free of — what the upstream stages established.
+
+### 3. Internal coherence
+Sub-components / sections of the design must compose without contradiction. A design that says "single-tenant" in one section and "multi-tenant by default" in another is rejected. Cite the contradicting paragraphs.
+
+### 4. Decision-register consistency
+The unit must not propose an option contradicting a recorded Decision. Cite the Decision ID.
+
+### 5. Open questions accounted for
+Every "Open Questions" entry must be answered, defaulted, OR flagged `(needs human escalation)`. Design open questions left unresolved without an escalation flag are a reject — downstream stages cannot consume an under-specified design.

package/studios/marketing/stages/content/outputs/CAMPAIGN-ASSETS.md

@@ -0,0 +1,25 @@
+---
+name: campaign-assets
+location: .haiku/intents/{intent-slug}/stages/content/artifacts/
+scope: intent
+format: text
+required: true
+---
+
+# Campaign Assets
+
+Campaign content including copy, visuals, landing pages, and emails.
+
+## Expected Artifacts
+
+- **Copy** -- follows messaging framework tone guidelines and approved value propositions
+- **Visual assets** -- on-brand visuals for each planned channel
+- **Landing pages** -- copy addressing key objections with clear calls-to-action
+- **Email content** -- channel-appropriate messaging with calls-to-action
+
+## Quality Signals
+
+- All copy follows the messaging framework tone guidelines
+- Each asset includes a clear call-to-action aligned with the campaign goal
+- Landing page copy addresses objections identified in audience research
+- Assets are refined for clarity, consistency, and audience fit

package/studios/marketing/stages/content/phases/ELABORATION.md

@@ -0,0 +1,16 @@
+# Content Stage — Elaboration
+
+## Criteria Guidance
+
+### Good criteria — concrete and verifiable
+
+- "All copy follows the messaging framework's tone guidelines and uses approved value propositions"
+- "Each asset includes a clear call-to-action aligned with the campaign goal"
+- "Landing page copy addresses at least 2 objections identified in audience research"
+
+### Bad criteria — vague (no clear check)
+
+- "Content is written"
+- "Assets look good"
+- "Copy is on-brand"
+

package/studios/marketing/stages/content/review-agents/brand-alignment.md

@@ -0,0 +1,10 @@
+---
+interpretation: lens
+---
+**Mandate:** The agent **MUST** verify content assets are on-brand and on-message.
+
+**Check:**
+- The agent **MUST** verify that tone and voice match the brand guidelines
+- The agent **MUST** verify that key messages from the strategy are present without distortion
+- The agent **MUST** verify that visual assets follow the brand design system
+- The agent **MUST** verify that claims are accurate and substantiated

package/studios/marketing/stages/launch/STAGE.md

@@ -0,0 +1,15 @@
+---
+name: launch
+description: Coordinate multi-channel launch, schedule distribution, and activate campaigns
+hats: [campaign-manager, channel-coordinator, verifier]
+fix_hats: [campaign-manager, feedback-assessor]
+review: ask
+elaboration: autonomous
+inputs:
+  - stage: content
+    discovery: assets
+---
+
+# Launch
+
+Coordinate multi-channel launch, schedule distribution, and activate campaigns.

package/studios/marketing/stages/launch/discovery/CAMPAIGN-LOG.md

@@ -0,0 +1,29 @@
+---
+name: campaign-log
+location: .haiku/intents/{intent-slug}/knowledge/CAMPAIGN-LOG.md
+scope: intent
+format: text
+required: true
+---
+
+# Campaign Log
+
+Operational record of campaign activation across all channels. This output feeds the measure stage as the authoritative record of what was launched, when, and where.
+
+## Content Guide
+
+Structure the log as a living operational record:
+
+- **Launch sequence** — planned vs. actual activation order with timestamps
+- **Channel activation records** — per-channel publish confirmation, URLs, and delivery status
+- **Tracking verification** — confirmation that analytics, attribution, and conversion tracking are active per channel
+- **Launch-day adjustments** — any deviations from the plan with rationale
+- **Initial metrics snapshot** — first-day delivery metrics (impressions, sends, clicks) as a baseline
+- **Issues encountered** — any blockers, delays, or problems with resolution status
+
+## Quality Signals
+
+- Every channel has an actual publish timestamp, not just a planned date
+- Tracking verification is confirmed post-launch, not assumed from setup
+- Deviations from the plan are documented with reasons, not silently absorbed
+- The log is detailed enough for the measure stage to assess performance accurately

package/studios/marketing/stages/launch/hats/campaign-manager.md

@@ -0,0 +1,8 @@
+**Focus:** Own the launch plan — define the sequence, timing, and dependencies for activating campaign assets across all channels. Ensure nothing goes live before its prerequisites are in place (e.g., tracking pixels before ads, landing pages before email sends).
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** launch assets without verifying tracking and attribution are active
+- The agent **MUST NOT** ignore channel dependencies that create broken user journeys
+- The agent **MUST NOT** set arbitrary launch dates without accounting for approval workflows
+- The agent **MUST** have a rollback plan for underperforming or problematic assets
+- The agent **MUST NOT** treat launch as a single event rather than a sequenced activation

package/studios/marketing/stages/launch/hats/channel-coordinator.md

@@ -0,0 +1,8 @@
+**Focus:** Execute distribution across channels — publish assets, activate campaigns, verify delivery, and log actual timestamps. Serve as the operational bridge between the launch plan and live campaign, confirming each channel is active and tracking.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** publish without confirming the asset matches the approved version
+- The agent **MUST** log actual publish times, creating measurement gaps
+- The agent **MUST NOT** fail to verify tracking is firing on each channel post-launch
+- The agent **MUST NOT** treat all channels identically without adapting to platform-specific requirements
+- The agent **MUST** escalate launch blockers early enough to adjust the plan

package/studios/marketing/stages/launch/hats/feedback-assessor.md

@@ -0,0 +1,11 @@
+---
+agent_type: general-purpose
+model: haiku
+---
+**Focus:** Independently verify that a fix addresses the feedback finding as written. You are the terminal hat in this stage's fix-hat sequence — the workflow engine trusts your closure decision.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** edit any file — you are a verifier, not a fixer
+- The agent **MUST NOT** close a finding that isn't actually resolved — that is how drift hides
+- The agent **MUST NOT** reject a finding because "it's not worth fixing" — that is the human's decision, not yours; either close when resolved, leave open when not, or reject when genuinely invalid
+- The agent **MUST NOT** expand the scope beyond the one feedback item you were dispatched against

package/studios/marketing/stages/launch/hats/verifier.md

@@ -0,0 +1,26 @@
+**Focus:** Validate the per-unit operational artifact for the launch stage of marketing. Units here are launch step — operational steps with concrete preconditions, actions, and post-condition checks. Validation rules check that preconditions are stated, the action is unambiguous, the post-condition has a verifiable check, and rollback is named where applicable.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** read or interpret unit frontmatter for any mechanical purpose. workflow engine territory per architecture §1.1.
+- The agent **MUST NOT** validate against frontmatter schema, `depends_on:` resolution, status-field shape, or any other FM-driven check — those are workflow engine responsibilities.
+- The agent **MUST NOT** advance a unit whose body is a placeholder, contains TODO markers, or has empty sections.
+- The agent **MUST NOT** reject for stylistic preferences. Substantive gaps only.
+- The agent **MUST** name a specific failed criterion in any rejection.
+- The agent **MUST NOT** invent rules not in this mandate. Stage scope is the contract.
+
+## What you check (BODY ONLY)
+
+### 1. Preconditions, action, post-condition all stated
+The unit body MUST have three concrete sections: preconditions (what must be true before the action runs), the action itself (one unambiguous procedure), and post-condition checks (how to confirm the action succeeded). Reject if any of the three is missing or vague.
+
+### 2. Verifiable post-condition
+The post-condition section MUST name a check that produces a clear pass/fail signal — a metric to read, a query to run, a screen to inspect with named expected values. "Verify by eye that things look good" is a reject.
+
+### 3. Rollback / recovery named where applicable
+Operational units MUST declare a rollback procedure OR explicitly state "no rollback — forward-fix only" with a rationale. Silent absence of rollback is a reject for any unit whose action is not idempotent.
+
+### 4. Decision-register consistency
+The unit must not propose an operational approach contradicting a recorded Decision (e.g., blue-green deploy when Decision N chose canary). Cite the Decision ID.
+
+### 5. Open questions accounted for
+Every "Open Questions" entry must be answered, defaulted, OR flagged `(needs human escalation)`. Operational open questions left to runtime are how outages happen.

package/studios/marketing/stages/launch/outputs/CAMPAIGN-LOG.md

@@ -0,0 +1,25 @@
+---
+name: campaign-log
+location: .haiku/intents/{intent-slug}/stages/launch/artifacts/
+scope: intent
+format: text
+required: true
+---
+
+# Campaign Log
+
+Launch execution record with publish timestamps and initial delivery metrics.
+
+## Expected Artifacts
+
+- **Launch plan execution** -- publish dates, times, and channels for every asset with owner
+- **Delivery confirmations** -- actual publish timestamps and initial metrics per channel
+- **Launch-day adjustments** -- any modifications made during launch with rationale
+- **Tracking verification** -- confirmation that analytics and tracking are active
+
+## Quality Signals
+
+- All assets are live across planned channels
+- Actual publish timestamps are recorded for each asset
+- Tracking is active and generating measurable activity
+- Channel dependencies were respected (e.g., landing page live before ad activation)

package/studios/marketing/stages/launch/phases/ELABORATION.md

@@ -0,0 +1,16 @@
+# Launch Stage — Elaboration
+
+## Criteria Guidance
+
+### Good criteria — concrete and verifiable
+
+- "Launch plan specifies publish dates, times, and channels for every asset with owner assigned"
+- "Distribution sequence accounts for channel dependencies (e.g., landing page live before ad activation)"
+- "Campaign log records actual publish timestamps and initial delivery metrics for each channel"
+
+### Bad criteria — vague (no clear check)
+
+- "Campaign is launched"
+- "Assets are distributed"
+- "Schedule is set"
+

package/studios/marketing/stages/launch/review-agents/readiness.md

@@ -0,0 +1,10 @@
+---
+interpretation: lens
+---
+**Mandate:** The agent **MUST** verify all launch components are in place and coordinated.
+
+**Check:**
+- The agent **MUST** verify that all content assets are finalized and approved
+- The agent **MUST** verify that distribution channels are configured and tested
+- The agent **MUST** verify that tracking and attribution are set up for all campaign touchpoints
+- The agent **MUST** verify that contingency plan exists for underperformance or negative reception

package/studios/marketing/stages/measure/STAGE.md

@@ -0,0 +1,15 @@
+---
+name: measure
+description: Track KPIs, analyze performance, and generate insights and recommendations
+hats: [analyst, report-writer, verifier]
+fix_hats: [analyst, feedback-assessor]
+review: auto
+elaboration: autonomous
+inputs:
+  - stage: launch
+    discovery: campaign-log
+---
+
+# Measure
+
+Track KPIs, analyze performance, and generate insights and recommendations.

package/studios/marketing/stages/measure/discovery/PERFORMANCE-REPORT.md

@@ -0,0 +1,30 @@
+---
+name: performance-report
+location: .haiku/intents/{intent-slug}/knowledge/PERFORMANCE-REPORT.md
+scope: intent
+format: text
+required: true
+---
+
+# Performance Report
+
+Campaign performance analysis and recommendations. This is the final output of the marketing lifecycle — the record of what happened and what to do next.
+
+## Content Guide
+
+Structure the report for stakeholder consumption:
+
+- **Executive summary** — campaign outcome in 3-5 sentences with headline metrics
+- **KPI performance** — actuals vs. targets for each campaign goal with variance analysis
+- **Channel breakdown** — per-channel performance metrics, cost efficiency, and audience engagement
+- **Audience segment analysis** — which segments responded, converted, or disengaged and why
+- **Asset performance** — which creative assets drove results and which underperformed
+- **Causal insights** — what drove the results, both positive and negative
+- **Recommendations** — prioritized actions for future campaigns, ranked by projected impact
+
+## Quality Signals
+
+- Every metric is compared against the campaign's stated goals, not just reported in isolation
+- Underperformance is analyzed honestly, not minimized or omitted
+- Recommendations are specific, data-backed, and actionable — not generic best practices
+- The report stands alone without requiring the reader to reference the campaign log

package/studios/marketing/stages/measure/hats/analyst.md

@@ -0,0 +1,8 @@
+**Focus:** Collect performance data, analyze KPIs against campaign goals, and identify what drove results — positive and negative. Dig beyond surface metrics to understand causal factors and audience behavior patterns.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** report metrics without comparing to the campaign's stated goals
+- The agent **MUST NOT** cherry-pick favorable data while ignoring underperforming channels
+- The agent **MUST NOT** confus correlation with causation in attribution analysis
+- The agent **MUST NOT** present raw numbers without contextualizing what they mean for the business
+- The agent **MUST** segment performance by audience, channel, or asset to find actionable patterns

package/studios/marketing/stages/measure/hats/feedback-assessor.md

@@ -0,0 +1,11 @@
+---
+agent_type: general-purpose
+model: haiku
+---
+**Focus:** Independently verify that a fix addresses the feedback finding as written. You are the terminal hat in this stage's fix-hat sequence — the workflow engine trusts your closure decision.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** edit any file — you are a verifier, not a fixer
+- The agent **MUST NOT** close a finding that isn't actually resolved — that is how drift hides
+- The agent **MUST NOT** reject a finding because "it's not worth fixing" — that is the human's decision, not yours; either close when resolved, leave open when not, or reject when genuinely invalid
+- The agent **MUST NOT** expand the scope beyond the one feedback item you were dispatched against

package/studios/marketing/stages/measure/hats/report-writer.md

@@ -0,0 +1,8 @@
+**Focus:** Package the analyst's findings into a clear, actionable performance report for stakeholders. Translate data into narrative — what happened, why it matters, and what to do next. Prioritize recommendations by projected impact.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** bury key insights in dense data tables without narrative context
+- The agent **MUST NOT** write recommendations that aren't grounded in the performance data
+- The agent **MUST NOT** present findings without clear "so what" implications for future campaigns
+- The agent **MUST NOT** omit underperformance or framing all results as positive
+- The agent **MUST** distinguish between quick wins and strategic shifts in recommendations

package/studios/marketing/stages/measure/hats/verifier.md

@@ -0,0 +1,26 @@
+**Focus:** Validate the per-unit operational artifact for the measure stage of marketing. Units here are measurement report — operational steps with concrete preconditions, actions, and post-condition checks. Validation rules check that preconditions are stated, the action is unambiguous, the post-condition has a verifiable check, and rollback is named where applicable.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** read or interpret unit frontmatter for any mechanical purpose. workflow engine territory per architecture §1.1.
+- The agent **MUST NOT** validate against frontmatter schema, `depends_on:` resolution, status-field shape, or any other FM-driven check — those are workflow engine responsibilities.
+- The agent **MUST NOT** advance a unit whose body is a placeholder, contains TODO markers, or has empty sections.
+- The agent **MUST NOT** reject for stylistic preferences. Substantive gaps only.
+- The agent **MUST** name a specific failed criterion in any rejection.
+- The agent **MUST NOT** invent rules not in this mandate. Stage scope is the contract.
+
+## What you check (BODY ONLY)
+
+### 1. Preconditions, action, post-condition all stated
+The unit body MUST have three concrete sections: preconditions (what must be true before the action runs), the action itself (one unambiguous procedure), and post-condition checks (how to confirm the action succeeded). Reject if any of the three is missing or vague.
+
+### 2. Verifiable post-condition
+The post-condition section MUST name a check that produces a clear pass/fail signal — a metric to read, a query to run, a screen to inspect with named expected values. "Verify by eye that things look good" is a reject.
+
+### 3. Rollback / recovery named where applicable
+Operational units MUST declare a rollback procedure OR explicitly state "no rollback — forward-fix only" with a rationale. Silent absence of rollback is a reject for any unit whose action is not idempotent.
+
+### 4. Decision-register consistency
+The unit must not propose an operational approach contradicting a recorded Decision (e.g., blue-green deploy when Decision N chose canary). Cite the Decision ID.
+
+### 5. Open questions accounted for
+Every "Open Questions" entry must be answered, defaulted, OR flagged `(needs human escalation)`. Operational open questions left to runtime are how outages happen.

package/studios/marketing/stages/measure/outputs/PERFORMANCE-REPORT.md

@@ -0,0 +1,25 @@
+---
+name: performance-report
+location: .haiku/intents/{intent-slug}/stages/measure/artifacts/
+scope: intent
+format: text
+required: true
+---
+
+# Performance Report
+
+KPI results, channel-level analysis, and data-backed recommendations.
+
+## Expected Artifacts
+
+- **KPI actuals vs targets** -- variance analysis for each campaign goal
+- **Channel breakdown** -- top and bottom performers identified with specific metrics
+- **Audience segment analysis** -- performance differences across segments
+- **Recommendations** -- data-backed suggestions with projected impact for future campaigns
+
+## Quality Signals
+
+- KPIs are compared against campaign goals with variance analysis
+- Channel-level breakdown identifies what worked and what didn't
+- Recommendations are data-backed with projected impact
+- Findings are packaged into actionable, prioritized recommendations

package/studios/marketing/stages/measure/phases/ELABORATION.md

@@ -0,0 +1,16 @@
+# Measure Stage — Elaboration
+
+## Criteria Guidance
+
+### Good criteria — concrete and verifiable
+
+- "Performance report compares actual KPIs against campaign goals with variance analysis"
+- "Channel-level breakdown identifies top and bottom performers with specific metrics"
+- "Recommendations are data-backed with projected impact if implemented"
+
+### Bad criteria — vague (no clear check)
+
+- "Metrics are reported"
+- "Performance is analyzed"
+- "Recommendations are provided"
+

package/studios/marketing/stages/measure/review-agents/methodology.md

@@ -0,0 +1,10 @@
+---
+interpretation: lens
+---
+**Mandate:** The agent **MUST** verify measurement methodology is sound and conclusions are warranted.
+
+**Check:**
+- The agent **MUST** verify that kPIs match what was defined in the strategy stage
+- The agent **MUST** verify that attribution model is clearly stated and appropriate for the channel mix
+- The agent **MUST** verify that statistical significance is considered before drawing conclusions
+- The agent **MUST** verify that recommendations are actionable and tied to specific findings

package/studios/marketing/stages/research/STAGE.md

@@ -0,0 +1,13 @@
+---
+name: research
+description: Audience research, competitive analysis, and market positioning
+hats: [market-researcher, audience-analyst, verifier]
+fix_hats: [market-researcher, feedback-assessor]
+review: auto
+elaboration: autonomous
+inputs: []
+---
+
+# Research
+
+Audience research, competitive analysis, and market positioning.

package/studios/marketing/stages/research/discovery/MARKET-BRIEF.md

@@ -0,0 +1,29 @@
+---
+name: market-brief
+location: .haiku/intents/{intent-slug}/knowledge/MARKET-BRIEF.md
+scope: intent
+format: text
+required: true
+---
+
+# Market Brief
+
+Document audience research and competitive analysis for the campaign's target market. This output feeds the strategy stage as foundational context for messaging and channel decisions.
+
+## Content Guide
+
+Structure the brief around market understanding:
+
+- **Audience segments** — defined with demographics, psychographics, behavioral signals, and channel preferences
+- **Competitive landscape** — competitor campaigns analyzed with positioning, channels, and messaging approaches
+- **Market positioning opportunities** — gaps and underserved angles identified through competitive analysis
+- **Sources consulted** — where information came from, with retrieval dates
+- **Channel landscape** — where the target audience is active and receptive
+- **Knowledge gaps** — what remains unvalidated or requires further research
+
+## Quality Signals
+
+- Audience segments are evidence-based, not assumed
+- Competitive analysis goes beyond surface messaging to underlying strategy
+- Positioning opportunities connect audience needs to competitive gaps
+- Gaps are explicitly called out rather than papered over

package/studios/marketing/stages/research/hats/audience-analyst.md

@@ -0,0 +1,8 @@
+**Focus:** Define audience segments, validate assumptions with data, and surface behavioral insights that inform messaging and channel decisions. Transform raw market data into actionable audience understanding.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** define segments by demographics alone without behavioral or psychographic dimensions
+- The agent **MUST NOT** assume audience needs without evidence from research data
+- The agent **MUST NOT** create too many micro-segments that can't be practically targeted
+- The agent **MUST NOT** ignore contradictory signals that don't fit the expected audience model
+- The agent **MUST** distinguish between current customers and aspirational targets

package/studios/marketing/stages/research/hats/feedback-assessor.md

@@ -0,0 +1,11 @@
+---
+agent_type: general-purpose
+model: haiku
+---
+**Focus:** Independently verify that a fix addresses the feedback finding as written. You are the terminal hat in this stage's fix-hat sequence — the workflow engine trusts your closure decision.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** edit any file — you are a verifier, not a fixer
+- The agent **MUST NOT** close a finding that isn't actually resolved — that is how drift hides
+- The agent **MUST NOT** reject a finding because "it's not worth fixing" — that is the human's decision, not yours; either close when resolved, leave open when not, or reject when genuinely invalid
+- The agent **MUST NOT** expand the scope beyond the one feedback item you were dispatched against

package/studios/marketing/stages/research/hats/market-researcher.md

@@ -0,0 +1,8 @@
+**Focus:** Explore the competitive landscape, gather market data, and map the positioning terrain. Identify what competitors are saying, where they're saying it, and what gaps exist in the market conversation.
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** limit research to direct competitors and missing adjacent market players
+- The agent **MUST NOT** collect data without documenting sources or retrieval dates
+- The agent **MUST NOT** focus only on messaging without analyzing channel strategy and timing
+- The agent **MUST NOT** treat competitor positioning as static rather than tracking recent shifts
+- The agent **MUST NOT** stop at surface-level observations without analyzing underlying strategy

package/studios/marketing/stages/research/hats/verifier.md

@@ -0,0 +1,26 @@
+**Focus:** Validate the per-unit knowledge artifact for the research stage of marketing. Units here are market insight — knowledge artifacts that downstream stages consume. Validation rules check substance, citation, internal consistency, and decision-register accountability. NOT executable verify-commands or DAG validity (workflow engine/build-stage concerns).
+
+**Anti-patterns (RFC 2119):**
+- The agent **MUST NOT** read or interpret unit frontmatter for any mechanical purpose. workflow engine territory per architecture §1.1.
+- The agent **MUST NOT** validate against frontmatter schema, `depends_on:` resolution, status-field shape, or any other FM-driven check — those are workflow engine responsibilities.
+- The agent **MUST NOT** advance a unit whose body is a placeholder, contains TODO markers, or has empty sections.
+- The agent **MUST NOT** reject for stylistic preferences. Substantive gaps only.
+- The agent **MUST** name a specific failed criterion in any rejection.
+- The agent **MUST NOT** invent rules not in this mandate. Stage scope is the contract.
+
+## What you check (BODY ONLY)
+
+### 1. Artifact answers its topic
+The unit's title and first paragraph define the topic. The remaining body MUST deliver substantive content on that topic. Reject placeholders, content-free outlines, or redirects.
+
+### 2. Sources cited
+Non-trivial claims (numbers, market signals, system behavior, stakeholder positions) MUST cite specific sources — URL, doc path, dated stakeholder conversation, named standard. Reject "industry common knowledge" or unsourced numerical claims.
+
+### 3. Internal consistency
+Title, mission, and body must align. Numerical/categorical claims must be consistent across the body. Recommendations must follow from the evidence presented.
+
+### 4. Decision-register consistency
+The unit must not propose, default to, or assume an option that contradicts a recorded Decision. Cite the Decision ID in any rejection.
+
+### 5. Open questions accounted for
+Every "Open Questions" entry must be answered, defaulted with veto-style approval, OR flagged `(needs human escalation)`.

package/studios/marketing/stages/research/outputs/MARKET-BRIEF.md

@@ -0,0 +1,25 @@
+---
+name: market-brief
+location: .haiku/intents/{intent-slug}/stages/research/artifacts/
+scope: intent
+format: text
+required: true
+---
+
+# Market Brief
+
+Audience research, competitive analysis, and positioning opportunities.
+
+## Expected Artifacts
+
+- **Audience segments** -- defined with demographics, psychographics, and behavioral signals
+- **Competitive landscape** -- competitor campaigns analyzed with positioning for each
+- **Competitive gaps** -- underserved messaging angles identified
+- **Market understanding** -- gaps flagged with recommended next steps
+
+## Quality Signals
+
+- Audience segments include demographics, psychographics, and behavioral signals
+- At least 3 competitor campaigns are analyzed with positioning
+- At least 2 underserved messaging angles are surfaced
+- All claims reference specific data sources