A translation card scoped to what the April 29 workshop conveyed. Bridges your everyday phrasing into the seven canonical concepts the workshop deliberately introduced.
What this is: a translation card for what the workshop introduced. The kit zip ships four reference artifacts: the v6 motion proposal (the why), the commission stack diagram (the architecture), the workshop walk (the 120-min pacing), and the webinar suite SPA (the output). v6 explicitly defines seven concepts — Codified workflow · SOP · Standard Work · Quality Rubric · Cowork · Hub · Connector — plus the pull / run / push cycle. How to use it: when you re-read v6 or the recap and a term confuses you, scan the bridge table; when someone uses a term in conversation and you want the precise meaning, jump to the seven anchors. Every link goes to a Monday Doc or to the OneDrive kit zip.
Left column draws from how you phrased things in the April 29 workshop and recap session. Right column draws from v6's seven canonical terms or directly from the kit + Monday workspace.
| What you said | Workshop concept | Where it actually lives |
|---|---|---|
| "the webinar kit" · "the kit" · "that zip file with all the webinar kit" | The cowork kit zip | A bundle of all four reference artifacts plus the Cowork prompts, the Asset Specs, the voice/proof-points/role files. Drop it onto Cowork to give the session everything it needs in one go. regscale-webinar-cowork-kit.zip |
| "the AI" · "Cloud" · "Claude" (used interchangeably in recap) | Cowork | The personal AI workspace with the kit loaded — not vanilla Claude.ai. v6's term for "the AI when it has been given the kit." Canonical entry-point doc: Cowork Session Orientation. |
| "orient it" · "kick it off with the orientation prompt" | PULL — the orientation chain | First Cowork prompt of any session. Loads Layer 1 (Foundations) → Layer 2 (Campaign frame) → Layer 3 (Event instance) into the session. ~5 min. Cowork Session Orientation · kit/prompts/01-orientation-chain.md |
| "go get this task and do the landing page" · "point it at any task" | PULL + RUN — the pull-and-execute prompt | Second Cowork prompt. Pulls a Monday subitem, follows the linked SOP, drafts the asset, runs the substance + voice checks. Same prompt for every campaign. kit/prompts/02-pull-and-execute.md |
| "tasks" · "the tasks queued up to be done" | Monday subitems in the Hub | Each subitem on a board carries the Asset Draft column, the Asset Files column, the Workshop Status column, and a SOP link in its description. Cowork operates on these as units of work. The Hub is canonical state. |
| "the sandbox" · "workshop sandbox" · "that board" | Workshop Sandbox board (the day's Hub) | Where Cowork wrote its outputs on April 29. Six subitems pre-staged (one per slot). Workshop Sandbox board (18410736703) · slot-by-slot work captured in Workshop Assignments. |
| "the SOP process" · "my SOP codification process" · "the standard work" | Codified workflow | v6's term for "the three linked artifacts that make a workflow run reliably": SOP (the steps) + Standard Work (the shape of the output) + Quality Rubric (the checks). Walked in detail in P3 of the workshop. Concept doc: Codification Framework — Concepts. |
| "60-day look back" · "post-event reporting" · "reporting look back" | SW-05 of the Webinar Lifecycle (QG-5 closure) | SW-05 Follow-Up & Repurposing. The chain doesn't close on the day of the event — it closes when the lessons are filed. QG-5 is the gate that prevents the FedRAMP 20x failure mode (post-event Report & Review cancelled in March 2026; the canonical failure described in Master Chain Definition). |
| "the form connected to a campaign" · "submissions tied to campaigns, which then feed into Salesforce" (Esty) | Connector pattern (HubSpot form ↔ HubSpot Campaign ↔ Salesforce Campaign mirror) | v6's term for "the wiring that lets a Cowork session reach into one of your tools." Connectors are Confirmed live (Monday + Cloudflare) or Representative (HubSpot, WPEngine, Salesforce, M365). The form-to-campaign-to-CRM flow is a Representative pattern. Reference: Master Chain Definition § Chain 3. |
| "Cloudflare process" · "the Cloudflare connector" | Connector — Cloudflare Pages (Confirmed live) | The capstone publish path Daniel demonstrated in P5. Pushes a rendered landing page to a public URL. This handoff kit is published the same way. Reference: Master Chain Definition § Chain 3 (Confirmed-live row) · kit/prompts/04-cloudflare-capstone.md. |
| "WordPress" · "WP Engine" | Connector — WPEngine (Representative) | The current production landing-page platform. Workflow shape demonstrated; instance staging-environment to be assessed. Esty in the recap: "we haven't explored WordPress connector yet." Reference: Master Chain Definition § Chain 3. |
| "the deck" · "the slides" · "slide 9" | Speaker session deck (Slot 4 in P4) | Morgan Johnson's slot on April 29 produced one slide of a SANS speaker deck (slide 9 — the Why-Us proof). Asset Spec triple lives in the kit: kit/specs/webinar-speaker-deck/. Authoring procedure governed by SOP — Asset Specification Library. |
| "Movement 2" · "Movement 3" | P4 / P5 in the v2 workshop walk | The v2-workshop-walk diagram (in the kit zip) re-frames Movements 1–4 as six phases P1–P6. Movement 2 ≈ P4 (Run it). Movement 3 ≈ P5 (Why · Capstone · Horizon). See section ④ below for the full P1–P6 mapping. kit/v2-workshop-walk.html |
| "Gartner event" (Esty) | Chain 2 anchor — Gartner Security & Risk Summit 2026 | Tier 1 event. Per Master Chain Definition: same six SOP suites as a webinar but scaled wider — multiple speaker sessions in parallel, multiple campaigns, daily status cadence T-7 → T+3. "The chain gets wider, not deeper." Master Chain Definition § Chain 2. |
| "FedRAMP 20x" (the cancelled one) | Chain 1 worked-example anchor · canonical failure mode | The completed Nov 19, 2025 webinar with CSA + Carahsoft. Post-event Report & Review was cancelled in March 2026 — the canonical failure the populated SOPs exist to prevent. Full timeline + team + failure-mode write-up in Master Chain Definition § Chain 1 worked-example anchor. |
Lifted verbatim from the v6 motion artifact's "Vocabulary used in this proposal" section. These are the seven words the workshop deliberately put in the room.
Hover any term in v6 itself to see the same definition inline (the dotted-underlined terms). v6 is in the kit zip — kit/v6-ai-native-gtm-motion.html.
A workflow written down all the way — the steps, the shape of what gets produced, and the checks that say it's ready to ship. Three linked artifacts: an SOP, a Standard Work, and a Quality Rubric.
Where it shows up in your work: any time someone says "the SOP process" or "the codified approach." Concept walked in P3 of the workshop. Reference: Codification Framework — Concepts.
The steps. "Do this, then this, then this. Hand off here." The instructions a teammate could follow tomorrow without losing fidelity.
Where it shows up in your work: the Webinar Lifecycle SOP suite (master + 6 SWs + Quality Rubric) governs every webinar. Master: SOP — Webinar Lifecycle.
The shape of the output. The sections a brief always carries, the fields a campaign always includes — the structure that makes deliverables consistent every time they're produced.
Where it shows up in your work: SW-00 through SW-05 inside the Webinar Lifecycle SOP. Each SW defines the shape of one phase's output. Example: SW-01 Strategic Brief.
The checks. Must-haves before something ships, things that should be done, and things that may be considered. The gate between a draft and a deliverable.
Where it shows up in your work: every SOP suite carries one. The Webinar Lifecycle Quality Rubric is the most-used in this kit. Reference: Quality Rubric — Webinar Lifecycle.
A personal AI workspace — where each team member would draft, review, and run codified workflows in this proposed model.
Where it shows up in your work: drop the kit zip onto Cowork; paste the orientation prompt; paste the pull-and-execute prompt. Cowork session canonical entry: Cowork Session Orientation.
The Monday workspace where shared state would live: codified workflows, references, work in flight, approvals. The single source of truth in this design.
Where it shows up in your work: AI Integration workspace. Cowork pulls from here at session start; pushes back here when work completes.
The wiring that lets a Cowork session reach into one of your tools. Confirmed live for this engagement: Monday and Cloudflare. Demonstrated as representative patterns in the workshop: HubSpot, WPEngine, Salesforce.
Where it shows up in your work: any time Cowork moves a Monday item, publishes a page to Cloudflare, or — on the representative side — talks about hooking into HubSpot or WPEngine. Reference: Claude Cowork Tool Integration Patterns — MOC · Master Chain Definition § Chain 3.
Every Cowork session moves work through three stages, illustrated in v6 against the strategic-brief moment of the webinar lifecycle. About 30 minutes from sit-down to brief-on-the-Monday-item-with-check-records-attached.
Cowork pulls the relevant context from the Hub — the Monday item, the partner agreement, the audience segment, prior briefs, the proof points, the voice guide. None of it has to be re-explained.
The codified workflow runs. The SOP defines the steps. The Standard Work defines the format. The Quality Rubric defines what "ready to ship" looks like. The substance check runs first, then the style check.
The result goes back to Monday: the draft and the check records. The item state advances. The next person in the chain pulls that as input and runs the next workflow.
From the v2 workshop walk diagram. When someone says "in P3 we saw…" or "the run-it part," this is the canonical reference.
Each slot subitem on the Workshop Sandbox board carries the actual asset that was produced live during P4 / Movement 2.