An index over the canonical RegScale marketing material. Not new content — a wayfinding overlay so the right doc is one click away when you have a real task in front of you.
What this is: three cuts of the same material. The stack shows architecture top-to-bottom (Seed corpus → L1 Foundations → L2 Campaign → L3 Event → SOPs → Chains → MCPs → Live execution). The ribbons show what cuts across every layer (Voice, Proof Points, Roles, Vocabulary, Asset Specs). The operator lookup answers "I need to do X — where do I look?" in one click. How to use it: skim the stack to orient; scan the ribbons to see what touches everything; jump to the lookup when you have a specific task. Every link goes to the canonical Monday Doc, the kit zip path, or a live URL.
Each layer's outputs become the next layer's inputs. Lower layers are durable; higher layers are event-specific.
The RegScale marketing chain is a commission stack: each layer commissions deliverables that feed the next. Layer 1 is durable (changes with strategy resets, not with campaigns). Layer 2 is campaign-overlay (changes per campaign). Layer 3 is event-instance (changes per event). The SOP layer sits below — it's the operational machinery that turns layered inputs into shipped assets. Chains compose SOPs. MCPs integrate with external tools. The live execution layer is where it all materializes — Monday's AI Integration workspace + this published handoff kit.
Eight input streams feed the chain. Most are not authored by the team — they're discovery artifacts, market research, contract documents. Touch this layer when you need to trace why a positioning claim or persona definition exists.
Two parallel research tracks (L1a Auto-GTM = 30-node AI-driven pipeline; L1b methodology-driven = curated inputs) produce parallel hypotheses, then a human-reviewed Reconciliation merges them into the canonical Layer 1. Touch this layer when you need to verify ICP, persona definitions, positioning, or messaging pillars.
20291879Layer 2 takes Layer 1 reconciled outputs and adds campaign-specific overlays: a messaging playbook (positioning + proof points + segment language), a campaign execution plan (planning function + open questions), a measurement framework (KPIs + attribution), and a Content Bill of Materials (canonical 6-section structure). One Layer 2 instance per campaign.
Layer 3 receives a human-reviewed handoff from Layer 2 and decomposes into five operational streams per event. This is where the chain actually runs — every Monday subitem you own probably points at a Layer 3 artifact for a specific event.
This is where the chain becomes operational. The Webinar Lifecycle SOP is the spine (SW-00 through SW-05). Three siblings are called from the spine at specific SW boundaries. Two gates run at every drafting moment (substance first, then style). One cross-cutting SOP runs in parallel. One infrastructure SOP backs every Monday board operation. One extension suite (Asset Specs) extends V7's three-artifact codification with an artifact-layer triple. All are addressable in Monday or in the kit zip.
Webinar Lifecycle SOP
6-phase pipeline (SW-00 → SW-05) with 6 quality gates (QG-0 → QG-5). FedRAMP 20x is the worked example; FS-ISAC FY27 is the live demo.
Campaign Brief → Multi-Asset Production
Called by Webinar Lifecycle at SW-01 (Brief Intake), SW-02 + SW-03 (Asset Drafting + Cross-Asset Consistency), SW-05 (Publish Handoff). The asset-bundle author.
Speaker Session Lifecycle kit only
Called when there's an internal speaker (Esty/Travis pattern). Active at SW-04 (Day-of Speaker Prep) and SW-05 (Post-Session Repurposing).
GTM Messaging Book Stewardship kit only
Called at every drafting boundary. Validates that claims align to canonical positioning + the 14 verbatim proof points. Substance review precedes style review per Brand Voice SOP Key Rule.
GTM Messaging Book (proximate source) · kit/sops/gtm-messaging-book-stewardship/
Brand Voice Stewardship
5 voice principles + forbidden words + CCM substitution gate. SW-01 Voice Review = Quick-Scan or Full-Depth. Esty is gatekeeper; Morgan is backup.
Status Update Cadence kit only
Default ad-hoc, event-driven; scheduled checkpoints when drift would be costly. The cadence that should have caught the cancelled FedRAMP 20x post-event Report & Review.
Board Creation & Schema Management
Standardized schema families. Canonical create-and-move pattern. Runs behind every Monday board operation — you don't invoke it directly, but you depend on it whenever you create a new event sandbox.
Asset Specifications Library
Each asset type = (schema.json, template.<ext>, README.md) triple. Extends V7's three-artifact codification with an artifact-layer spec triple. Promotional email + speaker deck are the two worked examples.
The Master Chain Definition locks three chain demos that show how the SOP suites compose. Chain 1 is the primary workshop demo (FedRAMP 20x past + FS-ISAC FY27 live). Chain 2 scales the same suites to a Tier 1 event (Gartner SRS 2026). Chain 3 traces the same SW activations through the integration layer (MCPs).
20275905 · Strategic Brief + 11 sibling artifacts (full lifecycle worked example)Per V7's transparency commitment, integrations are explicitly labeled. Confirmed live means Daniel demonstrated the workflow against the actual RegScale instance. Representative means the workflow shape was demonstrated and the integration is flagged as a target for follow-on work. Touch this layer when you want to extend automation beyond what's currently wired.
All canonical artifacts converge in Monday workspace 15179515 ("AI Integration"). Structure mirrors the workshop learning path. The handoff kit you're reading is published at regscale.elynox.ai via Cloudflare Pages — the same publish path the workshop demoed.
15179515 · ~55 client-facing docs (per v2 commission stack)Five concerns intersect every layer of the stack. They are the constant constraints under which every artifact is authored, gated, and shipped.
5 principles · forbidden-words list · CCM substitution gate · paired-gate architecture
What it is: the style filter every external-facing asset must pass. Five voice principles per the Brand Voice SOP: (1) category-defining; (2) practitioner-grounded; (3) proof-pointed with verbatim metrics; (4) system-specific, not framework-specific; (5) headless / invisible compliance. Plus a hard substitution gate: "Continuous Controls Monitoring (CCM)" — never "Continuous Compliance Monitoring" (auto-fail show-stopper).
Lands here: SOP — Brand Voice Stewardship · kit/voice/ (SW-00 Apply, SW-01 Review, Quality Rubric, Voice Pass Template).
Touches: every drafting moment in Layers 2, 3, SOP, Chain. Voice review (SW-01 Quick-Scan) runs at every asset's gate. Esty is gatekeeper; Morgan is backup.
14 verbatim metrics · enforced as JSON Schema enum · paraphrasing = auto-fail
What it is: 14 specific, enumerated metrics in the canonical Register (numbered 1–14) that Cowork can use verbatim and only verbatim. Voice-acceptable short forms (per Brand Voice SOP Key Rule 8): "FedRAMP High in 90 days vs. 12–18 months" · "60% audit prep reduction" · "8x faster control writing" · "10x staff productivity" · "~$200,000 per-ATO cost savings". Paraphrasing is a substance-gate auto-fail (Messaging Book SW-02 catches it; the asset-spec schema enforces an enum constraint on proof_points_used_verbatim).
Lands here: Proof Points Register (canonical) · also enumerated in every Asset Spec schema as a JSON Schema enum.
Touches: every claim-bearing asset in Layers 2, 3, SOP. Substance gate (Messaging Book) checks proof-point usage before voice gate runs.
FY26 holders · slot mapping · gatekeeper + backup chain
What it is: the canonical FY26 role registry. Six slots in the workshop demo cadence (Slot 1 = Esty Peskowitz / VP of Marketing / Brand Gatekeeper; Slot 2 = Amanda Greenspan-D'Souza / Field Marketing Operations; Slot 3 = Elyse Hoekstra / Paid Media Contractor; Slot 4 = Morgan Johnson / Brand & Design Lead + backup gatekeeper; Slot 5 = Brittany Gleason / Field Marketing Lead; Slot 6 = Alex White / PMM Lead). Plus supporting roles (Travis Howerton CEO, Jon Collette MarOps, Hong Diaz Web, Dave Waltermire SME, Gabrielle Hovendon Social, Daniel @ Elynox Engagement Lead).
Lands here: Role Holders FY26 · canonical Monday Doc.
Touches: every action in every layer. Every Monday subitem owner is one of these holders.
Pillar IDs (P1–P5) · persona IDs · CCM term · sector terminology · non-negotiable language
What it is: the terminology layer. Pillars are referenced by ID (P1 Speed · P2 Real-Time Visibility · etc.) so Cowork can pick deterministically. Personas have stable IDs. The CCM term is non-negotiable. Sector terminology (Federal/PS, FinServ, etc.) maps to ICP segments.
Lands here: GTM Messaging Book · Messaging Playbook · plus the substitution gate enforced in Brand Voice SOP.
Touches: every artifact in every layer. Wrong vocabulary = substance-gate fail.
Schema + template + README triples · deterministic hydration via Cowork
What it is: per-asset-type specifications stored as (schema.json, template.<ext>, README.md) triples. A populated JSONB instance conforms to the schema and hydrates the template. Two worked examples shipped: promotional-email + webinar-speaker-deck. 18 more stubbed for post-workshop population.
Lands here: SOP — Asset Specification Library · kit/specs/ (each asset type in its own directory).
Touches: every render moment in SOP layer. Asset specs are the bridge between data (JSONB) and finished assets.
For each common task, the spine layer it lives in, the ribbons that activate, and the canonical first-look location.
Rule of thumb: if your answer needs more than one click, the canonical isn't where you're looking. Every artifact in this table has a one-click destination. The Cowork chain orchestrates the rest — orientation prompt loads layers, pull-and-execute prompt runs the SOP, voice review runs the gate.
| I need to… | Spine layer | Ribbons | Where to look first |
|---|---|---|---|
| Kick off a Cowork session | Prompt chain | voiceproofvocab | kit/prompts/01-orientation-chain.md → 02-pull-and-execute.md. Or: Cowork Session Orientation (Monday canonical entry-point). |
| Write a promotional email | L3 + SOP SW-03 | voiceproofspecs | Asset Specs SOP → specs/promotional-email/ (worked example). Hydrate the JSONB; SW-03 Promotion Campaign for the spine context. |
| Write a landing page | L3 + SOP SW-02 | voiceproofspecs | SW-02 Landing Page & Registration. For canonical worked example: FS-ISAC Landing Page Copy. Cowork capstone publish: kit/prompts/04-cloudflare-capstone.md. |
| Gate an asset (Voice Review) | SOP layer | voiceproof | Brand Voice SOP §SW-01 Voice Review. Substance review (Messaging Book) runs FIRST; style review (Voice) runs SECOND. Esty = gatekeeper; Morgan = backup. Quick-Scan ≤ 2 minutes. |
| Brief a campaign | L2 + SOP SW-01 | voiceproofvocab | SOP — Campaign Brief to Multi-Asset. Pick from L1 menus (ICP/Persona/Pillars). Worked examples: SANS · FS-ISAC FY27. |
| Plan an event commitment | L3 + SOP SW-00 | rolesvocab | SW-00 Commitment & Tier Classification. Create parent on Active Marketing Programs. Schema via Board Creation SOP. |
| Publish via Cloudflare | SOP SW-02 + MCP | specs | kit/prompts/04-cloudflare-capstone.md. Confirmed live: regscale.elynox.ai + workshop landing page. See SW — Content CI-CD (Monday-prod variant) for the pattern. |
| Run promotion cadence | SOP SW-03 | voiceproof | SW-03 Promotion Campaign. Cadence template: Template — LinkedIn Promotion Cadence. Worked example: SANS — SW-03 Promotion Campaign Kit. |
| Run day-of execution | SOP SW-04 | roles | SW-04 Day-of Execution. FS-ISAC FY27 worked example: Day-of Execution Trace. |
| File a post-event Report & Review | SOP SW-05 (QG-5) | roles | SW-05 Follow-Up & Repurposing. QG-5 is non-negotiable — the FedRAMP 20x R&R was cancelled and is the canonical failure mode. Template: FS-ISAC FY27 Post-event R&R. |
| Status-update cadence / drift check | Status Update Cadence | roles | kit/sops/status-update-cadence/. Default: ad-hoc, event-driven; scheduled when drift would be costly. (SOP not yet pushed to Monday.) |
| Add a new asset type | Asset Specs ribbon | specs | Asset Specs SOP → Standard Work — Authoring an Asset Specification (in kit/specs/). Use Template — Asset Specification as the meta-template. |
| Find canonical positioning / ICP / personas | L1 Foundations | vocab | Layer 1: Foundations folder · ICP · Personas · Positioning. Reconciliation report: GTM Foundations Reconciliation Report. |
| Onboard a new role-holder | Roles ribbon | roles | Role Holders FY26. Then point them at Cowork Session Orientation + the kit zip + this map. |
| Validate a chain end-to-end | Chain layer | specs | Chain 1 Sandbox folder · 20275905 (FS-ISAC FY27 — full lifecycle exemplar, 12 artifacts). Or Workshop Sandbox board (April 29 Movement-2 7-slot run). |
Three escalation paths if the lookup table doesn't resolve your question fast enough.
Open kit/sops/_chains/Master Chain Definition.md. It traces every SW activation across the chain; find the trigger that matches your situation, follow the SW-ID to the canonical SOP.
Or, faster: paste kit/prompts/02-pull-and-execute.md into Cowork with your Monday subitem URL. Cowork reads the SOP link in the subitem's description and executes — you don't have to know which SOP applies.
Open Role Holders FY26. Match the work type to the FY26 role; the holder for that role is your point of contact. If the work touches gates: Esty is gatekeeper; Morgan is backup.
If the work is an event commitment, the parent owner on the Monday item is the canonical owner. Check the Active Marketing Programs board.
Check the layer it should be at. Layer 1 canonicals live in folder 20291879 (Layer 1: Foundations). Layer 2 + L3 live per-event. SOP canonicals live in the AI Integration workspace root. If a doc is in _archive folder 20258266, it's archived — don't link to it.
If it's not in Monday at all: it might be a kit-only artifact (Speaker Session Lifecycle SOP, Status Update Cadence SOP, GTM Messaging Book Stewardship SOP — flagged with the kit only tag in this map).