Brainforge Knowledge

linear-template

4 min read

Linear Template: Edge-to-Activation

Purpose: Starter milestones and issues for Edge-to-Activation engagements. Copy into the client’s Linear project at kickoff, or run the Edge-to-Activation Tickets Cursor skill (.cursor/skills/edge-to-activation-tickets/SKILL.md) to create issues with dependencies via MCP. Canonical Linear project name: Data — Edge-to-Activation (Canonical) (pattern per service README) Service line: Data Last updated: 2026-04-08

How to Use

  1. In Linear, open (or create) the client’s project: [Client Name] — Edge-to-Activation
  2. Set the Initiative to Data (and/or offering initiative such as Edge-to-Activation - Service per linear-views.md if your workspace uses it)
  3. Create Milestones for Phase 0, Phase 1, Phase 2 (if in scope)
  4. Create issues below (each is a full issue — not subtasks). Use blockedBy in dependency order
  5. Prefer labels: Phase 0, Phase 1, Phase 2, Edge-to-Activation; add Retainer on Phase 2 when applicable
  6. Align descriptions with linear-ticket-generation-from-transcript.md and linear-mcp-ticket-standards (team, project, initiatives)

Project Setup

Linear project name: [Client] — Edge-to-Activation
Initiative: Data (+ offering linkage as required by your workspace)
Team: Client delivery team (or Data — per engagement)
Labels: edge-to-activation (offering), Phase 0 / Phase 1 / Phase 2, data-platform or service-line labels per linear-cleanup-taxonomy.md

Milestone: Phase 0 — Signal Recovery Audit

Deploy Edge capture; baseline signals; discrepancy report; pilot scope. Typical duration: ~1 week.

Issue: Phase 0: Signal Recovery Audit — [Client]

Full issue body template and acceptance criteria: see .cursor/skills/edge-to-activation-tickets/SKILL.md (Phase 0 ticket) and SOP Phase 0 checklist.

Checklist (mirror acceptance criteria):

  • CDN/Edge capture deployed in parallel with existing stack
  • No removal of pixels or server-to-server tracking
  • Baseline traffic and conversion signals captured at Edge
  • Discrepancy report (client vs Edge) delivered
  • Attribution gap quantified by source/channel
  • Client sign-off on findings and pilot scope

Milestone deliverable: Discrepancy report + agreed Phase 1 scope

Milestone: Phase 1 — Pilot Implementation

Modular Edge implementation, warehouse schema, phased testing, documentation — typical duration ~4–6 weeks.

Create four issues in order (each blockedBy the previous):

OrderTitle
1Phase 1: Setup Cloudflare Workers — [Client]
2Phase 1: Configure BigQuery Schema — [Client]
3Phase 1: Implement Testing Framework — [Client]
4Phase 1: Documentation and Handoff — [Client]

Warehouse note: Title says BigQuery because that is the reference implementation in the Implementation Playbook. Rename to Snowflake (or other) in the issue title/body when the client warehouse is not BigQuery — patterns are the same (dataset/location, service role, tables, identifier bridging).

Phase 1 — issue 1 (Edge) checklist (summary):

  • Edge access and deploy rights verified; existing Workers/routes audited (chain or merge plan if needed)
  • Worker (or equivalent) deployed; events firing; cost validated
  • No material page-load regression

Phase 1 — issue 2 (Warehouse) checklist (summary):

  • Service account / role with insert + job permissions
  • Events + sessions (or agreed) tables; partitioning; identifier columns for reconciliation
  • Successful inserts from Edge path

Phase 1 — issue 3 (Testing) checklist (summary):

  • Dev → single-page → subdirectory → full pilot rollout executed without compressing phases
  • Client sign-off on testing results

Phase 1 — issue 4 (Docs) checklist (summary):

  • Attribution validation / discrepancy artifacts delivered
  • Runbooks and enablement complete; Phase 1 sign-off

Milestone deliverable: Working pilot + Phase 1 acceptance

Milestone: Phase 2 — Rollout & Maintenance (retainer)

Ongoing expansion and maintenance — commercial terms in retainer SOW.

Issue: Phase 2: Rollout & Maintenance — [Client]

Labels: Phase 2, Edge-to-Activation, Retainer (if used)

Checklist (summary — see skill + SOP Phase 2):

  • Channel rollout backlog agreed and sequenced
  • Ongoing monitoring and discrepancy process
  • Runbooks updated as publishers/stack change
  • Reporting integrated into client rhythms (dashboards, GTM reviews) as scoped

Milestone deliverable: Sustained operating model per retainer SOW

Automation

Issue Labels Reference

LabelWhen to use
Phase 0 / Phase 1 / Phase 2Phase alignment
Edge-to-ActivationAll issues for this offering
edge-to-activationOffering slug (if separate from display name in your workspace)
RetainerPhase 2 ongoing work
client-dependencyBlocked on client action
gateMust complete before next phase

Engagement Retro Checklist

After each engagement:

Graph View