This is the Cascade Execution Guide for the build of the Webgold Master GTM — the parent doctrine that establishes the foundation, the gate, and the filter through which every downstream Go-to-Market motion at Webgold must flow. It governs WG-21 (Strategic Marketing & DX Authority), WG-25 (the Webgold website), WG-14.3 (Service Architecture), WG-21.5 (Events), WG-21.6 (Social Presence Activation), and any future group-level GTMs for Buzz Media (BC-22) and Buzz Experiences (BX-23).
The Master GTM is not a marketing plan. It is a holistic strategy for the brand, the business and the authority of Webgold Designs Ltd.
Without a parent doctrine that all sub-GTMs inherit from, motions collide, contradict, and dilute. The white space identified in the April 2026 competitor audit — named expert + T&T-specific opinion + attributed outcomes + active publishing + owned audience — is unclaimed precisely because no firm in the market has built a coherent system to occupy it. The Master GTM is that system. It is also the gate that validates the in-flight WG-25 staging copy before public launch on April 30, and the filter that stays live week-on-week through the September 15 full launch.
Webgold is building a reef in clear water. The blue ocean — the white space the audit identified — is empty for a reason. Most prospects in our target market are still fishing the traditional grounds because that is where the food is. To bring the right fish to clear water, we have to build a healthy ecosystem first: structure for them to feed in and shelter in, the smaller bait that they feed on, the predictable conditions that signal safety and abundance. We attract their customers (the bait) into the digital environment, and the prospects we want follow.
The Reef is what The Beacon casts light on. It sits alongside the existing language of the Vehicle (Pipes / Engine / Shield / Beacon), Riverlets, Warfare, and Symphony. Reef is the governing metaphor of the Master GTM specifically; the others retain their roles. The Reef Team Briefing (Phase 7) makes this explicit so the team holds the metaphor stack cohesively.
Translation tax is the term. When a Caribbean business hires Deloitte, WebFX, or a US agency, they pay for the work and they pay the cost of explaining their market, their customers, their constraints, and their cultural context, every time. We absorb that. This sentence is the spine of every channel, every campaign, every piece of content. The Filter checks against it.
The Reef is a five-year construction project (2026 → 2031). Phase 0 of the Reef is May 2026 → September 15 2026: Webgold builds in-environment authority while the website ships in MVP form, then activates one service line per fortnight across seven sprints. The Master GTM phases bind to the WG-25 sprint cadence so that timeline shifts in either programme do not desync the marketing motion from the website surface.
One Spine — read-once doctrine — plus three operating instruments. The Gate runs quarterly for launch posture and weekly for tempo. The Filter runs weekly: a one-page card any motion must pass before it ships, with authority over the WG-25 staging copy. The Harmony Calendar is the single 13-week rolling view all motions write into.
The Filter validates the mix. The Gate adjusts the tempo.
The Master GTM Phase Architecture binds 1:1 to this calendar. If a sprint slips, the GTM motion for that service line slips with it.
| Window | Service line activated | GTM motion | External proof moment |
|---|---|---|---|
| Apr 30 | WG-25 MVP go-live (consultation-only) | Pre-MVP authority warm-up · Filter audit of WG-25 staging copy · Founder voice prep · One named-author piece test-drop | — |
| Sprint 1 · May 1–14 | Support · SMP/EMP checkout · Blog go live · Team page parallel sprint | Support authority push · First proof harvest · First four named-author pieces · Newsletter formally launched | Blog/Resources go live |
| Sprint 2 · May 15–28 | Commerce · CommUnity event page + registration live | Commerce authority piece · CommUnity event channel ramp begins · First gated lead-magnet · WhatsApp activated | CommUnity registration live |
| Sprint 3 · May 29–Jun 11 | Development | Development authority push · Build-in-public LinkedIn cadence formalised · First named partnership outreach | — |
| Sprint 4 · Jun 12–25 | Engagement + Products + Growth · CommUnity Jul 2 | Tri-pillar push · CommUnity event week ignition · First case study with named client + outcome metric · Email nurture sequence #1 live | CommUnity Jul 2 (PRos & COMMS) |
| Sprint 5 · Jun 26–Jul 9 | Content + Identity | Content & Identity authority push · Second gated research asset (T&T-specific) · Speaker positioning Q3/Q4 booked | — |
| Sprint 6 · Jul 10–23 | Intelligence | Intelligence authority push (the AI angle) · Anchor opinion piece on AI for Caribbean SMEs published | — |
| Sprint 7 · Jul 24–Aug 6 | DX / Transformation (flagship) | DX Authority full activation · Anchor case study · Gated 4D framework asset · Named-expert thought leadership campaign | DX Authority headline week |
| Buffer · Aug 7–Sep 14 | Hardening, optimisation, proof harvest | Channel optimisation · Second proof harvest · Pre-launch tempo build · Final Filter sweep · Gate quarterly review | — |
| Sep 15 | WG-25 full public launch | Master GTM transitions from low-volume authority to full-volume distributed posture · Paid media activation begins | Full launch |
| Field | Status |
|---|---|
| Subject | Stephan De Roche — CEO, Webgold |
| Brief governed by skill | founder-positioning-brief.skill (loaded at Infrastructure/Skills/) |
| Expected delivery | Friday 8 May 2026 |
| Phase impacted | Phase 1 — The Spine, Section 8 (Authorship Architecture) |
| Blocking | No — Spine ships v1.0 with placeholder. v1.1 cuts on FPB landing. |
| Use | Founder voice attributes, signature author bio, founder positioning statement, content arcs, opinion territory, signature opinion piece(s), bylined cadence. |
| Cross-impacts | WG-21 content pipeline rework (Phase 6 Filter Application 2 incorporates founder voice); Reef Briefing Deck (Phase 7); Channel Matrix (Phase 3, named-owner column for founder-attributed motions). |
| # | Question raised | Ruling | Lands in |
|---|---|---|---|
| DT-1 | Should Foundation, Gate, and Filter live in one document? | No. One Spine + three operating instruments. Three rhythms. | Cascade architecture; Phase 1, 5, 6 |
| DT-2 | Should the Gate also police harmony / tempo? | Yes. Two rhythms — Launch Posture (quarterly) + Tempo (weekly). | Phase 5; Tempo Today tab |
| DT-3 | Governing metaphor — Reef? | Yes. Sits alongside existing Vehicle / Beacon / Riverlets / Warfare / Symphony. | Spine §1; Phase 7 Reef Briefing |
| DT-4 | Voice / guardrail conflict — what wins? | The GTM is the final decider. The Filter strips banned vocabulary including from WG-25 staging copy. | DEC-MGTM-001 RESOLVED; Phase 6 Application 1 |
| DT-5 | Is Gem a founder? | No. Gem is Programme Architect / employee. Stephan is the only founder voice. | Standing rule #12; FPB slot |
| DT-6 | Timeline strategy — fixed dates or sprint-bound? | Sprint-bound. Master GTM Phase Architecture binds 1:1 to WG-25 sprint cadence. | Phase 2 — sprint binding table |
| DT-7 | Harmony — structural mechanism? | Yes. The Harmony Calendar — 13-week rolling, all motions write into it. | Phase 4 — Harmony Calendar |
| DT-8 | The fundamental sale? | Translation tax. Spine §2 — load-bearing sentence. | Spine §2; DEC-MGTM-003 |
| DT-9 | The five gaps — embed in Spine? | Yes. Numbered mandatory sections. | Spine §5, §6, §9, §10, §11 |
| DT-10 | Filter — produced or applied? | Applied immediately. Two first applications baked into Phase 6. | Phase 6 — Filter card + audits |
| DT-11 | Reef Team Briefing necessary? | Yes, as a phase deliverable. | Phase 7 — Reef Briefing |
| DT-12 | Decision Trail — capture pathway? | Yes. This appendix. | Appendix A |
| DT-13 | CMIF inheritance — explicit? | Yes. The Spine declares inputs and outputs. CMIF version-bumps in Phase 8. | Spine cross-refs; Phase 8.1 |
| DT-14 | FPB — block or slot? | Slot. Spine v1.0 ships with placeholder; v1.1 cuts on FPB delivery. | FPB slot; DEC-MGTM-002 |
| DT-15 | Eight-phase structure — final? | Yes. Old 7+8 merged into new Phase 8. New Phase 7 = Reef Team Briefing. | Build tab |
| DT-16 | Cascade Execution Guide — docx only or HTML? | Both. .docx is the canonical record; .html is the working tool (this document). | Phase 0 deliverables |
| DT-17 | HTML — static or interactive? | Interactive working tool. Persistent phase tracking, Filter Tester, editable Decision Log, weekly Tempo dial. | This document (rebuild after first pass) |
| DT-18 | Build ownership — who? | Gem alone (Claude as AI collaborator). Stephan rules on founder voice and posture-shift decisions; he does not build. No other team members assigned to this cascade. | Standing rule #12; ownership across all phase cards |
| DT-19 | Reef premise — passive reception or active invitation? | Active invitation. The Reef in formation IS the invitation — build-as-attraction, not build-then-attract. Events are the primary activation mechanism through 2026, governed by the Webgold Events Programme Warfare Doctrine and WG-21.5. Spine §1 sub-section "The Reef is built in public" + Spine §4 sub-section "Events as activation surface" make this explicit. §7 (Channel Hierarchy) and §10 (Kill List) reflect in v1.0. | Spine v0.5b §1 + §4; cross-refs to WG-21.5 and Warfare Doctrine; this document Phase 1 step 1.1 description updated |
| DT-20 | Mechanisations — concentrated in one phase or added along the way? | Added along the way. Phase 4 includes the Content Portfolio Ratio Validator (mechanised vs §6 ratios). Phase 5 includes the Tempo Gate dial (already mechanised). Phase 6 includes the Filter Tester (already mechanised). Phase 8 adds the Phase-State Tool (date → operational state lookup). Future post-cascade WG-21 work adds the Proof Factory pipeline tracker and the Economy projection model. The Spine itself stays prose-canonical; doctrine is read, not run. Mechanisations operationalise the doctrine as decision-support, never decision-replacement. | Phase 4, 5, 6, 8 deliverables updated; Phase 8.9 added |
| DT-21 | Spine v1.0 — text-only or augmented with infographics? | Augmented with five high-leverage visuals embedded in the HTML companion (Spine docx remains prose-canonical). The five: Reef ecosystem (§1), five-year construction timeline (§1), demand-architecture displacement diagram (§5), four positions × channels activation matrix (§4), Economy J-curve (§11). Built brand-compliant in inline SVG. The doctrine still tells the team what to do; the infographics make it land faster on a new reader. | Spine v1.0 HTML companion — 5 inline SVG infographics + activation matrix table |
| DT-22 | Marketing voices — who actually carries the marketing function? | Earlier drafts attributed "Marketing voices: Leah, Megan" — both wrong. Leah White is EA to the CEO (not marketing). Megan Gill is Events & Activations Lead (cross-entity, not marketing). Actual Webgold marketing layer per Org Structure: Gem David (Marketing Lead — Webgold Authority & Beacon, dual capacity until Yohance elevates) · Yohance Quamina-Boyce (Visual & Brand Strategist, research-integrative, on confirmed elevation pathway to Marketing Lead) · Anyah McNeill (Copy & Messaging Strategist, conditional, research-integrative) · Kevyn (Marketing Assistant, 40% retainer 16 hrs/week through end-2026 due to nursing programme). | Spine §4 + §8; Phase Architecture sprint cards; Channel Matrix Named Owner cells; Harmony Calendar seed + HTML; Team Intro deck slides 7 + 11 — all need correction. See Appendix C — Team Reference for canonical roster. |
| DT-23 | Megan Gill — what is her actual role? | Events & Activations Lead — ORG-level cross-entity role covering all three entities (Webgold authority events, Buzz Media community activations, Buzz Experiences travel events). Reports to Operations Architect. Megan is NOT in the marketing function. Event-attached motions (CommUnity Jul 2, workshops, executive roundtables, Caribbean Digital Awards, Caribbean Digital Transformation Conference) attribute to Megan as Events Lead, not collapsed into "marketing function." | Event-related references across Spine, Phase Architecture, Harmony Calendar — Megan named in event cards rather than collapsed into marketing. |
| DT-24 | How does the Master GTM produce content operationally? — the Nucleus integration | Content production flows through Nucleus CON blocks: CON-001 Content Strategy (60% human touch — pillars/personas; Anyah + Yohance contribute research-integrative) · CON-002 Editorial Calendar (30% human touch — central orchestration pipeline that receives motions from the Master GTM Harmony Calendar and routes production tasks via Fulfillment Engine INFRA-011) · CON-003 Core Visuals (50% human touch — Yohance owns; multi-platform optimisation automated) · CON-004 Video Shorts · CON-005 Lead Magnet · CON-006 Social Scheduling (20% human touch — automated distribution across LinkedIn/Instagram/X/Facebook/YouTube). The Master GTM Harmony Calendar (Phase 4) is the strategic register; CON-002 is the operational receiver. WG-21.6 (closes April 30) produces the 83-template library that feeds CON-003 + CON-006. Day-to-day social cadence is mostly automated once CON-002 + CON-003 are populated. | Harmony Calendar HTML to add Nucleus integration note; Spine §6 + §7 to reference Nucleus production chain; Phase 4 setup checklist to include CON-002/003/006 readiness gates. |
| DT-25 | How does the Master GTM connect to the PCC? | The Master GTM is NOT hosted inside the PCC. The PCC is the Project Control Centre — its purpose is project orchestration (tasks, HITL gates, dependencies, team availability, sprint progress, programme overview). The Master GTM lives at ops.webgold.co as its own set of surfaced pages: Spine, Phase Architecture, Channel Matrix view, Harmony Calendar view, Filter Card, Operating Architecture (companion). The PCC integration is two-fold: (1) the PCC side panel includes a Master GTM section with hyperlinks/iframe-embeds out to those surfaced pages — same surfacing pattern as the Ecosystem Map, the Operations Hub mockup, the Nucleus Block Map; (2) the PCC reads Airtable data tables that include the Harmony Calendar motion table and the Gate Register table because some Calendar motions become PCC tasks (when they require team allocation, HITL gates, or dependency tracking). PCC is consuming the GTM data, not hosting the GTM. Mental model: PCC controls projects; ops.webgold.co publishes the GTM; Airtable holds the shared data. | Phase 8 — Cascade Integration: PCC side-panel Master GTM section build; Operating Architecture companion clarifies the surface model; Cloudflare Pages deploy spec includes Master GTM routes; Airtable read-permissions for Harmony Calendar and Gate Register exposed to PCC. |
| DT-26 | What is the canonical sub-GTM template? Should every service-line GTM repeat the cascade-of-instruments pattern? | No. The cascade of instruments (Spine + Phase Architecture + Channel Matrix + Harmony Calendar + Gate Register + Filter Card — six artefacts) is Webgold-internal scaffolding for a complex operator running multiple service-line sub-GTMs. Sub-GTMs do NOT need their own cascade. The canonical sub-GTM template is the existing Support HQ GTM Execution Portfolio (support-hq-gtm-execution-portfolio.html) — a single execution portfolio HTML containing: Master inheritance preamble; modules (M1-M8); waypoint library (W1-W11); campaign index (Cn codes); persona journey maps tagged against CMIF Personas A-E; embedded calendar (filtered VIEW of Master Harmony Calendar, NOT separate); decisions log; intelligence layer. All sub-GTM copy runs through the Master Filter. All motions tagged into Master Harmony Calendar Airtable as service: <service-line>. Sub-GTMs surface as new linked spaces in PCC side panel. Master is the sun, sub-GTMs orbit. To productise: build a sub-gtm-builder skill on the FPB pattern (Phase 1 scaffolds HTML instance from template; Phase 2 finalises after content is filled in). | Phase 7 — Reef Briefing covers sub-GTM workflow; Phase 8 — register sub-gtm-builder skill at Infrastructure/Skills/; create Sub-GTM TEMPLATE.html in Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/; existing Support GTM gets re-alignment pass; cadence aligns to WG-25 sprints (Commerce S2, Dev S3, Engagement+Products+Growth+CommUnity S4, Content+Identity S5, Intelligence S6, DX S7, Website Release ~July). See Appendix D — Sub-GTM Framework tab. |
| DT-27 | How do clients receive the Reef methodology? Do they get the cascade? | No. Clients do NOT get the cascade of six instruments. The cascade is Webgold-internal scaffolding because we operate at scale that requires it. Clients receive a single GTM document scaled to their scope. SME / single-brand = one modest single-section GTM document. Mid-market / multi-product = one multi-section GTM document, one section per product line. Major / multi-brand or multi-entity = one large sectioned GTM document, sections per brand/entity. The shape is consistent (positioning, audience, channels, calendar, decisions, intelligence); depth scales with scope. The Reef methodology — translation-tax thinking, four-position commitment, channel harmony, motion calendar, filter/gate discipline — is the consulting IP that powers the work. The artefact delivered is the distilled output, not our internal architecture. Tier 1 Digital Products (Enrique Francis line) packages this as a Client GTM Template at three sizes: SME / Mid-Market / Major. | Spine §11 (Economy) — replace any "cascade-for-clients" framing with single-document tiered productisation; Cascade Execution Guide Phase 7 briefing covers the productised tiers; Operating Architecture companion captures the internal-vs-external distinction; Tier 1 Digital Products catalogue (Enrique) registers Client GTM Template at three sizes as Master GTM-derived assets. |
| DT-28 | What is the actual scope of the Master GTM? The organism, or just Webgold Designs Ltd? | Webgold Designs Ltd ONLY. The Master GTM (the Reef) governs Webgold Designs Ltd marketing exclusively. The Webgold organism comprises three entities — Webgold Designs Ltd, Buzz Media, and Buzz Experiences — but the Master GTM is NOT an organism-wide marketing doctrine. Buzz Media and Buzz Experiences will receive their own future GTMs (BC-22 Buzz Media Marketing in 2027, BX-23 Buzz Experiences Marketing in 2027) following this same cascade methodology, adapted for SaaS and B2C travel respectively. Where another entity intersects with Webgold Designs marketing — for example, Megan Gill's organism-wide Events & Activations Lead role contributing to Webgold Designs authority events through CommUnity and the Caribbean Digital Awards; Stephan De Roche serving as CEO of all three entities but operating as the founder voice for Webgold Designs in the Master GTM context; Gem David holding Operations Architect organism-wide alongside Marketing Lead Webgold-Designs-specific — the intersection is named explicitly and scoped to its Webgold Designs contribution. References to "the organism" in any Master GTM artefact must distinguish between the Organism (parent layer, Webgold Designs + Buzz Media + Buzz Experiences) and the Reef (Webgold Designs Master GTM). The metaphor stack reflects this layering: Organism (parent layer); Vehicle / Beacon / Riverlets / Warfare / Symphony (operational layer, scope varies by entity); Reef (Webgold Designs Master GTM specifically). | Spine §1 cross-references reframed (this build); Cascade Execution Guide Appendix C team reference scopes each role to Webgold Designs contribution (this build); all future Master GTM artefacts must observe this scope boundary; Sub-GTM Framework (Appendix D) is for Webgold Designs service-line sub-GTMs only. |
The Master GTM (the Reef) is the governance layer. It defines positioning, voice, four-position commitment, channel harmony, content portfolio ratios, kill list, economy, and the calendar of motions. Every sub-GTM operates under the Master. Sub-GTMs do not contradict the Spine; they instantiate it for a specific service line. Updates to the Master propagate to sub-GTMs through scheduled re-alignment passes — when the Spine cuts a new version, every sub-GTM gets a discrete pass to re-reference, re-Filter, re-tag personas, and confirm calendar wiring.
Modelled on the existing Support HQ GTM Execution Portfolio. A single execution portfolio HTML with seven elements:
To productise sub-GTM creation as services and solutions expand, build a sub-gtm-builder skill at Infrastructure/Skills/sub-gtm-builder.skill. Pattern mirrors the founder-positioning-brief skill (single .skill file containing SKILL.md; templates and workflow reference live in the project folder).
Trigger: "create a sub-GTM for [service-line]" / "build a sub-GTM for Commerce" / "start a sub-GTM for Identity".
Actions: extract the service line; scan project folder for existing material (service briefs, WG-25 sprint plans, CMIF persona refs, brand voice doc); scan Master Spine for governance clauses applicable to that service line; identify gaps; ask once in single grouped message for missing inputs (named expert, expert credentials, service-line opening date, persona alignment, intelligence-layer notes); create new HTML instance at Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/Sub-GTM — [service-line].html with Master inheritance preamble pre-filled, modules scaffolded, waypoints W1-W11 stubbed, campaign index empty, persona journeys pre-tagged against CMIF, calendar pulling filtered Master Harmony Calendar view, decisions log empty, intelligence layer with pre-filled territory data; deliver: HTML link + pre-fill summary + interview prep (5-7 questions) + next-step instruction.
Trigger: "information filled for [service-line] sub-GTM, please complete it" / "finalise the [service-line] sub-GTM".
Actions: load brand-compliance-check skill; read completed HTML instance; parse all filled fields; run Filter pass on all copy; confirm persona tags map to CMIF; verify campaign codes are unique; ensure motions are wired to push into Master Harmony Calendar Airtable as service: <service-line> records; produce final delivery: HTML instance polished and brand-compliance-passed; companion .docx if required; Airtable seed of new motions; Cloudflare Pages route registered for ops.webgold.co/gtm/<service-line>; PCC side-panel link added to Master GTM section.
Infrastructure/Skills/sub-gtm-builder.skill (single .skill, contains SKILL.md only).Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/Sub-GTM — TEMPLATE.html (canonical empty instance, modelled on Support HQ).Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/Sub-GTM — Workflow.html.Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/Instances/ (one HTML per sub-GTM instance).Project Packages/Webgold Master GTM/Documents/Master GTM — Alignment Filter.pdf (consumed by skill Phase 2).Each sub-GTM is built shortly before the WG-25 sprint that activates its service line. This keeps sub-GTM development tightly coupled to website release timing.
| Sub-GTM | WG-25 Sprint | Build window | Notes |
|---|---|---|---|
| Support | Sprint 1 (already activated) | Already exists — re-alignment pass scheduled | Reference Spine v1.0; Filter pass; re-tag personas A-E; confirm "Support" service-line naming; wire motions into Master Harmony Calendar. |
| Commerce | Sprint 2 | After Master Phase 8 lands, before Sprint 2 launch | PowerTranz integration depth; Persona E Maya is primary. |
| Development | Sprint 3 | Before Sprint 3 launch | Senior full-stack architect with WordPress + headless experience as named expert. |
| Engagement + Products + Growth + CommUnity | Sprint 4 | Before Sprint 4 launch | Three voices simultaneously; CommUnity Jul 2 sponsorship is anchor event motion. |
| Content + Identity | Sprint 5 | Before Sprint 5 launch | Yohance anchors Identity (Visual & Brand); Anyah anchors Content (Copy & Messaging). |
| Intelligence | Sprint 6 | Before Sprint 6 launch | Most authority-disproportionate role; AI strategist. |
| DX / Transformation | Sprint 7 | Before Sprint 7 launch | Senior transformation strategist with named-client transformation track record. |
| Website Release | (Spans launch) | July 2026 | Lift content from WG-25 Decision Log + Sitemap into proper Website Release sub-GTM HTML. |
Each sub-GTM, once produced via the skill, is surfaced in the PCC side panel under the Master GTM section as a new linked space. Same surfacing pattern as the Ecosystem Map and the Operations Hub mockup: hyperlink (or iframe-embed) from the side panel to the published HTML at ops.webgold.co/gtm/<service-line>. The PCC reads filtered Harmony Calendar data tagged for that service line and surfaces relevant motions as tasks where applicable. The sub-GTM does not become a PCC programme record on its own; it is a surfaced asset.
When the Master Spine version-bumps (e.g., v1.0 → v1.1 on FPB landing, or v1.1 → v2.0 on a posture shift), every existing sub-GTM gets a re-alignment pass scheduled in PCC as a discrete task. The pass updates Spine version reference at the top, re-runs the Filter on all copy, re-confirms persona tags against the latest CMIF, validates campaign codes for collisions, and confirms motion-tagging into the Master Harmony Calendar. This is the propagation discipline that keeps the symphony in tune.
Per DT-27, clients do NOT receive the cascade and do NOT receive sub-GTMs. They receive a single GTM document scaled to their scope. The Reef methodology is the consulting IP behind the work; the deliverable is the distilled artefact. Tier 1 Digital Products (Enrique Francis) packages this as a Client GTM Template at three sizes — SME (single-section), Mid-Market (multi-section, one per product line), Major (large sectioned, one per brand / entity / department). The internal sub-gtm-builder skill is NOT for client work; client work uses a separate client-gtm-builder skill (to be built when the Tier 1 catalogue is ready).
| Phase | Title | Status | Outstanding |
|---|---|---|---|
| 0 | Pre-execution audit, WG-25 sprint binding, Decision Trail | COMPLETE ✓ | DT-1 through DT-28 captured; Appendix C Team Reference + Appendix D Sub-GTM Framework added; Path-to-Complete + Master Task Register shipped. |
| 1 | The Spine — Webgold Master GTM (the Reef) v1.0 | AWAITING FPB | v1.0 build COMPLETE: §1-§11 + cross-references shipped; multi-voice re-cut applied; DT-28 scope correction backward-compat done; Claude Design infographics swapped in (T-MGTM-037 DN). Outstanding: (a) Spine v1.1 cut combining FPB §8 fill-in + DT-28 corrections — BL on Stephan FPB Friday 8 May 2026; (b) Stephan v1.0 ratification. |
| 2 | Phase Architecture & Sprint Binding | COMPLETE ✓ | HTML built with 10 sprint cards; multi-voice re-cut applied; sub-GTM build window callout (DT-26 cadence table) shipped; DT-28 scope boundary callout shipped. |
| 3 | Channel Harmonisation Matrix | COMPLETE ✓ | 5-sheet XLSX with 19 channels × 10 columns shipped; multi-voice owner cells; brand-compliance pass complete. No DT-25/26/27/28 update required. |
| 4 | Harmony Calendar + Airtable seed + Ratio Validator | COMPLETE ✓ | HTML 3-tab build + 45-motion seed script + Ratio Validator + Nucleus integration config-note (DT-24) + sub-GTM filtering config-note (DT-26) + DT-28 scope boundary config-note. Note: actual Airtable seed-script execution sits in Phase 8.4 (T-MGTM-054). |
| 5 | Gate Register & Tempo Protocol | BUILD COMPLETE ✓ | 2026-05-07. v1.0 HTML doctrine shipped — 10 sections covering Launch Posture Gate quarterly + Tempo Gate weekly + 8 gate criteria + 3 Tempo states + Airtable GATE_REGISTER schema connection + operational rhythm + escalation paths + mechanisations. Surfaced in PCC sidebar via Cycle 3 deploy (v88). Awaiting Stephan ratification (T-MGTM-152) + .docx canonical companion (T-MGTM-151). Detail: T-MGTM-056 to T-MGTM-060 all DN. |
| 6 | Filter card + WG-25 Staging Audit + WG-21 Pipeline Audit | PARTIAL — 1 of 3 | 2026-05-07. (1) Filter Card v1.0 HTML — DONE (T-MGTM-061). 5 sections, brand-compliant, surfaced via Cycle 4 deploy v89. (2) WG-25 Staging Copy Filter Audit — OVERDUE (T-MGTM-062). Was due before April 30 go-live; never executed; needs to run on next deploy cycle. (3) WG-21 Content Pipeline Filter Audit — NOT STARTED (T-MGTM-063). Covers WG-21.1 through WG-21.6. Phase 6 closes only when both audits ship. |
| 7 | Reef Team Briefing & Onboarding | BUILD COMPLETE ✓ — sessions pending | 2026-05-08. (1) Reef Team Briefing v1.0 HTML — DONE (T-MGTM-066). 9 sections + embedded metaphor stack cross-reference card. (2) Reef Team Briefing Deck v1.0 .pptx — DONE (T-MGTM-067). 11 slides + .pdf rendition. (3) Three sessions to RUN: Stephan + Gem (T-MGTM-069), marketing layer (T-MGTM-070), Megan events scope (T-MGTM-071). Phase 7 closes when all three sessions are run. |
| 8 | Cascade Integration, Publish, Brief, Verify | NOT STARTED | CMIF v1.1m → v1.2; WG-21 Project Package v1.3 → v1.4; Decision Log entries for DEC-MGTM-001 through 005 plus DT-1 through DT-28 mirrored; Airtable HARMONY_CALENDAR + GATE_REGISTER + FILTER_PASSES seeds; Cloudflare Pages deploy of GTM hub at ops.webgold.co (with PCC side-panel Master GTM section linking out per DT-25); Phase-State Tool; brand-compliance-check pass on every artefact; Operating Architecture companion (deferred to last per Gem decision); final Closure Roadmap update declaring project complete. |
Create directory at Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/. Inside: Sub-GTM — TEMPLATE.html (canonical empty instance modelled on Support HQ GTM Execution Portfolio); Sub-GTM — Workflow.html (human-readable how-to companion); Instances/ subfolder for produced sub-GTMs. Webgold Designs only.
Build at Infrastructure/Skills/sub-gtm-builder.skill — single .skill file containing SKILL.md, modelled on founder-positioning-brief skill. Two-phase workflow per Appendix D specification. For Webgold Designs internal sub-GTMs only — separate client-gtm-builder skill comes later for Tier 1 Digital Products.
Triggered by Gem when ready (no fixed date). Update the existing Support HQ GTM Execution Portfolio: reference Master Spine v1.0 at top; Filter pass on copy; re-tag personas A-E; confirm "Support" naming; wire campaign motions to push into Master Harmony Calendar as service: support records. First re-alignment under the framework — validates the workflow.
Per DT-28 audit: Spine §1 cross-references corrected (this build); Cascade Execution Guide Appendix C Team Reference corrected (this build); memory files (project_master_gtm_cascade.md, project_master_gtm_voice.md, new project_master_gtm_scope.md) updated to reflect DT-25/26/27/28; Phase Architecture HTML and Harmony Calendar HTML get light DT-26 updates (this build); Channel Matrix XLSX and Team Intro deck need no update.
Per Gem decision 2026-05-07: do NOT build the Operating Architecture companion document until everything else is closed. Building it now would create another artefact requiring backward-compatibility maintenance through Phases 5-8. Build it as the final closure act in Phase 8 — covers the four-layer system (Doctrine / Operating Instruments / Operating Data / Render layer), PCC integration model, Master-Airtable-ops.webgold.co data flow, update propagation discipline, internal-vs-client boundary (per DT-27), and full system map. Webgold Designs only with explicit boundary statements at top.
Once cascade closes (Phase 8 complete) and the sub-gtm-builder skill is shipped, sub-GTMs build on the WG-25 sprint cadence: Commerce before Sprint 2, Development before Sprint 3, Engagement+Products+Growth+CommUnity before Sprint 4, Content+Identity before Sprint 5, Intelligence before Sprint 6, DX before Sprint 7. Website Release sub-GTM lands ~July 2026. The 2027 BC-22 (Buzz Media) and BX-23 (Buzz Experiences) GTMs follow the same cascade methodology — explicitly OUT of Master GTM scope.
Comprehensive enumeration of EVERY task in the Master GTM cascade — both completed work (DN, with date) and outstanding work (NS / IP / BL / DEF / OD). Captures originally-scoped work and discovered/realised tasks along the cascade journey. Status flags: NS Not Started · IP In Progress · BL Blocked · DN Done · DEF Deferred · OD Overdue.
As of 2026-05-08 (latest update): Total 172 tasks · Done: 99 · In Progress: 1 · Blocked: 2 · Overdue: 1 · Deferred: 1 · Not Started: 68. This update: T-MGTM-160+161 flipped DN (Cycle 4 v89 deployed). T-MGTM-066+067+068+072 flipped DN (Phase 7 Reef Team Briefing v1.0 HTML + .pptx deck + cross-reference card embedded + brand-compliance pass). T-MGTM-163-170 added DN (Cycle 5 work). T-MGTM-171 promoted NEXT (Cycle 5 deploy v90). Phase 7 BUILD COMPLETE; three briefing sessions still pending (T-MGTM-069/070/071 — schedule when convenient). Cascade resumes UPWARD at Phase 8 once T-MGTM-171 lands.
The Master Task Register is NOT a linear top-to-bottom sequence. After completing any task, return to the Phase Status table at the top of this tab to determine next priority — usually the next-numbered Phase or a Sub-GTM build. Three patterns:
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-001 | Survey project folder structure; locate cascade methodology + prior cascade examples | DN | 2026-05-06. |
| T-MGTM-002 | Read CMIF, brand voice, messaging guardrails, white-space analysis, channel strategy, warfare doctrine, existing GTMs | DN | 2026-05-06. |
| T-MGTM-003 | Author Master GTM — Cascade Execution Guide v1.0.docx (Phase 0 canonical artefact) | DN | 2026-05-06. Brand-compliant. |
| T-MGTM-004 | Build Cascade Execution Guide v1.0.html (interactive working tool — Filter Tester, Decisions Log, Tempo Today, persistent phase tracking) | DN | 2026-05-06. |
| T-MGTM-005 | Brand-compliance-check pass on Cascade Execution Guide | DN | 2026-05-06. |
| T-MGTM-006 | Capture DT-1 through DT-19 in Decision Trail (Reef metaphor, translation-tax, Filter authority, Gem-not-founder, sprint-bound, eight phases, Reef Briefing, FPB slot, active invitation) | DN | 2026-05-06. |
| T-MGTM-007 | Capture DT-20 (mechanisations along the way) | DN | 2026-05-06. |
| T-MGTM-008 | Capture DT-21 (Spine v1.0 augmented with five infographics) | DN | 2026-05-06. |
| T-MGTM-009 | Capture DT-22 (marketing voices correction — actual layer is Gem/Yohance/Anyah/Kevyn) | DN | 2026-05-07. |
| T-MGTM-010 | Capture DT-23 (Megan = Events Lead, not marketing) | DN | 2026-05-07. |
| T-MGTM-011 | Capture DT-24 (Master GTM → CON-002 Editorial Calendar Nucleus integration) | DN | 2026-05-07. |
| T-MGTM-012 | Add Appendix C — Team Reference (canonical roster) | DN | 2026-05-07. |
| T-MGTM-013 | Capture DT-25 (PCC integration model — linked-space, not host) | DN | 2026-05-07. |
| T-MGTM-014 | Capture DT-26 (Sub-GTM template = Support GTM single-portfolio pattern; sub-gtm-builder skill spec) | DN | 2026-05-07. |
| T-MGTM-015 | Capture DT-27 (Client model — single-document tiered productisation, not cascade) | DN | 2026-05-07. |
| T-MGTM-016 | Capture DT-28 (Master GTM scope = Webgold Designs Ltd ONLY) | DN | 2026-05-07. |
| T-MGTM-017 | Add Appendix D — Sub-GTM Production Framework | DN | 2026-05-07. |
| T-MGTM-018 | Add Path to Project Complete section | DN | 2026-05-07. |
| T-MGTM-019 | Add Master Task Register (this update) | DN | 2026-05-07. |
| T-MGTM-020 | Fix DEC-MGTM-005 status from OPEN to RESOLVED | DN | 2026-05-06. DX Authority through Sprint 7. |
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-021 | Draft Spine §1 Reef premise + §2 Translation tax + §3 White space + §4 Four-position commitment | DN | 2026-05-06. |
| T-MGTM-022 | Draft Spine §5 Demand-architecture map | DN | 2026-05-06. |
| T-MGTM-023 | Draft Spine §6 Content portfolio mix and ratios | DN | 2026-05-06. |
| T-MGTM-024 | Draft Spine §7 Channel hierarchy | DN | 2026-05-06. |
| T-MGTM-025 | Draft Spine §8 Authorship architecture (placeholder; v1.1 cuts on FPB) | DN | 2026-05-06. Slot. |
| T-MGTM-026 | Draft Spine §9 Proof Factory | DN | 2026-05-06. |
| T-MGTM-027 | Draft Spine §10 Kill List | DN | 2026-05-06. |
| T-MGTM-028 | Draft Spine §11 The Economy | DN | 2026-05-06. |
| T-MGTM-029 | Author Spine cross-references (CMIF inheritance + sub-GTM relationships + Reef cross-walk) | DN | 2026-05-06. |
| T-MGTM-030 | Re-cut Spine v0.5 → v0.5b (build-as-attraction §1; events activation §4) | DN | 2026-05-06. |
| T-MGTM-031 | Build Spine v1.0 .html (reading-oriented, deployable to ops.webgold.co) | DN | 2026-05-06. |
| T-MGTM-032 | Build five inline SVG infographics in Spine HTML companion | DN | 2026-05-06. |
| T-MGTM-033 | Re-cut Spine §4 + §8 to multi-voice authorship | DN | 2026-05-06. |
| T-MGTM-034 | Brand-compliance-check pass on Spine .docx + .html | DN | 2026-05-06. |
| T-MGTM-035 | Save Spine v1.0 to /Project Packages/.../ (.docx + .pdf + .html) | DN | 2026-05-06. |
| T-MGTM-036 | Spine v1.0 §1 cross-references re-scoped to Webgold Designs (DT-28 backward-compat) | DN | 2026-05-07. Both .docx and .html updated; PDF regenerated. |
| T-MGTM-037 | Replace Spine HTML interim SVG infographics with Gem's Claude Design infographics | DN | 2026-05-07. All 5 visuals swapped: Reef ecosystem · Five-year timeline · Four positions × channels matrix · Demand-architecture displacement · Economy J-curve. Images in ../Infographics/. |
| T-MGTM-038 | Spine v1.1 cut — combine FPB landing (§8 fill-in) + DT-28 scope corrections | BL | Blocked by T-MGTM-115 (Stephan FPB ~Friday 8 May 2026). |
| T-MGTM-039 | Spine v1.0 ratification by Stephan (formal sign-off) | NS | Required for v1.0 to be canonical externally. |
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-040 | Build Phase Architecture & Sprint Binding.html (10 sprint cards: Pre-MVP, S1-S7, Buffer, Full Launch) | DN | 2026-05-07. |
| T-MGTM-041 | Re-cut Phase Architecture sprint cards to multi-voice authorship | DN | 2026-05-07. |
| T-MGTM-042 | Pre-MVP and Sprint 1 cards corrected — replace Leah/Megan-as-marketing with Yohance/Anyah/Kevyn under Gem | DN | 2026-05-07. |
| T-MGTM-043 | Add sub-GTM build window callout (DT-26 cadence) | DN | 2026-05-07. |
| T-MGTM-044 | Add Critical scope boundary callout (DT-28 — Webgold Designs only) | DN | 2026-05-07. |
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-045 | Build Channel Harmonisation Matrix.xlsx (5 sheets, 19 channels × 10 columns) | DN | 2026-05-07. |
| T-MGTM-046 | Multi-voice owner cells across Named Owner column | DN | 2026-05-07. |
| T-MGTM-047 | Brand-compliance-check pass (colour audit) on Channel Matrix XLSX | DN | 2026-05-07. |
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-048 | Build Harmony Calendar.html (3 tabs: 13-Week View filterable, Ratio Validator mechanised, Setup & Sync) | DN | 2026-05-07. |
| T-MGTM-049 | Build airtable-seed-harmony-calendar.py with 45 motions across all sprint windows | DN | 2026-05-07. |
| T-MGTM-050 | Build Content Portfolio Ratio Validator inline (mechanised against §6 ratios) | DN | 2026-05-07. |
| T-MGTM-051 | Add Nucleus integration config-note (DT-24) | DN | 2026-05-07. |
| T-MGTM-052 | Add sub-GTM filtering config-note (DT-26) | DN | 2026-05-07. |
| T-MGTM-053 | Add scope boundary config-note (DT-28) | DN | 2026-05-07. |
| T-MGTM-054 | Run airtable-seed-harmony-calendar.py — seed HARMONY_CALENDAR table | NS | Script exists; confirm not yet run, then execute. |
| T-MGTM-055 | Brand-compliance-check pass on Harmony Calendar HTML + seed script | DN | 2026-05-07. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-056 | Decide Gate Register design pattern | DN | 2026-05-07. Pattern A confirmed (separate table + FK). Captured as DT-26 + T-MGTM-130. |
| T-MGTM-057 | Build Gate Register Airtable table per chosen pattern | DN | 2026-05-07. Created via airtable-create-gtm-tables.py — table tblrwjOz3RTHHQlvf with full schema. |
| T-MGTM-058 | Author Master GTM — Gate Register & Tempo Protocol document (HTML form delivered; docx companion as T-MGTM-151) | DN | 2026-05-07. v1.0 HTML doctrine — 10 sections covering both gate types + 8 criteria + 3 Tempo states + Airtable connection. |
| T-MGTM-059 | Formalise weekly Tempo Gate dial spec into Phase 5 doctrine | DN | 2026-05-07. §3 of Phase 5 doctrine covers 3 Tempo states with explicit per-state action protocol. |
| T-MGTM-060 | Brand-compliance check on Phase 5 HTML | DN | 2026-05-07. Brand palette + typography applied; div + section balance 0. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-061 | Author Filter Card v1.0 HTML — 5 sections, 8 tests, banned vocabulary, outcomes-led principle, run-procedure, two first applications | DN | 2026-05-07. webgold-master-gtm-filter-card.html shipped via Cycle 4. .pdf companion as T-MGTM-162 follow-on. |
| T-MGTM-062 | Run WG-25 Staging Copy Filter Audit (Filter application) | OD | Filter Card now exists — execute audit on next deploy cycle. |
| T-MGTM-063 | Run WG-21 Content Pipeline Filter Audit | NS | Covers WG-21.1-21.6. |
| T-MGTM-064 | Build Filter Card standalone HTML — surfaced at /webgold-master-gtm-filter-card.html | DN | 2026-05-07. Sticky in-section nav, brand-compliant, sidebar-linked. Live in Cycle 4 deploy v89. |
| T-MGTM-065 | Brand-compliance check on Phase 6 HTML | DN | 2026-05-07. Brand palette + typography applied; balance 0. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-066 | Author Reef Briefing.pdf (one-page Reef explainer) | NS | Reef premise, four-position commitment, scope boundary (DT-28). |
| T-MGTM-067 | Build Reef Briefing Deck.pptx (30-minute team session) | NS | Multi-voice, sub-GTM workflow, productised client tiers. |
| T-MGTM-068 | Author Reef Briefing cross-reference card (metaphor stack) | NS | Reef alongside Vehicle/Beacon/Riverlets/Warfare/Symphony plus Organism layer. |
| T-MGTM-069 | Run Reef Briefing with Stephan + Gem (founder + architect) | NS | Internal ratification. |
| T-MGTM-070 | Run Reef Briefing with marketing layer (Yohance, Anyah, Kevyn) | NS | See also T-MGTM-122 (operational briefing). |
| T-MGTM-071 | Run Reef Briefing with Megan Gill (Webgold Designs events scope only, per DT-28) | NS | Events-scope briefing. |
| T-MGTM-072 | Brand-compliance-check pass on Phase 7 deliverables | NS | Standard QA gate. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-073 | Update CMIF Source Document Register v1.1m → v1.2 with Master GTM | NS | Phase 8.1. |
| T-MGTM-074 | Update WG-21 Project Package v1.3 → v1.4 with parent-doctrine reference | NS | Phase 8.2. |
| T-MGTM-075 | Mirror DEC-MGTM-001 through 005 in Webgold-wide Decision Log | NS | Phase 8.3. |
| T-MGTM-076 | Mirror DT-1 through DT-28 in Decision Log | NS | Phase 8.3. |
| T-MGTM-077 | Build airtable-seed-gate-register.py and run | NS | Blocked by T-MGTM-056 + T-MGTM-057. |
| T-MGTM-078 | Build airtable-seed-filter-passes.py and run | NS | FILTER_PASSES tracking. |
| T-MGTM-079 | Author Master GTM — Operating Architecture companion (FINAL ACT) | DEF | DEFERRED to last per Gem decision 2026-05-07. |
| T-MGTM-080 | Build Phase-State Tool (date → operational state lookup) | NS | Phase 8 mechanisation per DT-20. |
| T-MGTM-081 | Cloudflare Pages deploy of Master GTM hub at ops.webgold.co | NS | Phase 8.5. |
| T-MGTM-082 | Configure Cloudflare routes (/gtm/spine, /gtm/calendar, /gtm/filter, /gtm/sub-gtms/*, etc.) | NS | Per DT-25. |
| T-MGTM-083 | Build PCC side-panel Master GTM section linking to all surfaced GTM pages | NS | Per DT-25 — same surfacing pattern as Ecosystem Map. |
| T-MGTM-084 | Configure PCC Airtable read permissions for HARMONY_CALENDAR + GATE_REGISTER tables | NS | Per DT-25 — PCC consumes data, does not host. |
| T-MGTM-085 | Final brand-compliance-check pass across ALL Master GTM artefacts | NS | Final QA gate. |
| T-MGTM-086 | Final entry in File Creation Log declaring cascade complete; lock canonical versions | NS | Closure act. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-087 | Create Project Packages/Webgold Master GTM/Documents/Sub-GTM Framework/ folder | NS | Per Appendix D. |
| T-MGTM-088 | Build Sub-GTM — TEMPLATE.html (canonical empty instance, 7-element structure) | NS | Modelled on Support HQ GTM Execution Portfolio. |
| T-MGTM-089 | Author Sub-GTM — Workflow.html (human-readable how-to companion) | NS | Reference for the team. |
| T-MGTM-090 | Create Instances/ subfolder for produced sub-GTMs | NS | One HTML per service-line. |
| T-MGTM-091 | Build sub-gtm-builder.skill at Infrastructure/Skills/ | NS | Modelled on founder-positioning-brief skill. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-092 | Re-alignment pass on existing Support GTM (when Gem triggers) | NS | Reference Spine v1.0; Filter pass; re-tag personas; wire motions. |
| T-MGTM-093 | Build Commerce sub-GTM (before Sprint 2) | NS | PowerTranz; Persona E Maya primary. |
| T-MGTM-094 | Build Development sub-GTM (before Sprint 3) | NS | Senior full-stack architect. |
| T-MGTM-095 | Build Engagement+Products+Growth+CommUnity sub-GTM (before Sprint 4) | NS | Three voices; CommUnity Jul 2 anchor. |
| T-MGTM-096 | Build Content+Identity sub-GTM (before Sprint 5) | NS | Yohance/Identity; Anyah/Content. |
| T-MGTM-097 | Build Intelligence sub-GTM (before Sprint 6) | NS | AI strategist. |
| T-MGTM-098 | Build DX sub-GTM (before Sprint 7) | NS | Senior transformation strategist. |
| T-MGTM-099 | Build Website Release sub-GTM (~July 2026) | NS | Lift from WG-25 Decision Log + Sitemap. |
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-100 | Build Master GTM — Team Introduction.pptx (12 slides) | DN | 2026-05-07. |
| T-MGTM-101 | Render Team Introduction.pdf from .pptx | DN | 2026-05-07. |
| T-MGTM-102 | Update Team Intro deck slides 7 + 11 — replace Leah/Megan-as-marketing with Yohance/Anyah/Kevyn under Gem | DN | 2026-05-07. |
| T-MGTM-103 | Author Webgold Master GTM — Infographic Prompts.md (NotebookLM-tailored) | DN | 2026-05-06. |
| T-MGTM-104 | Assess NotebookLM-generated infographics + provide correction prompts | DN | 2026-05-06. Gem then chose Claude Design. |
| ID | Task | Status | Notes / Date |
|---|---|---|---|
| T-MGTM-105 | Write project_master_gtm_cascade.md memory | DN | 2026-05-06. |
| T-MGTM-106 | Write project_master_gtm_voice.md memory | DN | 2026-05-06. |
| T-MGTM-107 | Write reference_team_roster.md memory (canonical Webgold team roster) | DN | 2026-05-07. Prevents future Leah-as-marketing mistakes. |
| T-MGTM-108 | Update project_master_gtm_cascade.md with DT-25/26/27/28 architectural decisions block | DN | 2026-05-07. |
| T-MGTM-109 | Write project_master_gtm_scope.md memory (Webgold Designs scope rule) | DN | 2026-05-07. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-110 | Schedule quarterly Spine review (Q3 2026, Q4 2026, Q1 2027 onwards) | NS | Recurring task in PCC. |
| T-MGTM-111 | Schedule sprint-boundary Channel Matrix review | NS | Recurring at every WG-25 sprint launch. |
| T-MGTM-112 | Schedule weekly Tempo Gate review (Tempo Protocol cadence) | NS | Starts when Phase 5 ships. |
| T-MGTM-113 | Schedule weekly Filter Card check on in-flight motions | NS | Starts when Phase 6 ships. |
| T-MGTM-114 | Re-alignment pass discipline — when Master Spine version-bumps, every sub-GTM gets a discrete re-alignment task in PCC | NS | Process documentation + PCC trigger automation. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-115 | Stephan's Founder Positioning Brief delivery | BL | Due ~Friday 8 May 2026. Drives Spine v1.1 (T-MGTM-038). |
| T-MGTM-116 | WG-21.6 closure (Social Presence Activation & Template Production) | IP | Closes April 30 2026 — produces 83-template library feeding CON-003 + CON-006. |
| T-MGTM-117 | HubSpot CRM attribution integration — read attribution data into Calendar motion fields | NS | Sprint 4+ work. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-118 | Confirm Channel Matrix render strategy — XLSX-only, or also HTML view at ops.webgold.co/gtm/channel-matrix? | NS | PCC iframe-embed of XLSX is awkward. |
| T-MGTM-119 | Confirm Filter Tester surface — keep nested in Cascade HTML or extract into standalone Filter Card surface at ops? | NS | Decision affects T-MGTM-082 routes. |
| T-MGTM-120 | Confirm Tempo Gate dial surface — keep nested or extract to standalone Tempo surface at ops? | NS | Decision affects T-MGTM-082 routes. |
| T-MGTM-121 | Build Master GTM hub landing page at ops.webgold.co/gtm — list of all surfaced pages | NS | Index page that PCC side-panel parent link points to. |
| T-MGTM-122 | Brief marketing layer (Yohance, Anyah, Kevyn) on Reef + Filter + Calendar workflow (operational, separate from formal Reef Briefing T-MGTM-070) | NS | Hands-on session. |
| T-MGTM-123 | Confirm Persona E Maya (added 2026-04-01) is referenced in all relevant Master GTM artefacts | NS | Spine §5, Channel Matrix Persona owner cells, Sub-GTM TEMPLATE persona journey scaffolds. |
| T-MGTM-124 | Update Brand Voice doc downstream to honour Master Filter (DT-4) | NS | Schedule after Phase 6 Filter card ships. |
Cascade-level architectural decisions captured as discrete tasks. Each decision is one-time and DN once made — but the LOG itself is recurring (new decisions get added here as cascade work surfaces them).
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-129 | Single-base architecture decision — all PCC + GTM tables in appaRLtvQEiOHwdWz (Option A) vs. separate GTM base (Option B) | DN | 2026-05-07. Decided Option A by Gem. Memory captured at feedback_pcc_base_threshold.md. 15-table threshold flagged. |
| T-MGTM-130 | Gate Register design pattern decision — separate table with FK (Pattern A) vs. multi-select on Calendar (Pattern B) | DN | 2026-05-07. Decided Pattern A by Gem. |
| ID | Task | Status | Notes / Dependencies |
|---|---|---|---|
| T-MGTM-131 | Build airtable-create-gtm-tables.py — Meta API table creation for HARMONY_CALENDAR + GATE_REGISTER + FILTER_PASSES (single shot, idempotent) | DN | 2026-05-07. Created at pcc-prototype/. Outputs Worker TABLES snippet. |
| T-MGTM-132 | Build airtable-verify-gtm-tables.py — post-create verification + optional example records | DN | 2026-05-07. Verifies field counts; optional schema test inserts. |
| T-MGTM-135 | Gem runs airtable-create-gtm-tables.py — creates 3 tables, captures IDs | DN | 2026-05-07. HC=tbloA7vdWTtPStYm8, GR=tblrwjOz3RTHHQlvf, FP=tblAVYm6XVJbfZuBZ. |
| T-MGTM-136 | Gem runs airtable-seed-harmony-calendar.py — populates 45 motions into HARMONY_CALENDAR | DN | 2026-05-07. 45/45 motions; 0 failures; Pre-MVP through Full Launch covered. |
| T-MGTM-141 | Update Harmony Calendar HTML setup checklist + add HARMONY_CALENDAR_TABLE_ID + AIRTABLE_BASE_ID JS constants | DN | 2026-05-07. Items 1-3 marked DONE; item 4 → T-MGTM-140. |
| T-MGTM-140 | Wire Master GTM Harmony Calendar HTML to live Airtable fetch — replace SEED_MOTIONS rendering with /api/harmony-calendar endpoint similar to PCC /api/boot | NS | Constants already set; Worker endpoint + JS wiring pending. Phase 8.5 follow-on. |
Every PCC code change (Worker, index.html, surfaced HTMLs, new endpoints, schema additions) triggers a deploy cycle. A cycle has three steps: (1) code change in pcc-prototype/ → (2) zip rebuild + version bump → (3) Cloudflare Pages deploy. This is RECURRING — not a one-time closure act. Each new cycle gets its own row block. After a deploy lands, work returns UPSTREAM to whichever phase or build task is next on the priority list — typically the next-numbered Phase or a Sub-GTM build, NOT the rows below.
· Cycle 1 — initial Worker schema-extend (superseded by Cycle 2)
| ID | Task | Status | Notes |
|---|---|---|---|
| T-MGTM-133 | Cycle 1 — Update _worker.js TABLES array with 3 GTM entries + skipIfPlaceholder flag for graceful pre-creation deploy | DN | 2026-05-07. Never deployed — superseded by Cycle 2 with real IDs. |
| T-MGTM-134 | Cycle 1 — Rebuild pcc-deploy-latest.zip v85 → v86 with placeholder IDs | DN | 2026-05-07. Built but never deployed; superseded by Cycle 2 v87. |
· Cycle 2 — Worker patched with real GTM table IDs (in flight)
| ID | Task | Status | Notes |
|---|---|---|---|
| T-MGTM-138 | Cycle 2 — Patch _worker.js with real Airtable IDs from T-MGTM-135; remove skipIfPlaceholder flag | DN | 2026-05-07. Worker passes node --check. |
| T-MGTM-139 | Cycle 2 — Rebuild pcc-deploy-latest.zip v86 → v87 with patched Worker + DEPLOY_TS bump | DN | 2026-05-07. 490,088 bytes; 22 files; verified. |
| T-MGTM-137 | Cycle 2 — Gem deployed pcc-deploy-latest.zip v87 to Cloudflare Pages | DN | 2026-05-07. v87 deployed. Worker now serves HARMONY_CALENDAR via /api/boot. Phase 4 closed operationally. Note: schema-only, no UI surface — Cycle 3 follows immediately to add visibility. |
· Cycle 3 — Master GTM sidebar visibility + Phase 5 build (in flight)
| ID | Task | Status | Notes |
|---|---|---|---|
| T-MGTM-142 | Cycle 3 — Add Master GTM section to PCC sidebar (top of INTERACTIVE DOCUMENTS) with toggle + 6 active links + 4 placeholders | DN | 2026-05-07. sb-mgtm-item + toggleMasterGtmMenu(). Active: Spine, Phase Architecture, Channel Matrix, Harmony Calendar, Gate Register & Tempo Protocol, Cascade Execution Guide. Placeholders: Filter Card, Reef Briefing, Sub-GTM Framework, Operating Architecture. |
| T-MGTM-143 | Cycle 3 — Copy 4 Master GTM HTMLs into pcc-prototype/ with deploy-friendly slugs | DN | 2026-05-07. Spine, Phase Architecture, Harmony Calendar, Cascade Guide. |
| T-MGTM-144 | Cycle 3 — Convert Master GTM Channel Harmonisation Matrix XLSX → HTML with brand-compliant tabbed render | DN | 2026-05-07. 5 sheets, 28.7 KB, sticky header, hover row highlight. |
| T-MGTM-145 | Cycle 3 — Author Phase 5 Master GTM — Gate Register & Tempo Protocol v1.0.html | DN | 2026-05-07. 10-section doctrine, 26.7 KB, brand-compliant. |
| T-MGTM-146 | Cycle 3 — Copy Infographics/ folder into pcc-prototype/ so Spine HTML image refs resolve | DN | 2026-05-07. 5 PNGs ~28MB total — within Cloudflare 25MB per-file limit. |
| T-MGTM-147 | Cycle 3 — Bump index.html DEPLOY_TS v87 → v88 | DN | 2026-05-07. |
| T-MGTM-148 | Cycle 3 — Rebuild pcc-deploy-latest.zip v87 → v88 with 6 GTM HTMLs + Infographics folder + sidebar updates | DN | 2026-05-07. 27.7 MB; 33 files. |
| T-MGTM-149 | Cycle 3 — Gem deployed pcc-deploy-latest.zip v88 to Cloudflare Pages. Master GTM section visible in PCC sidebar. | DN | 2026-05-07. v88 deployed; Gem progressed to Phase 6 + landing-page UX request, confirming visibility worked. |
| T-MGTM-150 | Cycle 3 — Gem reviewed live Master GTM section; verified links and Infographics | DN | 2026-05-07. Verified — Gem moved forward with Cycle 4 / Phase 6. |
| T-MGTM-151 | Phase 5 follow-on — Author Master GTM — Gate Register & Tempo Protocol v1.0.docx canonical companion | NS | HTML shipped; docx parallel is formal canonical record per Cascade Methodology. |
| T-MGTM-152 | Phase 5 follow-on — Stephan ratification of Gate Register & Tempo Protocol v1.0 | NS | Required for Phase 5 to be canonical externally. |
· Cycle 4 — Master GTM hub landing page + shared in-section nav + Phase 6 Filter Card build (in flight)
| ID | Task | Status | Notes |
|---|---|---|---|
| T-MGTM-153 | Cycle 4 — Build Master GTM hub landing page (synopsis + 6-tier architecture + page grid with 7 active cards + 3 placeholder cards) | DN | 2026-05-07. Hub at /webgold-master-gtm-hub.html. |
| T-MGTM-154 | Cycle 4 — Build Phase 6 Filter Card v1.0 HTML — 5-section reference (8 tests, banned vocabulary, outcomes-led principle, run-procedure, two first applications) | DN | 2026-05-07. Phase 6 BUILD COMPLETE. |
| T-MGTM-155 | Cycle 4 — Inject shared mgtm-nav top bar into all 6 existing Master GTM pages | DN | 2026-05-07. Sticky black bar with orange accent, 11 link slots, current page highlighted. All 8 pages share nav. |
| T-MGTM-156 | Cycle 4 — Save canonical hub + filter-card copies to /Project Packages/.../Documents/ | DN | 2026-05-07. |
| T-MGTM-157 | Cycle 4 — Update PCC sidebar — Master GTM label → hub link; Filter Card → active; Hub link added in dropdown | DN | 2026-05-07. Click label opens hub; chevron toggles dropdown. |
| T-MGTM-158 | Cycle 4 — Bump index.html DEPLOY_TS v88 → v89 | DN | 2026-05-07. |
| T-MGTM-159 | Cycle 4 — Rebuild pcc-deploy-latest.zip v88 → v89 with hub + filter card + nav-injected pages + sidebar updates | DN | 2026-05-07. 27.7 MB; 35 files. |
| T-MGTM-160 | Cycle 4 — Gem deployed pcc-deploy-latest.zip v89 to Cloudflare Pages | DN | 2026-05-08. v89 deployed; Master GTM hub + in-section nav verified. |
| T-MGTM-161 | Cycle 4 — Gem reviewed live Master GTM hub + in-section nav | DN | 2026-05-08. Verified. |
| T-MGTM-162 | Phase 6 follow-on — Filter Card .pdf canonical companion (printable one-page reference) | NS | HTML version is shipped; PDF is print-ready/post-on-wall reference. |
· Cycle 5 — Phase 7 Reef Team Briefing build (in flight)
| ID | Task | Status | Notes |
|---|---|---|---|
| T-MGTM-163 | Cycle 5 — Build Reef Team Briefing v1.0 HTML (9-section explainer + embedded metaphor stack) | DN | 2026-05-08. webgold-master-gtm-reef-briefing.html. |
| T-MGTM-164 | Cycle 5 — Build Reef Team Briefing Deck v1.0 .pptx + .pdf rendition (11 slides) | DN | 2026-05-08. Brand-compliant. |
| T-MGTM-165 | Cycle 5 — Save canonical Reef Briefing copies to /Project Packages/.../Documents/ | DN | 2026-05-08. v1.0.html + v1.0.pptx + v1.0.pdf. |
| T-MGTM-166 | Cycle 5 — Update PCC sidebar — Reef Briefing flips from disabled placeholder to active link | DN | 2026-05-08. |
| T-MGTM-167 | Cycle 5 — Update mgtm-nav across 8 existing Master GTM pages — Reef Briefing flips to active link | DN | 2026-05-08. All 9 pages share 9-active-link nav. |
| T-MGTM-168 | Cycle 5 — Update Master GTM hub page card — Reef Briefing flips PENDING → LIVE | DN | 2026-05-08. 8 active page cards + 2 placeholders on hub. |
| T-MGTM-169 | Cycle 5 — Bump index.html DEPLOY_TS v89 → v90 | DN | 2026-05-08. |
| T-MGTM-170 | Cycle 5 — Rebuild pcc-deploy-latest.zip v89 → v90 | DN | 2026-05-08. 27.7 MB; 36 files. |
| T-MGTM-171 | → YOUR NEXT STEP. Cycle 5 — Gem deploys pcc-deploy-latest.zip v90 to Cloudflare Pages. After deploy: Reef Briefing accessible via sidebar OR via in-section nav from any Master GTM page; Hub card shows LIVE; .pptx deck in Project Packages folder. THEN: Phase 7 BUILD COMPLETE. Cascade resumes UPWARD at Phase 8 (Cascade Integration). Three Phase 7 briefing sessions remain (T-MGTM-069/070/071) — schedule when convenient. | NEXT | Human-driven. |
| T-MGTM-172 | Cycle 5 — Gem reviews live Reef Briefing page + opens .pptx deck | NS | Cycle 5 success confirmation. |
· Cycle 6+ — future cycles will be triggered by:
/gtm/filter/gtm/sub-gtms/<service-line>A new cycle row block gets added each time. Pattern stays: code change → zip rebuild + version bump → Cloudflare deploy.
These tasks fire ONCE — at the very end, when every other phase + sub-GTM + cross-cutting task is DN. They are NOT recurring; they are the cascade-complete declaration.
| ID | Task | Status | Notes |
|---|---|---|---|
| T-MGTM-125 | Final brand-compliance-check pass across ALL Master GTM artefacts (Spine, Cascade Guide, Phase Architecture, Channel Matrix, Calendar, Gate Register, Filter Card, Reef Briefing, Operating Architecture, all sub-GTMs) | NS | Fires only after every Phase ships and every sub-GTM lands. |
| T-MGTM-126 | Final Closure Roadmap update declaring cascade complete; lock canonical versions of Spine and Cascade Execution Guide | NS | Closure act paired with T-MGTM-086 (final File Creation Log entry). |
| T-MGTM-127 | Memory file final update — mark Master GTM cascade complete in project_master_gtm_cascade.md | NS | Memory hygiene at cascade close. |
| T-MGTM-128 | Spine HTML caption audit — rewrite captions on 5 infographics to match Claude Design renders | DN | 2026-05-07. §1 ecosystem refreshed; §1 timeline expanded; §4 four-positions rewritten; §5 unchanged; §11 J-curve expanded. |
/Project Packages/Webgold Master GTM/Documents/.