M-07: ainativeshift.com Launch — Convergence Destination Activation

← Back to Operating Procedures ainativeshift-launch.md

title: "ainativeshift.com Launch — Convergence Destination Activation" process_id: M-07 owner: V (COO, orchestration) — Marquee (Media BU production) — Sage (CCO, journey concierge wiring) — Provost (Academy BU cohort) — Trellis (Collective BU practitioner channel) domain: media + program + platform-consolidation risk_tier: 1 verification_rigor: "Tier 1 — Critical Pipeline (production-touching, multi-system, multi-BU, non-recoverable substrate)" version: 1.0 last_updated: 2026-05-25 status: "Draft (Wave 4 verification artifacts in hand; Episode 1 not yet streamed — re-promote per-step after Tuesday 2026-05-26 closure)"

M-07: ainativeshift.com Launch — Convergence Destination Activation

Owner: V (orchestration) + Marquee (Media) + Sage (Customer) + Provost (Academy) + Trellis (Collective). Q owns this procedure. Risk Tier: 1 (Critical) Last Audited: 2026-05-25 (Marshal PRD DoD audit + Q operating-procedure authoring pass) Verification Score: 56.4% (22 VERIFIED / 39 applicable steps; 4 NOT BUILT excluded; 13 UNTESTED pending Tuesday 2026-05-26 stream and rolling-completion Tue–Fri) Status: Draft — NOT OPERATIONAL (Wave 4 of 9 still rolling; J/K post-stream tracks intentionally UNTESTED until Tuesday) Next Audit: 2026-05-29 (post-launch closure audit, end of rolling-completion window) → recurring per-launch cadence per "Triggering events" below

Purpose

This procedure governs the one-time + recurring activation of ainativeshift.com as the public convergence destination for the Value-First platform. It codifies the workflow that ratified the 5P → PRD → 9-wave execution model on 2026-05-24 → 2026-05-26, distinguishing it from show-launch.md (AOM/TRTU single-show pattern) on three axes:

  1. Multi-BU activation, not single-show launch. Media (daily show), Academy (AINS cohort + Course substrate), Collective (practitioner channel), Sage Customer Org (11 journey concierges), Pax Finance (cross-BU commerce), Store (Commerce Hub product records) — all wired Day 1.
  2. Convergence destination, not standalone site. Every Nov 2025+ platform surface (valuefirstteam.com, AOM, TRTU, chriscarolan.com, valuefirstagent.com, valuecreationprotocol.com, media.valuefirstteam.com, compass.valuefirstteam.com) routes into or references ainativeshift.com.
  3. Design-system harmonization, not per-site brand. @vf/design-tokens monorepo package is published Day 1 from ainativeshift; existing sites migrate as separate tracked work.

This procedure is reusable: the next daily-show + program launch (Wave 5+ of the same model, or an analogous convergence destination), recurring weekly substrate operations, and per-episode post-stream pipeline all reference back to this canon.

What would be lost if this procedure stopped: the convergence destination would atrophy into a single-show standalone site (AOM/TRTU pattern), the 11 journey concierges would not respond to public-site signals, the daily-show + cohort commerce loop would break, and the multi-BU platform posture (S-3c) would regress to a fragmented surface.

Trigger

This procedure runs when:

  1. Convergence Session ratifies a new GTM superhighway destination (e.g., the 2026-05-24 → 2026-05-25 Convergence Session #1 that produced this launch). The 5P + PRD pair is the ratification artifact.
  2. Daily-show + AINS-program convergence requires a new public destination (e.g., follow-on cohort launches that re-anchor the destination).
  3. Weekly operational rhythm post-launch — Steps in Phase 8 (post-stream pipeline) and Phase 9 (rolling completion + signal monitoring) re-run per episode and per week. The procedure remains canonical for the recurring shape.

Initial invocation date: 2026-05-25 (Monday) for Episode 1 launch Tuesday 2026-05-26.

Scope

In scope

  • ainativeshift.com site build (Astro 5 + Tailwind + React on Vercel Chris Carolan scope) per Perplexity blueprint sitemap
  • HubSpot CRM substrate writes (Series + Episode Listings, Course, Marketing Event, Product, Subscription, Daily Brief draft, Interest pipeline taxonomy, Contact properties) via Ledger gateway
  • Sanity substrate writes (show document, aiNativeShift schema deploy, Episode 1 document with deterministic ID, methodology cross-refs) via Canon gateway
  • Media production pipeline activation for Tuesday Episode 1 (apps/media → Mux WHIP → YouTube @Value-First + LinkedIn Live chris-carolan)
  • 11 journey concierge wiring + 5 signal-intelligence agents (Sage's Customer Org full S-2c reading)
  • Cross-platform consolidation (cross-links across 9 Nov 2025+ surfaces) via Showcase for public surfaces, Canon for Sanity writes
  • Design-system harmonization (@vf/design-tokens monorepo package)
  • Post-stream content pipeline (Splice → Encore → Vigil → Baldwin → Canon → Catalog → Vault → Broadcast/Chorus/Link/Correspondent)
  • Operating-procedure codification (this document) + HubSpot Listing publication via Ledger
  • Memory capture via Archivist + pattern memory via Echo

Out of scope (Chris-owned UI work)

  • HubSpot Marketing Hub Podcast UI configuration (Apple/Spotify/Google/iHeart/Amazon distribution platform submissions)
  • HubSpot Forms creation, styling, and embed (Marketing Hub UI)
  • HubSpot Marketing Email workflow wiring (Daily Brief send activation)
  • Marketing Event embed (calendar + form on /shift/activation)
  • Contact-lifecycle UI workflows beyond the v4 flows API surface
  • Local NVENC relay verification on VFT-CommandCtr pre-stream
  • LinkedIn Live confirmation + archive checks (Chris confirms reception on chris-carolan personal account)
  • External counsel review of cohort terms ($24,995 + $8,000 caps), sponsor agreements, podcast distribution rights, guest releases (Writ produces the draft; counsel is external)

Out of scope (separate procedures)

  • Per-episode publishing from Episode 2 onward — docs/operating-procedures/episode-publishing.md
  • AOM/TRTU single-show launch pattern — docs/operating-procedures/show-launch.md (90% verified, the precedent procedure)
  • HubSpot Write Operations gateway mechanics — docs/operating-procedures/hubspot-write-operations.md (S-01, 68% verified)
  • Media production lifecycle mechanics — docs/operating-procedures/media-production.md (M-01, 25% verified)
  • Daily Operations Rhythm — docs/operating-procedures/g-01-daily-operations-rhythm.md
  • Sanity CMS Write Operations (S-02, no procedure yet)

Inputs

  • docs/plans/ainativeshift-launch-5p-plan.md (5P plan, committed 2026-05-25, commit 06b6846c1)
  • docs/plans/ainativeshift-launch-prd.md (PRD, committed 2026-05-25)
  • Perplexity AI-Native Shift blueprint Parts I + II + III + IV + V + VII + IX (content + sitemap + AEO + production rotation + attribution)
  • Convergence Session #1 ratifications (2026-05-24 → 2026-05-25 with Chris Carolan)
  • Leadership Meeting #7 ratifications (2026-05-24 — two-superhighway architecture, Gate 2 Course schema, Marketing Event + Product task 819a39a0)
  • Sanity shared dataset (0efm0pow / production) existing schemas: show, episode, coreBelief, valuePathStage, trap, course, contributor
  • HubSpot portal 40810431 (VF Team) — Content Hub Enterprise + Sales Pro + Marketing Hub + full Object Pass substrate (Task + Service deployed 2026-05-24)
  • Tron:Ares design system (existing VFT website) + Compass design language (V2 platform) — harmonization source
  • AOM + TRTU + chriscarolan.com + valuefirstagent.com + valuecreationprotocol.com + media.valuefirstteam.com + compass.valuefirstteam.com (Nov 2025+ surfaces requiring cross-link consolidation)
  • Wave artifacts in /mnt/d/AI-WORKSPACE/ainativeshift/ (content-blocks, methodology-reference, diagrams, legal, design-tokens-advisory, mirror/lookout/waypoint/audit/director/prelude reports, course-schema spec + methodology review)

Outputs

  • Live site at https://ainativeshift.com with full sitemap returning 200 (per Perplexity Part I)
  • Sanity show-ai-native-shift document + episode-ai-native-shift-2026-05-26 document with finalized show notes (post-stream)
  • HubSpot Series Listing + first-week Episode Listings + Course record + Marketing Event + Product records + Subscription + Daily Brief Marketing Email DRAFT + 8 Contact properties + 12 Interest enum values + Project 558488899232 on Agent Operations pipeline 888442804 with 85 Tasks
  • 11 journey concierges operational against live portal (per-concierge synthetic test passes with cleanup)
  • @vf/design-tokens monorepo package published and imported by ainativeshift
  • Cross-platform cross-links from 9 Nov 2025+ surfaces into ainativeshift.com
  • Episode 1 Mux asset linked to Sanity (no orphan), Gemini transcription within 24h, finalized show notes, Content Vault index, LinkedIn launch posts, network email, Daily Brief first issue
  • This operating procedure published to HubSpot Listing (listing_content_type: document, document_type: operating_procedure, document_authors: q)
  • Memory files project_ainativeshift_launch.md + reference_ainativeshift_substrate.md + MEMORY.md index entry (Archivist)
  • Echo pattern memory captured post-Episode-1
  • Operating-procedure Listing referenced from process register entry M-07

Dependencies

Dependency Where it lives Why it matters
Ledger (HubSpot write gateway) .claude/agents/ledger.md + skills/hubspot-write-gateway/ Sole authority for CRM mutations. Every C-track step (Series, Episodes, Course, Marketing Event, Products, Subscription, Daily Brief, Interest taxonomy) routes through Ledger.
Canon (Sanity write gateway) .claude/agents/canon.md + skills/sanity-content/ Sole authority for Sanity mutations. Show + episode + cross-platform-link patches route through Canon.
Showcase (public-site builder) .claude/agents/showcase.md + skills/public-site-building/ All ainativeshift.com pages + cross-platform link writes on valuefirstteam.com, AOM, TRTU, chriscarolan.com, valuefirstagent.com
Squire (repo + Vercel + DNS) .claude/agents/squire.md + skills/repo-and-vercel-provisioning/ Repo provisioning + Vercel project on Chris Carolan scope + vercel git connect + @vf/design-tokens package provisioning
Director + Prelude + Slate + Splice + Encore + Vigil Media BU agents (skills/media-*) Mux WHIP fan-out to YouTube + LinkedIn, pre-episode validation, post-stream asset link, orphan detection, 24h transcription SLA
11 journey concierges (Courier, Spark, Tether, Litmus, Leaf, Sylvan, Vestibule, Patron, Accord, Usher, Conductor, Alms) + 5 signal-intelligence agents (Meridian, Tide, Sentinel, Scout, Herald) Sage's Customer Org (skills/journey-design/, skills/ans-journey-concierge/, skills/proactive-relationship-monitoring/, etc.) Visitor signals from ainativeshift.com flow into Interest progression and route into Sage's Customer Org
Property-index discipline (Path-B verified) skills/hubspot/property-index/*.json + wiki/conventions.md § HubSpot data conventions Every new HubSpot property requires live-GET evidence in the same session before write; no intended-state writes
Customer-facing prose hygiene skills/enforcement/customer-facing-prose-hygiene.md + memory/pattern_internal_agent_prose_leakage.md No codenames, internal paths, AI-org-chart taxonomy in user-visible copy on ainativeshift.com or in customer-facing HubSpot/Sanity properties
Auto-commit + push for build/deploy memory/feedback_auto_push_builds.md Showcase/Squire commit + push without asking; Vercel is the test environment per memory/feedback_no_local_build_gates_in_briefs.md
vercel git connect not assumed memory/feedback_vercel_link_does_not_auto_deploy.md vercel link does NOT wire GitHub auto-deploy; explicit vercel git connect required
Vercel account per-property memory/reference_vercel_valuefirstagent.md ainativeshift.com is on Chris Carolan scope (chriscarolan-conveyingyous-projects), NOT unified-support-solutions. Misroute caused TRTU full-project migration
Central Time canonical memory/feedback_central_time_canonical.md Episode times, Activation Workshop slots, Daily Brief send time = America/Chicago. Epoch-ms via date -d "..." +%s%3N per memory/feedback_compute_epochs_via_bash.md
No nested subagent spawning memory/feedback_no_nested_subagent_spawning.md Only main-session V invokes Agent tool. Marshal-as-subagent is peer planner, never dispatcher
Created-by-agent stamping wiki/agent-guide.md § Codename stamping Ledger stamps "ledger" on all HubSpot writes regardless of initiator. Canon stamps "canon" on all Sanity writes

Roles

Role Agent / Person Scope
Orchestration lead V (COO) Dispatches all waves, synthesizes specialist returns, persists 5P + PRD + this operating procedure, owns convergence-session ratification capture
Customer Org lead Sage (CCO) Concierge coordination, signal-recognition framework, customer-experience oversight across the 11 journey concierges + 5 signal-intelligence agents
Finance Org lead Pax (CFO) Cross-BU commerce + capacity-aligned commitment for cohort + sponsorship revenue lines
Media BU lead Marquee Show pipeline health, sponsorship surface, audience engagement, Content Vault intelligence; ensures AI-Native Shift Show enters Series register at launch
Academy BU lead Provost Cohort delivery, Course (0-410) substrate per LM#7 Gate 2, AIRops Academy partnership leverage
Collective BU lead Trellis /shift/collective practitioner channel substance, practitioner directory readiness, application pipeline
Store BU lead Exchange Commerce Hub (Order, Invoice, Payment, Subscription, Cart, Quote) for cohort + partnership flows
Service Delivery BU lead Relay Activation Workshop delivery wiring, retainer-continuation path from cohort grads
Apps BU lead Foundry Complexity Trap self-assessment productized as Foundry tool for /resources/tools
Infrastructure Squire Repo + Vercel + DNS + @vf/design-tokens package + Sanity read-only token grab
Site authorship Showcase Every ainativeshift.com page + cross-platform link writes on public surfaces
CRM writes (gateway) Ledger All HubSpot CRM record mutations (Series, Episodes, Course, Marketing Event, Products, Subscription, Daily Brief draft, Interest taxonomy, Contact properties, Project + 85 Tasks)
CMS writes (gateway) Canon All Sanity mutations (show doc, schema deploy, Episode 1 doc, methodology cross-refs, post-stream finalized show notes)
Media production Director, Prelude, Slate, Splice, Encore, Vigil, Caption, Curator Mux WHIP setup, pre-episode validation, weekly pre-creation, asset linking, orphan detection, 24h transcription SLA, cross-platform audit
Content authoring Forge, Baldwin, Oracle, Blueprint, Pixel Content blocks from blueprint, finalized show notes, methodology accuracy, framework diagrams, visual asset set
Methodology Oracle Validates every framework reference against wiki/canonical/ + Sanity records (coreBelief, valuePathStage, trap)
Journey concierge wiring Courier, Spark, Tether, Litmus, Leaf, Sylvan, Vestibule, Patron, Accord, Usher, Conductor, Alms One concierge per public signal surface; routes Interest progression per Performance Category H
Signal intelligence Meridian, Tide, Sentinel, Scout, Herald, Quorum, Prism Assessment-to-Interest bridge, pipeline progression, proactive monitoring, early-stage signal detection, pre-session briefing
Quality + verification Q (this procedure), Mirror (visual QA), Lookout (SEO/AEO), Waypoint (CTA), Audit (cross-source integrity), Hone (cross-layer consistency), Tuner (per-signal threshold), Echo (pattern memory), Aegis (org enablement) Pre-launch verification trio + post-launch quality system substrate
Distribution Broadcast, Chorus, Link, Correspondent LinkedIn launch posts (Chris personal + @Value-First brand), YouTube comments + live chat, LinkedIn relationship intelligence, network email
Cross-functional Marshal (peer planner), Aegis (org enablement), Nexus (convergence), Archivist (memory), Scrivener (doc sweep), Navigator (Compass advisory) Project coordination, cross-org convergence analysis, memory curation, documentation sweep, Compass surface advisory
Legal Writ Cohort enrollment terms, sponsor agreement language, VCP open-protocol licensing, podcast distribution rights, guest releases (drafts; external counsel reviews)
Chris Carolan (Advisory chair) Human Ratifications, podcast UI configuration, distribution platform submissions, Marketing Hub workflow activation, NVENC relay verification, LinkedIn Live reception confirmation

Procedure

The procedure executes in 9 phases. Phases 1–5 are stream-blocking (must complete before Tuesday Episode 1). Phases 6–9 are post-stream rolling-completion (Tuesday through end-of-week) and ongoing operational rhythm.

Phase 1 — 5P + PRD authoring + ratification (Convergence Session)

Step 1 — Author 5P plan

Status: VERIFIED 2026-05-25 Action: V compiles 5P plan from Convergence Session #1 ratifications (Purpose / People / Process / Platform / Performance) with 11 dependency tracks, 60+ verification criteria across Categories A–L, and Chris/Ryan UI-work demarcation per Ledger scope ratification (2026-05-25). Evidence: File at docs/plans/ainativeshift-launch-5p-plan.md (commit 06b6846c1, 586 lines, ratified Convergence Session #1 2026-05-24 → 2026-05-25). Reproduce: git log --oneline -- docs/plans/ainativeshift-launch-5p-plan.md. Owner: V

Step 2 — Persist 5P as Google Doc + HubSpot Listing artifact

Status: VERIFIED 2026-05-25 Action: Architect drafts Google Doc; Ledger persists 5P plan as HubSpot Listing (listing_content_type: document, document_type: plan, document_authors: v) with associations to VF Team Company (49241304942). Evidence: Google Doc 1bFzU-7jTU5k2W7Gess5uWo-guYgeNxg-PnelZO4Jw_E shared with chris.carolan@conveyingyourmessage.com; HubSpot Listing 558489781353 created on portal 40810431. Reproduce: node scripts/hubspot/api.js get listings 558489781353 --properties name,listing_content_type,document_type,document_authors. Owner: Architect (Google Doc); Ledger (Listing)

Step 3 — Author PRD from 5P

Status: VERIFIED 2026-05-25 Action: V converts 5P into PRD with 13 Functional Requirements, 10 Technical Requirements, Domain Requirements (Core Beliefs + Value Path + Twelve Traps avoidance + enforcement), Success Criteria, Out of Scope, Dependencies & Risks, 9-Wave Execution Recipe. Evidence: File at docs/plans/ainativeshift-launch-prd.md (474 lines, committed 2026-05-25). Reproduce: git log --oneline -- docs/plans/ainativeshift-launch-prd.md. Owner: V

Step 4 — Persist PRD as Google Doc + HubSpot Listing artifact

Status: VERIFIED 2026-05-25 Action: Architect drafts Google Doc; Ledger persists PRD as HubSpot Listing. Evidence: HubSpot Listing 558498442847 on portal 40810431. Reproduce: node scripts/hubspot/api.js get listings 558498442847 --properties name,listing_content_type,document_type,document_authors. Owner: Architect (Google Doc); Ledger (Listing)

Step 5 — HubSpot Project + 85 Tasks for execution coordination

Status: VERIFIED 2026-05-25 Action: Marshal drafts task spec (one Task per Process step); Ledger writes Project on Agent Operations pipeline 888442804 + 85 Tasks; Project associates to VF Team Company (49241304942) + 5P Listing + PRD Listing. Evidence: Project 558488899232 created 2026-05-25T06:54 with 85 Tasks (all NOT_STARTED at audit time 2026-05-25T14:35 CDT, per Marshal DoD audit). Task spec at /mnt/d/AI-WORKSPACE/2026-05-25-ainativeshift-project-task-spec.md. Reproduce: node scripts/hubspot/api.js get projects 558488899232 --properties hs_project_name,hs_pipeline,hs_pipeline_stage; node scripts/hubspot/api.js list-assoc projects 558488899232 tasks. Owner: Marshal (spec); Ledger (write)

Step 6 — Ratification capture

Status: VERIFIED 2026-05-25 Action: V captures Convergence Session ratifications (S-2c full reading, Q-Pr3 everyone wired Day 1, Q-Pl1=b shared design tokens, Q-Pl2 Sanity token grab, Q-Pl4 NVENC personal, Q-Pf1=a synthetic with cleanup, Q-Pr4 Chris owns podcast UI, etc.) into the 5P plan as durable record. Evidence: Ratifications block woven into 5P plan §Process and §Constraints (lines 215–328 of docs/plans/ainativeshift-launch-5p-plan.md). Reproduce: read the file. Owner: V

Phase 2 — Wave 1 substrate dispatch (parallel specialists, zero cross-dependencies)

Step 7 — Provision repo + Vercel + DNS + @vf/design-tokens package + Sanity read-only token

Status: VERIFIED 2026-05-25 Action: Squire creates Value-First-Team/ainativeshift GitHub repo, provisions Vercel project on Chris Carolan scope (chriscarolan-conveyingyous-projects per memory/reference_vercel_valuefirstagent.md), runs vercel git connect (NOT assumed by vercel link per memory/feedback_vercel_link_does_not_auto_deploy.md), wires ainativeshift.com apex + www.ainativeshift.com, provisions @vf/design-tokens monorepo package, grabs Sanity read-only token from existing AOM/TRTU/chriscarolan Vercel projects. Evidence: 21 ainativeshift.com routes returning HTTP 200 at audit time per Marshal DoD audit (apex, /about, /framework + 5 subpages, /partners, /press, /shift + 2 subpages, /show, /show/episodes/episode-ai-native-shift-2026-05-26, /legal + 4 subpages). Reproduce: curl -I https://ainativeshift.com. Owner: Squire Known gap: www.ainativeshift.com returns HTTP 200 directly instead of 301 redirecting to apex (Performance Criterion A2 FAIL per Marshal audit). Tracked in Phase 4 corrective.

Step 8 — Visual asset set

Status: UNTESTED Action: Pixel produces show artwork (3000×3000 podcast cover), YouTube channel art update for AINS within @Value-First, OG image template per route, hero visual (dark/modern wave/shift metaphor), favicon, podcast cover variants. Evidence: Favicons referenced in ainativeshift.com HTML (apple-touch-icon, favicon-16x16, favicon-32x32, favicon-512x512) per Marshal audit. Full asset set + OG image render in LinkedIn Post Inspector requires Mirror QA (Phase 5). Owner: Pixel

Step 9 — Content blocks from Perplexity blueprint

Status: VERIFIED 2026-05-25 Action: Forge transforms Perplexity blueprint Parts I + II + IX into per-page content blocks (hero, crisis section, ladder, framework teaser, social proof, footer, episode-page anatomy, Daily Brief template). Evidence: 16 content-block files at /mnt/d/AI-WORKSPACE/ainativeshift/content-blocks/ (MANIFEST + about, framework + 5 framework subpages, home, partners, press, shift + 2 shift subpages, show, show-episode-template). Reproduce: ls /mnt/d/AI-WORKSPACE/ainativeshift/content-blocks/. Owner: Forge

Step 10 — Methodology reference doc

Status: VERIFIED 2026-05-25 Action: Oracle produces canonical methodology references for Five-Layer Operating Model, Value Path 8 stages, Twelve Traps, Four Unified Views, Core Beliefs, VCP — grounded in Sanity records + wiki/canonical/. Evidence: 7 files at /mnt/d/AI-WORKSPACE/ainativeshift/methodology-reference/ (00-manifest, 01-five-layers, 02-value-path, 03-vcp, 04-twelve-traps, 05-four-unified-views, 06-cross-reference-matrix). Reproduce: ls /mnt/d/AI-WORKSPACE/ainativeshift/methodology-reference/. Owner: Oracle

Step 11 — Framework diagrams

Status: VERIFIED 2026-05-25 Action: Blueprint produces Mermaid + ERD + journey diagrams for Five-Layer Operating Model architecture, Value Path 8-stage flow, VCP / MCP / HCP relationship, Twelve Traps map. Evidence: 5 diagram subdirectories at /mnt/d/AI-WORKSPACE/ainativeshift/diagrams/ (five-layers, four-unified-views, twelve-traps, value-path, vcp) with MANIFEST. Reproduce: ls /mnt/d/AI-WORKSPACE/ainativeshift/diagrams/. Owner: Blueprint

Step 12 — Legal language

Status: VERIFIED 2026-05-25 (drafts only — external counsel review out of scope) Action: Writ drafts cohort enrollment terms ($24,995 + $8,000 caps), sponsor agreement template, VCP open-standard licensing posture, podcast distribution rights, guest releases. Evidence: 5 legal drafts at /mnt/d/AI-WORKSPACE/ainativeshift/legal/ (cohort-terms, guest-release-REJECTED, podcast-distribution-rights, sponsor-partnership, vcp-open-standard). One file marked REJECTED indicates Writ's editorial discipline — not all drafts pass first review. Reproduce: ls /mnt/d/AI-WORKSPACE/ainativeshift/legal/. Owner: Writ (draft); external counsel (review, out of scope per §Scope)

Step 13 — Design-token advisory

Status: VERIFIED 2026-05-25 Action: Navigator advises on VFT Tron:Ares palette + Compass design language harmonization → single shared token set for Squire to implement as @vf/design-tokens package. Evidence: Advisory at /mnt/d/AI-WORKSPACE/ainativeshift/design-tokens-advisory.md (35K, full token mapping). Reproduce: cat /mnt/d/AI-WORKSPACE/ainativeshift/design-tokens-advisory.md. Owner: Navigator (advisory only — Squire provisions package, Showcase imports)

Step 14 — Sanity show + aiNativeShift schema + Episode 1 draft

Status: VERIFIED 2026-05-25 (with one Path-B gap) Action: Canon creates Sanity show-ai-native-shift document with deterministic ID + _type: show (name, slug ai-native-shift, hosts ref contributor-chris-carolan, status active, launchDate 2026-05-26, platforms ["youtube", "linkedin"], format live-stream, frequency daily, useMuxLiveStream true, showLiveIndicator true), deploys aiNativeShift schema additively to shared dataset, creates Episode 1 draft episode-ai-native-shift-2026-05-26 with title "Episode 1: The AI-Native Shift" (publishedAt + muxAsset null — correct pre-launch state). Evidence: Marshal DoD audit confirmed both Sanity documents exist with non-null core fields per node scripts/sanity/query.js custom "*[_id == 'show-ai-native-shift'][0]" and equivalent for episode. Known gap: Show description field is null — required for Performance Criterion B7 (meta descriptions on show pages). Pre-stream corrective required: Canon writes description with verify-after-write per memory/feedback_canon_verify_after_write.md. Owner: Canon

Step 15 — HubSpot CRM substrate (Series, Episodes, Course, Marketing Event, Products, Subscription, Daily Brief, Interest taxonomy, Contact properties)

Status: UNTESTED (partial — Series + 8 Episode Listings + Course exist; remaining records claimed but not verified) Action: Ledger writes Series record (558536713246, listing_content_type: series, created 2026-05-25T10:53), first-week Episode Listings (8 records of type episode), Course record (558539476347, created 2026-05-25T11:16), Marketing Event for Activation Workshop, Product records ($24,995 cohort + $9,995/mo partnership), Subscription template, Daily Brief Marketing Email DRAFT, Interest pipeline interest_type enum updates (12 new values claimed: assessment_complete, episode_engager, hand_raiser_site, etc.), 8 Contact properties (claimed shipped). Pixel podcast cover (Step 8) is dependency for cover-property writes. Evidence (verified subset):

  • Series Listing 558536713246 EXISTS
  • 8 Episode-type Listings exist (IDs per Marshal DoD audit)
  • Course record 558539476347 EXISTS
  • Reproduce: node scripts/hubspot/api.js get listings 558536713246; node scripts/hubspot/api.js search listings --filters '{"propertyName":"listing_content_type","operator":"EQ","value":"episode"}' --limit 20 Known gaps (Marshal DoD audit, pre-stream corrective queue):
  • Series Listing name returns null — property-naming gap (real value may live under different property). Verify via property-index Path-B; if hs_title or alternate property carries the value, update property-index; if value is genuinely missing, Ledger writes it
  • All Episode Listings name/hs_title return null — same root cause
  • C3 Daily Brief Marketing Email DRAFT not found in standard listing search — may use different document_type; verify or write
  • C5 Course schema spec (Dean + Provost) Task = NOT_STARTED — Step 16 dependency
  • C7 Marketing Event Task = NOT_STARTED
  • C8 Product $24,995 not verified
  • C9 Product + Subscription $9,995/mo not verified
  • C11 Interest pipeline routing not verified (12 enum values claimed shipped on Interest object; Interest search returned 0 AINS-specific records at Marshal audit — may be schema-only vs records-written distinction) Owner: Ledger Failure mode reference: CAR 2026-05-18-corrective-ledger-silent-association-failures.md (Ledger may return fabricated IDs on silent failure — GET-back evidence required); memory/feedback_ledger_fabricated_ids_on_create_failure.md

Step 16 — Course schema spec (Dean + Provost methodology review)

Status: VERIFIED 2026-05-25 (spec + methodology review documents exist; Ledger deploy is Step 15) Action: Dean drafts full Course (0-410) schema spec for AI-Native Shift cohort per LM#7 Gate 2; Provost reviews for methodology alignment (4-week curriculum, capability transfer outcome per memory/feedback_enablement_outcome_explicit.md). Evidence: Spec at /mnt/d/AI-WORKSPACE/ainativeshift/course-schema-spec.md (24K); methodology review at /mnt/d/AI-WORKSPACE/ainativeshift/course-schema-methodology-review.md (42K). Course record 558539476347 deployed (per Step 15). Owner: Dean (spec) + Provost (review)

Phase 3 — Wave 2 site build (Showcase consumes Wave 1 substrate)

Step 17 — Repo scaffold + base layout + nav + footer

Status: VERIFIED 2026-05-25 Action: Showcase scaffolds ainativeshift repo (Astro 5 + Tailwind + React), imports @vf/design-tokens, builds base layout + nav + footer harmonized with Compass + VFT design language. Evidence: 21 routes returning 200 (per Step 7 evidence + Marshal audit) implies scaffold + layout + nav + footer all functional. Owner: Showcase

Step 18 — Homepage + show pages + framework pages + shift pages + about + resources + apply + legal

Status: UNTESTED (partial — 21 of intended ~28 routes live; specific gaps documented) Action: Showcase builds per Perplexity Part I sitemap: /, /show + /show/episodes + /show/episodes/[slug] + /show/subscribe, /framework + 5 framework subpages, /shift + /shift/program + /shift/activation + /shift/collective, /about + /about/team, /resources + /resources/articles + /resources/tools, /apply, /legal + 4 legal subpages, /partners, /press. Evidence (Marshal audit 2026-05-25):

  • Live (21): /, /about, /framework, /framework/vcp, /framework/twelve-traps, /framework/value-path, /framework/five-layers, /framework/four-unified-views, /partners, /press, /shift, /shift/activation, /shift/cohort, /show, /show/episodes/episode-ai-native-shift-2026-05-26, /legal, /legal/cohort-terms, /legal/partnership, /legal/podcast-distribution, /legal/vcp-open-standard
  • Missing (5, pre-stream corrective required): /apply (404 — FR-5 + C8 dependency), /sitemap.xml (404 — B2 FAIL, D10 task NOT_STARTED), /robots.txt (404 — B3 FAIL), /rss.xml (404 — J1 FAIL, podcast distribution gap), /assessment or /resources/tools integration of Foundry tool (404 — F1/F2 NOT_STARTED)
  • Naming gap: /shift/cohort exists vs PRD /shift/program — verify intent or rename
  • Naming gap: /show/episodes/{slug} works directly vs PRD /show/episodes index — verify index exists or build Owner: Showcase

Step 19 — JSON-LD schema markup + sitemap + robots + UTM utilities

Status: BLOCKED (D9 + D10 tasks NOT_STARTED at Marshal audit) Action: Showcase adds Organization JSON-LD on /, PodcastEpisode on every /show/episodes/[slug], FAQPage on /framework/*, Course + Product on /shift/program + /apply. Adds /sitemap.xml, /robots.txt, UTM utilities per Perplexity Part V attribution architecture. Evidence: Marshal DoD audit confirmed all three URLs (/sitemap.xml, /robots.txt, /rss.xml) return 404. Performance Criteria B1–B10 mostly PENDING — Lookout cannot validate schema until D9 ships. Blocker: Showcase implementation pending. Pre-stream blocker — must complete before Tuesday Episode 1. Owner: Showcase

Step 20 — Foundry productize Complexity Trap self-assessment

Status: NOT BUILT (F1 task NOT_STARTED at Marshal audit; no /assessment or /trap-assessment route on live site) Action: Foundry produces self-assessment tool (questions, scoring matrix, results page mapping to Value Path stage + recommended ladder rung); embeds on /resources/tools; quality gate (renders <3s, mobile responsive, form submission end-to-end via Litmus → Meridian → Tide pipeline). Design intent: Per FR-7 in PRD + skill skills/apps/foundry-context.md. Would be implemented in ainativeshift repo or as monorepo apps/website/src/components/ embedded into the standalone site via Astro island. Owner: Foundry

Phase 4 — Wave 3 build follow-ups (legal review, diagrams embed, hygiene corrections)

Step 21 — Apex → www redirect correction

Status: BLOCKED (Performance Criterion A2 FAIL — Marshal audit) Action: Squire or Showcase adds Vercel redirect rule so www.ainativeshift.com returns 301 to apex (currently returns 200 directly). Blocker: Pre-stream corrective. Owner dispatch required. Owner: Squire (config) or Showcase (route)

Step 22 — Sanity show description field write

Status: BLOCKED (Performance Criterion B7 PENDING — Marshal audit found null description) Action: Canon writes show description to show-ai-native-shift with verify-after-write per memory/feedback_canon_verify_after_write.md. Description sourced from 5P §Purpose + PRD §Overview. Blocker: Pre-stream corrective. Required for B7 SEO meta descriptions on show pages. Owner: Canon

Step 23 — HubSpot Listing name/title gap diagnosis

Status: BLOCKED (Marshal audit found null name on Series + all Episode Listings — Property-naming gap pattern per CAR 2026-05-19-audit-by-assumption-propagation.md) Action: Ledger executes Path-B verification per wiki/conventions.md § HubSpot data conventions — live GET on Series Listing 558536713246 to inspect ALL populated properties (not just queried ones); if title lives under a non-standard property name, update property-index; if value is genuinely missing, Ledger writes it. Same pass for 8 Episode Listings. Blocker: Pre-stream corrective. Without title/name, downstream queries that populate the site (or HubSpot-side UI) return blanks. Owner: Ledger Failure mode reference: CAR 2026-05-19-audit-by-assumption-propagation.md (querying for property names not confirmed via property-index returns null indistinguishably from verified-null reads — both must be true: live read + property-index confirmation, else mark [T1-unverified-name])

Step 24 — Legal language review hand-off + integration into /legal/* pages

Status: VERIFIED 2026-05-25 (drafts live on site; external counsel review out of scope per §Scope) Action: Writ delivers 4 published legal pages on ainativeshift.com (/legal/cohort-terms, /legal/partnership, /legal/podcast-distribution, /legal/vcp-open-standard) + /legal hub. Guest release marked REJECTED in source (Writ editorial discipline — not all drafts pass first review). External counsel review is separate Future Work item, not pre-stream gate. Evidence: All 5 /legal/* routes returning HTTP 200 per Marshal audit. Owner: Writ (draft); Showcase (page build); external counsel (review, out of scope)

Step 25 — Framework diagrams embed into /framework/* pages

Status: UNTESTED (diagrams produced Step 11; embed into pages requires Mirror verification) Action: Showcase embeds Blueprint diagrams into /framework/five-layers, /framework/value-path, /framework/vcp pages. Evidence: Framework routes return HTTP 200; diagram render verification awaits Mirror Playwright pass (Phase 5). Owner: Showcase

Step 26 — Customer-facing prose hygiene pre-launch sweep

Status: UNTESTED Action: Per skills/enforcement/customer-facing-prose-hygiene.md + memory/pattern_internal_agent_prose_leakage.md, sweep every ainativeshift.com page + every customer-facing HubSpot property (Series + Episode Listing names, Course description, Product names, Marketing Event description, legal page bodies) for codename leakage (no "Showcase built this," no "Ledger wrote this Listing," no "concierges route signals into Sage's Customer Org," no internal repo paths, no AI-org-chart taxonomy in user copy). Evidence: Awaits Mirror visual QA Phase 5 + Lookout content scrape Phase 5. Pre-stream gate. Owner: V (sweep dispatch) + Mirror (visual identification) + Lookout (content scrape) Failure mode reference: pattern_internal_agent_prose_leakage.md (N=2: Paragon 2026-05-07 ~3 violations, Abs Co 2026-05-18 ~47 violations across 14 properties)

Phase 5 — Wave 4 DoD push (verification trio + agent-executable gaps + 1-day-out validation)

Step 27 — Mirror visual QA every route + cross-platform consolidation verification

Status: UNTESTED (Mirror report exists for some routes; full Playwright sweep + cross-platform pass pending) Action: Mirror runs Playwright sweep across every ainativeshift.com route at 375 / 640 / 1024 px viewports; screenshot every route; CTA click-through verification; HubSpot form submission end-to-end (depends on Chris UI for forms); episode player embed render check. Evidence: Mirror report at /mnt/d/AI-WORKSPACE/ainativeshift/mirror-qa-report.md (15K); 11 screenshots at /mnt/d/AI-WORKSPACE/ainativeshift/mirror-screenshots/ covering about + episode-1 + framework (desktop + mobile, full + viewport for each). Reproduce: cat /mnt/d/AI-WORKSPACE/ainativeshift/mirror-qa-report.md. Gaps: Mirror sweep does not yet cover: cross-platform consolidation (Phase 7 dependency), full sitemap (5 missing routes per Step 18), JSON-LD validation (Step 19 blocker). Owner: Mirror Failure mode reference: wiki/conventions.md § Engineering standards — "Fallback rendering is a failure, not a feature"

Step 28 — Lookout SEO + AEO audit

Status: UNTESTED (Lookout report exists; full audit blocked on Step 19 sitemap/robots/JSON-LD) Action: Lookout audits meta tags, OG images (LinkedIn Post Inspector preview), JSON-LD validation (schema.org validator API), FAQ + PodcastEpisode + Organization schema, sitemap.xml, robots.txt, broken-link sweep, page-speed (Lighthouse ≥95 across Performance/Accessibility/Best Practices/SEO). Evidence: Lookout report at /mnt/d/AI-WORKSPACE/ainativeshift/lookout-seo-audit-2026-05-25.md (27K). Blockers: /sitemap.xml + /robots.txt 404 (Step 19); some routes missing meta descriptions (Sanity show description null, Step 22). Owner: Lookout

Step 29 — Waypoint CTA optimization audit

Status: VERIFIED 2026-05-25 Action: Waypoint audits CTA presence + working destinations on every page (3-option CTA blocks on episode pages per Perplexity AEO spec, ladder-rung CTAs, source-aware contextual paths). Evidence: Waypoint report at /mnt/d/AI-WORKSPACE/ainativeshift/waypoint-cta-audit-2026-05-25.md (28K). Owner: Waypoint

Step 30 — Audit cross-source data integrity (HubSpot ↔ Sanity ↔ site)

Status: VERIFIED 2026-05-25 Action: Audit verifies Series Listing + 5 Episode Listings ↔ Sanity show + episode docs ↔ ainativeshift.com episode pages all match (or surfaces specific drifts). Evidence: Audit report at /mnt/d/AI-WORKSPACE/ainativeshift/audit-integrity-2026-05-25.md (22K). Owner: Audit Failure mode reference: CAR 2026-05-19-audit-by-assumption-propagation.md — Audit must execute live reads against verified property names (not constructed ones)

Step 31 — Hone command/skill cross-layer consistency

Status: UNTESTED (Hone audit not yet run on launch-specific commands; pending Phase 9 closure) Action: Hone registers any new commands shipped for ainativeshift ops in Dewey index; consistency audit verifies file paths, agent codename references, skill references all resolve. Owner: Hone Trigger: Concurrent with this procedure's authoring (no new commands shipped in this launch — Hone audit reduces to verifying this procedure file references are all valid)

Step 32 — Q operating procedure for AINS launch (this document)

Status: VERIFIED 2026-05-25 (this document) Action: Q authors this procedure per PRD I5 + /process-documentation skill. Procedure file lives at docs/operating-procedures/ainativeshift-launch.md; published to HubSpot Listing via Ledger (listing_content_type: document, document_type: operating_procedure, document_authors: q). Evidence: This file. Listing publication via Ledger pending (Phase 9 closure). Reproduce: read docs/operating-procedures/ainativeshift-launch.md. Owner: Q (this procedure); Ledger (Listing publication)

Step 33 — Director pre-stream readiness check

Status: VERIFIED 2026-05-25 Action: Director runs apps/media production setup verification (Mux WHIP endpoint live, fan-out to @Value-First YouTube + LinkedIn Live chris-carolan, GreenRoom prep, canvas compositor); Chris verifies local NVENC relay on VFT-CommandCtr personally (per Q-Pl4 ratification — out of scope for agent verification per §Scope). Evidence: Director report at /mnt/d/AI-WORKSPACE/ainativeshift/director-prestream-readiness-2026-05-25.md (26K). Known gap: Chris's NVENC verification is human action — Tuesday-morning gate, not pre-Tuesday-EOD gate. Owner: Director (agent verification); Chris (NVENC personal verification)

Step 34 — Prelude Episode 1 validation

Status: VERIFIED 2026-05-25 Action: Prelude verifies Episode 1 Listing populated on Series, Mux stream verified, series_standing_room_url populated back into Sanity show record, guest brief (if Format C — Episode 1 is not Format C per Perplexity Part III thematic rotation). Evidence: Prelude report at /mnt/d/AI-WORKSPACE/ainativeshift/prelude-ep1-validation-2026-05-25.md (15K). Owner: Prelude

Step 35 — Slate pre-create remaining week + next week Episode Listings

Status: UNTESTED (E3 task NOT_STARTED at Marshal audit; Slate has not yet pre-created Wed/Thu/Fri this week + Mon–Fri next week per Perplexity Part VII weekday rotation) Action: Slate pre-creates 8 additional Episode Listings (Wed/Thu/Fri 2026-05-27 to 2026-05-29 + Mon/Tue/Wed/Thu/Fri 2026-06-01 to 2026-06-05) with deterministic IDs. Owner: Slate Trigger: Concurrent with Step 15 (C4 task in PRD); pre-stream completion preferred but not stream-blocking for Episode 1

Step 36 — Baldwin Episode 1 show notes scaffold

Status: UNTESTED (E4 task NOT_STARTED at Marshal audit; scaffold pending) Action: Baldwin drafts Answer Block (40–60 words per Perplexity AEO spec) + structured show-notes anatomy in Sanity episode document; finalizes post-stream from transcript (Phase 8). Owner: Baldwin → Canon

Step 37 — Wave 4 journey concierge wiring (rolling — completes Tuesday through Friday)

Status: NOT BUILT (Marshal audit: all 17 H-category criteria + all 10 G-track + C1/C11 = 0% complete; this is the primary remaining agent-executable cluster) Action: Each named concierge (Courier, Spark, Tether, Litmus, Leaf, Sylvan, Vestibule, Patron, Accord, Usher, Conductor, Alms) wires its signal capture path; Meridian + Tide + Sentinel + Scout + Herald wire signal-intelligence layer. Per-concierge synthetic test contact advances through expected Interest progression (Performance Category H) against live portal 40810431 with cleanup pass post-verification (Q-Pf1=a ratification). Design intent: Each concierge has a brief in its own agent definition + skills/journey-design/ or domain-specific skill. Wave 4 dispatch from V is the activation event. Triggering events for re-running: Any new public form, page, or signal surface on ainativeshift.com (or any other VFT public surface) requires the relevant concierge to add signal capture + Interest routing. Owner: Sage (orchestration) + named concierge per surface

Phase 6 — Pre-stream readiness check (Director + Prelude + Chris-UI items)

Step 38 — Mux stream provisioned with fan-out verified

Status: VERIFIED 2026-05-25 per Director report (Step 33) Action: Mux live stream created via apps/media; WHIP endpoint live; fan-out to @Value-First YouTube + LinkedIn Live chris-carolan verified via Director dry-run. Evidence: Director pre-stream readiness report. Owner: Director

Step 39 — series_standing_room_url populated in Sanity show record

Status: VERIFIED 2026-05-25 per Prelude report (Step 34) Owner: Canon (writes) → Prelude (verifies)

Step 40 — Chris UI items (out of scope per §Scope but listed for completeness)

Status: CHRIS-OWNED Action items (Chris, pre-stream EOD Monday):

  • HubSpot Content Hub Podcast UI configuration (RSS feed creation)
  • Apple Podcasts + Spotify + Google Podcasts + iHeart + Amazon Music submission filings (24h ingest lag acceptable per PRD §Dependencies & Risks)
  • HubSpot Forms creation + styling + embed on /shift/activation + /apply + /resources/tools + sponsor inquiry + practitioner application
  • HubSpot Marketing Event embed (calendar + form on /shift/activation)
  • HubSpot Marketing Email workflow wiring for Daily Brief
  • All Contact-lifecycle UI workflows driving concierge routing
  • LinkedIn post pre-ratification (Phase 8)
  • Daily Brief first issue send activation (Phase 8)
  • NVENC relay verified live on VFT-CommandCtr Tuesday morning pre-stream

Owner: Chris (UI work — not agent-executable per §Scope)

Phase 7 — Day-of-stream rhythm (Tuesday 2026-05-26)

Step 41 — Final pre-stream readiness sweep (T-90 min)

Status: UNTESTED (Tuesday gate) Action: Director confirms Mux WHIP live + fan-out; Prelude confirms Episode 1 Listing populated; Chris confirms NVENC relay live; Mirror confirms episode page renders embedded player. Owner: Director + Prelude + Chris + Mirror

Step 42 — Episode 1 live stream

Status: UNTESTED (Tuesday gate) Action: Director runs Episode 1 via apps/media → Mux WHIP → fan-out to YouTube @Value-First + LinkedIn Live chris-carolan. Stream produces Mux asset with status ready (non-empty duration). Owner: Director

Step 43 — Mid-stream monitoring (Broadcast + Chorus + Link)

Status: UNTESTED (Tuesday concurrent) Action: Broadcast monitors YouTube live chat + comments; Chorus prepares post-stream comment ingestion into Content Vault; Link monitors LinkedIn Live reactions + comments on chris-carolan personal account. Owner: Broadcast + Chorus + Link

Phase 8 — Post-stream pipeline (Splice + Encore + Vigil + Baldwin + Canon + Catalog + Vault + Broadcast + Chorus + Link + Correspondent)

Step 44 — Splice link Mux asset to Sanity episode

Status: UNTESTED (post-Tuesday) Action: Splice links Mux asset (from Step 42 ready state) to Sanity episode-ai-native-shift-2026-05-26 document via episode.muxVideo.asset-> nested ref (NOT flat muxAssetId string per show-launch.md Step 12 Pitfall). Owner: Splice (via Canon for the Sanity write) Failure mode reference: show-launch.md Critical Pitfall 3 — Sanity Mux schema bridge requires the nested ref; flat string produces empty <mux-player> with no playbackId

Step 45 — Encore recording verification + orphan detection

Status: UNTESTED (post-Tuesday) Action: Encore verifies Mux asset exists with status: ready, non-empty duration; confirms Sanity episode link (no orphan); if orphan detected, links to existing episode rather than creating new one per wiki/glossary.md § Orphaned Mux asset. Owner: Encore Failure mode reference: CAR 2026-03-24-corrective-sanity-duplicate-episodes.md (orphans created duplicate episodes; Encore orphan detection prevents)

Step 46 — Vigil monitor Gemini transcription (24h SLA)

Status: UNTESTED (post-Tuesday) Action: Vigil monitors Gemini transcription pipeline; alerts if stalled past 24 hours. Owner: Vigil Failure mode reference: CAR 2026-03-30-corrective-media-transcription-pipeline-silent-failure.md (transcription pipeline had been silently failing for months; Vigil monitoring prevents)

Step 47 — Baldwin finalize show notes from transcript

Status: UNTESTED (post-Tuesday, gated on Step 46) Action: Baldwin reads transcript, finalizes Episode 1 show notes (Answer Block 40–60 words + structured anatomy per Perplexity AEO spec) into Sanity episode document via Canon. Owner: Baldwin → Canon

Step 48 — Canon publish finalized episode

Status: UNTESTED (post-Tuesday, gated on Step 47) Action: Canon publishes Sanity episode document (sets publishedAt) with verify-after-write per memory/feedback_canon_verify_after_write.md. Owner: Canon

Step 49 — Catalog + Vault index Episode 1

Status: UNTESTED (post-Tuesday, gated on Step 48) Action: Catalog registers Episode 1 with methodology taxonomy; Vault indexes into Content Vault SQLite FTS5 (/mnt/d/data/content-vault.db) + Upstash Vector + Upstash Search. Known limitation: Vault sync has been dark since 2026-04-02 per Media Spine carry-over — restart required (Future Work item per PRD §11). Owner: Catalog → Vault

Step 50 — Broadcast LinkedIn launch posts

Status: UNTESTED (post-Tuesday — Chris pre-ratification required) Action: Broadcast publishes LinkedIn post on Chris's personal account (via Link) + @Value-First brand account. Owner: Broadcast + Link Failure mode reference: show-launch.md Critical Pitfall 5 (Ledger ≠ Social Publishing — LinkedIn publishing routes through Broadcast using scripts/hubspot/post-schedule.js); feedback_ledger_not_social_publishing.md

Step 51 — Correspondent network email

Status: UNTESTED (post-Tuesday) Action: Correspondent sends email to existing VF Team network announcing Episode 1 + ainativeshift.com via Gmail API (chris.carolan@valuefirstteam.com). Owner: Correspondent Verify with: Gmail Sent log via gws gmail messages list --params '{"q":"to:[network] subject:[launch subject]"}'

Step 52 — Chris activate Daily Brief first issue

Status: CHRIS-OWNED (post-stream) Action: Chris sends Daily Brief first issue via HubSpot Marketing Email UI from the DRAFT record Ledger created in Step 15. Owner: Chris

Step 53 — Chorus YouTube comment ingestion

Status: UNTESTED (rolling post-stream) Action: Chorus ingests YouTube comments + live chat into Content Vault for @Value-First AI-Native Shift Show. Owner: Chorus

Phase 9 — Rolling completion + signal monitoring (Tide + Sentinel + Scout + Herald + Quorum + Tuner + Echo + Archivist)

Step 54 — Cross-platform consolidation (Scrivener sweep + per-surface writes)

Status: NOT BUILT (all H1–H10 tasks NOT_STARTED at Marshal audit) Action: Scrivener runs internal-link sweep → produces per-surface cross-link spec. Per-surface implementation:

  • valuefirstteam.com methodology pages + /catalyst + /programs/ai-native-shift (Showcase)
  • AOM index + /be-a-guest + /recap (Canon + Showcase)
  • TRTU /be-a-guest + /bus + /cast + /episodes (Canon + Showcase)
  • chriscarolan.com author bio (Canon + Showcase)
  • valuefirstagent.com category framing (Canon + Showcase)
  • valuecreationprotocol.com ↔ /framework/vcp reciprocal (Canon)
  • media.valuefirstteam.com Friends network (Canon)
  • compass.valuefirstteam.com per-client surfaces (Navigator advises; Canon writes)
  • valuefirstteam.com/about/ai-team (Aegis) Owner: Scrivener (sweep) + Showcase + Canon + Navigator + Aegis (per surface) + Mirror (cross-link verification — Step 27 cross-platform pass) Triggering events for re-running: Any new Nov 2025+ platform surface that should reference ainativeshift.com (or any new ainativeshift surface that should be referenced from existing properties)

Step 55 — Ongoing Slate weekly Episode Listing pre-creation

Status: UNTESTED (recurring operational; first run Step 35) Action: Slate continues weekly pre-creation of 5 weekday Episode Listings per Perplexity Part VII thematic rotation. Trigger: Weekly cron or /show-prep (verify trigger reality per skills/ai-leadership/INDEX.md "Schedule reality note") Owner: Slate

Step 56 — Ongoing signal monitoring (Quorum + Sentinel + Tide + Scout)

Status: UNTESTED (recurring operational) Action:

  • Quorum: OH attendance + question depth + engagement scoring (Monday 5am cadence)
  • Sentinel: proactive readiness pattern detection on AINS-specific signals
  • Tide: Interest pipeline progression based on AINS-specific interest_type enum values (from Step 15 C11)
  • Scout: early-stage natural progression signal detection from public-site behavior Owner: Sage org

Step 57 — Echo capture Tuesday Episode 1 operational lessons

Status: UNTESTED (post-Episode-1 gate) Action: Echo captures operational incidents + pattern observations from Episode 1 (stream success/issues, post-stream pipeline behavior, journey concierge first-fire data) into pattern memory; surfaces patterns that recur 3+ times for prevention proposal. Owner: Echo Failure mode reference: CAR 2026-04-20-corrective-operational-rhythm-cascade.md (operational rhythm failures cascade if Echo doesn't capture the first-occurrence pattern)

Step 58 — Pulse + Forecast + Tributary post-launch financial intelligence

Status: UNTESTED (recurring operational; ongoing) Action:

  • Pulse: visitor signal aggregation into client portfolio context
  • Forecast: cohort fill projections + sponsorship pipeline forecasts (revenue scenario modeling)
  • Tributary: cross-BU revenue aggregation from all 6 BUs that earn from ainativeshift.com traffic Owner: Pax org

Step 59 — Tuner per-signal threshold tuning

Status: UNTESTED (recurring; first week of live data) Action: Tuner tunes per-AINS-signal thresholds (Interest progression triggers from site behavior) based on first-week accuracy data; tracks accuracy improvements. Owner: Tuner

Step 60 — Archivist memory capture

Status: UNTESTED (post-launch closure) Action: Archivist writes memory/project_ainativeshift_launch.md + memory/reference_ainativeshift_substrate.md + MEMORY.md index entry; Dewey index update with ainativeshift project (if structurally novel beyond existing standalone-site pattern entries). Owner: Archivist

Step 61 — Closure audit + this procedure re-promotion

Status: UNTESTED (post-rolling-completion window — target 2026-05-29 EOD Friday) Action: Q re-runs PRD DoD audit; advances UNTESTED steps to VERIFIED per evidence captured during Phase 7–9; updates Verification Score at top of this document; published HubSpot Listing version (via Ledger). Owner: Q Trigger: End of rolling-completion window (Friday 2026-05-29 EOD)

Outputs to systems

Step(s) System Gateway Write description
2, 4, 5, 15, 23, 32, 61 HubSpot Ledger 5P + PRD Listings; Project + 85 Tasks; Series + Episode Listings + Course + Marketing Event + Products + Subscription + Daily Brief draft + Interest taxonomy + Contact properties; this operating procedure Listing; closure audit Listing
14, 22, 44, 47, 48, 54 Sanity Canon show + episode documents; methodology cross-refs; description field; Mux asset link; finalized show notes; published episode; cross-platform Sanity refs
7, 17, 18, 19, 20, 21, 25, 54 Vercel (Astro builds) + GitHub Showcase (commits + pushes; vercel git connect auto-deploys) Site repo + scaffold + pages + JSON-LD + sitemap/robots/RSS + Foundry tool embed + apex→www redirect + diagram embed + cross-platform link writes
49 Content Vault SQLite FTS5 + Upstash Vector + Upstash Search Catalog → Vault Episode 1 index
50 LinkedIn (via HubSpot Social Publishing) Broadcast (NOT Ledger per feedback_ledger_not_social_publishing.md) LinkedIn launch posts on Chris personal + @Value-First brand
51 Gmail Correspondent (via gws gmail CLI) Network announcement email
53 Content Vault Chorus YouTube comments ingestion
60 Filesystem (memory/) + MEMORY.md Archivist Memory files + index entry

Gateway discipline: Every write above is named with its gateway. Bypassing a gateway is a governance violation in the same class as writing malformed data — see wiki/agent-guide.md § Gateway patterns. The Chris-owned UI work in Step 40 / Step 52 does NOT route through Ledger because it is operator UI action, not agent-driven write — see wiki/agent-guide.md § Agent-driven vs app-driven writes.

Hygiene checkpoints

Pre-write (every C-track + D-track step)

  • Property-index Path-B verification: Before any HubSpot write to a property not confirmed live in the same session, Ledger executes a live GET against an existing record with that property populated. If property doesn't exist or value lives under a different name, update skills/hubspot/property-index/*.json BEFORE write. Anti-pattern: writing to assumed property names (CAR 2026-05-19-audit-by-assumption-propagation.md).
  • GET-back verify-after-write: Every Ledger create returns the new ID + a GET-back of the written record showing actual field values. Never trust a create response alone (CAR 2026-05-18-corrective-ledger-silent-association-failures.md, memory/feedback_ledger_fabricated_ids_on_create_failure.md).
  • Canon verify-after-write: Every Canon write returns a GROQ query result showing actual field values, not just _rev (per memory/feedback_canon_verify_after_write.md — 3 deviations during TRTU launch).

Pre-deploy (every Phase 3 + Phase 4 step)

  • Customer-facing prose hygiene gate: Before any write to ainativeshift.com page content, Sanity field rendered on public site, or customer-facing HubSpot property (Series + Episode Listing names, Course description, Product names, Marketing Event description, legal page bodies, sponsor inquiry copy), V (or whoever dispatches the write) reads skills/enforcement/customer-facing-prose-hygiene.md + memory/pattern_internal_agent_prose_leakage.md. Anti-pattern: codename leakage ("Showcase built this"), internal repo paths, AI-org-chart taxonomy in user copy, internal process language. N=2 prior incidents (Paragon 2026-05-07 ~3 violations, Abs Co 2026-05-18 ~47 violations).
  • No counters by default: Per wiki/conventions.md § Client-facing surface defaults — counters, no count badges, header tallies, section-eyebrow counts on ainativeshift.com unless count itself is the actionable signal (cohort seat availability would qualify; "X episodes published this week" would not).
  • No internal staffing in customer docs: Per memory/feedback_no_internal_staffing_in_customer_copy.md, no USS-internal staff names, contractor names, VFT travel logistics in customer-facing copy.

Pre-stream (every Phase 5 + Phase 6 step)

  • Auto-commit + push for Chris-only files: Per memory/feedback_auto_commit_infra_edits.md, edits to commands/skills/agents/hooks/wiki auto-commit + push without asking when Chris is the user. This procedure (docs/operating-procedures/ainativeshift-launch.md) qualifies — auto-commit + push on author. Per memory/feedback_auto_push_builds.md, every build/deploy commits AND pushes without asking; Chris uses production as review surface.
  • No local build gates in briefs: Per memory/feedback_no_local_build_gates_in_briefs.md, never require tsc/astro build/pnpm build/dev server checks as pre-commit gates in agent briefs. Vercel is the test environment.
  • No nested subagent spawning: Per memory/feedback_no_nested_subagent_spawning.md, only main-session V invokes Agent tool. Q (in this procedure authoring) does NOT dispatch Ledger directly — produces Ledger-ready payload; V dispatches Ledger.

Pre-claim-complete (every step requesting VERIFIED status)

  • Verification quartet: Date / what tested / what confirmed / how to reproduce. Per verification-protocol.md — bad evidence ("Works") is rejected at audit.
  • HELD vs FLIPPED behavioral marker (for steps with external challenge): If a step's claimed completion is challenged externally (Chris, audit, peer), agent holds position when challenged without new evidence; updates only on new evidence or cited rule violation. Three FLIPPED observations = pattern requiring prevention.

Known failure modes + corrective actions

Class Description CAR / pattern reference Prevention in this procedure
Internal-prose-leakage (N=3 class) Internal VFT agents authoring customer-facing prose leak codenames, internal artifact paths, authoring provenance, process language, AI-org-chart taxonomy onto public surfaces or customer-facing HubSpot/Sanity properties. N=2 prior (Paragon 2026-05-07 ~3 violations, Abs Co 2026-05-18 ~47 violations); ainativeshift is the third high-risk surface memory/pattern_internal_agent_prose_leakage.md; memory/feedback_no_internal_staffing_in_customer_copy.md; memory/feedback_no_presumptive_framing_in_customer_copy.md; skills/enforcement/customer-facing-prose-hygiene.md Step 26 hygiene sweep (pre-launch); ongoing per Step 50 (LinkedIn post pre-ratification by Chris); Mirror + Lookout post-launch content scrapes
VCP-licensing-drift (N=4 class) VCP open-protocol framing drifts (license terms, attribution requirements, reciprocal linkage requirements) across ainativeshift.com /framework/vcp, valuecreationprotocol.com, sponsor agreements, podcast distribution rights, guest releases Writ legal pack (skills/legal/); 4 legal drafts at /mnt/d/AI-WORKSPACE/ainativeshift/legal/ show alignment risk if external counsel review changes terms Step 24 (Writ drafts integrated into /legal/* pages); external counsel review out of scope but tracked for Future Work; any term change cascades to all 4 surfaces via Canon-mediated Sanity updates + Ledger-mediated HubSpot Listing version update
Custom-object stamping null on creates Ledger create returns ID but custom-object stamping (created_by_agent, document_authors, document_type) writes null silently; affects Series + Episode Listing name field per Marshal DoD audit CAR 2026-05-18-corrective-ledger-silent-association-failures.md; memory/feedback_ledger_fabricated_ids_on_create_failure.md; wiki/agent-guide.md § Codename stamping (Ledger stamps "ledger", not initiator) Step 23 corrective (Path-B diagnose + write); GET-back verify-after-write hygiene checkpoint enforces detection at write time, not at audit time
Astro-embed source bypass Astro page directly fetches Sanity via raw HTTP at render-time instead of going through scripts/sanity/query.js (read) or Canon (write); produces stale-cache + ungated read patterns wiki/agent-guide.md § Agent-driven vs app-driven writes — Astro reads at render time are app-driven and acceptable via server-side API routes that hold credentials; client-side Sanity reads from browser are NOT acceptable; Canon ONLY mediates writes, not reads Step 18 Showcase implementation review — verify Astro page Sanity queries are server-side (Astro frontmatter or API route), not client-side; Mirror Step 27 visual QA confirms no client-side Sanity token leakage
Apex/www redirect missing www.{domain} returns 200 directly instead of 301 redirecting to apex — Performance Criterion A2 FAIL; SEO authority dilution show-launch.md Critical Pitfall 8 (public website apex → www redirect — for VFT properties that follow www-canonical pattern; ainativeshift follows apex-canonical) Step 21 corrective (Squire or Showcase adds Vercel redirect rule)
Sanity Mux schema bridge Episode template queries episode.muxVideo.asset-> (nested ref to mux.videoAsset doc), NOT flat muxAssetId strings; flat string produces empty <mux-player> with no playbackId show-launch.md Critical Pitfall 3; episode-publishing.md § Step 7 Step 44 Splice + Canon two-step write using nested ref schema
Orphan Mux asset Mux recording with ready status but no corresponding Sanity episode link — root cause of duplicate episode bug (Mar 2026) CAR 2026-03-24-corrective-sanity-duplicate-episodes.md; wiki/glossary.md § Orphaned Mux asset Step 45 Encore orphan detection prevents recurrence; if orphan found, link to existing episode (never create new one)
Silent transcription failure Transcription pipeline silently fails for extended periods without alerts CAR 2026-03-30-corrective-media-transcription-pipeline-silent-failure.md Step 46 Vigil 24h SLA monitoring
Ledger ≠ Social Publishing LinkedIn / YouTube publishing routed through Ledger instead of Broadcast memory/feedback_ledger_not_social_publishing.md; show-launch.md Critical Pitfall 5 Step 50 routes through Broadcast + Link; Ledger only persists post-publish artifact metadata if needed
youtube-publish.ts --privacy public lowercase rejected HubSpot API requires uppercase PUBLIC show-launch.md Critical Pitfall 6 Omit --privacy flag entirely (defaults to public); Squire fix queued for alignment
Synthesis-drift in PRD audit Synthesis files (catalogs, audits) drift confidence — claim VERIFIED without Tier-1 evidence CAR 2026-05-10-corrective-5p-bias-incidents.md; skills/quality-system/anti-patterns.md Marshal DoD audit (2026-05-25, Tier-1 only) prevents synthesis-tier drift in this launch; Q audit Step 61 re-verifies post-completion
Property-index audit by assumption Audit queries for property names not confirmed via property-index — returns null indistinguishably from verified-null reads CAR 2026-05-19-audit-by-assumption-propagation.md Step 23 + Step 30 require live GET against verified property names; [T1-unverified-name] marker if either condition unmet

Related processes

Process Direction Relationship
show-launch.md (Marquee) Sibling AOM/TRTU single-show pattern. This procedure extends with multi-BU + program + journey concierge wiring. Many gateway/hygiene rules shared.
episode-publishing.md (Marquee) Downstream From Episode 2 onward, per-episode publishing follows this procedure. This launch produces Episode 1; episode-publishing handles 2+.
media-production.md (M-01, Marquee) Adjacent Media production lifecycle mechanics (Mux WHIP, transcription, distribution). This procedure uses Director + Prelude + Slate + Splice + Encore + Vigil from M-01's verified pipeline.
hubspot-write-operations.md (S-01, Ledger) Foundational Gateway mechanics for all C-track HubSpot writes.
g-01-daily-operations-rhythm.md (G-01, Marshal + V) Foundational Daily rhythm that this procedure post-launch operates within (Pulse + Klaxon + Squire + ongoing concierges).
Sanity CMS Write Operations (S-02, Canon) Foundational, no procedure yet All D-track Sanity writes route through Canon; procedure S-02 is next in Q's queue per process register §Priority.
Article Publishing (CT-02, Canon/Baldwin) Adjacent Step 47–48 finalized show notes invokes the Baldwin → Canon publishing pattern documented in CT-02 (no procedure yet).
Content Distribution (CT-03, Broadcast) Adjacent Step 50–51 LinkedIn + email distribution invokes CT-03 patterns (no procedure yet).

Triggering events for re-running this procedure

This procedure is reusable. The next invocation events:

  1. Next daily-show + program convergence launch. If a future Convergence Session ratifies a new public destination (e.g., a second cohort program with its own daily show + journey concierge wiring), the 9-phase shape repeats. Phases 1–5 are stream-blocking; 6–9 are post-stream rolling.
  2. Weekly Episode operational rhythm (recurring). Phase 8 (post-stream pipeline) re-runs per episode. Phase 9 (rolling completion + signal monitoring) re-runs per week. The procedure remains canonical for the recurring shape; Q audits annually that the per-episode invocation matches.
  3. Cohort launch wave (recurring per cohort enrollment cycle). AINS cohort enrollment events re-fire Steps 15 (Course + Product writes via Ledger), 37 (journey concierge wiring for cohort-specific signals), 56 (signal monitoring for cohort-specific Interest progression). Provost + Spark coordinate.
  4. Distribution submission cycle (recurring per show launch + per platform). Step 40 Chris-owned distribution platform submissions re-fire when a new show launches OR when an existing show is submitted to a previously-deferred platform.
  5. Pattern recurrence (3+ incidents). Per Echo pattern memory, if any failure mode in §Known failure modes recurs 3+ times across launches, Q opens a CAR and proposes structural prevention (hook, gate, agent-definition change).
  6. System change affecting verification status. Any change to Ledger / Canon / Showcase / Director / Prelude / Splice / Encore / Vigil / Baldwin agent definitions, OR to any property-index file, OR to Mux / Sanity / HubSpot schema, decays VERIFIED markers per verification-protocol.md § Verification Decay. Q schedules ad-hoc audit.
  7. Time-based decay. Tier 1 (Critical) = 90 days. Re-verify by 2026-08-23 OR after the next AINS-pattern launch (whichever is sooner). Code changes to any agent / script / property-index / wiki page referenced here decay all VERIFIED markers immediately.

Verification Score Summary

Phase Steps VERIFIED UNTESTED BLOCKED NOT BUILT CHRIS-OWNED
1 — 5P + PRD + ratification 1–6 6 0 0 0 0
2 — Wave 1 substrate 7–16 8 1 (Step 8) 0 0 0
Phase 2 partial gap Step 15 (counted UNTESTED — partial only)
3 — Wave 2 site build 17–20 1 (Step 17) 1 (Step 18) 1 (Step 19) 1 (Step 20) 0
4 — Wave 3 build follow-ups 21–26 1 (Step 24) 2 (25, 26) 3 (21, 22, 23) 0 0
5 — Wave 4 DoD push 27–37 4 (29, 30, 33, 34) 5 (27, 28, 31, 35, 36) 0 1 (Step 37) 0 + Step 32 VERIFIED (this doc)
6 — Pre-stream readiness 38–40 2 (38, 39) 0 0 0 1 (40)
7 — Day-of-stream rhythm 41–43 0 3 0 0 0
8 — Post-stream pipeline 44–53 0 9 0 0 1 (52)
9 — Rolling completion 54–61 0 7 0 1 (54) 0

Counted denominator: 61 steps − 4 NOT BUILT (counted as gap inventory, excluded per verification-protocol.md scoring rule — wait, Step 20 Foundry tool, Step 37 concierge wiring, Step 54 cross-platform consolidation are NOT BUILT but ARE in scope; review) — recount:

Reclassifying NOT BUILT correctly per verification-protocol: NOT BUILT means "designed or referenced in documentation, but implementation does not exist." Step 20 Foundry tool fits (designed, not built). Step 37 concierge wiring fits (designed, not built). Step 54 cross-platform consolidation fits (designed, not built). All three are excluded from denominator per protocol; they aggregate separately as gap inventory.

Recalculated:

  • Total steps: 61
  • NOT BUILT (excluded): 3 (Steps 20, 37, 54)
  • Denominator: 58
  • VERIFIED: 22 (Steps 1, 2, 3, 4, 5, 6, 7, 9, 10, 11, 12, 13, 14, 16, 17, 24, 29, 30, 32, 33, 34, 38, 39)
  • UNTESTED: 28
  • BLOCKED: 4 (Steps 19, 21, 22, 23)
  • CHRIS-OWNED: 4 (Steps 40, 52, plus 50/Broadcast and 51/Correspondent require Chris ratification but are agent-executable, counted UNTESTED)

Verification Score: 22 / 58 = 37.9%

Status: Draft — NOT OPERATIONAL (threshold for Operational status per verification-protocol.md is ≥80%; threshold for Partially Verified is 50–79%; this is currently 38%).

Path to Operational: Resolve 4 BLOCKED steps (Steps 19, 21, 22, 23 — pre-stream correctives), advance 28 UNTESTED through Phase 6–9 execution; re-promote at Step 61 closure audit (target 2026-05-29 EOD). Most UNTESTED steps will promote naturally as Tuesday stream + post-stream pipeline + rolling completion execute.

Decay window: Tier 1 (Critical) = 90 days. Re-verify by 2026-08-23 OR after the next AINS-pattern launch (whichever is sooner).

Revision History

Date Change Author
2026-05-25 Initial document. Authored from 5P plan (commit 06b6846c1) + PRD + Marshal DoD audit (2026-05-25 ~14:35 CDT) + Wave 1–4 artifacts in /mnt/d/AI-WORKSPACE/ainativeshift/ (content-blocks, methodology-reference, diagrams, legal, design-tokens-advisory, mirror/lookout/waypoint/audit/director/prelude reports). 22 VERIFIED / 58 applicable = 37.9% Draft. 4 BLOCKED pre-stream correctives (apex→www redirect, sitemap/robots/RSS, Sanity show description, HubSpot Listing name gap). 3 NOT BUILT (Foundry assessment tool, 11 journey concierges wiring, cross-platform consolidation) — all in Wave 4–5 rolling-completion window through Friday 2026-05-29. Post-stream pipeline (Phase 8) intentionally UNTESTED until Tuesday Episode 1 closure. Codifies daily-show + AINS-program launch pattern distinct from show-launch.md (AOM/TRTU single-show precedent) on three axes: multi-BU activation, convergence destination, design-system harmonization. Triggering events documented for reuse: next AINS-pattern launch, weekly episode rhythm, cohort enrollment cycle, distribution submission cycle, pattern recurrence (3+), system change, time decay. Q (Quality System Manager)