# 1-on-1 Standard (canonical going forward) This is the operating standard for Jason De Leon's weekly 1-on-1 with Stephanie Ervin and any future leadership 1-on-1 reviews that land in this archive. The HTML format on Cloudflare Pages replaces the prior DOCX pipeline as of 2026-05-11. The DOCX pipeline (python-docx + frozen build script) is preserved in `archive/legacy-build-system/` for historical reference only. Do not build new reviews against it. --- ## Where it lives - **Source folder:** `/Users/jasondeleon/GTME/Douglas/deliverables/jdl-internal-leadership/` - **Production URL:** `https://jdl-internal-leadership.pages.dev/` - **This week pattern:** `weekly-1-on-1-MM.DD.YY/index.html` - **Cloudflare Pages project:** `jdl-internal-leadership` (account `4190f6540aa53db95b2ecd7aa6d03443`) - **Access policy:** Cloudflare Access. Apollo email blanket. Allow rule = emails ending in `@apollo.io`. No PIN, no password. Google IDP (Apollo Workspace). --- ## When it ships Each Sunday or Monday before the Tuesday 1-on-1, build the new dated entry. Goal is to give Stephanie the link plus a paste-ready Slack message 12-24 hours before the call. --- ## What it contains (frozen layout) Mirror the structure of `weekly-1-on-1-05.11.26/index.html`. Sections in order: 1. **Crumb + Hero** with animated Apollo 4-path logo (validated SVG, viewBox `0 0 303 303`), eyebrow, h1 headline, meta line, date pill. 2. **KPI grid** (4 cards). Color-coded: default = Sand 100 + Sunbeam border; `warn` = pinkish-red background + Mist border; `win` = soft green background + Success border. Each card has number, label, sub-line. 3. **Week Headline** (1-2 short paragraphs in Source Serif 4 longform). Lead with the honest read; speak TO Stephanie, not at her. 4. **The Shift / Strategic Thinking** (optional, use when there is a time-allocation or focus shift to discuss). Two-card before/after with arrow between. 5. **What Building Looks Like / Pipeline Visual** (when AI-native or build-pattern content is the headline). Use the 7-stage build pipeline pattern: PROMPT to SKILL to CONNECT to COMMANDS to HOOKS to PLUGIN to SHIP. 6. **Anchor Sessions / Active Builder Examples**. 2-3 cards. Each card has account name, session description, italic "why it scaled" note, and a CTA button linking to the customer resource center if one exists. 7. **Wins** (2 callouts, Sand 100 background plus Sunbeam Core left border). 8. **Cross-Tool Evolution** (Sunbeam Light callout with 4 standing links). 9. **Discussion Items for Stephanie** (3-4 collapsible `
` cards). Title each as a question or invitation. Body uses "would love your read on", "curious how you would weigh", "thinking through". Optional `
` callout for source citations. 10. **Next Week Top Priorities** (max 7-row table, Function Black header). 11. **Footer** with build stamp and source-trace links. --- ## Hard rules every entry must pass - Em-dash scan (U+2014): 0 - En-dash scan (U+2013): 0 - Banned-word scan against the standing list in `.claude/rules/content-lifecycle.md`: 0 hits - Apollo logo: validated 4-path SVG, viewBox `0 0 303 303`, no `` in the logo block, no legacy yellow (`#E8FF00` or `#FEFF2C`) - Sunbeam Core `#F8FF2C` present (CSS variable plus accent uses) - Self-contained: only Google Fonts CDN; no JS frameworks, no external images, no analytics - WCAG AA accessibility: focus rings, 44px touch targets, aria-labels, prefers-reduced-motion respected - All hyperlinks resolve on first load - Mobile breakpoint at 768px; no horizontal overflow on iPhone-width - Print stylesheet visible content (no clipping on Print to PDF) --- ## Voice and tone Speak TO Stephanie. Not at her. Not about her. | Anti-pattern (do not do) | Pattern (do) | |---|---| | "Need alignment on X" | "Curious how you would weigh X" | | "The strategic ask" | "Something I would love your read on" | | "Stop being single point of capacity" | "Move from single point of capacity to shared ownership" | | "Discussion Items for Stephanie" | "Things I would love your read on" | | Hard demand phrasing | Invitation phrasing | | Status-update tone | Conversation tone | Other voice rules: - JDL voice (purpose-first, no preamble, conversational but precise) - Human-Tired-on-Tuesday standard - No banned words (full list at `.claude/rules/content-lifecycle.md`) - No em-dashes anywhere; use colons, semicolons, or periods - Short sentences when short sentences work - Lead with the play, not the infrastructure --- ## Design system (Apollo Beams) Tokens: - **Sunbeam Core** `#F8FF2C` (accent, KPI borders, pipeline rail, focus rings) - **Function Black** `#1A1A1A` (text, table headers, hero pill background) - **Sand** 100 `#F3F0EE` / 200 `#EDEBE8` / 300 `#E5E3E1` / 700 `#47423D` (backgrounds, supporting text) - **Sunbeam Light** `#FEFFD9` (Cross-Tool Evolution callout background, open details background) - **Iris 300** `#9C73FF` (hyperlinks) - **Mist 300** `#FF8077` (warn states, OOO or punted indicators) - **Ocean 300** `#3A6783` (info accents, supporting data) - **Success** `#22C55E` (Closed Won, positive deltas) Fonts: - **Space Grotesk** (hero, h1-h3) - **DM Sans** (body, UI, labels) - **Source Serif 4** (longform paragraphs, italic captions) - **JetBrains Mono** (numbers, code, eyebrow, badges) Radii: `--r-card: 8px`, `--r-container: 12px`, `--r-pill: 24px`. --- ## Recurring weekly workflow ```bash cd /Users/jasondeleon/GTME/Douglas/deliverables/jdl-internal-leadership # 1. Create next dated folder NEXT="weekly-1-on-1-MM.DD.YY" mkdir -p "$NEXT" # 2. Copy current week as starting template cp weekly-1-on-1-05.11.26/index.html "$NEXT/index.html" # 3. Update content (KPIs, headline, anchor sessions, asks, priorities) # Use Edit / Bash heredoc to avoid Write hook em-dash false-positives in QA verification text # 4. Add new entry row to landing index.html (see template inside that file) # 5. Run QA scans before deploy python3 -c "import sys; print(open(sys.argv[1]).read().count(chr(0x2014)))" "$NEXT/index.html" # Banned-word scan: load the list from .claude/rules/content-lifecycle.md and grep each word against the new file. Expect 0 hits per word. grep -c 'viewBox="0 0 303 303"' "$NEXT/index.html" # 6. Render thumbnail mkdir -p /tmp/qa-$NEXT qlmanage -t -s 1600 -o /tmp/qa-$NEXT "$NEXT/index.html" # 7. Deploy wrangler pages deploy . --project-name=jdl-internal-leadership --branch=main # 8. Verify production URL curl -sI https://jdl-internal-leadership.pages.dev/$NEXT/ | head -3 # 9. Update SURFACE-SYNC + 95-Memory pointer # 10. Send paste-ready Slack message to Stephanie with the link ``` --- ## Data sources for each weekly review Always pull from: - **Google Calendar** (filter to client-facing calls, external attendees > 0, exclude recurring internal blocks) - **Notion BoB** (ARR, renewal date, GTME owner per account touched) - **SFDC apollo-sfdc CLI** (`sf data query` for renewal pipeline plus closed-won plus GTME-owned opps) - **Slack** (`#csql-notifications` for CSQLs; relevant client channels for active threads) - **95-Memory deliverables plus research outputs** (modified within window) - **SURFACE-SYNC.md** (entries within window for cross-surface deliverables) - **Customer Hub CFQ dashboard** when available Cite every claim. Source-trace section in the footer lists every artifact referenced. --- ## What NOT to include going forward - Intervention conversion charts unless conversion is the headline ask - Big-number ARR Touched as the headline metric (volume is not the right signal) - Packaging Spec audits as a doc framing lens (the Packaging Spec is an example, not the rubric) - Hard-edged asks that read as demands - 1:1 call lists by account unless the volume signal is the explicit story - Anything that smells like a status update from a job application; this is a conversation with a manager --- ## What MUST appear every week - Honest call count and OOO context - Active-builder anchor sessions (1-3 cards) when they exist - 2-3 wins, each with a source link - Cross-Tool Evolution standing 4 links - 3-4 discussion items framed as invitations - Next week priorities (max 7 rows) - Source-trace footer --- ## Reference implementation `weekly-1-on-1-05.11.26/index.html`. Use as the structural and visual reference for every subsequent build. Customize headline, KPIs, sections, and discussion items per week; keep the topbar, favicon, brand lockup, frozen 10-section order, and design system tokens consistent. --- *Apollo.io GTME · Jason De Leon · Confidential · Apollo email-gated* *Standard locked 2026-05-11*