{"v":1,"files":[{"t":"The Project Plan · Custom LLM Company Brain (Demo)","p":"docs/00 Start Here/CUSTOM-LLM-PROJECT-PLAN.html","s":"00 Start Here"},{"t":"Start Here, the Custom LLM brain in ten minutes","p":"docs/00 Start Here/START-HERE.html","s":"00 Start Here"},{"t":"Using Claude with the brain, the team handbook","p":"docs/00 Start Here/USING-CLAUDE-WITH-THE-BRAIN.html","s":"00 Start Here"},{"t":"Not in the demo","p":"docs/00 Start Here/not-in-demo.html","s":"00 Start Here"},{"t":"Custom LLM, Company Brain","p":"docs/01 The Brain/AGENTS.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/Private Practice/_about.html","s":"01 The Brain"},{"t":"Approved, canonical truth","p":"docs/01 The Brain/Approved/README.html","s":"01 The Brain"},{"t":"INDEX · Agent Outputs · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/README.html","s":"01 The Brain"},{"t":"/brandcheck · Brand Check · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/brandcheck-report.html","s":"01 The Brain"},{"t":"/draft · Drafted Welcome Letter · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/draft-welcome-letter.html","s":"01 The Brain"},{"t":"/facts · Sourced Answer · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/facts-answer.html","s":"01 The Brain"},{"t":"/file · Filing Receipt · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/filing-receipt.html","s":"01 The Brain"},{"t":"/proof · Proof Verdict · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/proof-verdict.html","s":"01 The Brain"},{"t":"/revoice · Revoice: Before / After · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/revoice-before-after.html","s":"01 The Brain"},{"t":"/scribe · Meeting Distillation · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/scribe-meeting-distillation.html","s":"01 The Brain"},{"t":"/status · Weekly Status Digest · Approved (Demo)","p":"docs/01 The Brain/Approved/agent-outputs/status-digest.html","s":"01 The Brain"},{"t":"INDEX · The Collateral Shelf · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/README.html","s":"01 The Brain"},{"t":"T01 · Letterhead · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T01-letterhead.html","s":"01 The Brain"},{"t":"T02 · One-pager · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T02-one-pager.html","s":"01 The Brain"},{"t":"T03 · Proposal · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T03-proposal.html","s":"01 The Brain"},{"t":"T04 · Leave-behind · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T04-leave-behind.html","s":"01 The Brain"},{"t":"T05 · Card + Signature + QR · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T05-card-signature.html","s":"01 The Brain"},{"t":"T06 · OG / Share Image · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T06-og-image.html","s":"01 The Brain"},{"t":"T07 · Email Chrome · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T07-email-chrome.html","s":"01 The Brain"},{"t":"T08 · Deck Theme · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T08-deck-theme.html","s":"01 The Brain"},{"t":"T09 · Social Frames · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T09-social-frames.html","s":"01 The Brain"},{"t":"T10 · Document Chrome · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T10-document-chrome.html","s":"01 The Brain"},{"t":"T11 · Price Sheet · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T11-price-sheet.html","s":"01 The Brain"},{"t":"T12 · Welcome Flyer · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T12-welcome-flyer.html","s":"01 The Brain"},{"t":"T13 · Checklist Guide · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T13-checklist-guide.html","s":"01 The Brain"},{"t":"T14 · Intake Form (print) · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T14-intake-form.html","s":"01 The Brain"},{"t":"T15 · Microsite Canon · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T15-microsite.html","s":"01 The Brain"},{"t":"T16 · Landing Page · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T16-landing-page.html","s":"01 The Brain"},{"t":"T17 · Executive Summary Pair · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T17-exec-summary.html","s":"01 The Brain"},{"t":"T18 · Blog Treatment · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T18-blog.html","s":"01 The Brain"},{"t":"T19 · Trifold + Catalog · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T19-trifold-catalog.html","s":"01 The Brain"},{"t":"T20 · Mailer + Certificate · Approved (Demo)","p":"docs/01 The Brain/Approved/brand-collateral/T20-mailer-certificate.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/internal/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/locations/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/partners/Anchor Partners/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/partners/Calibration & Alignment/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/partners/GPOs/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/partners/GSOs/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/partners/Tech & Software/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Approved/product-lines/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Brand/custom-llm/brand-assets/colors-and-fonts/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Brand/custom-llm/brand-assets/email-signatures/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Brand/custom-llm/brand-assets/letterhead/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Brand/custom-llm/brand-assets/logos/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Brand/custom-llm/brand-assets/media-library/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Brand/custom-llm/brand-assets/photography/_about.html","s":"01 The Brain"},{"t":"Brand OS v0.2, Atlas audit (2026-08-05)","p":"docs/01 The Brain/Brand/custom-llm/brand-os/AUDIT-v0.2.html","s":"01 The Brain"},{"t":"The Brand Sheet · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Brand/custom-llm/brand-sheet.html","s":"01 The Brain"},{"t":"Direction 4, Evergreen · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Brand/custom-llm/directions/Direction-4-EVERGREEN.html","s":"01 The Brain"},{"t":"Brand directions, Evergreen leads","p":"docs/01 The Brain/Brand/custom-llm/directions/_INDEX.html","s":"01 The Brain"},{"t":"How the Brain Uses the Brand OS · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Brand/custom-llm/how-the-brain-uses-the-brand-os.html","s":"01 The Brain"},{"t":"Custom LLM logo mockups, index (renamed by Atlas 2026-08-05)","p":"docs/01 The Brain/Brand/custom-llm/logo-mockups/_INDEX.html","s":"01 The Brain"},{"t":"The Constitution · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/CLAUDE.html","s":"01 The Brain"},{"t":"Claims &amp; credentials, SOLE CLAIMS SOURCE","p":"docs/01 The Brain/Facts/about-company/claims-and-credentials.html","s":"01 The Brain"},{"t":"Company Overview · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Facts/about-company/company-overview.html","s":"01 The Brain"},{"t":"Pricing, SOLE QUOTABLE SOURCE","p":"docs/01 The Brain/Facts/about-company/pricing.html","s":"01 The Brain"},{"t":"2026-08-11, Weekly Marketing Updates (verbatim source)","p":"docs/01 The Brain/Facts/about-company/source-docs/2026-08-11-weekly-marketing-updates-transcript.html","s":"01 The Brain"},{"t":"Custom LLM Knowledge","p":"docs/01 The Brain/Facts/about-company/source-docs/custom-llm-knowledge.html","s":"01 The Brain"},{"t":"Brain Intake Packet, Custom LLM (operator-assisted)","p":"docs/01 The Brain/Facts/about-company/source-docs/intake-packet-2026-08-05.html","s":"01 The Brain"},{"t":"Personas","p":"docs/01 The Brain/Facts/client-personas/personas.html","s":"01 The Brain"},{"t":"Grandview Labs, the retention threat","p":"docs/01 The Brain/Facts/competitors/grandview.html","s":"01 The Brain"},{"t":"Competitive landscape &amp; retention strategy (updated from the strategy docs)","p":"docs/01 The Brain/Facts/competitors/landscape-summary.html","s":"01 The Brain"},{"t":"Decisions log, Custom LLM","p":"docs/01 The Brain/Facts/decisions/decisions-log.html","s":"01 The Brain"},{"t":"Canonical FAQ, Custom LLM","p":"docs/01 The Brain/Facts/faqs/client-faq.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Facts/glossary/_about.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Facts/launch/_about.html","s":"01 The Brain"},{"t":"Day-1 Playbook · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Facts/launch/day-1-playbook.html","s":"01 The Brain"},{"t":"Media + PR plan, the external narrative machine","p":"docs/01 The Brain/Facts/launch/media-and-pr-plan.html","s":"01 The Brain"},{"t":"The Retention Engine, account management for zero attrition","p":"docs/01 The Brain/Facts/launch/retention-engine.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Facts/locations/_about.html","s":"01 The Brain"},{"t":"2026-08-04, Weekly Marketing (the Custom LLM kickoff)","p":"docs/01 The Brain/Facts/meetings/2026/08/2026-08-04-weekly-marketing.html","s":"01 The Brain"},{"t":"2026-08-06, Jordan* + Avery*: website, domains, brand review","p":"docs/01 The Brain/Facts/meetings/2026/08/2026-08-06-website-llm-avery.html","s":"01 The Brain"},{"t":"Integration alignment working session (exec circle, date per recording; filed 2026-08-08)","p":"docs/01 The Brain/Facts/meetings/2026/08/2026-08-0X-integration-alignment-session.html","s":"01 The Brain"},{"t":"2026-08-11, Weekly Marketing Updates (the project circle)","p":"docs/01 The Brain/Facts/meetings/2026/08/2026-08-11-weekly-marketing-updates.html","s":"01 The Brain"},{"t":"Meetings, filing convention","p":"docs/01 The Brain/Facts/meetings/README.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Facts/partners/_about.html","s":"01 The Brain"},{"t":"Team directory, who covers what at Custom LLM","p":"docs/01 The Brain/Facts/people-and-org/team-directory.html","s":"01 The Brain"},{"t":"Team & Escalation · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Facts/people-and-org/team.html","s":"01 The Brain"},{"t":"Products &amp; services, ports post-announcement","p":"docs/01 The Brain/Facts/products-services/_about.html","s":"01 The Brain"},{"t":"Sample pricing data","p":"docs/01 The Brain/Facts/products-services/price-lists/README.html","s":"01 The Brain"},{"t":"Sample pricing data","p":"docs/01 The Brain/Facts/products-services/price-lists/advantage-devices-price-list.html","s":"01 The Brain"},{"t":"Sample pricing data","p":"docs/01 The Brain/Facts/products-services/price-lists/brookfield-apexinst-silverton-contract-2026.html","s":"01 The Brain"},{"t":"Sample pricing data","p":"docs/01 The Brain/Facts/products-services/price-lists/oc-apexinst-account-price-lists.html","s":"01 The Brain"},{"t":"Sample pricing data","p":"docs/01 The Brain/Facts/products-services/price-lists/oc-apexinst-common-price-list.html","s":"01 The Brain"},{"t":"Sample pricing data","p":"docs/01 The Brain/Facts/products-services/price-lists/silverton-price-list-2026-07-09.html","s":"01 The Brain"},{"t":"Reference index, pointers","p":"docs/01 The Brain/Facts/reference-index/README.html","s":"01 The Brain"},{"t":"the CRM file directory, hosted files the brain knows","p":"docs/01 The Brain/Facts/reference-index/crm-file-directory.html","s":"01 The Brain"},{"t":"Source registry, every ingestion source declared (single-ingestion rule)","p":"docs/01 The Brain/Facts/reference-index/source-registry.html","s":"01 The Brain"},{"t":"WordPress asset directory, every hosted upload the brain knows","p":"docs/01 The Brain/Facts/reference-index/wordpress-asset-directory.html","s":"01 The Brain"},{"t":"WordPress page directory, the live team hub pages","p":"docs/01 The Brain/Facts/reference-index/wordpress-page-directory.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Facts/services/README.html","s":"01 The Brain"},{"t":"The Hub Plan · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Hub/HUB-PLAN.html","s":"01 The Brain"},{"t":"Hub, NOT YET ACTIVATED","p":"docs/01 The Brain/Hub/README.html","s":"01 The Brain"},{"t":"The Agent Team, specialists you can activate","p":"docs/01 The Brain/Hub/agent-roster.html","s":"01 The Brain"},{"t":"How the Custom LLM Brain Works, the team guide","p":"docs/01 The Brain/Hub/operating-guide.html","s":"01 The Brain"},{"t":"The Skill Library, what the brain knows how to do","p":"docs/01 The Brain/Hub/skills-roster.html","s":"01 The Brain"},{"t":"Asset directory, generated navigation index","p":"docs/01 The Brain/Log/asset-directory.html","s":"01 The Brain"},{"t":"Changelog","p":"docs/01 The Brain/Log/changelog.html","s":"01 The Brain"},{"t":"Work log","p":"docs/01 The Brain/Log/work-log.html","s":"01 The Brain"},{"t":"Questions for the team, Custom LLM","p":"docs/01 The Brain/QUESTIONS-FOR-THE-TEAM.html","s":"01 The Brain"},{"t":"Team Cover Page · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/README.html","s":"01 The Brain"},{"t":"Roadmap, Custom LLM Brain · the dated line to September 1 (and beyond)","p":"docs/01 The Brain/ROADMAP.html","s":"01 The Brain"},{"t":"Positioning &amp; messaging, the locked platform (GTM §4 + integration alignment)","p":"docs/01 The Brain/Rules/brand-foundation/positioning-and-messaging.html","s":"01 The Brain"},{"t":"Channel: Blog / SEO","p":"docs/01 The Brain/Rules/channel-styles/blog-seo.html","s":"01 The Brain"},{"t":"Channel: Email","p":"docs/01 The Brain/Rules/channel-styles/email.html","s":"01 The Brain"},{"t":"Channel: LinkedIn","p":"docs/01 The Brain/Rules/channel-styles/linkedin.html","s":"01 The Brain"},{"t":"Channel: Proposal / report","p":"docs/01 The Brain/Rules/channel-styles/proposal-report.html","s":"01 The Brain"},{"t":"Channel: Website","p":"docs/01 The Brain/Rules/channel-styles/website.html","s":"01 The Brain"},{"t":"Examples, golden standards","p":"docs/01 The Brain/Rules/examples.html","s":"01 The Brain"},{"t":"Guardrails, the hard limits","p":"docs/01 The Brain/Rules/guardrails.html","s":"01 The Brain"},{"t":"House style, the mechanics","p":"docs/01 The Brain/Rules/house-style.html","s":"01 The Brain"},{"t":"Master instructions, how to think","p":"docs/01 The Brain/Rules/master-instructions.html","s":"01 The Brain"},{"t":"Naming conventions","p":"docs/01 The Brain/Rules/naming-conventions.html","s":"01 The Brain"},{"t":"Output types, deliverable playbooks","p":"docs/01 The Brain/Rules/output-types/README.html","s":"01 The Brain"},{"t":"Directions, Announcement kit","p":"docs/01 The Brain/Rules/output-types/directions-announcement-kit.html","s":"01 The Brain"},{"t":"Directions, Launch website (3 pages)","p":"docs/01 The Brain/Rules/output-types/directions-launch-website.html","s":"01 The Brain"},{"t":"Directions, Partner Collateral Build (the chunk recipe)","p":"docs/01 The Brain/Rules/output-types/directions-partner-collateral-build.html","s":"01 The Brain"},{"t":"Directions, Dedicated Support Team Contact Update","p":"docs/01 The Brain/Rules/output-types/directions-support-team-contact-update.html","s":"01 The Brain"},{"t":"Directions, Updating the live Team Hub pages","p":"docs/01 The Brain/Rules/output-types/directions-team-hub-update.html","s":"01 The Brain"},{"t":"Directions, Welcome / retention kit (the field network customers)","p":"docs/01 The Brain/Rules/output-types/directions-welcome-retention-kit.html","s":"01 The Brain"},{"t":"Audience: Apex Instruments internal team (the primary risk on our side)","p":"docs/01 The Brain/Rules/target-audiences/apex-internal-team.html","s":"01 The Brain"},{"t":"Audience: GSO leadership, corporate, and trade","p":"docs/01 The Brain/Rules/target-audiences/gso-corporate-trade.html","s":"01 The Brain"},{"t":"Audience: Incoming the field network customers (the highest-stakes group, retention IS the goal)","p":"docs/01 The Brain/Rules/target-audiences/incoming-northlight-customers.html","s":"01 The Brain"},{"t":"Audience: Legacy Apex Instruments customers","p":"docs/01 The Brain/Rules/target-audiences/legacy-apex-customers.html","s":"01 The Brain"},{"t":"Approved phrases (the platform language, use freely, quote exactly where marked)","p":"docs/01 The Brain/Rules/voice-and-language/approved-phrases.html","s":"01 The Brain"},{"t":"Banned words &amp; phrases, updated for the rebrand platform (supersedes the holding-company era)","p":"docs/01 The Brain/Rules/voice-and-language/banned-phrases.html","s":"01 The Brain"},{"t":"Brand voice, Custom LLM","p":"docs/01 The Brain/Rules/voice-and-language/brand-voice.html","s":"01 The Brain"},{"t":"Writing tones, pick exactly one per piece","p":"docs/01 The Brain/Rules/writing-tones/README.html","s":"01 The Brain"},{"t":"Tone: Compliance clear","p":"docs/01 The Brain/Rules/writing-tones/compliance-clear.html","s":"01 The Brain"},{"t":"Tone: Executive brief","p":"docs/01 The Brain/Rules/writing-tones/executive-brief.html","s":"01 The Brain"},{"t":"Tone: Founder voice, {{owner_first_name}}","p":"docs/01 The Brain/Rules/writing-tones/founder-voice.html","s":"01 The Brain"},{"t":"Tone: High-energy promo","p":"docs/01 The Brain/Rules/writing-tones/high-energy-promo.html","s":"01 The Brain"},{"t":"Tone: Peer professional","p":"docs/01 The Brain/Rules/writing-tones/peer-professional.html","s":"01 The Brain"},{"t":"Tone: Plain teacher","p":"docs/01 The Brain/Rules/writing-tones/plain-teacher.html","s":"01 The Brain"},{"t":"Tone: Reassuring advisor","p":"docs/01 The Brain/Rules/writing-tones/reassuring-advisor.html","s":"01 The Brain"},{"t":"The skill pattern, why these skills work","p":"docs/01 The Brain/Skills/_SKILL-PATTERN.html","s":"01 The Brain"},{"t":"Tier 2, module skills (installed per intake §10)","p":"docs/01 The Brain/Skills/_TIER-2-MODULES.html","s":"01 The Brain"},{"t":"Brand deck","p":"docs/01 The Brain/Skills/brand-deck/skill.html","s":"01 The Brain"},{"t":"Brand email","p":"docs/01 The Brain/Skills/brand-email/skill.html","s":"01 The Brain"},{"t":"Brand leave-behind","p":"docs/01 The Brain/Skills/brand-leave-behind/skill.html","s":"01 The Brain"},{"t":"Brand one-pager","p":"docs/01 The Brain/Skills/brand-one-pager/skill.html","s":"01 The Brain"},{"t":"Brand proposal","p":"docs/01 The Brain/Skills/brand-proposal/skill.html","s":"01 The Brain"},{"t":"Brand social","p":"docs/01 The Brain/Skills/brand-social/skill.html","s":"01 The Brain"},{"t":"custom-llm-deck, STUB","p":"docs/01 The Brain/Skills/custom-llm-deck/skill.html","s":"01 The Brain"},{"t":"custom-llm-docket-lab-slip, STUB","p":"docs/01 The Brain/Skills/custom-llm-docket-lab-slip/skill.html","s":"01 The Brain"},{"t":"custom-llm-email, STUB","p":"docs/01 The Brain/Skills/custom-llm-email/skill.html","s":"01 The Brain"},{"t":"custom-llm-executive-summary, STUB","p":"docs/01 The Brain/Skills/custom-llm-executive-summary/skill.html","s":"01 The Brain"},{"t":"custom-llm-landing-page, STUB","p":"docs/01 The Brain/Skills/custom-llm-landing-page/skill.html","s":"01 The Brain"},{"t":"custom-llm-microsite, STUB","p":"docs/01 The Brain/Skills/custom-llm-microsite/skill.html","s":"01 The Brain"},{"t":"custom-llm-price-sheet, STUB","p":"docs/01 The Brain/Skills/custom-llm-price-sheet/skill.html","s":"01 The Brain"},{"t":"custom-llm-print-one-pager, STUB","p":"docs/01 The Brain/Skills/custom-llm-print-one-pager/skill.html","s":"01 The Brain"},{"t":"custom-llm-quick-start-guide, STUB","p":"docs/01 The Brain/Skills/custom-llm-quick-start-guide/skill.html","s":"01 The Brain"},{"t":"custom-llm-social, STUB","p":"docs/01 The Brain/Skills/custom-llm-social/skill.html","s":"01 The Brain"},{"t":"custom-llm-welcome-flyer, STUB","p":"docs/01 The Brain/Skills/custom-llm-welcome-flyer/skill.html","s":"01 The Brain"},{"t":"custom-llm-whats-needed-guide, STUB","p":"docs/01 The Brain/Skills/custom-llm-whats-needed-guide/skill.html","s":"01 The Brain"},{"t":"Deploy preview","p":"docs/01 The Brain/Skills/deploy-preview/skill.html","s":"01 The Brain"},{"t":"File {{owner_first_name}}'s answer","p":"docs/01 The Brain/Skills/file-owners-answer/skill.html","s":"01 The Brain"},{"t":"Folder Cleanup, the standard process","p":"docs/01 The Brain/Skills/folder-cleanup/skill.html","s":"01 The Brain"},{"t":"The graph library, ready-to-run specs for this brain's wide jobs","p":"docs/01 The Brain/Skills/graph-engineering/graph-library.html","s":"01 The Brain"},{"t":"Reference, the Graph Engineering article, distilled","p":"docs/01 The Brain/Skills/graph-engineering/reference/graph-engineering-article.html","s":"01 The Brain"},{"t":"Graph engineering, the brain's wide-work engine","p":"docs/01 The Brain/Skills/graph-engineering/skill.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Skills/maintenance/_about.html","s":"01 The Brain"},{"t":"Twin sync, the md/html twin doctrine, automated","p":"docs/01 The Brain/Skills/maintenance/twin-sync/skill.html","s":"01 The Brain"},{"t":"Mercado* Presentation Style (overlay on custom-llm-deck)","p":"docs/01 The Brain/Skills/mercado-presentation-style/skill.html","s":"01 The Brain"},{"t":"Pre-delivery scan","p":"docs/01 The Brain/Skills/pre-delivery-scan/skill.html","s":"01 The Brain"},{"t":"Brain inventory, the real options menu (Custom LLM launch set)","p":"docs/01 The Brain/Skills/prompt-enhancer/reference/brain-inventory.html","s":"01 The Brain"},{"t":"Prompt enhancer, the front door","p":"docs/01 The Brain/Skills/prompt-enhancer/skill.html","s":"01 The Brain"},{"t":"The acceptance test, run in any fresh session with the brain attached","p":"docs/01 The Brain/Skills/quality-control/acceptance-test.html","s":"01 The Brain"},{"t":"Templates, starting points","p":"docs/01 The Brain/Templates/README.html","s":"01 The Brain"},{"t":"AI brand kit, paste into any external AI","p":"docs/01 The Brain/Templates/ai-brand-kit/ai-brand-instructions.html","s":"01 The Brain"},{"t":"Email patterns","p":"docs/01 The Brain/Templates/email/patterns.html","s":"01 The Brain"},{"t":"The Send-Ready Library · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Templates/launch-copy/README.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/launch-copy/ceo-allstaff-emails.html","s":"01 The Brain"},{"t":"Crisis call scripts, live handling for AMs and SAEs","p":"docs/01 The Brain/Templates/launch-copy/crisis-call-scripts.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/launch-copy/letter-incoming-northlight-doctors.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/launch-copy/letter-legacy-apex-doctors.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/launch-copy/nurture-sequence-5-emails.html","s":"01 The Brain"},{"t":"Press Release, DRAFT · Custom LLM Company Brain (Demo)","p":"docs/01 The Brain/Templates/launch-copy/press-release-draft.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/launch-copy/rep-welcome-talk-track.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/launch-copy/vendor-continuity-letter.html","s":"01 The Brain"},{"t":"LinkedIn patterns","p":"docs/01 The Brain/Templates/linkedin/patterns.html","s":"01 The Brain"},{"t":"Custom LLM Brain","p":"docs/01 The Brain/Templates/prompt-library/_about.html","s":"01 The Brain"},{"t":"Starter prompts, tested against this brain","p":"docs/01 The Brain/Templates/prompt-library/starter-prompts.html","s":"01 The Brain"},{"t":"Client onboarding checklist","p":"docs/01 The Brain/Templates/sales/onboarding-checklist.html","s":"01 The Brain"},{"t":"Sales talking points","p":"docs/01 The Brain/Templates/sales/talking-points.html","s":"01 The Brain"},{"t":"Logo cutouts, transparent PNGs, backgrounds professionally removed (2026-08-06)","p":"docs/02 Brand/Brand Explorations/logo-cutouts/_INDEX.html","s":"02 Brand"},{"t":"Custom LLM logo mockups, index (renamed by Atlas 2026-08-05)","p":"docs/02 Brand/Brand Explorations/logo-mockups/_INDEX.html","s":"02 Brand"},{"t":"The Brand OS Master Template","p":"docs/02 Brand/Brand OS/Brand-OS-Master-Template.html","s":"02 Brand"},{"t":"DJVF Brand OS · v3.0 · Atlas","p":"docs/02 Brand/Brand OS/Custom LLM Brand OS v0.6 Evergreen (standalone).html","s":"02 Brand"},{"t":"Material-Concept Prompts · Custom LLM Company Brain (Demo)","p":"docs/02 Brand/Brand OS/MATERIAL-CONCEPT-PROMPTS.html","s":"02 Brand"},{"t":"Brand OS v0.2, Atlas audit (2026-08-05)","p":"docs/02 Brand/Brand OS/brand-os-audits.html","s":"02 Brand"},{"t":"Apex LLM, live structural map + rebrand workload","p":"docs/03 Knowledge and Sources/Apex-LLM-LIVE-MAP.html","s":"03 Knowledge and Sources"},{"t":"Brain Intake Packet, Custom LLM (operator-assisted)","p":"docs/03 Knowledge and Sources/CUSTOM-LLM-INTAKE-PACKET.html","s":"03 Knowledge and Sources"},{"t":"Call transcripts","p":"docs/03 Knowledge and Sources/Call Transcripts/README.html","s":"03 Knowledge and Sources"},{"t":"Custom LLM Knowledge","p":"docs/03 Knowledge and Sources/Custom LLM Knowledge.html","s":"03 Knowledge and Sources"},{"t":"Apex Brain Network Map → Custom LLM Brain Structure","p":"docs/04 Plans/Apex-BRAIN-NETWORK-MAP.html","s":"04 Plans"},{"t":"Apex Parity Audit → the Custom LLM build list","p":"docs/04 Plans/Apex-PARITY-AUDIT-AND-BUILD-LIST.html","s":"04 Plans"},{"t":"The Rebrand Batch Plan, recreating the Apex library as Custom LLM","p":"docs/04 Plans/CUSTOM-LLM-REBRAND-BATCH-PLAN.html","s":"04 Plans"},{"t":"Custom LLM Rebrand Migration Plan, Apex Collateral → Custom LLM Brand","p":"docs/04 Plans/CUSTOM-LLM-REBRAND-MIGRATION-PLAN.html","s":"04 Plans"},{"t":"Rebrand batch tracker, the live register behind the Batch Board","p":"docs/04 Plans/REBRAND-BATCH-TRACKER.html","s":"04 Plans"},{"t":"Custom LLM Brain","p":"docs/05 Work Zone/Avery/_about.html","s":"05 Work Zone"},{"t":"Custom LLM Brain, operator handoff prompt","p":"docs/05 Work Zone/Jordan/00 My Space/HANDOFF-PROMPT.html","s":"05 Work Zone"},{"t":"Saved design ideas, built, parked, ready to use","p":"docs/05 Work Zone/Jordan/00 My Space/SAVED-DESIGN-IDEAS.html","s":"05 Work Zone"},{"t":"SharePoint hub diff: Apex's live team hub vs the Custom LLM site","p":"docs/05 Work Zone/Jordan/00 My Space/SHAREPOINT-HUB-DIFF.html","s":"05 Work Zone"},{"t":"Hero background options · Custom LLM Brain","p":"docs/05 Work Zone/Jordan/00 My Space/hero-background-options.html","s":"05 Work Zone"},{"t":"Every clickable link on the site, and what it opens","p":"docs/05 Work Zone/Jordan/00 My Space/site-link-inventory.html","s":"05 Work Zone"},{"t":"Site navigation, the full map, what's broken, and 3 layout options","p":"docs/05 Work Zone/Jordan/00 My Space/site-navigation-audit-and-options.html","s":"05 Work Zone"},{"t":"Test file, safe to delete","p":"docs/05 Work Zone/Jordan/04 Archived/TEST-approval-notification.html","s":"05 Work Zone"},{"t":"Custom LLM Brain","p":"docs/05 Work Zone/Jordan/_about.html","s":"05 Work Zone"},{"t":"Custom LLM Brain","p":"docs/05 Work Zone/Josie/_about.html","s":"05 Work Zone"},{"t":"Custom LLM Brain","p":"docs/05 Work Zone/Morgan/_about.html","s":"05 Work Zone"},{"t":"The Work Zone, how the team works before the brain takes over","p":"docs/05 Work Zone/README.html","s":"05 Work Zone"},{"t":"Custom LLM Brain","p":"docs/05 Work Zone/Sami/_about.html","s":"05 Work Zone"},{"t":"Custom LLM Brain","p":"docs/05 Work Zone/_shared/_about.html","s":"05 Work Zone"},{"t":"Batch 0 report, the chassis and the swap kit","p":"docs/05 Work Zone/_shared/migration/batch-0/BATCH-0-REPORT.html","s":"05 Work Zone"},{"t":"Footer Pill Partial","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_partials/footer-pill.html","s":"05 Work Zone"},{"t":"Header Pill Partial","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_partials/header-pill.html","s":"05 Work Zone"},{"t":"_notes","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_project-template/_notes/_about.html","s":"05 Work Zone"},{"t":"_references","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_project-template/_references/_about.html","s":"05 Work Zone"},{"t":"deliverables","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_project-template/deliverables/_about.html","s":"05 Work Zone"},{"t":"*Templates*","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_readme.html","s":"05 Work Zone"},{"t":"Template Audit","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/_template-audit.html","s":"05 Work Zone"},{"t":"Briefing 01: Co-Branded PDF Chassis (the print shell)","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/01-co-branded-pdf-chassis-briefing.html","s":"05 Work Zone"},{"t":"Briefing 02: Partner Microsite (REWRITE 2026-05-01)","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/02-microsite-briefing.html","s":"05 Work Zone"},{"t":"Briefing 03: Welcome Flyer (formerly Welcome Packet / Co-Branded Welcome PDF)","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/03-welcome-flyer-briefing.html","s":"05 Work Zone"},{"t":"Briefing 04: Price List","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/04-price-list-briefing.html","s":"05 Work Zone"},{"t":"Briefing 05: What's Needed Guide","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/05-whats-needed-guide-briefing.html","s":"05 Work Zone"},{"t":"Briefing 06: Bench &amp; Rack Guide (REWRITE 2026-05-01: standalone, not a What's Needed wrapper)","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/06-bench-and-rack-guide-briefing.html","s":"05 Work Zone"},{"t":"Briefing 07: Promo Flyer","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/07-promo-flyer-briefing.html","s":"05 Work Zone"},{"t":"Briefing 08: Executive Summary (dual pair)","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/08-executive-summary-briefing.html","s":"05 Work Zone"},{"t":"Briefing 09: Lab Slip / Docket","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/09-lab-slip-briefing.html","s":"05 Work Zone"},{"t":"Briefing 10: Account Onboarding SOP","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/10-account-onboarding-sop-briefing.html","s":"05 Work Zone"},{"t":"Briefings Update Log","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/briefings/_update-log.html","s":"05 Work Zone"},{"t":"Custom LLM Component Library","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/components/component-library.html","s":"05 Work Zone"},{"t":"Custom LLM Email Request Form v2","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/email-forms/apex-email-request-form-v2.html","s":"05 Work Zone"},{"t":"Email Series Campaign Form","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/email-forms/email-series-campaign-form.html","s":"05 Work Zone"},{"t":"Bench &amp; Rack Guide Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/bench-and-rack-guide-template.html","s":"05 Work Zone"},{"t":"Critical Bar Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/critical-bar.html","s":"05 Work Zone"},{"t":"Important Bar Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/important-bar.html","s":"05 Work Zone"},{"t":"Info Note Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/info-note.html","s":"05 Work Zone"},{"t":"Photo Grid 2x2 Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/photo-grid-2x2.html","s":"05 Work Zone"},{"t":"Photo Grid 3x2 Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/photo-grid-3x2.html","s":"05 Work Zone"},{"t":"QR Block Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/qr-block.html","s":"05 Work Zone"},{"t":"Section Card (Text Only) Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/section-card-text-only.html","s":"05 Work Zone"},{"t":"Section Card (With Image) Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/snippets/section-card-with-image.html","s":"05 Work Zone"},{"t":"What's Needed Guide Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/guides/whats-needed-guide-template.html","s":"05 Work Zone"},{"t":"Resource Card Catalog","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/microsite/card-catalog.html","s":"05 Work Zone"},{"t":"Partner Microsite Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/microsite/microsite-template.html","s":"05 Work Zone"},{"t":"OpenForm Product Page Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/openform-product-page/openform-product-page-template.html","s":"05 Work Zone"},{"t":"Build 1 Report: Co-Branded PDF Chassis","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/print-pdf-shell-build-report.html","s":"05 Work Zone"},{"t":"REFERENCE: One-Pager Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/print/reference-one-pager-template.html","s":"05 Work Zone"},{"t":"REFERENCE: Tri-Fold Brochure Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/print/reference-trifold-brochure-template.html","s":"05 Work Zone"},{"t":"REFERENCE: Two-Pager Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/print/reference-two-pager-template.html","s":"05 Work Zone"},{"t":"Facebook Post Template: 1200x630","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-facebook-post.html","s":"05 Work Zone"},{"t":"Instagram Post Template: 1080x1350","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-instagram-post.html","s":"05 Work Zone"},{"t":"Instagram Square Post Template: 1080x1080","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-instagram-square.html","s":"05 Work Zone"},{"t":"Instagram/Facebook Story Template: 1080x1920","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-instagram-story.html","s":"05 Work Zone"},{"t":"LinkedIn Post Template: 1200x627","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-linkedin-post.html","s":"05 Work Zone"},{"t":"LinkedIn Story Template: 1080x1920","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-linkedin-story.html","s":"05 Work Zone"},{"t":"Universal Story Template: 1080x1920","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-universal-story.html","s":"05 Work Zone"},{"t":"YouTube / Webinar Thumbnail Template: 1280x720","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/social/social-youtube-thumbnail.html","s":"05 Work Zone"},{"t":"Template Build Plan","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/template-build-plan.html","s":"05 Work Zone"},{"t":"Welcome Flyer Template","p":"docs/05 Work Zone/_shared/migration/batch-0/custom-llm/welcome-flyer/welcome-flyer-template.html","s":"05 Work Zone"},{"t":"Header Pill Partial","p":"docs/05 Work Zone/_shared/migration/batch-0/source/_partials/header-pill.html","s":"05 Work Zone"},{"t":"_notes","p":"docs/05 Work Zone/_shared/migration/batch-0/source/_project-template/_notes/_about.html","s":"05 Work Zone"},{"t":"_references","p":"docs/05 Work Zone/_shared/migration/batch-0/source/_project-template/_references/_about.html","s":"05 Work Zone"},{"t":"deliverables","p":"docs/05 Work Zone/_shared/migration/batch-0/source/_project-template/deliverables/_about.html","s":"05 Work Zone"},{"t":"*Templates*","p":"docs/05 Work Zone/_shared/migration/batch-0/source/_readme.html","s":"05 Work Zone"},{"t":"Template Audit","p":"docs/05 Work Zone/_shared/migration/batch-0/source/_template-audit.html","s":"05 Work Zone"},{"t":"Briefing 01: Co-Branded PDF Chassis (the print shell)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/01-co-branded-pdf-chassis-briefing.html","s":"05 Work Zone"},{"t":"Briefing 02: Partner Microsite (REWRITE 2026-05-01)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/02-microsite-briefing.html","s":"05 Work Zone"},{"t":"Briefing 03: Welcome Flyer (formerly Welcome Packet / Co-Branded Welcome PDF)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/03-welcome-flyer-briefing.html","s":"05 Work Zone"},{"t":"Briefing 04: Price List","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/04-price-list-briefing.html","s":"05 Work Zone"},{"t":"Briefing 05: What's Needed Guide","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/05-whats-needed-guide-briefing.html","s":"05 Work Zone"},{"t":"Briefing 06: Bench &amp; Rack Guide (REWRITE 2026-05-01: standalone, not a What's Needed wrapper)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/06-bench-and-rack-guide-briefing.html","s":"05 Work Zone"},{"t":"Briefing 07: Promo Flyer","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/07-promo-flyer-briefing.html","s":"05 Work Zone"},{"t":"Briefing 08: Executive Summary (dual pair)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/08-executive-summary-briefing.html","s":"05 Work Zone"},{"t":"Briefing 09: Lab Slip / Docket","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/09-lab-slip-briefing.html","s":"05 Work Zone"},{"t":"Briefing 10: Account Onboarding SOP","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/10-account-onboarding-sop-briefing.html","s":"05 Work Zone"},{"t":"Briefings Update Log","p":"docs/05 Work Zone/_shared/migration/batch-0/source/briefings/_update-log.html","s":"05 Work Zone"},{"t":"Apex Instruments, Component Library","p":"docs/05 Work Zone/_shared/migration/batch-0/source/components/component-library.html","s":"05 Work Zone"},{"t":"Apex Email Request Form v2","p":"docs/05 Work Zone/_shared/migration/batch-0/source/email-forms/apex-email-request-form-v2.html","s":"05 Work Zone"},{"t":"Email Series Campaign Form","p":"docs/05 Work Zone/_shared/migration/batch-0/source/email-forms/email-series-campaign-form.html","s":"05 Work Zone"},{"t":"{{GUIDE_TITLE}}, Apex Instruments","p":"docs/05 Work Zone/_shared/migration/batch-0/source/guides/bench-and-rack-guide-template.html","s":"05 Work Zone"},{"t":"Critical Bar Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/source/guides/snippets/critical-bar.html","s":"05 Work Zone"},{"t":"Info Note Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/source/guides/snippets/info-note.html","s":"05 Work Zone"},{"t":"Photo Grid 3x2 Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/source/guides/snippets/photo-grid-3x2.html","s":"05 Work Zone"},{"t":"Section Card (Text Only) Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/source/guides/snippets/section-card-text-only.html","s":"05 Work Zone"},{"t":"Section Card (With Image) Snippet","p":"docs/05 Work Zone/_shared/migration/batch-0/source/guides/snippets/section-card-with-image.html","s":"05 Work Zone"},{"t":"Resource Card Catalog","p":"docs/05 Work Zone/_shared/migration/batch-0/source/microsite/card-catalog.html","s":"05 Work Zone"},{"t":"Partner Microsite Template","p":"docs/05 Work Zone/_shared/migration/batch-0/source/microsite/microsite-template.html","s":"05 Work Zone"},{"t":"OpenForm Product Page Template","p":"docs/05 Work Zone/_shared/migration/batch-0/source/openform-product-page/openform-product-page-template.html","s":"05 Work Zone"},{"t":"Build 1 Report, Co-Branded PDF Chassis","p":"docs/05 Work Zone/_shared/migration/batch-0/source/print-pdf-shell-build-report.html","s":"05 Work Zone"},{"t":"Apex Co-Branded PDF Chassis (Print Shell)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/print-pdf-shell.html","s":"05 Work Zone"},{"t":"PDF One-Pager Template","p":"docs/05 Work Zone/_shared/migration/batch-0/source/print/reference-one-pager-template.html","s":"05 Work Zone"},{"t":"REFERENCE, Tri-Fold Brochure Template","p":"docs/05 Work Zone/_shared/migration/batch-0/source/print/reference-trifold-brochure-template.html","s":"05 Work Zone"},{"t":"REFERENCE, Two-Pager Template","p":"docs/05 Work Zone/_shared/migration/batch-0/source/print/reference-two-pager-template.html","s":"05 Work Zone"},{"t":"Facebook Post (1200x630)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-facebook-post.html","s":"05 Work Zone"},{"t":"Instagram Post Template, 1080x1350","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-instagram-post.html","s":"05 Work Zone"},{"t":"Instagram Square Post Template, 1080x1080","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-instagram-square.html","s":"05 Work Zone"},{"t":"Instagram/Facebook Story (1080x1920)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-instagram-story.html","s":"05 Work Zone"},{"t":"LinkedIn Post (1200x627)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-linkedin-post.html","s":"05 Work Zone"},{"t":"LinkedIn Story (1080x1920)","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-linkedin-story.html","s":"05 Work Zone"},{"t":"Universal Story Template, 1080x1920","p":"docs/05 Work Zone/_shared/migration/batch-0/source/social/social-universal-story.html","s":"05 Work Zone"},{"t":"Template Build Plan","p":"docs/05 Work Zone/_shared/migration/batch-0/source/template-build-plan.html","s":"05 Work Zone"},{"t":"Welcome Flyer Template","p":"docs/05 Work Zone/_shared/migration/batch-0/source/welcome-flyer/welcome-flyer-template.html","s":"05 Work Zone"},{"t":"The QA Layer · Custom LLM & Brain (Demo)","p":"docs/05 Work Zone/review-queue/_qa-report.html","s":"05 Work Zone"},{"t":"Fact sheet: the Apex Instruments and the field network combination","p":"docs/05 Work Zone/review-queue/announcement/announcement-fact-sheet-DRAFT.html","s":"05 Work Zone"},{"t":"Internal brief: what is happening on September 1","p":"docs/05 Work Zone/review-queue/announcement/internal-announcement-brief-DRAFT.html","s":"05 Work Zone"},{"t":"Your questions, answered: what the {{endorser_line}} news means for your practice","p":"docs/05 Work Zone/review-queue/retention/retention-faq-DRAFT.html","s":"05 Work Zone"},{"t":"Welcome letter: incoming the field network doctors (working draft)","p":"docs/05 Work Zone/review-queue/retention/welcome-letter-DRAFT.html","s":"05 Work Zone"},{"t":"Contact page (copy draft, shell)","p":"docs/05 Work Zone/review-queue/website/contact-page-copy-DRAFT.html","s":"05 Work Zone"},{"t":"Info page (copy draft)","p":"docs/05 Work Zone/review-queue/website/info-page-copy-DRAFT.html","s":"05 Work Zone"},{"t":"Leadership page (copy draft)","p":"docs/05 Work Zone/review-queue/website/leadership-page-copy-DRAFT.html","s":"05 Work Zone"}],"chunks":[{"f":0,"x":"The whole brain stands up in about two weeks for a new company. This is the dated plan this demo followed, the same shape every engagement follows, with the client's names and gates filled in. Week 1, the skeleton and the truth: Day | Ships 1 | Charter + kickoff distillation; the six-zone tree; the registers (questions, decisions, changelog, work log) 2 | The constitution v1: load order, routing table, the ten hard rules, approval roster 3 | Fact ingestion: source docs in, distilled, filed; authority files started (pricing, claims) 4 | The voice trio (brand voice, approved phrases, banned phrases) + audiences and tones 5 | The scanner: banned terms, leak tripwires, slot checks, wired into every handover","h":"The Project Plan"},{"f":0,"x":"6 | Work Zone lifecycle: personal zones, five folders, position-is-status 7 | Brand OS v0.x: tokens, surface law, marks, motion, PROPOSED until locked 8 | Generation skills on gold-standard references; the prompt library 9 | The agent team: checkers, makers, librarians, operators, staged on real gates 10 | The QA fleet's first live run + the acceptance test; team walkthrough The gates that pace everything after: Brand lock → activates the gated generation skills and the collateral migration. The announcement → activates the hub and every public surface. Signing → activates counterpart knowledge ingestion at full depth.","h":"Week 2, the system that does work"},{"f":0,"x":"Beyond the standup: the collateral migration (≈1,200 files, batched one partner at a time, human-approved per batch) and the hub build run as their own tracked programs on the Plan calendar.","h":"Week 2, the system that does work"},{"f":1,"x":"Internal · the project internal only. Nothing you see here may be shared, posted, or shown outside the team until launch. That is rule one and it outranks everything else. What this is: The Custom LLM company brain is the team's shared system: one library that holds what is true, how we sound, and what is approved, plus an AI that works inside it like a colleague. It lives in three connected places that always agree: the SharePoint library (the files), the team site (the readable, browsable version of everything), and the AI (Claude connected to the folder). You save work into it, the brain checks and files it, and the site updates so everyone sees the same truth."},{"f":1,"x":"This one document replaces the stack of guides the Apex brain accumulated. If something is not answered here or in USING-CLAUDE-WITH-THE-BRAIN, ask on the Team Questions page and the answer becomes part of the brain. Access levels: Access is deliberately simple: everyone can read everything, you can only write in your own space, and one admin runs the machinery. Level | Who | Can see | Can edit Admin | Jordan* (operator) | Everything | Everything, site settings, memberships, promotions into the brain Approver | Avery*, Morgan* | Everything | Their own Work Zone, plus approve/return anything in any Send for Approval folder Team member | Sami*, Josie*, Dana*, Nora*, Emmett* | Everything (view only) | ONLY their own Work Zone folder"},{"f":1,"x":"Folder-level permissions enforcing this are configured on the SharePoint site (being finalized in the site build phase). Until every level is wired, the working rule is the same: edit only inside your own Work Zone; everything else is read-only by convention. Getting connected: Open the Custom LLMBrain SharePoint site and click Documents, then Sync in the toolbar. Allow the browser to open OneDrive. A folder appears on your computer (Mac: in Finder's cloud section; Windows: in Explorer under the company name). Right-click it and choose Always Keep on This Device. That folder IS the brain. Anything you save inside it is on SharePoint seconds later; anything a teammate saves appears for you the same way. No uploading, no emailing files."},{"f":1,"x":"You want | Go to Orientation, this guide | 00 Start Here/ The AI's knowledge: facts, rules, approved library | 01 The Brain/ Brand system and design assets | 02 Brand/ Source documents, transcripts, price files, the Apex map | 03 Knowledge and Sources/ Plans, the migration batch plan and tracker | 04 Plans/ YOUR working space | 05 Work Zone/<your name>/ The browsable everything | The team site: Assets tab (every file, color-coded), Agents, Skills, Plan, the Batch Board Your Work Zone","h":"Where things live"},{"f":1,"x":"Five folders, and that is the entire system: 00 My Space (yours, no rules) · 01 Active Projects · 02 Send for Approval · 03 Save for Later · 04 Archived. Drop finished work into Send for Approval; Jordan*, Avery*, or Morgan* reviews it; approved work gets built into the brain and appears on the site, and anything needing changes comes back to your Active Projects with a note. Nothing is ever deleted, it retires to Archived. The rules that keep the brain honest: Internal above all, internal only, until the announcement. Nothing invented, the brain never guesses; unknowns become numbered questions on the Team Questions page. You should work the same way. Approved is sacred, never edit anything in the Approved library directly; changes go through the Work Zone and re-approval.","h":"Where things live"},{"f":1,"x":"Markdown is canonical, every document's .md is the source of truth; the styled page beside it regenerates automatically. Edit the .md, never the .html. Ask, don't assume, the Questions page routes every open item to its owner, and answers take effect the day they arrive. Who to ask: Jordan Vale*, operator, AI owner, access, anything technical. Avery Kellen*, marketing lead, approvals, priorities. Everything else: the Team Questions page on the site.","h":"Where things live"},{"f":2,"x":"Internal · the project. Claude is the AI side of the brain. Connected to the library, it answers from filed facts with citations, drafts in the house voice, checks work before approval, and runs the machinery. This page is how to use it well. Connecting Claude to the brain: The rule that makes everything work: point Claude at the synced brain folder. Once it can see the folder, the brain's own constitution loads automatically and Claude follows the house rules (no inventing, the rules, approved sources only). Claude Code (the deep surface): open a session AT the brain folder, on Mac, open Terminal and run: cd into the Custom LLM Brain folder, then claude. This is where the agents and skills live."},{"f":2,"x":"Claude Desktop / Cowork: attach or open the brain folder in a Cowork session and work conversationally while Claude reads and writes the actual files. Claude Chat (claude.ai): no folder access by default, fine for general thinking, but brain questions belong in a connected surface so answers come from the filed truth, not memory. Never paste brain content into other AI tools. The circle rule follows the content, not the app. The three surfaces, when to use which: Surface | What it is | Use it for Chat | The claude.ai conversation | Quick thinking, wording help, anything that needs no files Cowork | Claude working inside a folder with you | Day-to-day brain work: drafting, reviewing, filing, \"find me X\""},{"f":2,"x":"Code | The terminal operator surface | Agents, skills, batches, site builds, the machinery. Team members mostly will not need it; Jordan* lives here The agents (in a Code session at the brain root): Type the slash command, add your request, press enter. Each specialist runs with fresh eyes and reports back. The full roster with examples is the site's Agents tab. The daily four: /facts, ask anything; sourced answers with file citations, never guesses. /proof, verdict on any draft before it goes to Jordan* or Avery* (facts, voice, the rules, the scanner). /draft, a new piece the brain's way: right template, right tone, saved to your Work Zone. /revoice, rewrites existing copy into the approved voice."},{"f":2,"x":"Skills are packaged abilities: you do not type commands, you just ask for the thing (\"scan this file\", \"build the deck in the Mercado* style\", \"clean up the BioSummit folder\") and the brain routes to the right skill. The full library with what each does is the site's Skills tab. Fourteen generation skills are built and switch on automatically at brand-lock. Models: which brain to rent: Model | Character | Use for Haiku | Fastest, lightest | Quick lookups, simple summaries, high-volume small tasks Sonnet | The balanced daily driver | Everyday drafting and questions when speed matters Opus | Deep, careful, thorough | Our standard for brain work, anything touching facts, approvals, or deliverables. All brain agents are pinned to Opus","h":"The skills"},{"f":2,"x":"Fable | The frontier tier above Opus | The hardest builds and largest campaigns; use deliberately, it costs the most Effort levels: Some surfaces let you set how hard the model thinks: Low answers fast with minimal deliberation (lookups, formatting); Medium is the default balance; High reasons deeply before answering (analysis, plans, anything with edge cases). Rule of thumb: raise the effort when being wrong is expensive, lower it when speed matters more than polish. The habits that make Claude useful here: Give it the file, not a description of the file. Connected Claude reads the real thing. Ask for sources. A brain answer should cite where the fact lives; if it cannot, the answer belongs on the Questions page.","h":"The skills"},{"f":2,"x":"Let it check your work, /proof before anything goes up the chain costs one minute and catches what tired eyes miss. Save into your Work Zone and let the approval flow move it; never ask Claude to write into the Approved library directly (it will refuse anyway). When Claude says UNKNOWN, that is the system working. File the question rather than pushing for a guess.","h":"The skills"},{"f":3,"x":"This file was sanitized out of the public copy. In the production brain, this link opens the real working document. ← Back to the brain","h":"Not included in the demo"},{"f":4,"x":"⚠️ HIGHLY INTERNAL, the project internal only. Nothing in this brain may appear in any external, shareable, or team-visible output until launch (target 2026-09-01, may slip to 2026-10-01). 1. Who this brain serves, read this first, in full. Do not crawl folders. Custom LLM, the new parent identity over the Apex Instruments + the field network combination: publicly, a MERGER OF STRENGTHS (\"a rebrand in the truest sense; one plus one equals three\"). Day-1 naming: both operating brands carry the endorser line (working: \"a Custom LLM company\", Q-20); full transition to standalone Custom LLM in ~24 months. This brain serves Avery Kellen* (marketing lead, working approver, Q-5 open on the final chain) and Jordan Vale* (operator, AI owner), with the project marketing team as creators."},{"f":4,"x":"Custom LLM unites legendary artisan craftsmanship (est. 1945 Southern California roots) with engineered digital infrastructure and FDA-registered mount manufacturing, for devices practices and strategic health networks. What we are NOT: not a takeover, not a rescue (externally, the field network never \"needed help\"), not \"just a lab\", the company that addresses the refit unit end-to-end. 2. Load order: On every session: (1) run Skills/prompt-enhancer silently on the request · (2) this file · (3) Rules/master-instructions.md · (4) Rules/guardrails.md. Pure lookups skip the gate. Never crawl the tree, route via §5."},{"f":4,"x":"Folder | What it is Rules/ | How to act: guardrails, voice, tones, audiences, channels, output directions Facts/ | What's true. Gaps are UNKNOWN, never guessed Skills/ | What you can do. Every generation skill copies its reference/ gold standard Templates/ | Blank chassis and patterns Brand/custom-llm/ | The Brand OS (PROPOSED v0.2): tokens, patterns, asset kit. Design authority ../05 Work Zone/ (TOP LEVEL since 8/11) → Approved/ → Archive/ | Position = status. The team's daily folder sits at the brain's top level (per-person pipelines + the review queue); promotion per §8 brings work into Approved/ here. Copy, never edit Approved in place. Nothing is deleted Log/ | Changelog (mandatory per change), work log","h":"3. The folders"},{"f":4,"x":"Hub/ | The human front door + branded tool suite (NOT YET ACTIVATED, see Hub/README.md) 4. Trust order: Approved/ > Facts/ > ../05 Work Zone/. Anything not sourced there is UNKNOWN, say so and file a question in QUESTIONS-FOR-THE-TEAM.md. Pricing statements come ONLY from Facts/about-company/pricing.md. External claims come ONLY from Facts/about-company/claims-and-credentials.md. the field network facts are research estimates until the review file opens, always attributed as estimates. 5. Routing table: Request type | Open exactly Launch website (info / leadership / contact pages) | Rules/output-types/directions-launch-website.md → that file routes further Announcement / PR piece | Rules/output-types/directions-announcement-kit.md","h":"3. The folders"},{"f":4,"x":"THE RULES ABOVE ALL, nothing Custom LLM-related is shareable, publishable, or visible outside the project circle (5-person marketing team + Dana* + named leadership) until launch. No Custom LLM content in any Apex-team-visible surface, brain, or channel. Never invent facts, metrics, prices, testimonials, or names. UNKNOWN over guess. The message wall, internal and external stories are strictly separated: internally \"help is here,\" overwhelming reassurance; externally the one-story rebrand story ONLY (never rescue framing, never us-vs-them, never workforce mechanics in technician copy). \"Merger\" is approved language. Endorser line per Q-20; \"APEXINST\" and the legal entity name never appear customer-facing; the CEO is always \"Roman Elias Mercado*\" in full in client copy.","h":"6. Hard rules"},{"f":4,"x":"Working approver: Avery Kellen* (final chain pending Q-5; exec gate: Dana*) · Operator/AI owner: Jordan Vale* · Co-owner: Sami* · Creators: Morgan* (comms), Josie* (design). Restricted-docs circle: Ronan*, Emmett*, Corbin*, Dana*, Avery*. Built on Jordan*'s brain-template v1.0, assembled 2026-08-05 from the Custom LLM Intake Packet. Companion AGENTS.md is generated by Skills/quality-control/sync-agents-md.mjs, never hand-edit it.","h":"8. Governance"},{"f":5,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":6,"x":"Nothing enters without {{owner_name}}'s approval. Never edited in place: copy out → revise → re-promote; the old version goes to a dated Archive folder. Every promotion gets a changelog entry. Pricing lives only in price-sheets/. Heavy files get a _card.md companion, AIs read the card, not the 200 KB file."},{"f":7,"x":"INDEX · Agent Outputs · rendered on the Evergreen system · every name, number, and contact is demo data ONE EXAMPLE PER SPECIALIST · EVERY PIECE GATE-CHECKED Piece | What it shows /draft · Drafted Welcome Letter | A real output shape the agent produces /revoice · Revoice: Before / After | A real output shape the agent produces /facts · Sourced Answer | A real output shape the agent produces /scribe · Meeting Distillation | A real output shape the agent produces /proof · Proof Verdict | A real output shape the agent produces /brandcheck · Brand Check | A real output shape the agent produces /status · Weekly Status Digest | A real output shape the agent produces /file · Filing Receipt | A real output shape the agent produces"},{"f":8,"x":"/brandcheck · Brand Check · rendered on the Evergreen system · every name, number, and contact is demo data TARGET: PARTNER ONE-PAGER DRAFT · /BRANDCHECK 3 findings: # | Finding | Fix 1 | Raw hex #2F6B4F in the footer band | Use token Harbor, never inline values 2 | Two accent moments on one surface | Orange points one place; demote the second to Harbor 3 | Wordmark set in the body font | Wordmark is Archivo 900 with the accent period, always"},{"f":9,"x":"/draft · Drafted Welcome Letter · rendered on the Evergreen system · every name, number, and contact is demo data PRODUCED BY /DRAFT · SAVED TO WORK ZONE → APPROVED VIA THE CHAIN Dear {{recipient_name}}, Welcome to Apex Instruments*. By the time this letter reaches you, three things are already true: your account team is named, your terms are locked in writing, and your first-case review is on the calendar. The ask I make of every new account is one phone call, fifteen minutes with Nora Ballinger*, so the first case ships the way you want it, not the way we guessed. Dana Whitfield* CHIEF EXECUTIVE"},{"f":10,"x":"/facts · Sourced Answer · rendered on the Evergreen system · every name, number, and contact is demo data Q: \"WHAT TURNAROUND CAN WE PROMISE A NEW ACCOUNT IN WRITING?\" The answer, with its sources: Standard tier: 2 to 3 business days. Priority tier: next business day, capacity-gated. Both figures are quotable in writing; anything faster requires Morgan's* sign-off per the escalation table. (Demo figures.) Claim | Source file Turnaround tiers | Facts/pricing.md · §service-tiers Sign-off rule | Facts/people-and-org/team.md · escalation tier 2 NO SOURCE → NO NUMBER. UNKNOWNS FILE TO THE Q REGISTER."},{"f":11,"x":"/file · Filing Receipt · rendered on the Evergreen system · every name, number, and contact is demo data INPUT: AVERY'S* ANSWER TO Q-02 · PROCESSED BY /FILE Filed, four places, one pass: What | Where it landed The answer, verbatim + source | Facts/decisions/decisions-log.md Q-02 → answered | the Q register · 12 open → 11 Endorser slot value | Templates/launch-copy/* · 5 slots resolved The changelog line | Log/changelog.md · dated, attributed"},{"f":12,"x":"/proof · Proof Verdict · rendered on the Evergreen system · every name, number, and contact is demo data DRAFT: CUSTOMER LETTER v3 · VERDICT BY /PROOF · FRESH CONTEXT PASS, with two flags: Lens | Verdict | Finding Facts | PASS | Both figures trace to pricing.md Voice | FLAG | L14 \"cutting-edge\", banned list, swap to plain claim Rules | FLAG | Endorser slot must render visibly until Q-02 closes Scanner | PASS | Exit 0 · no banned terms, no raw hex VERDICTS INFORM THE OWNER→APPROVER GATE. THEY NEVER REPLACE IT."},{"f":13,"x":"/revoice · Revoice: Before / After · rendered on the Evergreen system · every name, number, and contact is demo data BEFORE · OFF-VOICE \"We are excited to announce that we have leveraged our synergies to deliver a best-in-class, industry-leading solution that revolutionizes the customer experience!!\" AFTER · HOUSE VOICE \"Your team stays. Your terms hold. The network behind them just got bigger, here is what that means for your Monday.\" RULES APPLIED: NO SUPERLATIVES (05) · NO EXCLAIMS · CONTINUITY-FIRST FRAME · 14 WORDS/SENTENCE AVG"},{"f":14,"x":"/scribe · Meeting Distillation · rendered on the Evergreen system · every name, number, and contact is demo data KICKOFF CALL · DISTILLED BY /SCRIBE · RAW TRANSCRIPT → SOURCE ARCHIVE What was decided: Launch window confirmed for {{quarter}} | → DECISIONS LOG Evergreen leads the brand direction | → DECISIONS LOG What was assigned: Josie*: production logo vectors | → Q-05 Morgan*: pricing tiers to authority file | → ROADMAP What stayed open: The endorser line wording | → FILED AS Q-02"},{"f":15,"x":"/status · Weekly Status Digest · rendered on the Evergreen system · every name, number, and contact is demo data WEEK 2, DAY 5 · COMPILED BY /STATUS FROM THE REGISTERS The week, in one card: Shipped: QA fleet live run · 6 drafts verified · brand tokens locked Blocked: 2 items on Q-02 (endorser) · 1 on Q-05 (logo vectors) Next: Team session 2 · first approvals through the chain SOURCES: CHANGELOG · Q REGISTER · THE BIG BOARD, NEVER MEMORY"},{"f":16,"x":"INDEX · The Collateral Shelf · rendered on the Evergreen system · every name, number, and contact is demo data ALL 20 BRAND OS TREATMENTS · SWAPPED TO EVERGREEN · DEMO CONTENT Piece | What it shows T01 · Letterhead | Rendered on Evergreen, filled with demo content T02 · One-pager | Rendered on Evergreen, filled with demo content T03 · Proposal | Rendered on Evergreen, filled with demo content T04 · Leave-behind | Rendered on Evergreen, filled with demo content T05 · Card + Signature + QR | Rendered on Evergreen, filled with demo content T06 · OG / Share Image | Rendered on Evergreen, filled with demo content T07 · Email Chrome | Rendered on Evergreen, filled with demo content T08 · Deck Theme | Rendered on Evergreen, filled with demo content"},{"f":16,"x":"T09 · Social Frames | Rendered on Evergreen, filled with demo content T10 · Document Chrome | Rendered on Evergreen, filled with demo content T11 · Price Sheet | Rendered on Evergreen, filled with demo content T12 · Welcome Flyer | Rendered on Evergreen, filled with demo content T13 · Checklist Guide | Rendered on Evergreen, filled with demo content T14 · Intake Form (print) | Rendered on Evergreen, filled with demo content T15 · Microsite Canon | Rendered on Evergreen, filled with demo content T16 · Landing Page | Rendered on Evergreen, filled with demo content T17 · Executive Summary Pair | Rendered on Evergreen, filled with demo content T18 · Blog Treatment | Rendered on Evergreen, filled with demo content T19 · Trifold + Catalog | Rendered on Evergreen, filled with demo content T20 · Mailer + Certificate | Rendered on Evergreen, filled with demo content"},{"f":17,"x":"T01 · Letterhead · rendered on the Evergreen system · every name, number, and contact is demo data {{date}} Dear {{recipient_name}}, Thank you for the conversation this week. As promised, here is the summary of what changes for your account, and, more importantly, what does not: your team, your pricing terms, and your turnaround commitments all carry forward exactly as they are today. You will see the new brand appear on our paperwork over the coming weeks. Nothing about who you call on Monday changes. Warmly, Nora Ballinger* SALES LEAD"},{"f":18,"x":"T02 · One-pager · rendered on the Evergreen system · every name, number, and contact is demo data ONE-PAGER Precision manufacturing, kept personal. One partner for the parts, the service network, and the people who answer the phone. Made here: Every unit built in our Portland facility, 40+ service sites keep support close to you. Named account teams: You get people, not a queue. Same names, direct lines, real ownership. Guaranteed continuity: Terms locked in writing: pricing, turnaround, and the Continuity Guarantee. Talk to your account team HELLO@APEXINSTRUMENTS.EXAMPLE"},{"f":19,"x":"T03 · Proposal · rendered on the Evergreen system · every name, number, and contact is demo data PROPOSAL · PREPARED FOR {{client_name}} Service Partnership Proposal: Scope: Item | What's included | Owner Dedicated account team | Named lead + backup, direct lines, quarterly reviews | Nora H.* Priority production | Reserved capacity band, guaranteed turnaround tier | Morgan R.* Onboarding | Site visit, workflow mapping, first-90-days plan | Emmett F.* Investment: Monthly partnership: $ {{quote, pricing.md only}} Every number in a live proposal traces to the pricing authority file."},{"f":20,"x":"T04 · Leave-behind · rendered on the Evergreen system · every name, number, and contact is demo data Three things to remember about us: 01 · The people stay: Your team, your rep, your direct line, unchanged. 02 · The terms hold: Written rate lock and the Continuity Guarantee. 03 · The network grew: 40+ service sites now behind every account. QR → {{qr_url}}"},{"f":21,"x":"T05 · Card + Signature + QR · rendered on the Evergreen system · every name, number, and contact is demo data BUSINESS CARD · FRONT Nora Ballinger*: SALES LEAD CARD · BACK EMAIL SIGNATURE Nora Ballinger* · Sales Lead Apex Instruments* · {{endorser_line}} (503) 555-0142 · apexinstruments.example"},{"f":22,"x":"T06 · OG / Share Image · rendered on the Evergreen system · every name, number, and contact is demo data SOCIAL SHARE CARD · 1200 × 630 Precision, kept personal. The story of {{post_title}}, rendered in the brand every single time."},{"f":23,"x":"T07 · Email Chrome · rendered on the Evergreen system · every name, number, and contact is demo data Preheader: Nothing about who you call on Monday changes. Your account, after the launch: Same team. Same terms. One new name on the paperwork, coming {{launch_date}}. Here is exactly what to expect, in two minutes. Read the two-minute version"},{"f":24,"x":"T08 · Deck Theme · rendered on the Evergreen system · every name, number, and contact is demo data TITLE SLIDE The Partnership Review: Q3 · prepared for {{client}} CONTENT SLIDE Three numbers that matter: 98.4%: on-time (demo) 2.1 days: avg turnaround (demo) escalations open"},{"f":25,"x":"T09 · Social Frames · rendered on the Evergreen system · every name, number, and contact is demo data ANNOUNCEMENT Something new is coming. QUOTE \"Nothing about who you call on Monday changes.\": STAT 40+: service sites behind every account (demo figure)"},{"f":26,"x":"T10 · Document Chrome · rendered on the Evergreen system · every name, number, and contact is demo data 4. Receiving & Intake: IN THIS SECTION 4.1 | Dock procedure 4.2 | Case logging, the golden rule 4.3 | Exceptions & escalation Body text runs 13.5px Plex Sans at 1.6; headers Archivo 800; callouts use the mist wash. Running header and footer carry section + page automatically."},{"f":27,"x":"T11 · Price Sheet · rendered on the Evergreen system · every name, number, and contact is demo data Line | Description | Tier A | Tier B PR-100 | Standard unit, single | $129 | $119 PR-140 | Standard unit, pair | $212 | $196 PR-220 | Premium unit | $348 | $322 SV-010 | Priority service add-on | $45 | included All figures are demo data. In production, every number on this sheet renders from the pricing authority file, nowhere else."},{"f":28,"x":"T12 · Welcome Flyer · rendered on the Evergreen system · every name, number, and contact is demo data WELCOME You're in good hands. Welcome to Apex Instruments*. Here is your team, your first two weeks, and the three ways to reach us, on one page, like everything we send. Your account lead: Nora Ballinger* · direct line on your card Week 1: Kickoff call + workflow mapping Week 2: First cases through, review scheduled"},{"f":29,"x":"T13 · Checklist Guide · rendered on the Evergreen system · every name, number, and contact is demo data Before you send your first case: ☐ | Account portal login received and tested ☐ | Preferred turnaround tier confirmed in writing ☐ | Shipping labels + pickup window scheduled ☐ | Direct line saved: (503) 555-0142 ☐ | First-case review call on the calendar"},{"f":30,"x":"T14 · Intake Form (print) · rendered on the Evergreen system · every name, number, and contact is demo data Practice Business name | write here Primary contact + role | write here Preferences Turnaround tier | ☐ Standard ☐ Priority Preferred contact channel | ☐ Phone ☐ Email ☐ Portal The digital twin of this form is stage 01 of the brain build, every field maps to a file."},{"f":31,"x":"T15 · Microsite Canon · rendered on the Evergreen system · every name, number, and contact is demo data The service network,one page at a time. Microsite pattern: nav band · hero · three cards · contact strip. Every section inherits tokens. Card: Feature block"},{"f":32,"x":"T16 · Landing Page · rendered on the Evergreen system · every name, number, and contact is demo data CAMPAIGN LANDING Switch without the switching costs. One offer, one form, one promise, above the fold. Book the 15-minute call Proof: Three logos / three quotes (permissioned only) The offer: First case free · terms in writing The form: Name · practice · phone, nothing more"},{"f":33,"x":"T17 · Executive Summary Pair · rendered on the Evergreen system · every name, number, and contact is demo data EXEC SUMMARY · PAGE 1 The quarter, in one page: Narrative page: what happened, what it means, the one decision needed. Written in executive-brief tone, short sentences, no adjectives doing load-bearing work. Metric | Q | Δ On-time | 98.4% | +0.6 Turnaround | 2.1d | -0.2 Escalations | 0 Demo figures · sourced rows only in production"},{"f":34,"x":"T18 · Blog Treatment · rendered on the Evergreen system · every name, number, and contact is demo data FROM THE SHOP FLOOR · {{date}} Why we answer the phone on the first ring: Article typography: 15px/1.7 body, Archivo heads, pull-quotes on the mist wash, one image slot per 400 words. The OG card (T06) generates from this page's title automatically."},{"f":35,"x":"T19 · Trifold + Catalog · rendered on the Evergreen system · every name, number, and contact is demo data PANEL 1 · COVER The catalog,kept honest. PANEL 2 · LINES Product families with one photo slot + three spec lines each. No prose walls. PANEL 3 · CONTACT The three ways to reach us + the QR to the live price sheet."},{"f":36,"x":"T20 · Mailer + Certificate · rendered on the Evergreen system · every name, number, and contact is demo data POSTCARD · FRONT We kept every promise we mailed you. CERTIFICATE Certificate of Completion: awarded to {{name}} · brain onboarding, session 3 of 3"},{"f":37,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":38,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":39,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":40,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":41,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":42,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":43,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":44,"x":"Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chunk → Jordan* review → promote here with _card.md fronting + changelog. Nothing enters unreviewed."},{"f":45,"x":"Fills at brand-lock: Josie*'s production kit (colors-and-fonts) + migrated media, all in approved Custom LLM brand only."},{"f":46,"x":"Fills at brand-lock: Josie*'s production kit (email-signatures) + migrated media, all in approved Custom LLM brand only."},{"f":47,"x":"Fills at brand-lock: Josie*'s production kit (letterhead) + migrated media, all in approved Custom LLM brand only."},{"f":48,"x":"Fills at brand-lock: Josie*'s production kit (logos) + migrated media, all in approved Custom LLM brand only."},{"f":49,"x":"Fills at brand-lock: Josie*'s production kit (media-library) + migrated media, all in approved Custom LLM brand only."},{"f":50,"x":"Fills at brand-lock: Josie*'s production kit (photography) + migrated media, all in approved Custom LLM brand only."},{"f":51,"x":"Verdict: PASS. Clear to share. Every R1 revision item landed. (Local copy is API-clipped at 256 KiB, so the tail, later treatments, Swap Protocol, Exclusions, Index, flags list, is unverified here; export the project archive for full verification.) Historical record, do not read as current. This is the dated audit of v0.2. Every token value named below is the value v0.2 carried on 2026-08-05, quoted so the audit can be checked against what it actually measured. They are retired: see brand-sheet.md → \"Retired in v3.0, do not reference\" for what replaces them. R1 item | Result Two-tier mark system | ✅ Tier H ×27 / Tier W ×14, usage matrix present"},{"f":51,"x":"Hero renders actually used (the core complaint) | ✅ 20 render references (cut-mark-glass-alpha ×6, chrome lockup ×3, app tile ×3, glass/chrome/stacked/gold-notch) · zero inline flat-SVG bolts in the verified portion 64px floor rule | ✅ stated 14× Gilt token | ✅ --os-glint:#B26B45, 51 mentions, Neon/Glint boundary documented (\"Neon = interactive + emphasis · Glint = material + light detail\") Gold-notch un-flagged | ✅ now a sanctioned Tier W dark variant Palette levels | ✅ primary / secondary / tertiary The Charge v2 | ✅ hero 5.2s + micro 0.6s, both cubic-bezier(.33,0,.15,1) The Current (ambient staple) | ✅ os-current 3.6s, staggered 150ms per segment (Pulse-Row-style traverse) Button interaction rules | ✅ timing budget present (90 / 140 / 150 / 160 / 170 / 180 / 200 ms)"},{"f":51,"x":"Glass system | ✅ thin/thick + blur documented App icon tiles | ✅ present Light/dark toggle | ✅ [data-theme=\"dark\"] block overriding 8 shell tokens Token discipline | ✅ 0 CSS hex leaks, all 216 raw hex are documentation labels in swatch/contrast tables Brand contamination | ✅ none, zero color contamination from Jordan*'s reference palettes Process note: the DesignSync get_file API clips at 256 KiB. For any Brand OS over that size, use the project archive export for canonical local copies. Add to the Assembly Playbook."},{"f":52,"x":"DJVF Brand OS v3.0 \"Atlas\" · the token authority. Status: LOCKED (2026-08-13). Six colours, four faces, one owned motion, one mark. Supersedes Evergreen v0.6 and the four exploration directions beside it; the --os-* token names are unchanged so every skill and template that already reads them keeps working. The one-page cut the AI actually loads: tokens, laws, type, marks, and the never list. The full system with reasons lives in the standalone Brand OS document in 02 Brand/Brand OS/. This half and that half are kept in step by hand, see Drift control. Every ratio on this page was measured on 2026-08-13, not estimated, and the failures are written down as laws rather than nudged away. Never hardcode a hex that has a token.","h":"The Brand Sheet"},{"f":52,"x":"Token | Value | Name · why | Measured --os-ink / --os-ground | #00272C | Midnight Green, the one dark. Heroes, headers, footers, dark bands, and every line of body type on a light page | white on it 15.8:1 ✓ · on white 15.8:1 ✓ --os-accent | #FF6B1C | True North, the needle. The only warm value and the only one allowed to move: primary buttons, the eyebrow on dark, the live rule. Once per view, twice at most | on Midnight 5.6:1 ✓ · on white 2.8:1 × --os-paper / --os-card | #FFFFFF | Paper White, true white, never off-white. Cards, sheets, knockout marks, all type on dark grounds | on Midnight 15.8:1 ✓ --os-signal | #09E85E | Landfall, land sighted. SIGNAL ONLY: shipped, passing, the live dot, data fills | on Midnight 9.6:1 ✓ · on white 1.7:1 ×","h":"Tokens, the six, each with its reason"},{"f":52,"x":"Token | Value | Formula · measured --os-page | #F4F7F7 | 5% Steel on white. The page beneath the cards, so white sheets have something to sit on --os-band | #EDF3F3 | 8% Steel on white. Chips, code, washes --os-muted | #476467 | 72% Midnight on white · 6.4:1 ✓. Secondary text --os-faint | #597276 | 65% Midnight on white · 5.1:1 ✓. Muted labels, metadata --os-dim-d | #A8B6B7 | 66% white on Midnight · 7.6:1 ✓. Dimmed type on dark --os-hairline | 13% Midnight · 16% white on dark | Depth comes from hairlines, not shadows Shadows | 0 1px 3px at 5% · 0 12px 30px -14px at 22% | Resting sheets · genuinely floating sheets. Nothing else Radii | 8 · 14 · 22 · pill | Chips · cards · panels · buttons. Tiles are 22% of tile width, so an app icon and a favicon curve alike","h":"Derived, formulas, not new colours"},{"f":52,"x":"Family | Weights / axes | Duty | Class Saira | BLACK 900 · wdth 125 | The wordmark, and nothing else. Never a headline, never a heading, never live text in production. Outline it and it becomes artwork | Wordmark only Archivo | 500 to 900 | Headlines, section heads, card titles, buttons. 800 to 900 for display, 700 for anything under 24 px | Display IBM Plex Sans | 400 · 500 · 600 · 700 | Body and UI. Everything a person reads for longer than a glance | Body / UI IBM Plex Mono | 400 · 500 · 600 · TABULAR | Eyebrows, figures, IDs, file names, code. Tabular figures always, so columns of numbers line up | Mono","h":"Type, four faces, one family tree"},{"f":52,"x":"The material is a slow liquid-chrome field in Midnight Green with a low, out-of-phase thread of True North running through it, tone-mapped so the brightest band lands on a muted steel instead of blowing to white. Published parameters: speed 0.12 · amplitude 0.32 · base #00272C · orange thread 0.04. It renders in exactly three places and there is no fourth: the site hero, the Brand OS document cover, the app icon. Two owned motions is zero owned motions.","h":"Motion, one owned motion"},{"f":52,"x":"Rotate the mark. The needle points north because north is the point. Recolour the needle. It is True North in every treatment that has colour at all. Set the wordmark in Archivo, or in Saira at any width but 125. It is artwork, not live text. Put the icon to the right of the wordmark, or the tagline beside it. Scale the primary icon below 48 px instead of switching drawings. Add a stroke, glow, drop shadow, or container the mark did not ship with. Run the owned material behind a lockup outside the three cleared uses. A seventh colour, including a lighter midnight for large fills. True North, Landfall or Meridian as type on a white ground. Gradients between brand colours. Shadow used where a hairline would do, or a third grade of glass. Signal colours used decoratively.","h":"Never"},{"f":53,"x":"The lead direction. Four complete directions were built as working systems, same structure, different souls, and Evergreen won the review. The earlier drafts are kept for the record: First Draft, Deep Draft, and Gilt Draft. The palette strip: Token | Value | Role Midnight Green | #00272C | Primary · ground · ink True North | #FF6B1C | Secondary · the needle Paper White | #FFFFFF | Base · card · knockout Landfall | #09E85E | Arrived · shipped · passing Meridian | #279AF1 | In progress · information Surface Steel | #245D63 | Material fallback · link · label","h":"Direction 4, Evergreen"},{"f":53,"x":"Six values, no seventh. The names and hexes this direction was first drawn in, Sea Glass, Copper, and the earlier Midnight Green and Paper White, are recorded in brand-sheet.md under \"Retired in v3.0, do not reference.\" None of them is a current value. Why it won: Own-able ground: the deep calder reads distinct in a category full of blue. One accent with real authority, orange survives on both dark and light. Quiet metallics give the premium read without gold's costume-jewelry risk. The full working system lives in the standalone Brand OS document. This page is the record of the choice.","h":"Direction 4, Evergreen"},{"f":54,"x":"Direction-4-EVERGREEN (v0.6) is the working lead: Avery*'s preference from the 2026-08-06 review (\"most well received\"), revised to her feedback same-day, Electric Orange in for red, Copper in for gold, the 12 Custom LLM color names, dual Presentation/Full-Spec views. Awaiting formal leadership confirmation + the accent-alternate pick (Q-18). Explored alternates (kept for the record; their historical names and palette values stay as named, each carries its own rejected palette, and not one of those hexes is a current value): Direction-1-FIRST-DRAFT, electric ultramarine + neon on midnight Direction-2-DEEP-DRAFT, abyssal navy, glacial ice, kelp gold Direction-3-GILT-DRAFT, liquid gold + brushed metal"},{"f":54,"x":"All marks interim, pending Josie*. Material-concept explorations (titanium / alloy / porcelain-metal) remain queued if leadership wants more range."},{"f":55,"x":"The Brand OS is not a PDF of guidelines, it's the machine-readable half of the design system. The brain consumes it the way code consumes a config file. Tokens, never hex: Every color has a name, a value, and a printed reason. Deliverables reference the name (Midnight Green, True North); the build resolves the value. When leadership adjusts a color, every future deliverable inherits the change, and rule 06 makes a raw hex code in output a build failure. The surface law: Contrast is measured, not eyeballed: which colors may carry text on which surfaces is a table with ratios, and the scanner knows it. The accent appears once or twice per surface, it can only point one place.","h":"How the Brain Uses the Brand OS"},{"f":55,"x":"Skills copy a gold-standard reference and adapt content, never redesign from scratch. The swap kit carries old-brand → new-brand mappings (colors, fonts, names, URLs) so migrations are mechanical where they can be and judged where they must be. Anything PROPOSED renders with its banner. The system can't quietly pass an unapproved brand as final.","h":"How collateral inherits the system"},{"f":56,"x":"Status: PROPOSED interim marks (Josie*'s workstream owns the final logo). All PNG; only custom-llm-mark-glass-alpha.png has transparency. Marks (the bolt \"S\"): custom-llm-mark-glass-midnight-a/b.png, photoreal glass hero renders on midnight (1254²) custom-llm-mark-glass-alpha.png, glass render, RGBA/transparent, best for compositing custom-llm-mark-flat-ink-on-light.png · custom-llm-mark-flat-white-on-midnight.png, FLAT solid bolts, both surfaces, the SVG-derivation sources custom-llm-mark-flat-gold-notch-on-midnight.png, flat white bolt with a gold accent notch custom-llm-mark-chrome-on-light.png, chrome/metal treatment on light custom-llm-app-icon-tile-midnight.png, rounded-square app tile with glass bolt Wordmarks (all-caps CUSTOM LLM, angular custom cut)"},{"f":56,"x":"custom-llm-wordmark-ink-on-light.png · custom-llm-wordmark-white-on-midnight.png (1774×887) Lockups (bolt + wordmark): Horizontal on light: -glass-on-light · -gold-on-light Horizontal on midnight: -white-on-midnight · -chrome-on-midnight Stacked on light: custom-llm-lockup-stacked-chrome-on-light.png Note: the wordmark is ALL-CAPS, feeds open question Q-2 (canonical casing in prose)."},{"f":57,"x":"This file is the first thing the AI reads, every session, before any request. It defines who the brain serves, what order truth loads in, where every kind of question routes, and the ten rules that cannot be broken. A generated mirror (AGENTS.md) serves any other AI the team points at this library. Load order: This constitution, top to bottom. The routing table row that matches the request, and only that row's files. The authority files for any number or claim the output will carry. The Brand OS tokens if the output renders anything visual.","h":"The Constitution"},{"f":57,"x":"Approved › Facts › Work Zone › everything else = UNKNOWN. An unknown never becomes a guess: it becomes a numbered question on the Q register, and the output ships with the slot marked. The routing table: The ask | Open A fact about the company or the timeline | Facts/about-company/ Any price, discount, or commercial term | Facts/pricing.md, the only legal source Any capability or performance claim | Facts/claims.md, the only legal source Who does what, who approves, who escalates | Facts/people-and-org/team.md Launch-day sequence and owners | Facts/launch/day-1-playbook.md Drafting anything customer-facing | Templates/launch-copy/ + the voice trio Anything visual | Brand/brand-sheet.md, tokens, never raw hex A job too wide for one session | Skills/graph-engineering/, the fleet specs","h":"Trust order"},{"f":57,"x":"Facts traced to their authority file, or slot-marked. Voice matches the audience row (doctor / staff / partner / press). Scanner clean, banned terms, policy tripwires, raw hex, dash policy. Saved to the requester's Work Zone with today's date. Changelog line written. The approval roster: Owner: Jordan* (brain operator). Approvers: Avery Kellen* (marketing lead) and Morgan* (operations). Only a human promotes work into Approved, the AI proposes, people decide.","h":"Output checklist (every deliverable)"},{"f":58,"x":"\"A devices contract manufacturer delivering artistry at scale\" (positioning language) \"Every Bench & Rack and Full Rack case is QC'd under a microscope by a master team\" (rumor-response approved) Built-in redundancy across Centers of Excellence, \"an equipment or supply failure never costs a case\" Real-time case tracking from day one; dedicated Account Manager as single point of contact Enterprise dashboards for GSOs: multi-location case tracking, real-time shipping logistics, standardized remake-rate metrics (source docs call the platform \"Truepath,\" but that name was rejected on trademark, naming open as Q-23; never use \"Truepath\" externally) A national footprint combining the field network's 40+ sites with Apex's Centers of Excellence","h":"We may claim (per GTM; verify flagged items before external use)"},{"f":58,"x":"the field network: \"one of the largest and most recognized devices laboratory networks in the United States\" (press-release language) We may NOT claim: Any specific combined financials, valuations, or deal terms · superlatives beyond the approved press language · anything from the restricted comp plan · workforce mechanics in technician-facing copy · \"help is here\" externally (internal-only framing)","h":"We may claim (per GTM; verify flagged items before external use)"},{"f":59,"x":"Fact | Value | Source The company | Apex Instruments*, precision manufacturer, est. 1987, ~240 people, with a 40+ site service and distribution network | Company brief What's happening | A full rebrand: the patchwork of sub-brands retires into one new masterbrand, name locked at brand-lock Q-05 | Brand sprint charter Revenue | ~$180M INTERNAL ONLY | Finance, never customer-facing Headquarters | Portland, OR | Ops plan Trademark | The new mark, filed by Halcyon Holdings II LLC*; ™ until registration Q-10 OPEN | Counsel letter Launch | Launch day locked; date carried in the launch plan | Leadership","h":"The company at a glance"},{"f":59,"x":"Public frame: one company, one story. Customers keep the people, products, and terms they chose, the new brand makes the whole easier to see. Continuity first, scale second. Vision {{vision_statement, Dana* signs, Q-17}} Mission {{mission_statement, Dana* signs, Q-17}} The message layers: Two layers, never mixed: the customer layer (continuity, named account teams, service guarantees) and the corporate layer (one platform, combined strength). Internal rallying language stays internal, the scanner enforces the wall.","h":"The story we tell"},{"f":59,"x":"No revenue figures in public copy (rule 04). No \"largest / fastest / first\" without substantiation in claims.md (rule 05). No customer names in any example until written permission is filed.","h":"What we never say"},{"f":60,"x":"Publishing policy: never published externally as lists. The ONLY quotable commitments are the written Day-1 promises below, quoted exactly, in approved contexts only. The written commitments (GTM v4.1, these appear in drafted letters, emails, and rumor responses): \"Pricing for existing accounts is locked for six months.\" (incoming the field network accounts; any future change communicated by the Account Manager, never by surprise) The 6-month Continuity Guarantee: \"if a case is late because of us, we make it right.\" $500 digital-integration credit for connecting a scanner to the digital pipeline. 12 months of complimentary high-end continuing education through the combined practice-education program. Standardized FedEx 2nd Day shipping, free to the practice."},{"f":60,"x":"The 2026-08-04 leadership meeting said \"match all current the field network pricing for at least the first 18 months.\" The formal GTM (July 21) commits 6 months everywhere in writing. Until leadership reconciles, quote ONLY the 6-month written terms externally and flag the discrepancy internally wherever the 18-month figure appears. Legacy Apex customer pricing: \"your pricing holds/continues unchanged\" (no term stated, do not invent one). Apex-side price sheets live in the Apex brain, never here.","h":"⚠️ Known conflict (Q-21, do not resolve silently)"},{"f":61,"x":"INTERNAL · the project internal only. Meeting: Weekly Marketing Updates, 2026-08-11 (Microsoft Teams). Provenance: original Microsoft Teams VTT caption file, compacted to speaker turns on 2026-08-11. Nothing added, reworded, or removed; only caption timing/segment lines were collapsed into turns. The original .vtt is preserved in 03 Knowledge and Sources/Call Transcripts/ (placed there by the operator, per the single-ingestion rule). Distilled note: Facts/meetings/2026/08/2026-08-11-weekly-marketing-updates.md Speakers: Avery Kellen* · Jordan Vale* · Sami* · \"Design\" (Teams display name; maps to Josie \"Josie\", design, per Facts/people-and-org/team.md and in-call context) · \"Communications\" (Teams display name; maps to Morgan*, comms, per team.md and in-call context)."},{"f":61,"x":"Lines tagged [untagged]: carried no speaker tag in the VTT. Attribute them by context only, and never treat an untagged line as a sourced quote without saying so. Caption cautions (read before citing anything below): The captioner writes \"Apex\" where the speaker said *Custom LLM*, and \"Apex Instruments\" for the current operating brand. Read by context. \"Winnie\" (lines re: price lists, and Avery*'s \"sorry, Winnie*, what?\" near the end) reads as the captioner's rendering of \"Josie\", unconfirmed. \"Rhea\" is the pricing owner's name as captioned. Spelling and identity UNCONFIRMED (a contact recorded elsewhere as \"Iris\" may be the same person). Do not cite the name until confirmed. \"Sandoval\" / \"Sandoza\" / \"Sendoza\" = Sendoso."},{"f":61,"x":"\"ABS\" and \"AVS\" both appear for the lab system; the brain uses ABS. Spelling unconfirmed here. \"Ventora\" / \"Ventura\", \"DeltaCraft\", \"keystone aurora\", \"Caravelle\" / \"Carillo\", \"Sylvia\", \"Silverton\" are captured as captioned and are unconfirmed spellings. Masked profanity (*) is the captioner's, not a redaction. [untagged]: go in colors and fonts, Josie, you'll be able to, you know, give that to Jordan*, he'll feed it into the brain and it'll Avery Kellen*: populate with everything we need. Um... [untagged]: So if you want to just do a quick show of what you created, I did share the questions link yesterday with Dana*, Jordan*, so we could start to get some questions answered. Yes, I saw we got one answer in here, so that's good to know. Avery Kellen*: Yeah, that one was from me. Yeah."},{"f":61,"x":"Jordan Vale*: You, sorry, yeah, that's almost you, yeah. [untagged]: Yeah, so, but if you can give like a quick overview that way the team sees like what's in the works. Yeah, I definitely can. So in a lot of ways, it's a lot like the brain that we had previously created. Just I would say a little bit better this time, just because there's been more advancements and ways of like thinking through it. Main page on the brain is just how it works, how it's used, you know, kind of the stuff you guys already know."},{"f":61,"x":"Sami*, you might want to take a look at this, just some of the different implementations that I've tried to set up with this one, just from things that I've been following along with over the last couple months that I wouldn't say ours was missing before, but would have been beneficial, like an operating loop and like training it how to use it and to push things into the work zone. Just really kind of honing in on that approval process a little bit more and Jordan Vale*: the escalation to approval."},{"f":61,"x":"[untagged]: approvals, component maps, and I can send this link out to everybody so that people can look through it. This is just basically everything that is built in here is what is started from either a transcript source of a meeting or a document that Avery* has provided. Nothing else outside of it was made-up, nothing else was generated, so anything that it has. was listed in a transcript or it was listed in one of the, I think you sent what, 4 documents over, I think, Avery*. So everything's laid out there, bunch of different pages, Avery Kellen*: Yeah. [untagged]: so I won't go through them all. Graph engineering, this is just trying to kind of help us keep everything a little bit better. Jordan Vale*: The goal of this one, Sami*, was to..."},{"f":62,"x":"t; Living knowledge file for the Custom LLM brain build. Everything learned so far about the Custom LLM project, the rebrand, the team, and how the new brain should be set up. Update this file as new transcripts, documents, and decisions come in. t; ⚠️ HIGHLY INTERNAL. The rebrand below is known only to the marketing team and executives. Nothing in this file may appear in any external, shareable, or team-visible output until launch. *Created 2026-08-04 from the Weekly Marketing Updates transcript (meeting held Tuesday, Aug 4, 2026) + review of Jordan*'s prior brain builds. Owner: Jordan*.*"},{"f":62,"x":"Apex Instruments (Apex), a ~$60M/yr devices contract manufacturer (Orange County HQ), is in the final stages of the review process to acquire the field network, one of the largest and oldest devices lab networks in North America. Custom LLM (S-P-E-K-T-R-A) is the new parent entity/brand created for the deal. The name is a nod to Apex Instruments (the \"Spek\" + the K for Apex). Registration and trademark are already secured (Dana* drove this with the trademark attorney).","h":"1. The headline: what Custom LLM is"},{"f":62,"x":"Estimated revenue $300M, $500M/yr; ~40 sites across the country; big education/training center in Florida with a hard-to-get *international accreditation*; owned by private equity; est. 500 to 1,000 employees. One of the top labs alongside Grandview Labs, Dashwood, Row Devices. Strong brand foothold but popularity dwindling ~5 to 10 years; high attrition; hasn't modernized workflows, which is why a $60M company can buy them. ~80% of the field network's business is private practice, the opposite of Apex's GSO focus. Private practice cares most about price and turnaround time. the field network uses the CRM for marketing (huge win for Sami*) and Salesforce for sales.","h":"About the field network (from research, not confirmed documents)"},{"f":62,"x":"Once the news leaks, Grandview Labs will 100% run campaigns to scoop the field network's customers. Retaining acquired business = retaining the rebrand's value. Pricing: match all current the field network pricing for at least the first 18 months. Turnaround: meet or beat the field network's current TAT. Heavy gifting strategy via Sendoso (welcome boxes, thank-you boxes, service-recovery gifts), part of why the pricey Sendoso contract was approved. Incentive programs for staying are pitched to leadership; awaiting approval (monetary incentives).","h":"Retention / anti-poaching strategy"},{"f":62,"x":"Avery* is blocking new projects for a ~2-week sprint. Deliverable to leadership: a handful of logo options + a handful of color options + a couple of font options → leadership picks top two → one round of revisions → done. No long back-and-forth. Workstream | Owner | Notes Logo | Josie (Josie*) | Full creative freedom; doesn't need to nod to the Apex logo. At least one option with movement/animation (team liked ORENDA's animated logo, Europe-based repair group). She starts on paper/iPad + stylus. Fonts | Josie* + Morgan* | Modern, highly readable digitally AND in print; avoid expensive licenses. Morgan* consults as the \"full-time proofing genius.\"","h":"2. The 3-week brand sprint (the team's current #1 priority)"},{"f":62,"x":"Agreed on the call: Copy the current Apex LLM brain to the desktop as a reference (done, it's in 05 Reference Examples/Apex LLM (reference copy)/). Jordan* is NOT overriding the Apex brain; Custom LLM gets a brand-new brain. Roughly 50% of the Apex brain carries over, rules, skills, structure, since Jordan* and Sami* built a lot that crosses over. Sami*: bring the skills, but no Apex branding. Work incrementally: have the model build a transfer plan and move things over one at a time with review, \"if you give it too much and it takes on too much, it gets dicey.\" Feed the brain (as materials arrive): This meeting transcript ✅ (in Call Transcripts/)","h":"3. The Custom LLM brain plan (Jordan*'s build)"},{"f":63,"x":"t; HISTORICAL SNAPSHOT (2026-08-05). This is the intake record as gathered at kickoff; the brand has since evolved (Midnight v0.6, the 12 Custom LLM color names). Current design truth: 01 The Brain/Brand/custom-llm/brand-sheet.md. ⚠️ HIGHLY INTERNAL, the project internal only. Nothing external until launch (target 2026-09-01, may slip to 10-01). Template spec: v1.0 · Compiled by Atlas 2026-08-05 from Jordan*'s inputs + Custom LLM Knowledge.md + the 2026-08-04 marketing transcript · the first assembly on this brain system. Open questions are numbered Q-# and double as the future brain's questions register."},{"f":63,"x":"Name: Custom LLM (with a K, from \"Spek\"trum + Apex). Trademark secured (Dana* + attorney). ™ placement rule: the ™ goes after \"Custom LLM,\" never after a longer name. What it is: the new parent entity/brand over the Apex + the field network rebrand. Presents publicly as a neutral third-party holding company (PE-style) that acquired *both* companies. The world must never read Custom LLM as \"Apex Instruments renamed.\" Origin story (from Jordan*, 2026-08-05): began 1945 as Southern California devices craft → ~8 decades → uniting legendary master labs + pioneering digital workflows + FDA-registered manufacturing infrastructure; bridges timeless artisanry and modern engineered operating procedures.","h":"1 · Identity → L1, L3, Facts"},{"f":63,"x":"Brand feel (from the sprint brief): \"modern, streamlined, engineered with precision.\" Narrative: two companies with unique advantages become a super devices-technology company; intrigue from an unknown name. Language observed in the drafts: \"legendary,\" \"engineered,\" \"uncompromised,\" \"artisanry,\" \"at scale.\" Q-8: 3 to 5 voice adjectives + banned words for Custom LLM (inherit Apex's list? add rebrand-specific bans, e.g. \"rebrand,\" \"takeover,\" \"rebrand\"?). → Q-9: 3 writing samples in the voice you want (Avery*'s press-release draft would be sample #1, pending Dana*'s OK). →","h":"4 · Voice → L4"},{"f":63,"x":"THE RULES ABOVE ALL: nothing Custom LLM-related shareable, publishable, or visible outside the project circle until launch. No Custom LLM content in any Apex-team-visible surface. The world never reads Custom LLM as Apex renamed, holding-company voice always. ™ after \"Custom LLM\" only. Never invent the field network facts, the review file is sealed (even C-suite can't see internals until signing); all the field network numbers are research estimates, marked as such. Pricing commitments are locked promises: match the field network pricing ≥18 months; meet-or-beat the field network TAT, never restate loosely. Brand elements are PENDING/PROPOSED until leadership locks them, every branded output carries the flag.","h":"5 · Hard rules → L3"},{"f":63,"x":"Mock logo (Jordan*, interim): photoreal glass lightning-bolt \"S\" on midnight. Hero-render only, an SVG flat derivation is REQUIRED for the kit (favicon, mono, print, knockout). Test palette (Jordan*'s sports-rebrand research): White Solid #F4F5FA · First Draft #C8FF00 · Magic Ink #0247FE · Midnight Edition #0C121B, with measured contrast (19.28:1 / 17.75:1 / 6.29:1 / 18.78:1) + a blue↔neon gradient ramp + button set (light: ink-filled/outline/midnight · dark: neon-filled/neon-outline/white). Surface law observed in Jordan*'s samples: First Draft is a DARK-surface accent only (neon on white ≈ 1.1:1, never text on light); on light surfaces the accent is Magic Ink.","h":"8 · Brand → L8, status: PROPOSED (sprint in flight, leadership picks)"},{"f":63,"x":"The launch website (info page + leadership page + contact page, Jordan* owns, deliberately tiny) The announcement kit (designed press release + og/social cards + LinkedIn announcement set) The retention/welcome kit (the field network-customer welcome piece + Sendoso gift inserts + account-manager one-pager) Full menu enablement can wait for the brand lock; these three carry the launch. 10 · Modules & infra: Website module: ON (tiny 3-page launch site, draft-gated, on Jordan*'s AI infrastructure). Meetings module: ON (Tue/Thu + weekly ingestion, define the single ingestion flow w/ Sami* to avoid duplicates). Team pipeline: ON (5-person marketing team + approvers). Partner kits: LATER (post-merge). SEO/content: OFF at launch.","h":"9 · Collateral menu → L6/L7, Atlas's recommended day-one three (confirm: Q-15 →)"},{"f":64,"x":"See Rules/target-audiences/ for the four working audiences (private-practice technician · GSO leadership · the field network talent · press). Deeper personas UNKNOWN until the review file opens and the field network customer data is real. Do not build demo personas."},{"f":65,"x":"The certainty: once news leaks, Grandview Labs runs campaigns to scoop the field network's customers. The counter is the retention strategy (see landscape file). Treat every retention deliverable as racing this clock. Deep dossier UNKNOWN, live research post-announcement or via the intel module."},{"f":66,"x":"$43B global devices industry. The three lab names with national recognition: Grandview Labs ($450 to 500M, \"a drop in the bucket\"), the field network (soon ours), Dashwood. Everyone else is unknown to the market: Row, Midvale Devices, Apex, Clarite, Verity. Nobody dominates the refit unit, that is the opening. The active threat: Grandview Labs (and forum speculation) will counter-message on price hikes and capacity within days of the announcement. The pre-approved holding statements live in Facts/launch/day-1-playbook.md; a marketing owner monitors Devicestown, LinkedIn, trade forums, and press daily for the first 30 days. Nothing beyond a holding statement without CGO/PR approval.","h":"The market picture (leadership's own framing)"},{"f":66,"x":"The full engine is Facts/launch/retention-engine.md: named owner for every account from Day 1 (no orphans) · coverage tiers · the top-20% program with CEO access · win-back for lapsed accounts (30 to 90 day window, \"first case on us\") · decliner watch measured in order volume, not logos · weekly retention tracking against a zero-attrition target.","h":"The retention counter-machine"},{"f":67,"x":"Date | Decision | Approver | Status ~2026-07 | \"Custom LLM\" name + trademark secured; ™ after \"Custom LLM\" only | Dana* + attorney | LOCKED ~2026-07 | Public posture: neutral holding company that acquired both Apex and the field network | Leadership | SUPERSEDED 2026-08-08 (one-story rebrand row below) ~2026-07 | Apex + the field network keep operating names ~12 months post-announcement | Leadership | LOCKED 2026-08-04 | Retention: match the field network pricing ≥18mo; meet-or-beat TAT | Leadership | SUPERSEDED 2026-08-08 by the written terms (conflict filed as Q-21) 2026-08-04 | Announcement target Sept 1 2026 (soft; may slip to Oct 1) | Leadership | ACTIVE 2026-08-04 | Brand sprint scope: options → leadership top-2 → one revision round | Avery* | ACTIVE"},{"f":67,"x":"2026-08-04 | New brain for Custom LLM (not an Apex-brain override); ~50% Apex carry-over minus all branding; incremental | Jordan* + Sami* + Avery* | ACTIVE 2026-08-05 | Brand OS built as full working system per color direction; First Draft = direction 1 of 5, sent to Avery* | Jordan* | PROPOSED Open decisions = the Q register (root file). 2026-08-06 | Midnight preferred as the lead direction (\"most well received\"), pending formal leadership pick | Avery* (working) | ACTIVE · renamed \"Evergreen\" 2026-08-08 (same direction, same palette, see row below)"},{"f":67,"x":"2026-08-08 | Lead direction renamed \"Midnight\" → \"Evergreen\", the old name came from the retired water-themed set (First Draft / Deep Draft / Gilt Draft) and read as oceanic, while the winning palette is deep space, electricity and precision metal. \"Evergreen\" is already in the token vocabulary (Harbor: \"steel tempered by heat and pressure; engineered strength\") and carries the double meaning of hardened-by-process and measured. Nothing else changed: same 12 tokens, same marks, same motion. | Jordan* | ACTIVE 2026-08-06 | Red retired; Electric Orange #FF6B1C as the flag/energy accent, license expanded beyond trim; alternates (coral/burnt/salmon/yellow) rendered for leadership | Avery* + Jordan* | ACTIVE"},{"f":67,"x":"2026-08-06 | Gold dropped from Midnight; Copper family (#245D63/#A8B6B7/#A8B6B7) as the warm metal; Chrome stays lead; Paper White confirmed | Avery* + Jordan* | ACTIVE 2026-08-06 | Apex Devices / Health / Global / Group .com bundles purchased (new GoDaddy acct, APEXINST card), SEO/squatter protection; final family pick open | Avery* | LOCKED (purchase) 2026-08-07 | The 12 Custom LLM color names locked into the Brand OS (Midnight Green, Paper White, Sea Glass, Harbor, Tide, Inkwell, Mist, Basalt, Stone, Electric Orange, Chrome, Copper), each with a printed rationale | Jordan* | ACTIVE 2026-08-07 | Brand OS v0.6: dual-view (Presentation / Full Spec), executive opener, sample-content mocks, the leadership-ready cut | Jordan* | PROPOSED to leadership"},{"f":67,"x":"2026-08-08 | POSITIONING SUPERSEDED: the public frame is a MERGER OF STRENGTHS (\"1+1=3\", internally \"=5\"), the holding-company/never-say-rebrand rule is retired | Leadership (GTM + integration session) | LOCKED 2026-08-08 | Day-1 naming: endorser approach, both brands, working line \"a Custom LLM company\" (integration alignment; GTM drafts say \"an Apex Instruments company\", Q-20 confirms) · Apex drops customer-facing (the K in Custom LLM is the homage) · \"National\" phases out · standalone Custom LLM in ~24 months | Mercado*/Whitfield/Kovach | ACTIVE 2026-08-08 | Messaging: the two-layer message (doctor continuity-first / corporate combined-strength) + the Five Pillars + the message wall (internal \"help is here\" only) | Leadership (\"naming and messaging, boom, done\") | LOCKED"},{"f":67,"x":"2026-08-08 | Written retention terms adopted (6-mo rate lock, Continuity Guarantee, $500 equipment credit, 12-mo CE, FedEx 2nd Day), supersedes the 18-mo verbal figure pending Q-21 | GTM v4.1 | ACTIVE 2026-08-08 | Day-1 cascade dates locked: Aug 25 T-7 sign-off · Aug 28 T-4 manager briefings · Aug 31 go/no-go · Sep 1 hour-by-hour | GTM §5 to 6, §11 | LOCKED 2026-08-08 | PR agency shortlist: HarlowReeve, Redwing Studio, NinefoldBranding, select within the week | GTM §6.3 | ACTIVE"},{"f":68,"x":"Still empty BY DESIGN until approval. The comm docs landed (Q-11 answered) and a full retention-FAQ draft now exists at Work Zone/review-queue/retention/retention-faq-DRAFT.md, built strictly from the pricing authority file + the day-1 playbook's rumor-control answers. It moves here only after Avery*/leadership approval. Never improvised."},{"f":69,"x":"Clinical/product terminology. Ports from Apex glossary; SME verification flags carry over."},{"f":70,"x":"The Day-1 launch playbook layer, distilled from the GTM Strategy v4.1 plus the Internal + External Comm Plans (all deal-NDA tier). Source of truth for the cascade, crisis handling, the retention engine, and the media/PR phase plan. Drafted send-ready copy lives in Templates/launch-copy/."},{"f":71,"x":"The hour-by-hour for launch day. Every row has one owner. If a gate fails, the cascade holds, nothing downstream fires until the go/no-go clears it. The gates before the day: Gate | When | What must be true | Owner T-7 · Executive sign-off | One week out | All launch copy approved; endorser line locked (Q-02) | Dana* T-4 · Manager briefings | Four days out | Manager packet delivered; FAQ live internally | Avery* Go / No-Go | Day before | Press list confirmed (Q-06); site staged; inboxes staffed (Q-07) | Leadership","h":"Day-1 Playbook"},{"f":71,"x":"Time | What fires | Owner 7:00 | Leadership huddle, final go confirmation | Dana* 7:30 | All-staff announcement + manager huddles open | Avery* 8:00 | Site briefings begin · press release crosses the wire | Comms 8:30 | Web + announcement video live | Sami* 9:00 | Customer emails send · account teams begin calls | Nora* 10:00 | Vendor + partner letters | Morgan* Midday | Social + forum monitoring; escalation matrix live | Emmett* If something breaks: Crisis scripts live beside this playbook, one per scenario, pre-approved. Escalation: account team → Emmett* → Avery* → Dana*. Timestamps logged. No improvised statements. If the scripts don't cover it, the answer is \"we'll come back to you\" plus an escalation.","h":"Launch day, hour by hour"},{"f":72,"x":"Source: External Comm Plan (the field network Marketing, 2026-06-10, deal-NDA) + GTM v4.1 §6/Appendix A. This is the corporate megaphone only, customer/internal sequences live in day-1-playbook.md and retention-engine.md. Voice of the rebrand: CEO Roman Elias Mercado*. Where this plan and GTM v4.1 conflict, the GTM (later, 2026-07-21) wins. The four phases: Phase | Window | What happens I, Control the narrative | Sep 1, 2026 (Day 1) | 8:00 press release on devices + corporate newswires · 8:30 homepage splash/video banner + Vimeo CEO announcement + landing pages live · 10:00 vendor/partner B2B technical briefings"},{"f":72,"x":"II, Editorial blitz | Q4 2026 | Sept: LinkedIn digital ads to devices C-suite + procurement · Oct: pre-recorded CEO podcasts released across networks · Nov/Dec: print features, sponsored thought-leadership columns, cover stories in the trades III, Live circuit | Early 2027 | Heavy presence at the trade circuit, Lakeside Winter Show, the trade fair, the ops summit, the industry assoc, OGA + targeted GSO Tech Summit · podium spots, private VIP dinners, premium swag, high-visibility sponsorships IV, The Apex Summit | 2028 (planning from Q2, Q4 2027) | Proprietary capstone event: key partners, vendors, high-volume clinicians, solidifies market leadership"},{"f":72,"x":"Jul 1, Aug 15: produce the CEO video (public cut: unifying vision, expanded national infrastructure, market stability) · media kit (hi-res brand assets, corporate headshots, Orange County master-lab facility photography, press release) · splash banners + landing pages staged for instant Day-1 go-live · B2B position papers for manufacturing partners/suppliers · PR crisis playbooks (rapid-response matrices for competitor counter-campaigns and forum rumors on price hikes / capacity bottlenecks). Jun 15, Aug 1 (long print leads): pitch executive editors for late-Q3/Q4 features, sponsored inserts, covers · pre-book and record CEO/President podcasts through July, August with hard release dates ON or just after Sep 1 to match the blitz.","h":"Pre-launch build (the external half)"},{"f":72,"x":"HarlowReeve (works with Northbridge/Kessler) · Redwing Studio (Orvane) · NinefoldBranding (US Service Partners, Ridgeworks Vertex). Publication targets (Phase II priority order, with the why): Outlet | Audience | Angle Inside Devices Technology (IDT) | Lab trade (premier) | Highest priority for Q4 editorial, sponsored articles, feature spreads LabPress Magazine | Lab decision-makers | The business bible; feature/cover cements corporate scale Journal of Devices Technology (JDT) | NGIL peer-reviewed | Official structural credibility in the organized lab industry Group Practice Wire | GSO/group practice | \"Scale without Friction\" straight to enterprise executives Devices Economics | High-producing independents | The business-of-instrumentation champion; independent-practice message","h":"PR agency shortlist (engage immediately)"},{"f":72,"x":"Cordell Devices + GSO Review | Corporate/M&A watchers | Where procurement + PE look for devices M&A news Instrumentation Today | Practicing clinicians | Clinical results story with high-end aesthetic case photos Devices Products Report (DPR) | Tech/materials | Technical articles on scanning integration + engineered workflows InstrumentationIQ | Digital-first aggregate | Rapid distribution, video interviews, splash banners Praxis | Clinical CE | CE partnership underscores the education retention pillar Resonance Magazine (+ Resonance Bench Podcast) | Leadership/culture | The \"human side\" of the rebrand story","h":"PR agency shortlist (engage immediately)"},{"f":72,"x":"Show | Host(s) | The CEO's talking point Voices from the Line | Wes Calloway, Marguerite Selby | #1 lab-industry show. Peer-to-peer: preserving craftsmanship while scaling digital design. Artistry at scale, engineered precision Confessions from the Shop Floor | Gerald Bostwick | M&A logistics without corporate fluff; QC and elite aesthetics stay consistent The Digital Bench Podcast | Curtis Wren | National footprint expands scanning infrastructure, AI design workflows, localized production Group Practice Wire Show | Grant Ellery, Rosalind Pike | Pure B2B: scale, risk mitigation, supply-chain redundancy; master price agreements stable","h":"Podcast tour (CEO booking list, with the talking point per show)"},{"f":73,"x":"Source: GTM v4.1 §8 (deal-NDA). The single biggest risk is losing the field network accounts; the single biggest cause would be communication. Every account gets a named human from Day 1. Objective + principles: Zero attrition of the field network accounts. No account ever orphaned. Proactive, not reactive, owners reach out on cadence; doctors never chase. Build from within: keep the people who already hold the relationships. Day-1 buildout: Inventory relationship-holders at every the field network site (reps, CS staff, site leads + their accounts) → assign an interim owner to EVERY account immediately (the person the doctor already knows) → tier accounts → stand up the CRM records (owner, tier, cadence)."},{"f":73,"x":"Tier | Owner | Service Enterprise/GSO | Strategic Account Executive | 1:1 exec relationship, enterprise dashboards (platform name open, Q-23), QBRs, custom reporting; contacted within 48h of Day 1 High-volume practice | Senior Account Manager | Named AM, monthly proactive check-ins, priority support, education access Standard private practice | Account Manager | Named AM via the Day-1 sequence, scheduled check-ins, single point of contact Phases","h":"Coverage tiers"},{"f":73,"x":"0 (Day 1): triage, interim owners, no orphans · 1 (Days 1 to 30): map + launch, tiering, welcome outreach, the CRM, cadence · 2 (Days 30 to 90): formalize, convert capable the field network reps to AMs, QBRs, education rollout · 3 (90+): unify onto the Apex partnership model (dashboards, bespoke partner sites). Measured weekly against zero attrition; every Priority Care flag and save logged. The field sales team (net-new capability, handle with care)","h":"Coverage tiers"},{"f":73,"x":"Reassure the reps FIRST (their roles/comp), an anxious rep transmits anxiety to doctors. Day-1 field card: nothing changes for your doctors · stronger together · the AM partners with you, not replaces you · flag worried accounts today · your relationships are the reason this works. Reps = early-warning system (the CRM flag form + weekly SAE huddle) and prime AM candidates. The top 20% (accounts we cannot lose): Named senior ownership + expanded outreach · a stated direct line to CEO Mercado* · executive video box (CEO message on the inside flap + endorsed swag: apparel, surgical caps, notepads, Docket pads, mouse pads) · AM-hosted lunch-and-learn with education content. Every top-20% account hears from a named person within two weeks.","h":"Coverage tiers"},{"f":73,"x":"Lost customers (no order in 2 years): launch 30 to 90 days post-Day-1, one shot, acknowledge they left for a reason, explain what changed, \"your first case is on us,\" then a personal call. Decliners: retention is order volume, not logos; the CRM flags falling volume → compassionate check-in email + call (\"I am not calling to sell you anything\"), route material issues to escalation/top-20% paths. Drafted copy for both: Templates/launch-copy/.","h":"Win-back + decliner watch"},{"f":74,"x":"Sites and Centers of Excellence. Apex: HQ Orange County, LA, Texas. the field network locations (~40 sites, estimates) enter in phase 2."},{"f":75,"x":"Source: Facts/about-company/source-docs/2026-08-04-weekly-marketing.vtt · Distilled per the meeting schema. Questions raised: What is Custom LLM and how does it present publicly? · What's the brand sprint scope and who owns each workstream? · How do we retain the field network customers when news leaks? · Which docs feed the brain and when? · Sub-brand architecture (unanswered → Q-4)"},{"f":75,"x":"Summary: Apex is in final the review process to acquire the field network; Custom LLM is the trademarked parent brand presenting as a neutral holding company. A ~3-week brand sprint kicked off (logo Josie* · fonts Josie*+Morgan* · colors Jordan* · handles Sami* · voice/PR Avery* · website Jordan*). Retention strategy locked. The Custom LLM brain approved as a new build carrying ~50% of Apex's system, no Apex branding. Decisions / resolutions: Retention: match the field network pricing ≥18 mo, meet-or-beat TAT · Announcement target Sept 1 (soft) · Sprint format: options → leadership top-2 → one revision · New brain, incremental build (all → decisions log)"},{"f":75,"x":"Systems & projects touched: the project (Basecamp) · the brand sprint · the Custom LLM brain · Sendoso (onboarding Aug 10-11) · PR agency interviews · social handle grab Action items: Josie* → logo options · Jordan* → color research + brain build ✅ · Sami* → handles · Avery* → PR interviews + comm docs (Q-11) + Ronan* recording (Q-12) · Dana* → doc clearance"},{"f":76,"x":"Source: Jordan*'s Desktop transcript (⚠️ raw .vtt contains payment card details read aloud, REDACTED here; raw file should be deleted or scrubbed before any ingestion). Questions raised: Which Apex site pages go live and what does the agency need? · Which domain family do we buy? · Which brand direction reads best? · What replaces red and gold in Midnight?"},{"f":76,"x":"Summary: Apex website, agency to turn the reviewed pages into a full demo on apexinstruments.example; careers page requested; product-page images still pending. Domains, purchased via new GoDaddy account (marketing email, APEXINST card): Apex Devices / Apex Health / Apex Global / Apex Group .com bundles (.net/.info etc.) as SEO/squatter protection; Avery*: \"probably going to come down to devices, health, or global.\" Brand, Avery* reviewed all four directions; Midnight (Kraken-derived) is \"the one that would be most well received.\""},{"f":76,"x":"Decisions / resolutions: Replace red with a vibrant orange (or coral/yellow family; orange chosen) with license beyond trim · Drop gold from Midnight; try copper; chrome + glacier white confirmed strong · Jordan* to run additional material-concept directions (titanium/alloy/porcelain) · Avery* to review the guide + merge her running questions into the register (→ affects Q-3: domain family narrowing to Apex-prefixed .coms) Systems & projects touched: Apex website/agency · GoDaddy/domains · the four Brand OS directions · the master guide · Josie*'s logo workstream (\"Winnie\"/Josie owns final marks)"},{"f":76,"x":"Action items: Jordan* → v0.5 revision of Midnight ✅ (same day) · Jordan* → send Avery* the guide download · Avery* → question list merge + review after 3pm · Jordan* → email agency re: demo site + careers page"},{"f":77,"x":"Source: Facts/about-company/source-docs/Custom LLM_Integration_Strategy.pdf (brief + full transcripts). Participants per doc: Roman Elias Mercado* (CEO), Dana* Whitfield (CGO), Emmett* Kovach (President), Arturo Bellamy (Transition Leader), Marek, Doyle, Brannon mentioned. Note: transcript speaker labels rotate; attribute with care. \"Ronnell\"/\"Ronan\" in earlier transcripts = Roman Elias Mercado*. Questions raised: What is the Day-1 naming architecture? What is the external vs internal message? How bad is the field network brand sentiment really? Who becomes the account managers?"},{"f":77,"x":"Summary: Leadership aligned the naming path: Day 1 endorser approach with BOTH operating names carrying the new parent line (\"Apex Instruments, a Custom LLM company\" and \"National Vantex, a Custom LLM company\"), full transition to standalone Custom LLM in roughly 24 months. Apex drops from customer-facing use (the K in Custom LLM is the homage); \"National\" is to be phased out fast. Custom LLM trademark is approved; \"Apex\" alone and \"Truepath\" were rejected (trademark). Messaging: strict internal/external wall, internally \"help is here\" with overwhelming communication; externally the 1+1=5 one-story rebrand story told through the Five Pillars, never \"better contract manufacturer\" to private practice."},{"f":77,"x":"The long-game pitch: nobody dominates the refit unit (Summitline owns mounts at 10% of instrumentation, Trueline owns calibration at 10%; Grandview Labs is $450-500M in a $43B industry), Custom LLM builds the end-to-end company that addresses the unit. Decisions / resolutions: Naming + messaging \"boom, done\" (endorser = a Custom LLM company; two-layer message) · 24-month masterbrand horizon (not 12) · Apex and National phase out · win-back window = first 90 days · Vern Castellano (Larchwood) letter at T-10 + co-calls with prominent clinicians · account managers sourced from the field network relationship-holders, not outside hires · swag/culture budget approved (\"overwhelm people with swag\")"},{"f":77,"x":"Systems & projects touched: trademark/domains (custom-llm.com $100K negotiable) · the field network board materials (their own rebrand mandate, $300K estimate) · the CRM · the brand sprint · the project timeline (Sept 1 confirmed) Action items: Dana* → run the endorser branding · surveys of the field network customers/lapsed customers · pressure-test naming with the field network execs · circulate the field network board book · Thursday all-hands naming debate prep"},{"f":78,"x":"INTERNAL · the project internal only. Source: Facts/about-company/source-docs/2026-08-11-weekly-marketing-updates-transcript.md (Teams VTT, compacted to speaker turns; the original .vtt is preserved in 03 Knowledge and Sources/Call Transcripts/) · Distilled per the meeting schema. Present: Avery Kellen* · Jordan Vale* · Sami* · Morgan* (Teams display name \"Communications\") · Josie* / Josie (Teams display name \"Design\"). Display-name mapping is by Facts/people-and-org/team.md plus in-call address (Avery* addresses \"Design\" as \"Josie\" and \"Communications\" as \"Morgan\"); it is consistent but never stated outright, so treat surnames as UNKNOWN."},{"f":78,"x":"Reading notes: the captioner writes \"Apex\" where the speaker said *Custom LLM*; prose below uses the correct names, quotes are verbatim and therefore carry the caption spellings. Many decisive lines carried no speaker tag in the VTT, attributions marked *(untagged; by context)* are inferred from the surrounding tagged turns, not stated. The compaction also splits single sentences around other speakers' interjections (\"Mhm,\" \"Yeah,\" \"Okay\"); quotes below are rejoined across those splits without ellipsis, and the join never adds, drops, or reorders a word. Check any quote against the source file before it leaves this brain. Questions raised: What document architecture does the brain read from, MD or HTML?"},{"f":78,"x":"(Sami*) · What is the Custom LLM brain's scope, the marketing team only, or the whole company? · Does it make sense to build knowledge outside marketing assets? · Where does the authoritative partner/product fee schedule live and who owns it? · Who monitors caseinfo@apexinst and where does it route? · Why does support@apexinst route to LA only, and do we need an Orange County mailbox? · Can a the CRM sales sequence re-send to non-openers? · Should the Larchwood ticket tracker split revenue across a doctor's multiple offices? · Will Sendoso also serve the field network, and whose brand carries the Day-1 gift? · Who at the field network must be retained for a smooth transition? · Why are 11 NEXA 360 accounts in ABS with only 3 completed onboardings?"},{"f":78,"x":"Summary: Jordan* walked the team through the Custom LLM brain (operating loop, approvals, component maps, changelog, decisions log, big board, team-questions register, rebrand migration, graph engineering) and stated its provenance rule out loud: *\"everything that is built in here is what is started from either a transcript source of a meeting or a document that Avery* has provided."},{"f":78,"x":"Date | Commitment 2026-08-11 (call day, Tue) | Josie* sends three logo options · Morgan* drops the master fee-schedule Excel in chat · Fairline five-free-case email sent to 33 · Sendoso call one hour after this meeting · Avery* meets Dana* in the afternoon 2026-08-12 (Wed) | Larchwood lotto sends rise to 200/day 2026-08-13 (Thu) | Print-don't-pour email #2 to 460 contacts goes live (Sami*: *\"scheduled to go live in two days\"*), seven days after the 2026-08-06 send to 112 2026-08-14 (Fri) | Larchwood lotto sending continues through Friday 2026-08-15 (Sat) | Josie officially full time 2026-08-17 to 2026-08-21 | Larchwood lotto sends Monday through Friday, an exception to the usual no-Monday rule","h":"Dates, deadlines and commitments stated on the call"},{"f":78,"x":"the field network phase-out: 18 months on this call vs ~24 months in the register. Avery* (untagged; by context): *\"we'll start to phase out the field network brand. It'll take 18 months.\"* Facts/decisions/decisions-log.md (2026-08-08, Mercado*/Whitfield/Kovach) says *\"standalone Custom LLM in ~24 months\"*, and 2026-08-0X-integration-alignment-session.md records a *\"24-month masterbrand horizon (not 12).\"* Filed as a conflict; the logged decision stands until leadership rules.","h":"Conflicts flagged (not silently accepted)"},{"f":79,"x":"<year>/<month>/YYYY-MM-DD-topic.md (summary) + source transcript beside it. Summary format (adopted 2026-08-06 from the Cerebras Knowledge distillation schema, structure beats raw text for later recall): Questions raised: the questions someone would actually search for later, one line each Summary: short prose recap Decisions / resolutions: what was decided, by whom Systems & projects touched: named things affected (campaigns, partners, tools) Action items: owner + item Filed so far: 2026-08-04 weekly marketing (source: Facts/about-company/source-docs/). Incoming: Tue/Thu rebrand meetings, weekly marketing. Single-ingestion rule: transcripts enter through Jordan* only (Sami*'s auto-ingestion skill must not double-file here)."},{"f":80,"x":"Per-partner knowledge briefs (the Apex brain holds 16). Port de-branded during the migration chunks; each brief lists the partner's team + current collateral."},{"f":81,"x":"t; Internal · the project. Ported 2026-08-11 from the Apex approved roster (roster 4, 2026-06-30) per Jordan*: same people, same titles, now at Custom LLM. Emails remain the current working @apexinstruments.example addresses until the Custom LLM domain lands (the naming SPKs); partner names are the real accounts and stay as-is. This is the internal register; the branded Partner Team Directory page rebuilds in the migration (batch B1/B2 family). Partners and their coverage: Partner | Category | Account Executive | Account Manager(s) | Additional Support | Dedicated Email Vantage Devices+ | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Kinship | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example"},{"f":81,"x":"Fairline Care | GSO | Victor Salcedo, Fairline Account Manager; Delaney Prescott, Fairline Account Manager; Marisol Duarte, Fairline Account Manager; Hal Winslow, Fairline Account Manager | caseinfo@apexinstruments.example Larchwood Devices | GSO | Adrienne* Ledoux, Strategic Account Executive | Desmond Kirkley, Account Manager; Paloma Cintron, Account Manager | Yvette Carranza, VP Mount Engineering & Projects | larchwood.support@apexinstruments.example Harlan | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example BrightPath | GSO | Adrienne* Ledoux, Strategic Account Executive | Reese* Danforth, BrightPath Account Manager | Yvette Carranza, VP Mount Engineering & Projects | brightpath@apexinstruments.example"},{"f":81,"x":"CoreCraft | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Crescent Group | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Beacon Health | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Dorian Health | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Broadview | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Prisma Devices Partners | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example UnionSix Devices | GSO | Nadia Pemberton, Associate Account Executive | Kaz Petrenko, Account Manager | Victor Salcedo, Technical Advisor | UnionSix@apexinstruments.example"},{"f":81,"x":"OneSix | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Parkline Health | GSO | Dario Villaseca, Account Executive | Hal Winslow, Account Manager | dario.villaseca@apexinstruments.example ProBeam | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Purewell | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Crestline Demo Alliance | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Comet Health | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Choice Devices Mgmt | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example"},{"f":81,"x":"Inkstone | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example SmartSpan | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Sunrise Brands | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Solstice Source | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Summit West | GSO | Dario Villaseca, Account Executive | dario.villaseca@apexinstruments.example Lumen Devices Studio | Mount | Hector Zavala, Director of Aesthetics (Custom LLM) | Rosa Escalante, Account Manager | Warren Boone, FRX & Fieldline Expert (Lumen-side) | contactus@lumendevicesstudio.example BioSummit | Mount | Sloane* Ballard, Strategic Account Executive | sloane.ballard@apexinstruments.example"},{"f":81,"x":"Name | Title | Email | Role | Partners covered Rafael Ordonez | Assistant General Manager, San Antonio | Rafael.Ordonez@apexinstruments.example | Leadership | Custom LLM Texas (Location) Victor Salcedo | Technical Advisor | vsalcedo@apexinstruments.example | Technical | UnionSix Devices, Fairline Care, Caravelle, Private Practice Delaney Prescott | Fairline Account Manager | delaney.prescott@apexinstruments.example | Account Manager | Fairline Care Warren Boone | FRX & Fieldline Expert (Lumen-side) | wboone@lumendevicesstudio.example | Team | Lumen Devices Studio Adrienne* Ledoux | Strategic Account Executive | adrienne.ledoux@apexinstruments.example | Account Executive | BrightPath, Larchwood Devices","h":"Team members"},{"f":82,"x":"Person | Role | In the brain Dana Whitfield* | Chief Executive | Signs vision/mission (Q-17); final gate on launch copy Avery Kellen* | Marketing lead | Approver; owns the brand sprint and comms cascade Morgan Reyes* | Operations + pricing | Owns the pricing authority file; vendor letters Jordan Vale* | Brain operator | Runs the library, the fleets, and the approval queue Sami Torres* | Design engineering | Web + video; Brand OS consumer Josie Renwick* | Brand design | Production logo set (Q-05); photography (Q-12) Nora Ballinger* | Sales lead | Rep talk tracks; account-team cascade Tessa Renfro* | Customer success | Support inbox (Q-07); day-1 monitoring","h":"The circle"},{"f":82,"x":"Tier | What qualifies | Route | Window 1 | Routine question, single customer | Account team | Same day 2 | Churn signal, pricing dispute, press inquiry | Emmett* → Avery* | 4 hours 3 | Anything touching the transaction or legal | Avery* → Dana* + counsel | 1 hour Each person has a Work Zone folder under 05 Work Zone/. The brain routes drafts to the right approver automatically from this table.","h":"Escalation tiers"},{"f":83,"x":"Arrives from the Apex brain (de-branded) once Q-4 (sub-brand architecture) answers what shape it takes: product levels · service lines · TAT by product · scanner compatibility · mount education (incl. the component datasets). Folders get created WITH their content, not before. Exception, arrived early (2026-08-11): price-lists/, four Apex-side price files ingested directly at Jordan*'s direction (the OC/APEXINST consolidation, Vantage, Silverton 7/9, the Fairline Silverton contract). Read its README first: semantics and accuracy flags live there. The Q-4-gated catalog port above still stands."},{"f":84,"x":"Demo placeholder, the engagement's pricing dataset is removed from this copy. In production this is the pricing AUTHORITY file: the only source the brain may quote a price from."},{"f":85,"x":"Demo placeholder, the engagement's pricing dataset is removed from this copy. In production this is the pricing AUTHORITY file: the only source the brain may quote a price from."},{"f":86,"x":"Demo placeholder, the engagement's pricing dataset is removed from this copy. In production this is the pricing AUTHORITY file: the only source the brain may quote a price from."},{"f":87,"x":"Demo placeholder, the engagement's pricing dataset is removed from this copy. In production this is the pricing AUTHORITY file: the only source the brain may quote a price from."},{"f":88,"x":"Demo placeholder, the engagement's pricing dataset is removed from this copy. In production this is the pricing AUTHORITY file: the only source the brain may quote a price from."},{"f":89,"x":"Demo placeholder, the engagement's pricing dataset is removed from this copy. In production this is the pricing AUTHORITY file: the only source the brain may quote a price from."},{"f":90,"x":"Published pages: NONE (nothing is public; that's the point). Launch site target: 3 pages (info · leadership · contact), draft-gated, hosting per Q-16. Brand media: Brand/custom-llm/ (Brand OS v0.2 + logo mockups). Social handles: Sami* securing (FB, LinkedIn, IG; no Snapchat)."},{"f":91,"x":"t; Harvested 2026-08-11 from the Apex brain: 279 unique the CRM-hosted URLs (file manager CDN + landing assets). Sami* is building the full line-item structure in the CRM; a complete file-manager pull happens in Phase 4 with Jordan*'s the CRM access. https://10000000.fs1.cdn.example/hub/10000000/hubfs/Full%20Rack%20Info%20Image.png https://10000000.fs1.cdn.example/hub/10000000/hubfs/Full%20Rack%20Info%20Image.png?width=1200&height=900&name=Full%20Rack%20Info%20Image.png https://10000000.fs1.cdn.example/hub/10000000/hubfs/MXR%20Whats%20Needed%20Image.png?width=1200&height=900&name=MXR%20Whats%20Needed%20Image.png https://10000000.fs1.cdn.example/hubfs/ https://10000000.fs1.cdn.example/hubfs/10000000/ https://10000000.fs1.cdn.example/hubfs/10000000/3D%20devices%20resin%20printer.jpeg"},{"f":91,"x":"https://10000000.fs1.cdn.example/hubfs/10000000/FRX.jpg https://10000000.fs1.cdn.example/hubfs/10000000/Fairline%20Housings%20and%20Mounts%20Logo.png https://10000000.fs1.cdn.example/hubfs/10000000/Fairline/Fairline%20Care%20%C3%97%20Apex%20Apex%20%E2%80%93%20Digital%20Housing%20Partnership%20Executive%20Summary.pdf https://10000000.fs1.cdn.example/hubfs/10000000/Fairline/Fairline%20Care%20Onboarding%20Video%20New.mp4 https://10000000.fs1.cdn.example/hubfs/10000000/Fairline/CEO%20Video%20-%20June%2017%2c%202026.mp4 https://10000000.fs1.cdn.example/hubfs/10000000/Trueline%20ART/ClearForm%20ART%20Clinical%20Education%20Course%20Final%2c%20Rev%20B_process%20focused.pptx https://10000000.fs1.cdn.example/hubfs/10000000/Lumen%20Devices%20Studio%20Logo-2.png"},{"f":91,"x":"https://10000000.fs1.cdn.example/hubfs/10000000/Lumen%20Devices%20Studio%20Logo.png https://10000000.fs1.cdn.example/hubfs/10000000/Lumen%20Devices%20Studio%20and%20Apex%20Apex%20Logos.png https://10000000.fs1.cdn.example/hubfs/10000000/Lumen%20Devices%20Studio/Lumen%20Apex%204.8.26%20Webinar%20Invite%20QR%20Code.png https://10000000.fs1.cdn.example/hubfs/10000000/Lumen%20Devices%20Studio/Apex%20Apex%20%26%20Aurora%20Devices%20Studio%20Logos%20Full%20White.png https://10000000.fs1.cdn.example/hubfs/10000000/Lumen%20Devices%20Studio/Apex%20Apex%20&%20Aurora%20Devices%20Studio%20Logos%20Full%20White.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Larchwood%20Devices%20Lab%20Slip%20Digital%20Docket%20(3.30.2026"},{"f":91,"x":"https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Larchwood%20Devices%20Logo%20Full.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Larchwood%20Axis.mp4 https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Larchwood%20Wordmark%20Logo.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Larchwood-Devices-Emblem.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/LFXONiX%20%20Ridge%20in%20the%20Unfitted%20High%20Lantern.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/LFXONiX%20%20Ridge%20not%20visible.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/LFXONiX%20Frontal%20Relaxed.png"},{"f":91,"x":"https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Locator%20Fixed%20Image.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20Devices%20Files/Apex%20Apex%20&%20Larchwood%20Devices%20Logos.png https://10000000.fs1.cdn.example/hubfs/10000000/Larchwood%20MXR%20Whats%20Needed.pdf https://10000000.fs1.cdn.example/hubfs/10000000/B-Roll%20Edit%20-%20Apex%20Apex%20Shoot%20-%20January%2029th%202026.m4v https://10000000.fs1.cdn.example/hubfs/10000000/B-Roll%20Edit%20-%20Apex%20Apex%20Shoot%20-%20January%2029th%202026.m4v` https://10000000.fs1.cdn.example/hubfs/10000000/Before%20and%20After%202.png https://10000000.fs1.cdn.example/hubfs/10000000/BioSummit%20Authentic%20Connection%20Badge.png"},{"f":91,"x":"https://10000000.fs1.cdn.example/hubfs/10000000/BioSummit%20Logo%20Color.png https://10000000.fs1.cdn.example/hubfs/10000000/BioSummit%20Logo%20White.png https://10000000.fs1.cdn.example/hubfs/10000000/BioSummit-logo-new-orange-white.png https://10000000.fs1.cdn.example/hubfs/10000000/BioSummit-logo.png https://10000000.fs1.cdn.example/hubfs/10000000/Biosummit%20Files/Biosummit%20Onboarding%20-%207%20May%202026.mp4 https://10000000.fs1.cdn.example/hubfs/10000000/Biosummit%20Files/Biosummit%20x%20Basalt%20x%20Apex%20Apex%20Logos%20White.png https://10000000.fs1.cdn.example/hubfs/10000000/Biosummit%20Files/Biosummit%20x%20Basalt%20x%20Apex%20Apex%20Logos.png https://10000000.fs1.cdn.example/hubfs/10000000/Biosummit%20Files/Gideon%20Halvorsen%20Profile%20Picture.png"},{"f":92,"x":"Source | What it is | How it enters | Cadence | Owner Weekly marketing meeting | Team sync transcript (.vtt) | Jordan* files to Facts/meetings + source-docs | Weekly (Tue) | Jordan* Tue/Thu rebrand meetings | Corbin*/leadership planning | Avery* records → Jordan* files | 2×/week once recording starts | Jordan* Strategy docs (GTM v4.1 + Integration brief) | The Day-1 playbook + exec naming/messaging alignment | ARRIVED 2026-08-08, filed to source-docs (Q-11 answered) | Done | Jordan* Comm plans (Internal + External, the field network Marketing 2026-06-10) | Crisis call scripts, timed Day-1 comms, full media/PR phase plan + publication/podcast targets | ARRIVED 2026-08-08, filed to source-docs; predate GTM v4.1, GTM wins on conflicts | Done | Jordan*"},{"f":92,"x":"Ronan* brain-dump | Notion recording on Custom LLM's future | Pending from Avery* (Q-12) | Once | Jordan* Brand assets | Josie*'s logo/font workstream output | Jordan* files to Brand/custom-llm/brand-assets | As produced | Jordan* Basecamp \"the project\" | Task/decision threads | Manual pull as needed (MCP later) | Ad hoc | Jordan* Rule: one owner per source; Sami*'s auto-ingestion skill must NOT write to this brain (prevents the duplicate-filing issue from the Aug 4 call)."},{"f":93,"x":"t; Harvested 2026-08-11 by grepping the entire Apex brain for apexinstruments.example/wp-content/uploads links: 978 unique hosted files, grouped by upload month. Use these live URLs to source real images and PDFs when building collateral. A complete media-library pull direct from WordPress happens in Phase 4 with Jordan*'s session. 2026-08 (2 files): https://apexinstruments.example/wp-content/uploads/2026/08/Fairline-Care-, -Apex-Price-List-07312026.pdf https://apexinstruments.example/wp-content/uploads/2026/08/DeltaCraft-Price-Sheet-Checklist-08042026.pdf"},{"f":93,"x":"https://apexinstruments.example/wp-content/uploads/2026/07/2026-Vantage-Devices-Apex-Lab-Slip.pdf https://apexinstruments.example/wp-content/uploads/2026/07/2026-Keystone-Apex-Lab-Slip.pdf https://apexinstruments.example/wp-content/uploads/2026/07/FRX-Fixture-Guide_-Whats-Needed_06092026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/FRX-Fixture-Guide_-Whats-Needed_07162026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-%C2%B7-Apex-Price-List-07152026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-FRX-Appointment-Guide-2026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-Bench-Rack-Guide-2026.pdf","h":"2026-07 (59 files)"},{"f":93,"x":"https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-Mount-Whats-Needed-2026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-Price-List-2026-1.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-Remake-Charge-Chart.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-Welcome-Flyer-2026-1.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Vantage-Devices-Welcome-Flyer-Alt-2026-1.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Larchwood-Devices-, -Apex-Welcome-Packet.pdf https://apexinstruments.example/wp-content/uploads/2026/07/Reese_Danforth-scaled.png https://apexinstruments.example/wp-content/uploads/2026/07/Caravelle-Pricing-07101016.pdf","h":"2026-07 (59 files)"},{"f":93,"x":"https://apexinstruments.example/wp-content/uploads/2026/07/BrightPath-Aperture-Program-Guide-, -Apex-2026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/BrightPath-, -Apex-Welcome-2026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/DIGITAL-FRX-Photogrammetry-Workflow-Guide-07172026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/DIGITAL-FRX-Photogrammetry-Workflow-Guide-07172026.pdf` https://apexinstruments.example/wp-content/uploads/2026/07/DeltaCraft-TAT-Case-Checklist-07312026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/DeltaCraft-TAT-Case-Checklist-2026.pdf https://apexinstruments.example/wp-content/uploads/2026/07/First-2-Bench-Units-%E2%80%94-Apex-1.pdf","h":"2026-07 (59 files)"},{"f":93,"x":"https://apexinstruments.example/wp-content/uploads/2026/06/2026-Vantage-Devices-Apex-Lab-Slip.pdf https://apexinstruments.example/wp-content/uploads/2026/06/2026-Fairline-Apex-Lab-Slip-6.16.26.pdf https://apexinstruments.example/wp-content/uploads/2026/06/2026-Parkline-Health-Apex-Lab-Slip.pdf https://apexinstruments.example/wp-content/uploads/2026/06/2026-Apex-Lab-Slip-1.pdf https://apexinstruments.example/wp-content/uploads/2026/06/2026-Apex-Lab-Slip.pdf https://apexinstruments.example/wp-content/uploads/2026/06/Abigail-Magnusen-300x300.png https://apexinstruments.example/wp-content/uploads/2026/06/Abigail-Magnusen.png https://apexinstruments.example/wp-content/uploads/2026/06/AdobeStock_238112580-1-scaled.jpeg","h":"2026-06 (136 files)"},{"f":93,"x":"https://apexinstruments.example/wp-content/uploads/2026/04/2026-UnionSix-Price-List-Apex.pdf https://apexinstruments.example/wp-content/uploads/2026/04/2026-UnionSix-Price-List-, -Apex.pdf https://apexinstruments.example/wp-content/uploads/2026/04/Kestrel-Logo-scaled.png https://apexinstruments.example/wp-content/uploads/2026/04/Kestrel_Export_Guide-scaled.png https://apexinstruments.example/wp-content/uploads/2026/04/kestrel-icon-logo.png https://apexinstruments.example/wp-content/uploads/2026/04/FRX-Icon-2.png https://apexinstruments.example/wp-content/uploads/2026/04/Fairline-White-Logo.png https://apexinstruments.example/wp-content/uploads/2026/04/Trueline-Technology-Apex-Executive-Summary.pdf https://apexinstruments.example/wp-content/uploads/2026/04/Miriam-Feld-Apex-Headshot-1.png","h":"2026-04 (180 files)"},{"f":94,"x":"t; Harvested 2026-08-11 from the Apex brain's page-directory. These are the LIVE WordPress pages on apexinstruments.example; the Custom LLM domain versions rebuild at the WordPress move. Use for sourcing and reference. Page | URL (unnamed) | https://apexinstruments.example/team-site/ Operating Hub | https://apexinstruments.example/operating-hub/ Prompt Library | https://apexinstruments.example/prompt-library/ Templates & Quick-Start | https://apexinstruments.example/templates-quick-start/ Brand Assets Gallery | https://apexinstruments.example/brand-assets-gallery/ Asset Directory | https://apexinstruments.example/asset-directory/ Page Directory | https://apexinstruments.example/team-site/page-directory/"},{"f":94,"x":"Partner Team Directory | https://apexinstruments.example/team-site/partner-team-directory/ Meet the Apex Team | https://apexinstruments.example/team-site/meet-the-team/ Interactive Demo | https://apexinstruments.example/team-demo/ Mount Atlas | https://apexinstruments.example/team-site/mount-atlas/"},{"f":95,"x":"Custom LLM-level service architecture is UNKNOWN pending Q-4 (sub-brands). Operating-company services live in their own worlds (Apex brain for Apex). Do not merge."},{"f":96,"x":"Status: GATED. The team hub is a public-ish surface, it waits for launch day by design. Building it early would put the new brand on a discoverable page before launch day. The gate is the launch itself. The eleven planned pages: Page | What it holds Welcome | The story, the endorser line, the \"what changes for you\" answer Team directory | People cards from the org data model, photo, role, contact How to use the brain | The team onboarding guide, embedded Ask the brain | The question form wired to the register Published pages | Everything promoted to Approved, browsable Asset directory | The color-coded tree, team view Plan & calendar | The dated line, read-only Brand center | The locked Brand OS + downloads Templates | The send-ready library, gated links","h":"The Hub Plan"},{"f":96,"x":"Questions | The open register, answerable in place Changelog | The record, newest first The data model: People data lives in one JSON file, stable IDs, reporting lines, headshot slots, so the directory, the org chart, and the approval roster all render from the same source. OWED: reporting lines + headshots (Josie*)","h":"The Hub Plan"},{"f":97,"x":"The Hub (the browsable front door + the 22-tool branded generator suite) activates post-announcement, or once a private hosting path exists (Q-16). It is deliberately absent now: the Hub is a team-visible surface and nothing Custom LLM may be team-visible pre-launch. Activation: the toolkit installs from Jordan*'s master template, gets branded from Brand/custom-llm/ tokens, and deploys behind access control only."},{"f":98,"x":"Internal · the project. A skill does one thing; an agent chains skills into a finished outcome. Each specialist below activates with a slash command in a Claude Code session opened at the brain root (Custom LLM Brain/): type the command, add your request, press enter. Checkers check, makers make, librarians remember, operators run the machinery. Every agent obeys the constitution, nothing external, nothing invented, nothing into Approved without a human. Checkers: They verify. Fresh eyes on anything before it goes up the chain."},{"f":98,"x":"status: ACTIVE does: Checks any draft against the brain's facts, voice, and the rules, runs the scanner, and returns a pass/flag/fail verdict with line numbers. Run it before anything goes to Jordan* or Avery*. example: /proof 05 Work Zone/review-queue/retention/welcome-letter-DRAFT.md never: Rewrite or edit the piece (that is /revoice's job). /brandcheck, The Brand Guardian: does: Verifies tokens-only color use, the surface law, mark rules, PROPOSED flags, and the name rule on anything visual or branded. example: /brandcheck 05 Work Zone/review-queue/website/info-page-copy-DRAFT.md never: Redesign the piece or pick new colors.","h":"/proof, The Proofer"},{"f":98,"x":"status: OPERATOR does: Runs 21 independent verifier agents over every draft in the review queue at once and files the ranked report. Operator command. example: /qa never: Edit any draft (report only, fixes are decided by Jordan*). Makers: They produce. Drafts and rewrites, always the brain's way, always into the Work Zone. /draft, The Drafter: does: Builds a new piece the brain's way: right template, right tone, facts from the authority files, scanned clean, saved to your Work Zone. example: /draft a one-page internal update for the project circle on where the brand sprint stands never: Invent a fact, price, name, or testimonial to fill a gap.","h":"/qa, The Fleet Marshal"},{"f":98,"x":"does: Rewrites any copy into an approved tone, fixes banned words, hype, and off-voice phrasing without touching the facts. example: /revoice 05 Work Zone/Jordan/01-scratch-pad/partner-email.md into reassuring-advisor never: Alter a fact, price, or commitment while rewording. /proposal, The Proposal Builder: status: STAGED does: STAGED · Assembles a complete partner proposal from the account brief, approved positioning, and the template. Activates at brand-lock. example: /proposal Trellis (after brand-lock) never: Commit to pricing, terms, or dates not in the authority files.","h":"/revoice, The Voice Editor"},{"f":98,"x":"does: STAGED · Builds a new partner's complete onboarding kit, flyer, lab slip, guides, checklist, in one consistent run. example: /onboard BioSummit (after brand-lock) never: Mix another partner's details in via template residue, sweep every field. Librarians: They remember. Sourced answers, filed meetings, registered decisions. /facts, The Librarian: does: Answers any question from the brain's filed knowledge, with a citation for every fact. Says UNKNOWN rather than guessing, and drafts the question that would close the gap. example: /facts what are our written retention commitments, exactly? never: Fill a gap with general devices-industry knowledge, the brain's files or UNKNOWN, nothing else.","h":"/onboard, The Partner Onboarder"},{"f":98,"x":"does: Files a meeting the brain's way: verbatim source stored, decisions and action items distilled, conflicts with the decisions log flagged. example: /scribe [paste the transcript of today's marketing call] never: Paraphrase a decision loosely, quote decisive language exactly. /file, The Registrar: does: Files an incoming answer end to end: fact recorded with attribution, every placeholder it unlocks filled, the question checked off. example: /file Q-13 is answered: leadership confirmed Archivo + IBM Plex (Avery*, today) never: File an ambiguous answer, if it could mean two things, draft the clarifying question instead.","h":"/scribe, The Scribe"},{"f":99,"x":"the project, Internal. Five minutes to read; everything else is discoverable from here. What this is: One shared brain the whole launch runs on: an AI system that holds what's true about Custom LLM, follows our rules without exception, and produces our materials on demand. It is not new software, it is a smart shared folder with a constitution. You talk to the AI; the AI reads the brain. How a request flows (the whole model in one paragraph)"},{"f":99,"x":"You ask for something → a silent gate checks the ask is clear (vague asks get 2-3 multiple-choice questions) → a routing table opens exactly the right files, never the whole tree → the matching skill adapts an approved gold-standard example, never designs from scratch → facts come only from approved sources → an automated scanner checks voice, brand, and the rules → the draft lands in YOUR Work Zone folder → review → approval → it becomes official in the Approved library. Every change is logged, dated, and attributed. Nothing is ever deleted."},{"f":99,"x":"Nothing leaves the project circle until the announcement. The AI physically refuses to produce anything for external use. Test it yourself, ask it to write a LinkedIn post about the rebrand. The AI never invents. No made-up numbers, quotes, or testimonials. Unknowns come back as UNKNOWN plus a numbered question for the team. Approved is the truth. If it's not in Approved or Facts, it's not official, drafts are drafts. Prove it in three minutes, the acceptance test","h":"The three rules that matter most"},{"f":99,"x":"Ask these four, in a fresh session: \"What are our retention commitments to the field network customers?\" (exact quotes, sourced) · \"What's the field network's revenue?\" (answered as labeled estimates, never fact) · \"Write a LinkedIn post announcing the rebrand\" (refuses) · \"Add a customer testimonial\" (refuses, offers a slot). Four for four = the brain is healthy. Your folder: Everyone in the team has a Work Zone: Work Zone/<your name>/ with seven stages from inbox to archive. Position = status; finished work goes to 03-for-review. Approvers check there.","h":"The three rules that matter most"},{"f":99,"x":"Templates/prompt-library/starter-prompts.md, sixteen tested prompts, copy and fill the brackets. Then just talk to it; the brain routes itself. Who runs it: Operator/AI owner: Jordan* · working approver: Avery* · everything money/legal: Avery* + Dana* · brand: Josie*'s workstream, the AI carries interim marks until her set lands. Questions the brain can't answer live in QUESTIONS-FOR-THE-TEAM.md, answering any item there upgrades the whole system the same day.","h":"Where to start"},{"f":100,"x":"Internal · the project. A skill is one packaged ability: a recipe the brain follows every time so the output is consistent. You do not type commands for these, open a Claude Code session at the brain root (Custom LLM Brain/) and ask for the thing; the constitution routes your request to the right skill automatically. The use line under each skill shows a natural ask. Generation skills are built and waiting on brand-lock: the day leadership locks the brand, their gold-standard references get built from the approved Brand OS and all eighteen switch on."},{"f":100,"x":"Active now. These run the brain's daily machinery and every request passes through some of them. graph-engineering, The Wide-Job Engine: status: ACTIVE does: Runs work too big for one sitting as coordinated agent fleets, fan out, verify with fresh eyes, synthesize one answer. Powers the QA fleet, the coming migration batches, and the brain's own audits. use: \"Run the qa-fleet workflow\" · \"Run this ingestion as a graph\" home: 01 The Brain/Skills/graph-engineering/ prompt-enhancer, The Front Door: does: Runs first and silently on every request; scores completeness and asks only real-option questions before any work starts. use: Automatic, every request passes through it. home: 01 The Brain/Skills/prompt-enhancer/","h":"Working skills"},{"f":100,"x":"does: The last gate before any handover: banned words, the rules tripwires, pricing sources, phone formats, dash police. Half deterministic script, half judgment. Exit code, not opinion. use: Automatic on every deliverable · \"Scan this file\" home: 01 The Brain/Skills/pre-delivery-scan/ quality-control, The Script Suite: does: The generators that build the machinery itself: the team site, the styled twins, the Asset Directory, AGENTS.md, the brain audit. Operator surface. use: \"Rebuild the guide\" · \"Regenerate the asset directory\" home: 01 The Brain/Skills/quality-control/","h":"pre-delivery-scan, The Scanner"},{"f":100,"x":"does: Keeps every markdown file's styled html twin current: staleness scan, regeneration with the day's stamp, and the never-hand-edit-a-twin rule. use: \"Run twin-sync\" home: 01 The Brain/Skills/maintenance/twin-sync/ file-owners-answer, The Answer Filer: does: Turns a team member's answer into filed fact with attribution, cleared placeholders, a checked-off register question, and a refreshed site. Also lives as the /file agent. use: \"File this answer: Q-24, our locations are...\" home: 01 The Brain/Skills/file-owners-answer/","h":"twin-sync, The Twin Keeper"},{"f":100,"x":"does: Builds a gate-verified preview bundle of the site when push-to-deploy is not available, so a change can be reviewed before it ships. use: \"Build a preview bundle\" home: 01 The Brain/Skills/deploy-preview/ folder-cleanup, The Tree Groomer: does: The standard library-cleanup process, ported from Apex's proven pattern: version ranking, archive-never-delete, card refreshes, promotion mechanics. Run on any Approved folder that has grown messy. use: \"Clean up the BioSummit folder\" home: 01 The Brain/Skills/folder-cleanup/","h":"deploy-preview, The Preview Bundler"},{"f":100,"x":"does: Roman Elias Mercado*'s presentation language, density doctrine, photo treatments, badges, stat cards, stair-steps, overlaid on any deck bound for his desk. Ported from the proven Apex build. use: \"Build this deck in the Mercado* style\" home: 01 The Brain/Skills/mercado-presentation-style/ Generation skills: Built and GATED on brand-lock. Each one copies a gold-standard reference that gets created from the approved Brand OS the day leadership locks the brand, then all of these switch on at once.","h":"mercado-presentation-style, The CEO Deck Style"},{"f":101,"x":"Every folder and file in this brain, one line each. AIs: use CLAUDE.md §5 routing first; this index is for lookups the routing table doesn't cover. AGENTS.md, Custom LLM, Company Brain CLAUDE.html, html twin CLAUDE.md, Custom LLM, Company Brain QUESTIONS-FOR-THE-TEAM.html, html twin QUESTIONS-FOR-THE-TEAM.md, Questions for the team, Custom LLM README.html, html twin README.md, Custom LLM, Company Brain ROADMAP.html, html twin ROADMAP.md, Roadmap, Custom LLM Brain · the dated line to September 1 (and beyond) Approved/ README.md, Approved, canonical truth Private Practice/ _about.md, Fills via the rebrand migration (04 Plans/CUSTOM LLM-REBRAND-MIGRATION-PLAN.md): rebrand chun internal/ locations/ partners/ GSOs/ GPOs/ Anchor Partners/ Calibration & Alignment/ Tech & Software/ product-lines/"},{"f":101,"x":"Archive/ README.md, Archive, nothing is ever deleted 2026-08-06-direction4-v04/ Direction-4-DEEP-CURRENT.html, human-readable twin / rendered doc 2026-08-07-brand-os-early-versions/ Custom LLM Brand OS PROPOSED v0.1.dc.html, human-readable twin / rendered doc Custom LLM Brand OS PROPOSED v0.2.dc.html, human-readable twin / rendered doc Custom LLM Brand OS v0.5 Midnight.dc.html, human-readable twin / rendered doc 2026-08-08-master-guide-v2/ CUSTOM LLM-MASTER-GUIDE-v2.html, human-readable twin / rendered doc Brand/ custom-llm/ brand-sheet.html, html twin brand-sheet.md, Custom LLM Brand Sheet, Midnight v0.6 (the lead direction) how-the-brain-uses-the-brand-os.html, html twin how-the-brain-uses-the-brand-os.md, How the Brain Uses the Brand OS, the September 1 machine brand-assets/"},{"f":101,"x":"colors-and-fonts/ _about.md, Fills at brand-lock: Josie*'s production kit (colors-and-fonts) + migrated media, all in app email-signatures/ _about.md, Fills at brand-lock: Josie*'s production kit (email-signatures) + migrated media, all in app letterhead/ _about.md, Fills at brand-lock: Josie*'s production kit (letterhead) + migrated media, all in approved logos/ _about.md, Fills at brand-lock: Josie*'s production kit (logos) + migrated media, all in approved Spekt media-library/ _about.md, Fills at brand-lock: Josie*'s production kit (media-library) + migrated media, all in approv photography/ _about.md, Fills at brand-lock: Josie*'s production kit (photography) + migrated media, all in approved brand-os/ AUDIT-v0.2.md, Brand OS v0.2, Atlas audit (2026-08-05) support.js, runtime"},{"f":101,"x":"directions/ Direction-1-FIRST-DRAFT.html, human-readable twin / rendered doc Direction-2-DEEP-DRAFT.html, human-readable twin / rendered doc Direction-3-GILT-DRAFT.html, human-readable twin / rendered doc _INDEX.md, Brand directions, Midnight leads logo-mockups/ _INDEX.md, Custom LLM logo mockups, index (renamed by Atlas 2026-08-05) custom-llm-app-icon-tile-midnight.png, image custom-llm-lockup-horizontal-chrome-on-midnight.png, image custom-llm-lockup-horizontal-glass-on-light.png, image custom-llm-lockup-horizontal-gold-on-light.png, image custom-llm-lockup-horizontal-white-on-midnight.png, image custom-llm-lockup-stacked-chrome-on-light.png, image custom-llm-mark-chrome-on-light.png, image custom-llm-mark-flat-gold-notch-on-midnight.png, image"},{"f":101,"x":"custom-llm-mark-flat-ink-on-light.png, image custom-llm-mark-flat-white-on-midnight.png, image custom-llm-mark-glass-alpha.png, image custom-llm-mark-glass-midnight-a.png, image custom-llm-mark-glass-midnight-b.png, image custom-llm-wordmark-ink-on-light.png, image custom-llm-wordmark-white-on-midnight.png, image Facts/ about-company/ claims-and-credentials.md, Claims & credentials, SOLE CLAIMS SOURCE company-overview.html, html twin company-overview.md, Custom LLM, company overview pricing.md, Pricing, SOLE QUOTABLE SOURCE source-docs/ 2026-08-04-weekly-marketing.vtt, meeting transcript Rebrand_External_Com_Plan_2026.docx, docx file Rebrand_GTM_Strategy_v4.1.pdf, pdf file Rebrand_Internal_Com_Plan_2026.docx, docx file README.md Custom LLM_Integration_Strategy.pdf, pdf file"},{"f":101,"x":"external-com-plan-extracted.txt, txt file gtm-strategy-v4.1-extracted.txt, txt file intake-packet-2026-08-05.md, Brain Intake Packet, Custom LLM (operator-assisted) internal-com-plan-extracted.txt, txt file custom-llm-integration-strategy-extracted.txt, txt file custom-llm-knowledge.md, Custom LLM Knowledge client-personas/ personas.md, Personas competitors/ grandview.md, Grandview Labs, the retention threat landscape-summary.md, Competitive landscape & retention strategy (updated from the strategy docs) decisions/ README.md, Decisions decisions-log.html, html twin decisions-log.md, Decisions log, Custom LLM faqs/ client-faq.md, Canonical FAQ, Custom LLM glossary/ _about.md, Clinical/product terminology. Ports from Apex glossary; SME verification flags carry over. launch/"},{"f":102,"x":"2026-08-12 · THE AGENT TEAM GREW TO 45, ACROSS NINE DEPARTMENTS, and the three surfaces that disagreed about it now agree. The roster went from 15 named specialists to 45, grouped into nine departments (chief of staff, intake, knowledge and records, brand and design, production studio, communications, revenue and accounts, quality risk and assurance, engineering and delivery). Two things worth recording rather than quietly fixing. (1) The departments are new. This brain has always partitioned the same work three other ways, by behavior, by system layer, by deliverable type, and the word \"department\" appears nowhere in it. The shelf is new packaging; every agent hanging on it is real and cited. The Agents tab says so above the fold, because saying it first is what makes the rest believable."},{"f":102,"x":"(2) Three surfaces held three different numbers. The Agents tab said \"12 specialists · 9 active now\", the 8/11 entry below said 15, and the roster itself held 15 cards. Nobody edited a number wrongly; each surface was written on a different day and none of them read the others. That is precisely what /audit exists to catch and precisely what it had not been run against. Every count on the tab, in the Skills component card and in this entry is now computed from one list at build time, so the next disagreement is impossible rather than unlikely. The ledger as it stands: 19 running, 7 built but never run, 10 staged on real gates, 7 buildable, 2 blocked on a named dependency. The smaller true number leads, because a roster where everything is shipped is a lie."},{"f":102,"x":"Every card also publishes the one thing its agent refuses to do, at the same weight as what it does, a refusal is testable and an aspiration is not. By Atlas. 2026-08-12 · Q-1 FILED, the trademark answer, and the three questions it woke up. Avery*'s answer from the site inbox (counsel's letter of June 16) is filed at last, and the register did what a good register does: one answer in, three sharper questions out. Filed as fact in the company overview: the CUSTOM LLM trademark belongs to Halcyon Holdings II LLC, Serial No. 99599185, Class 40, published for opposition June 16, and the mark stays ™ never ® until a declaration of commercial use is filed after launch."},{"f":102,"x":"What the letter could not settle became Q-63: the letter proves who owns the mark, not whose name goes in footers and contracts, and counsel's own phrasing (\"APEXINST's application\" for a Halcyon Devices II filing) is exactly why nobody should guess. Two follow-ups nobody had asked: Q-64, the 30-day opposition window closed around July 16 and the brain should not assume silence means success, so did the Notice of Allowance arrive; and Q-65, the Statement of Use filing that only becomes possible once September 1 puts the mark in commerce, now a named row on the day-1 playbook so registration does not stall in a drawer after launch. Register: 58 open became 60, one answered, three born. Q-1 moved to Answered with full attribution. By Atlas."},{"f":102,"x":"2026-08-12 · HERO LAYOUT SET, the glass panel found its final shape. Jordan*'s composition pass on the new hero: the liquid glass panel now spans the full content column with equal margins both sides instead of hugging its text, the thinking orb moved inside the glass to rest above the title, and everything on the panel is centered, orb, title, sub line, pills. The hero reads as one composed card over the flowing chrome now, not a stack of left-aligned pieces. By Atlas. 2026-08-12 · THE HERO CALMED DOWN, Jordan*'s three refinements, same day. (1) Subtler: a tone map now caps the chrome's bright bands at a muted steel blue instead of letting them run to pure white, and it guards the shader's singularity against dead pixels."},{"f":102,"x":"(2) A thread of Electric Orange: a second band field, out of phase with the first, weaves #FF6B1C through the flow at low strength, thin copper filaments that surface and sink rather than a second loud color. (3) The text went liquid glass: the title, sub line, and pills now sit on a frosted glass panel, blur and saturation pulled from the backdrop, so the motion behind the words is diffused exactly where the eyes rest, and the title's 18 second gradient sweep is retired, static gradient now. Net effect: the same living metal, at a murmur instead of a shout. By Atlas. 2026-08-12 · LIQUID CHROME ON THE HOME HERO."},{"f":103,"x":"Done: batch 0 full cycle (stage, swap kit, 8-agent fleet, honest FAIL, remediation, gates calder, report filed, B0 RUNNING pending Jordan*) · Work Zone 8x5 rebuild · guides consolidated 12-to-2 + the How To site page · team directory ported (Iris Kaminski* found = Q-58) · WP pages/uploads + the CRM registries (978 + 279 URLs) · folder-cleanup skill live · auto-publish launchd armed (30-min cycle, audit-gated). Open: Jordan* approves batch 0 · Phase 4 site build with Jordan* · approval-folder notifications (Power Automate, with Jordan*).","h":"2026-08-12 (early), Batch 0 + the pre-Phase-4 package (Atlas)"},{"f":103,"x":"Done: Find view removed (assets absorbs it; legacy hashes remapped) · aggrid overflow fixed (min-width 0 + code wrapping) · 15 agent icons drawn inline · Batch Board view built from the new tracker register (22 batches, 0 done) · verified in-browser: no horizontal scroll on agents/skills, #find lands on Assets, board renders. 2026-08-11 (close), Phases 2 and 3 shipped (Atlas): Done: map generator rewritten with difficulty scoring + sha1 dedup + per-partner rollups (read-only on Apex, ~6GB hashed) · 1,860 unique masters quantified · batch plan written with real numbers, Jordan*'s 8/11 rules, and the per-batch runbook · routing row added. Next session: Batch 0 (the chassis + swap kit) on Jordan*'s go.","h":"2026-08-11 (last), Site catch-up pass (Atlas)"},{"f":103,"x":"Done: Custom LLMBrain library synced to the Mac (after the authorization-webview saga: shortcut removed, sync re-fired, OneDrive restarted, credentials checked, odopen handoffs with REST-fetched IDs, and finally the zombie registration surfacing as the live mount under OneDrive-SharedLibraries) · write round-trip verified server-side before the move · stale copy deleted · 1,040 files in · _answers-worker kept off SharePoint by design · ritual re-pointed (protect _answers-worker in the git sync) · publish cycle run from the new home as proof. Open threads: Northgate IT question (why new library syncs hang at authorization on this Mac) · remove the duplicate OneDrive shortcut · Desktop copy renamed-retired, trash ~8/18 after moving 05 Reference Examples out.","h":"2026-08-11 (evening), Phase 1: the move to SharePoint (Atlas)"},{"f":103,"x":"Done: read-only scanner over the production OneDrive library (4,600 files / 1,300 dirs / 15.2 GB, zero writes) · live map + twin filed in 03 Knowledge and Sources · §5 routing row (map for structure, Apex's own Master-Asset-Directory.md for descriptions) · drift vs the July index quantified (archives + Work Zone + the _Graph Obsidian overlay account for the doubling; only 2 files gone, both partner price-list PDFs) · Custom LLM domain files spotted in the team-shared Apex root and flagged. 2026-08-11 (night), Assets/Agents/Skills to the top bar (Atlas)","h":"2026-08-11 (late), The Apex LLM mapped live (Atlas)"},{"f":103,"x":"Done: 4 price files extracted to md tables (9,753 data rows total) with deterministic verification (row counts exact, cell-level comparison, 0 failures) · BioSummit bundle hunt (4 SKUs matrixed across every source) + Fairline cross-check (36 match / 5 conflict / 1 part duplicated inside the contract) · Librarian live test 3/3 exact with citations, volunteered the Q-57 flag · the Scribe distilled the 8/11 weekly call fresh-context (meeting note + verbatim; caption fixes Morgan*/Josie; five conflicts flagged incl. the master-Excel home ruling) · Q-57 to 62 opened, register 58 open · asset directory generator written (Apex page UI pulled + Evergreen reskin, two variants, live tree walk, 97 Apex-parity grafts, folder search added over Apex's file-only search) · 174 twins generated so rule 2 ho","h":"2026-08-11 (later), Price lists in, the call filed, the asset directory built (Atlas)"},{"f":103,"x":"Done: Skills/graph-engineering/ built from the article Jordan* supplied, doctrine (skill.md), 6 ready-to-run specs (graph-library.md), distilled source (reference/). CLAUDE.md routing row added; AGENTS regenerated; ritual run. The unlock order: review-queue QA fleet is runnable TODAY on the 7 waiting drafts; the ingestion cross-check fires on the next knowledge dump; the migration batch sweep is staged for brand-lock and turns the 1,200-file rebrand from a months-long chain into per-batch parallel runs with Jordan* reviewing batch reports. Frozen-rule inheritance is the Custom LLM-specific addition: every spawned agent carries the constitution, because in this brain the worst silent failure is a leak, not a wrong fact.","h":"2026-08-08, Graph engineering installed (Atlas)"},{"f":104,"x":"Internal · the project. The brain never guesses. Anything it doesn't know lands here as a numbered item, with what we need, why it matters, and who most likely owns it. Answer any item any time, on the team site or straight to Jordan*, and it takes effect immediately. Answered items are never deleted. Open: Blocking the launch copy, answer these first: Q-20 ⚠️ The endorser line: \"a Custom LLM company\" or \"an Apex Instruments company\"? ask: Which line ships on Day 1, under both operating brands? why: Leadership aligned on \"a Custom LLM company\" in the integration session, but every drafted GTM letter and email says the other. Five finished drafts are holding an empty slot for it, and it appears on letters, emails, banners, and signatures. One answer sweeps them all. who: Dana* + leadership"},{"f":104,"x":"Q-21 ⚠️ The retention rate lock: 6 months or 18? ask: Which promise is real, the 6-month written lock in the GTM customer letters, or the 18-month verbal match from the Aug-4 meeting? why: Two different commitments are in circulation right now. Nothing carrying a number can reach a doctor until one wins, and the wrong one is a pricing commitment we may not be able to honor. who: Leadership Q-23 ⚠️ What do we call the enterprise dashboard? ask: The GTM and both comm plans call it \"Truepath,\" but the integration session rejected that name on trademark grounds. What replaces it? why: GSO demos and every piece of enterprise copy reference this platform. Until it has a cleared name, nothing external can mention it at all. Q-26 What response times can we actually promise?"},{"f":104,"x":"ask: What service commitments are real and approved to publish, how fast an Account Manager responds, and whether an executive is ever promised within a set window? why: The QA fleet caught a \"reach a named executive within 48 hours\" commitment sitting in two finished drafts that exists in no approved source. Either it becomes a real commitment or it comes out of the copy. Right now it is a promise nobody agreed to make. who: Leadership + Dana* (commitments gate) Q-27 Can the Day-1 promises be published as a list? ask: May the four written retention commitments appear as a public bulleted list (website, fact sheet), or only quoted in context inside a letter?"},{"f":104,"x":"Q-15 Confirm the day-one three ask: Confirm the three Day-1 deliverables, launch website, announcement kit, welcome/retention kit, or tell us what replaces them. why: This sets build priority for the entire remaining sprint. If the list is different, the plan rebuilds around it immediately. Q-16 Hosting accounts for the launch site ask: Does the launch site live on new Custom LLM accounts (Cloudflare, GitHub), or on Apex's existing ones? why: It determines who owns the domain, the certificates, and the deploy keys on Day 1, and whether a painful handover is needed later. who: Avery* + Jordan* Q-22 Does the standalone Custom LLM site ship for Day 1?","h":"Build decisions"},{"f":104,"x":"Q-24 The facility locations list ask: The canonical list of locations that may appear in customer-facing material, which sites, which addresses, and which are safe to name before the consolidation plans are final. why: The locations file is empty, so the brain refuses to write an address anywhere; the contact page draft literally carries a note saying never improvise one. Letterhead, contact pages, flyers, and shipping information all need this. who: Dana* + operations Q-25 The product and service catalog ask: The canonical list of what Custom LLM sells, product lines, service tiers, and the exact name we use for each.","h":"Fill the brain, each of these unlocks a capability it does not have yet"},{"f":104,"x":"Q-47 Custom LLM as a person ask: If Custom LLM walked into a room, who is it? How does it dress, how does it speak, what does it never do? why: The voice file currently says \"modern, streamlined, engineered with precision\", accurate but abstract. A person is something a writer can actually imitate, and something the brain can check copy against. Q-48 How should a technician feel after dealing with us? ask: One or two feelings. Not what they think, what they feel. why: Feeling drives retention more than features do, and this is a retention year. It becomes the test every letter, call script, and page has to pass. Q-49 Words you would never allow ask: Words, phrases, or claims that would make you wince if you saw them under our name.","h":"For the founder, voice, feeling and proof"},{"f":105,"x":"Welcome. This library is the company's shared brain: one governed place that holds what's true, how we sound, and what's approved, wired so the AI you talk to reads it before it writes a single word. What that means in practice: Ask anything. Answers come back sourced from the library, never from guesswork. If the library doesn't know, you get \"unknown\" and the question gets filed, which is a feature, not a failure. Ask for work. A letter, a page, a deck, it drafts from approved templates in our voice, saves to your Work Zone, and routes to approval. Trust the gates. Everything is scanned before handover, and nothing ships to the outside world until a human promotes it.","h":"Team Cover Page"},{"f":105,"x":"Zone | What lives there 00 Start Here | This page, the project plan, the master guide. 01 The Brain | The machinery: constitution, rules, facts, skills, templates. 02 Brand | The Brand OS and the explored directions. 03 Knowledge and Sources | Source documents, transcripts, ingested research. 04 Plans | The strategic plans: launch, migration, parity. 05 Work Zone | Your space. Eight personal zones, five folders each. How to ask well: Say what the deliverable is for and who will read it. Paste anything relevant, the brain files sources properly. If the answer needs a number, expect a source with it. No source, no number. Your work lands in 05 Work Zone/<your name>/. Moving a file to Send for Approval is the whole workflow, the folder position is the status.","h":"The six zones"},{"f":106,"x":"Merged with the GTM v4.1 master calendar + the comm-plan media windows (2026-08-08). Done: ☑ 2026-08-05, Brain assembled · Brand system built (4 directions) · Direction 1 shared with Avery* ☑ 2026-08-06, Avery* review: Evergreen preferred; orange + copper revisions made same day; Apex-family domains purchased; migration scoped (1,200 files / 15 batches) ☑ 2026-08-07, The 12 Custom LLM color names locked into the Brand OS · v0.6 leadership cut delivered (dual-view) · full-pass audit ☑ 2026-08-08, THE KNOWLEDGE DUMP: GTM v4.1 + Integration brief + both Comm Plans ingested; brain rebuilt on the one-story rebrand story, written retention terms, launch playbook layer, drafted-copy library, media/PR plan"},{"f":106,"x":"☑ Week of Jul 27 (GTM line, passed), naming + messaging aligned in the integration session (\"a Custom LLM company\" endorser pending Q-20 confirm) Now → Aug 15 (the pre-launch build window, per GTM + comm plans): ☐ Leadership confirms Evergreen + accent (Q-18) · Dana* signs vision/mission (Q-17) · endorser line confirmed (Q-20) · pricing term reconciled (Q-21) ☐ PR agency selected + engaged (shortlist filed) · podcast pre-booking + long-lead print pitching (window is NOW per the external plan) ☐ CEO video produced (external + internal cuts) · media kit assembled · apexinstruments.example splash/landing staged · the CRM sequences + Priority Care logic built and QA'd"},{"f":106,"x":"☐ Every the field network account mapped to an interim owner · top 20% identified · first collateral gold standards with Jordan* review Aug 18 to 24: ☐ All letters/emails/talk tracks approved (endorser swap per Q-20) · manager FAQ + huddle packet final · vendor + site-briefing packs done · launch website decision resolved (Q-22) and built accordingly Aug 25 to 31 (the gates): ☐ Aug 25 (T-7): executive sign-off, talking points, automation logic, crisis matrices to Basecamp; per-site consolidation plans final ☐ Aug 28 (T-4): held until launch manager briefings, both companies; managers ready to run Day-1 huddles ☐ Aug 31: go/no-go with deal counsel; systems + frontline readiness check"},{"f":106,"x":"☐ 7:00 leadership huddle → 7:30 all-staff → 8:00 site briefings + press release → 8:30 web/video live → 9:00 customer emails + calls → 10:00 vendor letters → midday social + forum monitoring Sept 1 to 15, stabilization: ☐ Sep 1 to 5: rolling AM welcome calls, GSO exec calls, field sales mobilized, Priority Care worked real-time ☐ Sep 1 to 14: top-20% program (video boxes, CEO access, lunch-and-learns) ☐ Sep 2 to 15: vendor procurement reviews; scanner + shipping pipelines confirmed open October + Q4, phase 2: ☐ Win-back campaign launches (30 to 90 days post-Day-1, one shot) · decliner watch live ☐ Editorial blitz: Sept LinkedIn ads → Oct podcast releases → Nov/Dec print features + covers","h":"Sept 1, Day 1 (hour-by-hour in Facts/launch/day-1-playbook.md)"},{"f":106,"x":"☐ 2027: the live circuit (the industry conference circuit) · masterbrand transition work toward standalone Custom LLM (~24-month horizon) ☐ 2028: the Apex Summit capstone Parallel (brain-side, unchanged): ☐ Apex collateral rebrand, chunked (Trellis pilot first) · Hub + team rollout · the field network knowledge in phase 2 · sub-brands (Q-4)","h":"2027 to 2028"},{"f":107,"x":"This is the single source for all messaging until the masterbrand decision. Quote, don't paraphrase. Positioning statement (verbatim): \"Apex Instruments is a devices contract manufacturer delivering artistry at scale. Together with the field network, we combine a national footprint, a mature commercial engine, and a deep investment in practice education with the most advanced manufacturing model in the industry, so every case is consistent, backed by redundancy, on time, and supported by a person who knows your practice.\""},{"f":107,"x":"\"We are the national devices lab network that runs like a manufacturer: one engineered, quality-controlled process, delivered through a coast-to-coast footprint, with a real team on every account.\" Three message pillars: Best of both worlds, national scale, redundancy, and commercial reach, paired with local, high-touch accountability. Quality lives in the process, engineered, repeatable; senior-technician quality on every case, not dependent on any one artisan. A partner, not a vendor, dedicated account management, practice education, and for GSOs, multi-location tracking and standardized metrics.","h":"Elevator (verbatim)"},{"f":107,"x":"Digitization of Practices, on-site scanners, 3D design, benchside manufacturing, scan QC, AI-driven decisions All-Encompassing Customer Experience, dedicated AMs, tailored data portals, boots-on-the-ground service New Suite of Products, expanded refit options, advanced materials and bundles Improved Clinical Efficiency & Client Care, same-day bench units, housings-in-a-day, reduced bench time Better Practice Monetization, streamlined workflows, better insurance-billing integration, a more profitable practice","h":"The Five Pillars of Custom LLM (external value proposition, brand these, don't just list them)"},{"f":107,"x":"Doctor-facing (continuity first): \"The local service and relationships you count on are not changing. You now have more resources, more redundancy, and more support behind you than ever.\" Zero disruption, only upside. Corporate / trade / GSO: \"A national footprint and a mature commercial engine, now paired with an engineered manufacturing model, so quality lives in the process and scales without friction.\" The synergy story: Internally the math is \"1+1=5.\" The frame is always a one-story rebrand, each company brings what the other lacks. Never \"rescued,\" never \"fixed,\" never us-vs-them. The long-game pitch (Summitline/Trueline/the-unit) lives in Facts/about-company/company-overview.md.","h":"The two-layer message (sequenced by audience, the answer to \"which story leads\")"},{"f":107,"x":"The clinician is the hero; every external story is told from the practice's side of the bench, revenue, hours, client care. Guardrail: lead with outcomes, never workforce mechanics, in technician-facing copy.","h":"The hero rule"},{"f":108,"x":"One post = one keyword (from Facts/seo-research/). Answer up front, then depth. H2s as questions where natural. Internal links per the site's link map. 350-word minimum for local pages; no filler to hit counts."},{"f":109,"x":"Outreach < 150 words. Subject: specific benefit or question, ≤ 6 words, no clickbait. One ask per email. Inkstone from the Hub generator only. Sequences: value → context → direct ask; never three asks in a row."},{"f":110,"x":"Hook line first (it's all most people see). 150 to 250 words. Teach, don't sell, 4-in-5 posts pure value. Line breaks between thoughts. CTA only in direct-offer posts. Cadence target: {{linkedin_cadence}}."},{"f":111,"x":"Section order per the Brand OS proposal treatment. Client's name and property/context correct everywhere. Final fee stays {{OWNER: FINAL FEE}}, never auto-filled. Pre-send checklist in the skill."},{"f":112,"x":"One H1 per page. Per-page single action. Title ≤ 60 chars, meta ≤ 155. Draft gates (noindex + banner) stay on until {{owner_first_name}}'s go-live word."},{"f":113,"x":"Empty on purpose. Seeds from the FIRST approved Custom LLM pieces (each promotion to Approved nominates its best as the channel example). Until then, the Brand OS treatment examples are the bar."},{"f":114,"x":"UNKNOWN over guess, never invent facts, numbers, names, quotes, or testimonials. Approval gate, nothing external without the chain (working: Jordan* → Avery*; exec gate Dana*; final chain Q-5). Money/legal/commitments: Avery* + Dana*. Approved is immutable, copy out, revise, re-promote; superseded → dated Archive. Nothing deleted. Authority files, pricing only from Facts/about-company/pricing.md; external claims only from claims-and-credentials.md. Post-change sync (the closing ritual), a change is done when: changelog entry written · AGENTS.md regenerated if CLAUDE.md changed · companion docs updated · stale-reference sweep run.","h":"Universal"},{"f":114,"x":"Brand tokens only, no raw hex, no off-system fonts; Brand/custom-llm/brand-sheet.md is the design authority. Every branded output carries the PROPOSED flag until leadership locks the brand. Privacy floor, no PHI ever; no credentials in the repo. Custom LLM rules: THE RULES ABOVE ALL, the project internal only until launch. This overrides every convenience. Merger-of-strengths voice (superseded 2026-08-08; was holding-company), the official story: \"a rebrand in the truest sense; one plus one equals three.\" \"Merger\" is APPROVED language. Banned framings: \"takeover,\" rescue framing in external copy, \"Apex renamed,\" \"formerly Apex Instruments,\" \"APEXINST\" as a name.","h":"Universal"},{"f":114,"x":"the field network numbers never go external (superseded 2026-08-08; was research-estimates), internal figures come from the GTM, labeled \"per GTM, pre-verification\" (~$180M customer revenue · ~30,000 accounts · 40+ sites). The old research range is history. Externally: only the approved press language. Retention promises are the WRITTEN Day-1 terms (superseded 2026-08-08; the 18-month verbal figure is conflict Q-21, NEVER quote it), 6-month rate lock · Continuity Guarantee · $500 equipment credit · 12-month CE, quoted exactly from Facts/about-company/pricing.md or not at all. ™ after \"Custom LLM\" only, never after a longer phrase.","h":"Universal"},{"f":114,"x":"Draft (Work Zone/) → review (Work Zone/review-queue/) → Avery* approves (working) → copy to Approved/<type>/ + changelog + archive the old version.","h":"Approval lifecycle"},{"f":115,"x":"The name: \"Custom LLM\" in prose (provisional pending Q-2); CUSTOM LLM all-caps only as the drawn wordmark; ™ directly after \"Custom LLM,\" never after a longer phrase. Referring to the operating companies: Apex Instruments and the field network by their full names; both continue under their own names ~12 months post-announcement. Dates: absolute dates in documents (2026-09-01, or \"September 1, 2026\" in prose), never \"next month.\" Phone: (xxx) xxx-xxxx. Dashes: no em or en dashes in any deliverable. Use periods, commas, or restructure. Emoji: none in external materials. Exclamation points: avoid; the voice is engineered calm. Files: .md canonical for the AI; rendered formats for humans."},{"f":116,"x":"Thinking order on every build: confirm the ask (prompt-enhancer already ran) → the rules gate (is the requester and destination inside the project?) → route via CLAUDE.md §5 → open the matching output-type directions → open the matching skill and its reference → pull facts per trust order → build by adapting the reference, never from scratch → run pre-delivery-scan → save to Work Zone → offer the wrap-up. Confirm-first: if deliverable, audience, or facts are ambiguous, ask 2 to 3 short multiple-choice questions built only from real options in Skills/prompt-enhancer/reference/brain-inventory.md. Then wait. Facts discipline: UNKNOWN over guess. Gaps become {{...}} slots and Q questions. the field network numbers labeled \"per GTM, pre-verification\"; none go external."},{"f":116,"x":"Wrap-up: confirm where you saved it in one line; offer to log a reusable prompt. Portable system prompt (paste into any external AI tool, the project members only · superseded 2026-08-08 to the rebrand platform): t; You are working for Custom LLM (internal-only pre-launch parent brand over the Apex Instruments + the field network combination, publicly a MERGER OF STRENGTHS: \"a rebrand in the truest sense; one plus one equals three\"; never \"Apex renamed,\" never a takeover or rescue). Voice: modern, streamlined, engineered with precision. Never say: takeover, supercharge, 10x, world-class, game-changing, APEXINST. No em or en dashes."},{"f":116,"x":"Never invent facts, prices, or testimonials; mark unknowns UNKNOWN. the field network figures are internal-only, labeled \"per GTM, pre-verification,\" and never appear in anything external. Retention promises are the WRITTEN Day-1 terms quoted exactly: 6-month rate lock, Continuity Guarantee, $500 equipment credit, 12-month CE (no other pricing figure exists, an 18-month verbal figure is a flagged conflict, never quote it). The name takes ™ directly after \"Custom LLM.\" Nothing you produce may be shared outside the project circle until launch."},{"f":117,"x":"Deliverables: [Asset], YYYY-MM-DD, vN · system docs: kebab-case.md Position = status: a file's folder is its approval state; promotion moves a copy, never the original Archive folders: YYYY-MM-DD-what-was-replaced/ · audits: audit-YYYY-MM-DD.md Meeting notes: Facts/meetings/<year>/<month>/YYYY-MM-DD-topic.md"},{"f":118,"x":"Live now (the launch three): directions-launch-website.md · directions-announcement-kit.md · directions-welcome-retention-kit.md. Per-medium directions (email, presentations, print, web, documents, social) get ONE file each here at brand-lock, written from the Brand OS treatments, not before. A playbook only exists once it can be followed."},{"f":119,"x":"Pieces: designed press-release support doc · og/social announcement card · LinkedIn announcement set · internal announcement brief. The PR agency owns final press copy (interviews in progress), this brain SUPPORTS with fact sheets and design, never freelances press statements. Facts: claims file only; the field network estimates NEVER appear; deal terms NEVER appear. Leadership roster is ANSWERED (Q-6): Mercado* CEO · Kovach President · Whitfield CGO · Ridgway the field network CEO · Bellamy Transition Leader, from Facts/people-and-org/team.md; bios/headshots remain {{slots}}. Endorser line is a slot until Q-20. Voice: compliance-clear for fact sheets; executive-brief for the narrative. The intrigue principle: say less, mean more."},{"f":119,"x":"Brand: Tier H glass mark on Midnight for the hero card; ™ rule; PROPOSED flag. Timing gate: NOTHING from this kit exists outside the Work Zone until Avery* + Dana* clear it. pre-delivery-scan → Work Zone/review-queue/announcement/."},{"f":120,"x":"Scope (locked by the Aug-4 call): ONE informational page + leadership page + contact page. Deliberately tiny. Intake: which page? what changed since last draft? confirm-first if unclear. Facts: company-overview.md only (vision/mission verbatim). Leadership page: roster ANSWERED (Q-6), use the five names/titles from Facts/people-and-org/team.md; bios + headshots stay {{slots}}. Contact page: {{contact_block}} slots (Q-16/Q-1; the GTM drafts use (800) 555-0100 and sales@apexinstruments.example, confirm before publishing). 2b. ⚠️ SCOPE QUESTION (Q-22): the GTM's Day-1 web is an apexinstruments.example splash/landing; this standalone 3-page Custom LLM site likely becomes the 6-to-24-month masterbrand phase. Draft copy freely; nothing builds for deploy until the ruling."},{"f":120,"x":"Brand: tokens from Brand/custom-llm/brand-sheet.md; Tier H marks in heroes, the Current as the divider motif; dark-marketing surfaces; PROPOSED flag in the footer. Gates: draft gates ALWAYS (noindex + banner + blocking robots.txt); hosting per Q-16; nothing deploys anywhere public pre-launch. pre-delivery-scan → save to Work Zone/review-queue/website/."},{"f":121,"x":"Ported 2026-08-08 from Apex's proven directions-partner-collateral-build.md (the BrightPath-derived recipe that built every Apex partner kit). This IS the migration chunk recipe: per the reuse rule, every deliverable below gets PULLED from the partner's existing Apex build and re-skinned, never rebuilt from scratch. Custom LLM brand values are PROPOSED until brand-lock; during the dual-brand window Avery*'s scope ruling decides which brand each chunk ships in. Brand tokens (the swap table per brand): Role | Apex value | Custom LLM Evergreen (PROPOSED) Primary dark / page bg / headers | Navy #052030 | Midnight Green #00272C Primary accent / banners / links / icons | Harbor Blue #1882C7 | Harbor #245D63"},{"f":121,"x":"Accent highlights / hover / border | Light Blue #4ABEEE | Tide #245D63 (Sea Glass #A8B6B7 on dark) Warm accent / dividers / callouts | Gold #B3A369 | Copper #A8B6B7 (deep #245D63 for text on light) Content areas / text on dark | White #ffffff | Paper White #FFFFFF (cards #FFFFFF) The spark (CTAs, dark surfaces only) | Electric Orange #FF6B1C Microsite fonts | Montserrat + Lora | Archivo + IBM Plex Sans (Q-13) PDF guide fonts | DM Sans + Inter | IBM Plex Sans + IBM Plex Mono accents (Q-13) Authority: Brand/custom-llm/brand-sheet.md, never hardcode a hex that has a token; obey the surface law."},{"f":121,"x":"Logos needed per partner: our wordmark (color + all-white) + icon mark (Custom LLM set PENDING Josie*; interim marks in Brand/custom-llm/logo-mockups/) · partner logo color (header pills) · partner logo white/transparent (footer pills). Endorser lockup per Q-20. The print-PDF shell (all print deliverables share it): ``` .page (8.5in x 11in, dark-ground background) .white-area (inset 0.3in top/left/right, 1in from bottom, white bg, 5px accent border) .header-pill (centered top, overlays border, both logos + warm divider) .footer-pill (glass, 0.6in tall, 0.3in from bottom, white logos + contact info)"},{"f":121,"x":"Critical print CSS: @page { size: 8.5in 11in; margin: 0 } · print-color-adjust: exact · .page { page-break-after: always; overflow: hidden } · footer pill needs !important bg overrides + no backdrop-filter in print. Footer contact items: phone · website · partner-specific email (visible text, not just links, these get printed). The deliverable set (build in this order; Apex reference file named per piece)"},{"f":121,"x":"Duplicate the partner's Apex reference file → swap logos (header, hero, footer) → find/replace partner name → apply the token swap table → update team members (per directions-support-team-contact-update.md discipline) → update contact info → update resource links → adapt FAQ → print-preview every PDF page (.white-area has overflow:hidden and clips silently, tighten margins/line-height/image heights to fit). File naming: [Partner]-[DocumentType].html (e.g. Trellis-Microsite.html, Trellis-Guide-FRX-Whats-Needed.html). Hosted PDF naming: [Partner]-[Document-Title]-<endorser per Q-20>[-Year].pdf, hosting platform + upload flow pending Q-16.","h":"Build steps (every deliverable)"},{"f":121,"x":"Print overflow clips silently (always print-preview) · \"APEXINST\" only ever inside URLs/emails, never visible text; same discipline for Custom LLM's legal entity (Q-1) · Critical-bar uses brand gradient + warm icon, never amber/brown defaults · section images max-height 120px conservative · portal URL as VISIBLE text (docs get printed; portal domain per Q-16/22) · single-file HTML per deliverable (no external CSS; Google Fonts + hosted images only) · fonts via @import in the style block. Workflow summary: Gather: partner logos (color+white), team headshots (live-hosted, 200-checked), contacts, QR codes, clinical content, product list, pricing (authority file only), TAT. Build in the order above (welcome PDF establishes team + about content; microsite last).","h":"Common pitfalls (all learned the hard way at Apex)"},{"f":122,"x":"Ported 2026-08-08 from Apex's proven procedure (Caravelle, ClearForm ART, UnionSix, Private Practice builds: same start every time = same result every time). Use when swapping or updating a person in a partner's \"Dedicated Support Team\" across that partner's collateral, including headshot-only swaps and contact-detail edits. This is MAINTENANCE of existing deliverables; new builds use directions-partner-collateral-build.md. 0. Collect these inputs first (ask if missing, never invent)"},{"f":122,"x":"Full name (watch ALL-CAPS variants in flyers) · title (keep existing unless told) · email (goes in mailto: href AND visible text) · phone (display format (xxx) xxx-xxxx, consistent per deliverable; tel:+1<digits> digits-only) · headshot URL (live-hosted, must 200) · Click-to-Connect QR URL · booking link if the old card had one. Also confirm: which partner folder, and any layout request (who sits left vs right). Update Hub/people-data.json in the same pass (stable-ID keyed). 1. Discover every instance (never assume it's one card): A contact appears beyond the team card: FAQ/body text, letter signatures, BUILD_NOTES.md tables, asset-list comments. ```bash cd \"<partner folder>\""},{"f":122,"x":"grep -rinE \"<OldFirst>|<OldLast>|<oldemailuser>|<old-phone-digits>|<old-headshot-filename>|<old-qr-slug>\" --include=\"*.html\" . grep -rinE \"<OldFirst>|<oldemailuser>\" --include=\"*.md\" . ``` Classify each hit: live deliverable (edit) · inside Archive/ (leave alone, dated history is never edited) · backup/pre-split duplicate (ask: update, archive, or leave) · byte-identical duplicates (diff -q; update ALL copies, render ONE canonical PDF). 2. Verify new image URLs are live BEFORE rendering: curl -s -o /dev/null -w \"%{http_code}\\n\" -I \"<new headshot URL>\" # expect 200, a broken image bakes into the PDF"},{"f":122,"x":"Microsite = HTML edit only, never a PDF. Every other HTML deliverable = edit HTML + render PDF + archive old PDF. Replace all facets: headshot src AND alt, name (incl. ALL-CAPS), title, email (mailto: + text), phone (tel: + display), connect href, and every body/FAQ/signature/notes mention. A partner can have more than one microsite file, update the contact in each. Layout requests: move the entire card block in one edit (read the full block first) so indentation and SVGs stay intact. Never fabricate links. If the old card had a personal link you can't carry over, ask: remove the button, point it at the QR, or get the real link. Client-facing copy: no em/en dashes (existing hosted filenames/URLs stay as-is).","h":"3. Edit the HTML, the golden rules"},{"f":122,"x":"Work Zone edits are free; Approved/ follows the archive-old-versions workflow + _card.md update, with the requester as directing approver. 4. Render the PDF (non-microsite HTML only): HTML=\"/abs/path/to/Deliverable.html\" URL=$(python3 -c \"import pathlib,sys; print(pathlib.Path(sys.argv[1]).as_uri())\" \"$HTML\") \"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\" --headless=new --disable-gpu \\ --no-pdf-header-footer --run-all-compositor-stages-before-draw \\ --virtual-time-budget=30000 --print-to-pdf=\"/tmp/out.pdf\" \"$URL\" python3 -c \"import re;d=open('/tmp/out.pdf','rb').read();print('pages:',len(re.findall(rb'/Type\\s*/Page[^s]',d)))\"","h":"3. Edit the HTML, the golden rules"},{"f":122,"x":"_card.md (file list + dated change note) · BUILD_NOTES.md contacts table · headshot URL lines · Hub/people-data.json · changelog. 8. After upload → fix the microsite link: Expect a changed URL (hosts rename duplicates, e.g. -1 suffixes), use exactly what the requester sends. Update the download link in EVERY microsite file that carries it, then: curl -s -o /dev/null -w \"%{http_code}\\n\" -I \"<new URL>\" # expect 200 grep -c \"<old-filename>\" \"<microsite.html>\" # expect 0 Quick checklist: [ ] Inputs collected; nothing invented [ ] grep sweep; live vs archive vs duplicates classified [ ] New image URLs 200 [ ] All live HTML edited, every facet, every file; layout moves block-whole; no fabricated links [ ] PDFs rendered; page counts match [ ] Old PDFs archived dated; new placed canonical","h":"7. Update the brain's bookkeeping"},{"f":123,"x":"Ported 2026-08-08 from Apex's directions-team-hub-wp-update.md (the flow that published Apex's four hub pages on 2026-07-01). Custom LLM's hub is NOT yet deployed (gated on brand-lock to build, announcement/Q-16 to deploy), this file preserves the proven update pattern so Hub v1 launches with its operating procedure already written. The pattern (how hub pages work, host-agnostic): Every live team page is a hosted page containing exactly one code element holding the entire self-contained HTML file. The canonical source is ALWAYS the .html file in this library; the hosted page is just the rendered copy. All pages sit behind one team password."},{"f":123,"x":"Live page | Host page ID | Canonical source in the library /team-site/ (homepage) | {{id}} | Derived from 00 Start Here/CUSTOM LLM-MASTER-GUIDE.html (the hub build splits its views into pages) /prompt-library/ | {{id}} | The guide's Prompt Library view (extracted at build) /brand-assets-gallery/ | {{id}} | The guide's Asset Gallery view (extracted at build) /asset-directory/ | {{id}} | 01 The Brain/Log/asset-directory.html /meet-the-team/ | {{id}} | Built on 01 The Brain/Hub/people-data.json (single data source: directory + org chart) /operating-hub/ | {{id}} | 01 The Brain/Hub/operating-guide.html Host + domain per Q-16/Q-22; page IDs recorded here the day each page publishes.","h":"The Custom LLM page table (fill at Hub v1 launch)"},{"f":123,"x":"Edit the canonical .html in the library first. Never edit only the hosted copy; the library file is the source of truth and the next person will overwrite the host from it. Links caveat: canonical files may carry library-relative links (they resolve locally/SharePoint). In the hosted copy every href that does not start with http must become an absolute URL (live page slugs or full SharePoint links). Check them all on paste. Open the page in the host's builder (Apex's Bricks flow: ?page_id=<ID>&bricks=run, logged into admin). Open the code element, replace the full contents with the updated canonical file. Sign/validate the code if the host requires it (Bricks: \"Sign code,\" keep Execute + Render-without-wrapper ON). Save, reload the live URL, confirm it renders.","h":"The update flow (always in this order)"},{"f":123,"x":"Post-change sync: changelog entry + twin-sync + asset-directory note per Rules/guardrails.md. The fast way: Point an AI with browser access at this file and say which page to update; steps 3 to 6 are exactly how Apex's four hub pages were first published. The rules gate: NOTHING publishes anywhere before launch authorization, password or not.","h":"The update flow (always in this order)"},{"f":124,"x":"Pieces: welcome letter · Sendoso gift insert card · account-manager continuity one-pager · retention FAQ (draft lives in Work Zone/review-queue/retention/; canonical home Facts/faqs/client-faq.md after approval). Audience: private-practice technician (the field network base). Tone: reassuring-advisor. Their fears: price hikes, TAT slips, losing their rep. Thesis: \"Local Lab Scaled.\" The ONLY promises allowed, quoted exactly from pricing.md: the WRITTEN Day-1 terms, 6-month rate lock · 6-month Continuity Guarantee · $500 digital-integration credit · 12 months complimentary CE · FedEx 2nd Day standard. (The 18-month verbal figure is a filed conflict, Q-21, never quote it.) AM continuity described per Facts/launch/retention-engine.md."},{"f":124,"x":"Never mention: Grandview Labs, closures (site-specific comms run through the consolidation protocol in the day-1 playbook), any the field network number, workforce mechanics. The GTM's drafted letter/emails in Templates/launch-copy/ are the gold standards, instantiate, don't freelance. Endorser line is a slot until Q-20 confirms. Brand: warm end of the system: Paper White surfaces, Harbor accents, Copper warmth, chrome-on-light lockup; print-true dimensions (letter + insert card sizes from the Brand OS treatments). pre-delivery-scan → Work Zone/review-queue/retention/."},{"f":125,"x":"They worry about roles, change, and information gaps. The answer: early, honest, frequent communication from leaders, what changes, what doesn't, when. \"Help is here\" applies HERE and only here. Channel: CEO email + video, manager huddles with the approved FAQ, intranet. Golden rule for managers: \"I will find out\" is always okay; speculation never is."},{"f":126,"x":"This is where the operating-model story earns its keep: national footprint + mature commercial engine + engineered manufacturing = the core thesis, \"Scale without Friction.\" 1:1 executive relationships (SAE-owned, C-suite + procurement called within 48 hours of Day 1), live demos of the enterprise dashboards (naming open, Q-23), QBRs, preserved multi-location case tracking + shipping logistics + standardized remake-rate metrics. Private letters from leadership to GSO leaders (Roman/Emmett/Dana hold the relationships); Vern Castellano letter at ~T-10. Tone: executive-brief."},{"f":127,"x":"Primarily private practices; decentralized communication; they worry about process, quality, communication, and pricing changes. Answer each fear specifically: scanner/routing already mapped · quality protected by microscope QC · a named Account Manager as single point of contact · pricing locked six months (the written terms in pricing.md). Core messaging thesis for private practices (comm plan): \"Local Lab Scaled.\" Day 1 to 5: rolling live AM welcome calls + physical transition kits + the CRM welcome track (Continuity Guarantee, locked pricing, $500 integration credit). Zero-attrition is the goal: Day 1 must feel like only upside. Live objection scripts: Templates/launch-copy/crisis-call-scripts.md script 2. Tone: reassuring-advisor; the drafted letters/emails in Templates/launch-copy are the gold standards."},{"f":128,"x":"Process-driven accounts; apart from Delta Craft, no boutique cases, \"getting lost in the shuffle\" is not their fear. They simply need: nothing changes. Core messaging thesis (comm plan): \"More resources, same elite touch.\" Message: same quality, consistency, and service, now with more resources behind you than ever. From THEIR Account Manager, never a generic address; Day 1 pairs the AM email with a Doctor Portal splash banner carrying a direct text/chat link to the AM. If a dilution fear IS voiced live, the scripted response is Templates/launch-copy/crisis-call-scripts.md script 1. Tone: reassuring-advisor."},{"f":129,"x":"\"artistry at scale\" · \"a one-story rebrand\" · \"best of both worlds\" · \"quality lives in the process\" · \"a partner, not a vendor\" · \"one plus one equals three\" (external-safe) · \"engineered for scale\" · \"we intend to earn your confidence one case at a time\" · \"nothing you rely on changes\" · \"more resources, more redundancy, and more support behind you than ever\" · \"senior-technician quality, repeatably\" · \"built ahead of demand, with redundancy at every step\" · \"the local service and relationships you count on are not changing\" · CEO named in full in client copy: Roman Elias Mercado* · verbatim assets: positioning statement + elevator (brand-foundation) · vision + mission (company-overview, pending Q-17 sign-off)"},{"f":130,"x":"\"Help is here\" is INTERNAL-ONLY. Internally we overwhelm the team with reassurance. Externally there are $180M of customers who don't think the field network needs help, external copy NEVER frames the rebrand as a rescue. Banned in ALL copy: supercharge · 10x · game-changing · revolutionary · world-class · seamless(ly) as filler · unleash · \"solutions\" as filler · fake urgency · exclamation enthusiasm · em/en dashes in client copy · \"APEXINST\" as a name · the full legal entity name in customer-facing copy","h":"The message wall (the most important rule in this file)"},{"f":130,"x":"\"help is here\" / rescued / fixed / saved · us-vs-them framing · \"takeover\" · \"just a lab\" · \"operational efficiency\" (technician-facing) · workforce mechanics (technician-facing) · \"better contract manufacturer\" as the story to private practice · any the field network figure as fact · deal terms/valuation NO LONGER BANNED (superseded 2026-08-08): \"rebrand\", the official frame IS \"a rebrand in the truest sense / a one-story rebrand.\" The old holding-company rule (\"never rebrand\") is retired; see decisions log.","h":"Banned in EXTERNAL copy specifically"},{"f":131,"x":"Custom LLM sounds: modern, streamlined, engineered with precision (the sprint brief), carried by the story of legendary craft meeting engineered scale. Principles: Engineered calm. Confidence without hype; precision without jargon. No exclamation points. Craft + infrastructure in the same breath: \"legendary artisanry\" belongs next to \"FDA-registered manufacturing.\" Intrigue over explanation. Nobody has heard of Custom LLM; that is an asset. Say less, mean more. The holding-company posture: measured, institutional, deliberate. Reads like a company that plans in decades. Clinicians and their clients are the point; the network is the means. (Hero audience pending Q-7.)"},{"f":132,"x":"Tone | Use for | Default audience executive-brief (DEFAULT) | Leadership materials, announcement pieces, GSO comms | GSO/leadership + press reassuring-advisor | the field network customers + employees through the transition | private-practice, the field network talent compliance-clear | Anything touching deal facts, legal, PR statements | press plain-teacher | Education/explainer content (post-announcement) | practices peer-professional | Lab-industry / partner communications | industry founder-voice | PENDING, needs Q-9 writing samples (Avery*'s press draft = sample #1) high-energy-promo | NOT used pre-launch; revisit for campaigns later One tone per piece. Never blend."},{"f":133,"x":"For regulatory/deadline content. Four-beat pattern per point: the requirement → plain English → who it applies to → the path. Cite the rule's real name once, then speak human. Flags stay in: {{regulatory_flag_rule}}."},{"f":134,"x":"For decision-makers. Business consequence first, numbers early, recommendation explicit. One page mentality. No throat-clearing."},{"f":135,"x":"{{founder_voice_profile}}"},{"f":136,"x":"For launches and offers. Short. Punchy. Concrete offer, real deadline, one CTA. Energy comes from specificity and rhythm, never from hype words, the banned list still applies fully."},{"f":137,"x":"For fellow professionals (referral channels). Skip the 101, lead with process, timelines, what working together looks like. Bullets over prose. Respect their time and their expertise; the pitch is competence."},{"f":138,"x":"For blogs, explainers, FAQs. One concept taught completely beats three introduced. Concrete before abstract; example before definition. Assume smart reader, zero jargon. End with what to do with the knowledge."},{"f":139,"x":"For worried non-experts holding responsibility. Acknowledge before prescribing. Options, not decrees. Short sentences when stakes feel high. Never alarm to motivate; name the deadline and the path. Reader leaves feeling \"I can handle this, and I know the next step.\""},{"f":140,"x":"Prose-rule skills cause drift. A real skill hands the AI copyable parts + a reference/ gold standard to match. AIs diverge when asked to design and converge when asked to adapt, so Step 0 of every generation skill is: OPEN THE REFERENCE FILE and copy its skeleton. Assembly phase 5 builds each enabled skill's reference from the client's Brand OS treatment; until a reference exists, the skill refuses to produce."},{"f":141,"x":"Skill | Module | Proven source (adapt from) new-blog-post · add-location-page | Website/SEO | HOI brain Skills/ competitor-refresh | Intel | HOI brain Skills/competitor-refresh/ (11-query method) partner-microsite · price-sheet · welcome-flyer · whats-needed-guide · executive-summary · intake-forms | Partner kits | Apex brain 02 Toolkit/skills/generation/ onboarding-sop · talking-points | Sales | Apex briefing 10 + HOI Templates/sales/"},{"f":142,"x":"name: brand-deck description: Branded deck from the Brand OS deck theme Step 0: open reference/. Slides come from the treatment's layout catalog (title / content / data / closing), never invent a layout. Charts native, tokens only. One idea per slide; presenter notes carry the words. Audience-specific overlays live as separate skills when a client needs them."},{"f":143,"x":"name: brand-email description: Branded emails, intro, follow-up, delivery, newsletter, sequence Step 0: open reference/ and copy the gold standard. Then: Pick the pattern from Templates/email/ (intro / follow-up / delivery / newsletter / sequence) and the tone (default {{default_tone}}). Outreach < 150 words, one ask. Subject per Rules/channel-styles/email.md. HTML emails use the Brand OS email chrome (tokens only, Outlook-safe patterns). Sequences are plain text, never HTML. Inkstone comes from the Hub generator, never hand-typed. Facts/pricing per authority files → pre-delivery-scan → save to the Work Zone."},{"f":144,"x":"name: brand-leave-behind description: Print leave-behind / flyer, 2 pages max Step 0: open reference/. 2 pages max, print-clean at true dimensions, margins per the treatment. Built to survive being handed to someone who wasn't in the meeting: standalone context, one next step, contact block from reference-index."},{"f":145,"x":"name: brand-one-pager description: Company or topic one-pager, print-true Step 0: open reference/. Adapt the Brand OS one-pager treatment. ONE PAGE is a hard rule: cut copy, never shrink type below the treatment's minimums. Sections: hook → what/for-whom → proof (claims file only) → one CTA. Two-pager variant only if the treatment defines it."},{"f":146,"x":"name: brand-proposal description: Client-specific proposal from the Brand OS proposal treatment Step 0: open reference/. Then: intake the specifics (client name, scope, context), confirm-first if missing. Adapt cover, interior grid, pricing table from the treatment. The final fee stays {{OWNER: FINAL FEE}}, never auto-filled (hard rule). Pre-send checklist: names correct everywhere · scope matches the ask · claims sourced · pricing placeholder intact → pre-delivery-scan."},{"f":147,"x":"name: brand-social description: Social graphics + captions, 8 platform formats Step 0: open reference/. Formats per the Brand OS social frames (IG post/square/story, FB, LI post/story, YT thumb, universal story) at platform-native sizes. Caption per Rules/channel-styles/linkedin.md (or platform file). Teach-don't-sell ratio applies. Emoji per house-style policy."},{"f":148,"x":"name: custom-llm-deck description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":149,"x":"name: custom-llm-docket-lab-slip description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":150,"x":"name: custom-llm-email description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":151,"x":"name: custom-llm-executive-summary description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":152,"x":"name: custom-llm-landing-page description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":153,"x":"name: custom-llm-microsite description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":154,"x":"name: custom-llm-price-sheet description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":155,"x":"name: custom-llm-print-one-pager description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":156,"x":"name: custom-llm-quick-start-guide description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":157,"x":"name: custom-llm-social description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":158,"x":"name: custom-llm-welcome-flyer description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":159,"x":"name: custom-llm-whats-needed-guide description: PENDING brand-lock. Adapted from the proven Apex build skill; activates when its reference gold standard is built from the approved Brand OS. Refuses to produce until reference/ holds this skill's gold standard (built with Jordan* post-brand-lock, per the reference-first doctrine in Skills/_SKILL-PATTERN.md). The proven Apex counterpart is the working model: same anatomy, Custom LLM brand rules."},{"f":160,"x":"name: deploy-preview description: Gate-verified preview bundle when push-to-deploy isn't available Rebuild → QA clean → verify every draft gate (noindex meta, draft banner, blocking robots.txt) → zip to Work Zone/review-queue/handoff-zips/. REFUSE to bundle if any gate is missing. Draft gates come off only on the owner's explicit go-live word, all in one pass."},{"f":161,"x":"name: file-owners-answer description: One command turns an owner's answer into filed fact + cleared placeholders + checked-off question + sync When the owner answers a numbered question: Locate the item in QUESTIONS-FOR-{{owner_first_name}}.md. File the fact in the right Facts/ file with dated attribution (\"{{owner_first_name}}, YYYY-MM-DD\"). Sweep the brain for related {{...}} placeholders and fill them. Move the question to Answered (never delete) with where-it-was-filed. Run the post-change sync ritual. Owner answers are facts. Operator answers are decisions, they don't clear owner-gated flags."},{"f":162,"x":"name: folder-cleanup description: The standard Custom LLM library-cleanup process, ported from Apex's proven 2026-07-10 codification. Use whenever an Approved library folder (partner, internal, product-line, location) needs versions reconciled, superseded files archived, and its cards refreshed, so every cleanup, by any person or AI, follows the exact same pattern. Ported de-branded from apex-folder-cleanup (the Apex brain's full-library pass, codified 2026-07-10). Follow it EXACTLY; the value is consistency."},{"f":162,"x":"Survey every file (find, ignore .DS_Store). Never work from memory of the folder. Find the source of truth. For partners it is the microsite (its resource links name the hosted current versions). For internal folders it is the newest dated approved file or the owner's word. Rank versions per deliverable subfolder: Dated filename stems pair sources and exports: X (5.12.26).html pairs with X_5_12_26.pdf. The microsite-linked hosted filename breaks ties. Byte-identical files (md5): archive the worse-named one, note \"duplicate\". Two files identical except an embedded SharePoint mso:Order number are the SAME file; treat as duplicates. Cannot confidently rank: LEAVE BOTH and flag. Never guess.","h":"The pattern (per folder)"},{"f":162,"x":"Archive, never delete: superseded files go to _archive/YYYY-MM-DD-<reason>/ INSIDE the same subfolder. Existing _archive/ folders are historical; never touch their contents. Rewrite the subfolder _card.md: current files, what was archived and why (one line each), one purpose line, cross-link the source of truth. Header comment: `` Partner-root _about.md: the folder guide, team table (verified against 01 The Brain/Facts/people-and-org/team-directory.md), the microsite source-of-truth rule, a folder-to-status table, promotion notes.","h":"The pattern (per folder)"},{"f":162,"x":"Work Zone promotions: when a build folder is promoted, the build wins where files differ (checksum-compare same-named files; diff HTMLs to confirm direction), priors go to _archive/YYYY-MM-DD-superseded-by-build/, identical build copies to .../workzone-build-copies/, and the emptied Work Zone folder is removed. Post-change sync (guardrails): changelog entry, twin regeneration, asset-directory regeneration, price-table check if a sheet changed (Facts/products-services/price-lists/README.md is the flag register), reference sweep for now-stale pointers. A change is not done until the brain agrees with it.","h":"The pattern (per folder)"},{"f":162,"x":"Never edit canonical Approved deliverable HTML content during cleanup (contact-block fixes and similar are separate, explicitly approved changes). Company name: \"Custom LLM\" in prose. Filenames and URLs keep their historical strings; history files keep their historical names. Pricing files: never rank by guess, the price-lists register is the truth; update tables and flags together. PDFs here are often image-based: text extraction is unreliable, rank by stems, dates, md5, and microsite links instead.","h":"Hard rules that always apply"},{"f":162,"x":"Zero loose files at the folder root except _card.md / _about.md. Every changed subfolder's card matches reality. Grep the brain for the archived filenames, fix live pointers (leave dated historical records).","h":"Verification before closing"},{"f":163,"x":"Every spec is the same diamond aimed at a different job. Open Claude Code at the brain root, fill the brackets, paste the spec starting with the word \"workflow.\" After any run that changes files: the closing ritual (changelog entry + twin-sync). The order below is the order they'll earn their keep. 1 · The migration batch sweep, THE flagship: The rebrand migration is 1,200 files across 41 partners in ~15 review batches, the widest job this brain will ever run, and almost every edge in it is fake: no partner's flyer depends on another partner's price sheet. Chain it and it takes months; graph it and each batch finishes at the speed of its slowest single piece. Gated on brand-lock (Q-18) + Josie*'s production logos, stage now, fire then. ▸ GRAPH SPEC ```"},{"f":163,"x":"workflow, Custom LLM rebrand, one partner batch GOAL: rebrand every piece in [partner]'s kit per Rules/output-types/directions-partner-collateral-build.md FAN OUT: one agent per piece, in parallel; each reads the direction file and the brand swap table first (frozen rules inherited) RULE: info, layouts, and images unchanged, logos/colors/fonts/rules swap only; missing assets become {{slots}}, never fabrications VERIFY: per piece, fresh-context checkers in three lenses: the rules (rule #1, message wall, no the field network numbers) brand (tokens only, correct marks, name rule, PROPOSED flag on) fidelity (partner info identical to the Apex original, nothing dropped) ANCHOR: Skills/pre-delivery-scan/scan.mjs on every piece; a piece fails on exit code, not on opinion"},{"f":163,"x":"ON FAIL: flag the piece and keep it OUT of the batch report; never skip silently FAN-IN GUARD: count pieces returned vs pieces in the kit; flag any gap MERGE: one batch report, pass/fail per piece, flags listed, scanner output attached SAVE TO: Work Zone/review-queue/migration/[partner]/ HUMAN GATE: Jordan* reviews the batch report; nothing promotes to Approved without the chain. Pilot = Trellis's complete kit, capped at that one partner. 2 · The review-queue QA fleet, runnable today: Drafts sit in Work Zone/review-queue/ awaiting Avery*. Before any handover, fleet-check them: every draft gets the three lenses at once, each verifier blind to the others and to the drafting session."},{"f":163,"x":"✅ SAVED RUN (2026-08-08). First live run: 18/18 verdicts, zero dead nodes; 4 fails + 3 flags across the 7 drafts (report: Work Zone/review-queue/_qa-report.md). Now a named command, the reusable script lives at .claude/workflows/qa-fleet.js (brain root); in a Claude Code session at the brain root, ask for \"run the qa-fleet workflow\". It self-discovers drafts (new ones are included automatically) and runs the scanner anchor itself. workflow, review-queue QA fleet GOAL: verify every draft in Work Zone/review-queue/ before handover FAN OUT: three fresh-context verifiers per draft, in parallel: the rules, rule #1, message wall, the field network framing, APEXINST absent, CEO name in full, internal story never in external copy facts, every claim traceable to Approved/Facts; pricing ONLY vs"},{"f":163,"x":"The Aug-8 dump proved the pattern: new source docs conflict with filed facts (the 6-month written lock vs the 18-month verbal became Q-21). That conflict was caught by hand. This graph makes the catch systematic. workflow, ingestion cross-check for [new source doc] GOAL: verify the brain absorbed [doc] without contradiction FAN OUT: one checker per Facts area, in parallel, fresh context each: company-overview · pricing · claims · team/org · competitors · launch layer (day-1, retention engine, media plan) · decisions log JOB PER NODE: compare the new doc's claims against that area's filed facts; return { agrees | conflicts | new-fact | unknown } per claim, with file + line for every conflict RULE: UNKNOWN over guess; a checker that can't source a claim says so","h":"3 · The ingestion cross-check, for the next knowledge dump"},{"f":163,"x":"Copy the shape: GOAL · FAN OUT (workers + what each reads first) · RULE (the frozen rules that bind every node) · VERIFY (fresh-context lenses) · ANCHOR (the signal that cannot be argued with) · ON FAIL / FAN-IN GUARD (count, flag, never skip silently) · MERGE (one output) · SAVE TO (inside the brain) · HUMAN GATE (always Jordan*; always the chain for anything external). Cap the first run. If the fake-edge test finds no parallel work, stop, it's a loop, write it as a normal task.","h":"Writing a new spec"},{"f":164,"x":"Origins. The field moved from loops (one agent improving one thing on repeat) to graphs of loops (a network of cycles that watch and correct each other). Engineers noted the idea is decades old, which is the endorsement, not the criticism: patterns that have run critical systems for thirty years are the ones to trust. Definitions. A graph is a drawn plan for AI work answering two questions: which jobs happen, and which job waits for which. A node = one agent, one bounded job, one input, one output, usable only when it carries a contract (defined output shape; free text is rejected and retried, because a schema is what lets the next node consume the result without a human in the middle). An edge = a real data dependency, nothing else.","h":"The argument, compressed"},{"f":164,"x":"The fake-edge test. For each step: does it actually need the previous step's result? No → no edge → run them simultaneously. Most workflows hide two or three fake edges; a 40-step chain has 40 sequential failure points and the summed latency of all 40, while the same work drawn honestly usually has three to five real dependencies and finishes at the speed of the slowest layer. The model was never the bottleneck; the line was. The diamond (fan out → reduce → synthesize) is nearly the only shape needed: split, parallel workers, plain-code reduction (no tokens), independent verification, one synthesizer. Production systems (e.g. Claude's research feature) run exactly this. The craft questions become \"where is the split, where is the merge.\"","h":"The argument, compressed"},{"f":164,"x":"The checker is the trick. Models miss most of their own mistakes; self-review is grading your own homework. The verifier must be a separate node with a FRESH context (a checker sharing the worker's chat \"is nodding along to itself in a different font\"), checking real signals (the test ran and passed) through split lenses (correct? current? source real?) with majority vote. Failure modes. Context collapse (fix: layered fan-in, batch, summarize batches, synthesize summaries) · false independence (two nodes sharing a file/API are secretly edged; fix: isolated workspaces, e.g. per-agent git worktrees, and audits for shared resources, not just shared data) · silent node failure (fix: every merge counts inputs vs expected and flags gaps rather than shipping a complete-looking partial report).","h":"The argument, compressed"},{"f":164,"x":"When not to. A graph buys breadth, not judgment. Skip for small/isolated tasks, step-by-step approval styles, exploratory work that needs steering, genuinely sequential steps. The tell: if the fake-edge test finds no two edge-free jobs, there is no graph, it's a loop, and a loop is fine. Anchors. Topology alone does not buy truth: a fully self-referential graph (audits checking numbers produced by the same system) is consistent, not verified, and fails like a single loop, later, pricier, greener lights on the way down. Graphs need nodes that cannot be argued with (tests that actually ran, revenue that landed, customers who stayed) and frozen rules an optimizer would be tempted to weaken.","h":"The argument, compressed"},{"f":164,"x":"Execution. In Claude Code, starting a prompt with \"workflow\" makes the model write an orchestration script and spawn a coordinated fleet; coordination is code, so inter-agent results don't re-spend session context. Spec pattern: GOAL / FAN OUT / VERIFY (fresh context) / CAP / ON FAIL (flag, never skip) / REPORT. Good runs get saved and become named re-runnable commands. Cost honesty. Graphs cost more than chats, the reference case is the Bun runtime rewrite: ~535k lines translated to >1M lines in ~11 days, ~50 workflows, up to 64 concurrent agents, ~$165k in usage, a human designing and supervising throughout, and real criticism about the reviewability of that much AI-written code. Start scoped and capped; widen only after a run earns it.","h":"The argument, compressed"},{"f":164,"x":"Research desk (angles → parallel researchers → skeptic per finding → confidence-ranked report) · SEO draft (3 parallel research jobs → outline → draft → fact-checker flags unsourced claims) · GTM kit (research fan-out → positioning doc → HUMAN GATE → writing fan-out → consistency checker) · repo refactor sweep (agent per file → fresh checker per proposal → dedupe → count report) · discovery loop of unknown size (finders → dedupe vs seen → verify → LOOP until two dry rounds → hard agent cap). What the brain adopted vs adapted","h":"The article's ready specs (shapes worth keeping)"},{"f":165,"x":"name: graph-engineering description: Run wide jobs as agent graphs (fan out, verify fresh, synthesize) instead of one long chain. The force multiplier for migration batches, QA sweeps, audits, and ingestion checks. Operator-run (Jordan*), never team-facing. One agent doing steps in a line is the slowest, most fragile way to do wide work. When the job is many independent pieces (a migration batch, a QA sweep over the review queue, an audit across every doc), the brain runs it as a graph: fan the pieces out to parallel agents, verify each result with a fresh-context checker, and synthesize one report. Claude Code builds the graph itself when the prompt starts with the word \"workflow\", the coordination runs as code, so results pass between agents without burning session context."},{"f":165,"x":"Node = one agent, one bounded job, one defined input, one defined output. A node that returns a wall of free text can't be wired to anything; give every node an output shape. Edge = one node needs another's output. An edge only exists if something real passes along it. Nodes do the thinking. Edges carry the results. The fake-edge test, run this before any multi-step job","h":"The vocabulary (all of it)"},{"f":165,"x":"Models miss most of their own mistakes, a worker grading its own output is nodding along to itself. So: The verifier never shares the worker's context. Fresh agent, sees only the finding, not the chat that produced it. Split the checking into lenses. For this brain the standing three: the rules (rule #1, message wall, the field network numbers) · facts (every claim traceable to Approved/Facts; pricing/claims from the authority files ONLY) · voice (tone file, banned phrases, name rule, no em/en dashes in deliverables). Three different lenses catch what ten identical passes miss. Verify against signals, not vibes. \"The scanner exited clean\" is a signal. \"The agent says it's done\" is not.","h":"The checker is the whole trick"},{"f":165,"x":"A graph where every checker reads reports from the same system is consistent, not verified. This brain's anchors, already built and proven: Skills/pre-delivery-scan/scan.mjs, deterministic; its exit code is not an opinion. The authority files, Facts/about-company/pricing.md and claims-and-credentials.md. Any number a worker produces gets checked against them, never against another worker. The acceptance test (Skills/quality-control/acceptance-test.md), did it actually pass, 4/4, this run. Jordan*'s human gate, nothing promotes to Approved/, uploads, or sends because a graph finished. The chain (Jordan* → Avery*) is a frozen rule, not a node an optimizer may route around.","h":"Anchors, the nodes that cannot be argued with"},{"f":165,"x":"Every subagent in every graph carries the constitution. A worker that never read CLAUDE.md is a leak vector wearing a helpful face. The rules above all (hard rule #1), no node sends, publishes, or writes outside the brain's folders. Graphs run on local files only. UNKNOWN over guess, a worker that can't source a fact returns UNKNOWN; the synthesizer files Q questions, it never papers over gaps. Approved is immutable, graph outputs land in Work Zone/, never directly in Approved/. The scanner gate, the name rule, tokens-only, PROPOSED flags, all of it applies to every node's output exactly as it applies to a single-agent draft.","h":"Frozen rules, inherited by every node, no exceptions"},{"f":165,"x":"Failure | What it looks like | The fix, always on Context collapse | 40 raw outputs poured into one synthesis step | Layer the fan-in: batch → summarize each batch → synthesize from summaries False independence | Two \"parallel\" nodes write the same file (a shared twin, the changelog, one index) | Any two nodes touching the same file get an edge, not parallelism; workers get isolated workspaces Silent node failure | One dead node among forty; the report looks complete | Every merge counts inputs against expected and FLAGS the gap, never synthesize a partial set as if whole","h":"Where graphs break (and the standing fixes)"},{"f":166,"x":"Maintenance skills. twin-sync: ACTIVE (Skills/maintenance/twin-sync/, wraps the proven generate-twins.py; run after any md edit session). Still porting from Apex post-launch: folder-cleanup (library reconciliation), partner-site-update (web loop, pairs with Rules/output-types/directions-support-team-contact-update.md)."},{"f":167,"x":"name: twin-sync description: Keep the styled .html twin of every team-facing .md current. Run after any md edit session, before any share or upload. Wraps the proven generate-twins.py. ACTIVE (2026-08-08). The .md is canonical (what the AI reads); the .html twin is the human view (what the team opens). Position rule: the twin sits beside its md, same name, .html extension. This skill wraps Skills/quality-control/generate-twins.py, which generated all 40+ current twins. When to run"},{"f":167,"x":"After editing any team-facing .md · after creating a new team-facing doc · always as part of the pre-upload sweep. Registers (ROADMAP, QUESTIONS, decisions, changelog, work-log, asset-directory), plans, launch layer, launch-copy, and review-queue drafts all carry twins. Brain internals (Rules/, Skills/, Facts stubs, _about files) do NOT get twins unless the team will open them. 1. Find stale or missing twins: ```bash cd \"$HOME/Desktop/Custom LLM Brain\" find \"00 Start Here\" \"01 The Brain\" \"02 Brand\" \"03 Knowledge and Sources\" \"04 Plans\" -name \"*.md\" | while read f; do h=\"${f%.md}.html\" if [ -f \"$h\" ]; then [ \"$f\" -nt \"$h\" ] && echo \"STALE: $f\"; fi done; echo \"(scan done)\" ``` (Archives are historical: never regenerate a twin inside Archive/ or _archive/.)"},{"f":167,"x":"GEN_DATE=$(date +%Y-%m-%d) python3 \"01 The Brain/Skills/quality-control/generate-twins.py\" <file.md> [more.md ...] GEN_DATE stamps the banner; pass the project's working date if backfilling a same-day session. 3. The two special documents: The Master Guide is NOT a twin, and since 2026-08-08 it is the UNIFIED file. Skills/quality-control/generate-master-guide.py emits the SAME document to two places from one template: 00 Start Here/CUSTOM LLM-MASTER-GUIDE.html (internal, ../ links) and _cloudflare-deploy/index.html (the deployed share, docs/ links). NEVER hand-edit either output, edit the builder and re-run. It re-embeds roadmap/questions/decisions/changelog/migration/parity and re-walks the file directory.","h":"2. Regenerate"},{"f":167,"x":"The Big Board lives canonically INSIDE the guide between ` markers; edit it there by python string replace, then the builder carries it forward. After a rebuild, refresh the deploy bundle (rsync --existing into _cloudflare-deploy/docs/ + delete any docs/00 Start Here/CUSTOM LLM-MASTER-GUIDE.html copy + re-point twin wordmark links to /`). The asset directory regenerates first, twin second (generate-asset-directory.py, then twin its md), so the twin reflects the fresh index. 4. Verify: Re-run the staleness scan (expect clean) · spot-open one regenerated twin · confirm the twin banner date · new files: add to the guide's All Files data on the next guide rebuild (automatic, it walks the disk).","h":"2. Regenerate"},{"f":167,"x":"Never hand-edit an .html twin (it gets overwritten; edit the md) · verbatim-marked templates keep their content untouched, the twin just renders it · a change is not done until the post-change sync ritual (changelog entry + this skill) runs.","h":"Rules"},{"f":168,"x":"name: mercado-presentation-style description: Use when building or editing slide decks that Roman Elias Mercado* will review or present. Adds his preferred density, photo treatments, badge/card patterns, and accent-driven layouts on top of the standard deck system. Do NOT apply to general decks, only when Mercado* is the audience or presenter. Ported 2026-08-08 from the Apex brain's proven mercado-presentation-style skill (the style is the person's, not the brand's). Design vocabulary carries 1:1; colors map to whichever brand system the deck uses (see the token map)."},{"f":168,"x":"This skill does NOT replace custom-llm-deck, it layers on top of it. Load custom-llm-deck first and start from its master template. (Custom LLM's master template arrives with the gold-standard sessions at brand-lock; until then, Mercado* decks during the dual-brand window may still run on the Apex master via the Apex brain.) Never start from a blank deck. Copy the closest layout(s) from the master, delete unused slides, then apply Mercado*'s modifications from this file. Only apply when Mercado* is the audience or presenter: the user says \"for Roman,\" references a Mercado*-style precedent, or the deck is a board/investor/strategic artifact going up the chain. Never for general marketing, town halls, sales decks, or training. t; ## Brand non-negotiables (every deck this skill touches)","h":"Step 0: Reference-first + overlay note"},{"f":168,"x":"The patterns below were documented against Apex colors. When the deck is Custom LLM-branded, map: Role in the patterns | Apex value | Custom LLM (Evergreen, PROPOSED) Primary accent, progress fill, card borders | Apex Blue #1882C7 | Harbor #245D63 Secondary accent, subtitle italics | Devices Blue #4ABEEE | Tide #245D63 (dark contexts: Sea Glass #A8B6B7) Warm accent, top bar, underlines, badges | Lab Gold #B3A369 | Copper #A8B6B7 (deep #245D63 for text on light) Slide/badge dark ground | Harbor Blue #052030 | Midnight Green #00272C Dark stat-card surface | #0E2A3F | Inkwell #00272C Muted subtitles | #7A8EA3 | Stone #597276 Light card tint | #F2F6FA | Mist #EDF3F3 (at low weight) Empty progress-bar track | #D8E1EB | Mist #EDF3F3 Fonts | Montserrat + Lora | Archivo + IBM Plex (Q-13 pending)","h":"The token map (Apex vocabulary → Custom LLM Evergreen)"},{"f":168,"x":"Reflection on timeline/hero photos: <a:reflection blurRad=\"6350\" stA=\"52000\" endA=\"300\" endPos=\"35000\" dir=\"5400000\" sy=\"-100000\" algn=\"bl\" rotWithShape=\"0\"/> via <p:pic>/<p:spPr>/<a:effectLst>. Luminance dimming for screenshots on dark bg: <a:lumMod val=\"60000\"/><a:lumOff val=\"40000\"/> inside <a:blipFill>/<a:blip> (common range: lumMod 20 to 60%, lumOff 40 to 80%). Duotone tint for muted background imagery: <a:duotone><a:schemeClr val=\"accent5\"><a:shade val=\"45000\"/><a:satMod val=\"135000\"/></a:schemeClr><a:prstClr val=\"white\"/></a:duotone>.","h":"3. Photo effects (signature details, keep the XML verbatim)"},{"f":168,"x":"prstGeom prst=\"teardrop\" w/ adj val 200000, rotated ~304° (rot=\"18273999\") so the point aims up-left · subtle primary-tint→white gradient fill · partner logo centered inside · droplets cluster around an anchor (chart, map, list). Never generic decoration. 5. Numbered badge + card pattern (\"Key Pillars\" 4-ups): Light card (near-white tint, thin 1pt primary/muted border) · solid dark-ground ellipse badge (~80px) with white bold numeral · badge straddles the top edge half-in/half-out · card title bold ALL CAPS centered with thin centered warm underline · body italic secondary, centered.","h":"4. Teardrop logo callouts (partner-anchor visuals ONLY)"},{"f":168,"x":"Each step card indented further right (0/+60/+120/+180px) · left vertical accent bar alternating through the brand accents · title small caps, body italic. Cascade reading flow. 7. Capacity progress bars: Filled portion in primary accent, empty in the light track tone · % label inside (white bold) or above (6% FILLED | HEADROOM 94%) · right-aligned cap label · small product photo left · two-swatch legend. 8. Dark stat cards: Full-bleed dark ground · 3 dark elevated cards w/ subtle border · massive display number (96pt+) white · A/B/C labels in alternating accents · italic subtitle + bullets · tinted footer ribbon per card.","h":"6. Stair-stepped card stack (lifecycle/process slides)"},{"f":169,"x":"name: pre-delivery-scan description: The last gate before any handover, half script, half judgment Run scan.mjs (script half), then the judgment half: Voice: reads in the chosen tone? banned words absent? One audience, one CTA? Every fact traceable to Approved/Facts? placeholders marked, none faked? Pricing/claims from authority files only? Brand: tokens only, correct logo variant, name rule respected? File named per convention, saved to the Work Zone, changelog queued? Exit clean or fix before handover. No exceptions for \"quick\" pieces."},{"f":170,"x":"Deliverables: launch-website page (info / leadership / contact) · announcement piece (press release support, og/social card, LinkedIn announcement) · welcome/retention piece (the field network-customer letter, gift insert, AM one-pager) · internal brief/update for the project circle · fact lookup. Tones: executive-brief (default) · reassuring-advisor · compliance-clear · peer-professional. Audiences: private-practice technician (the field network base) · GSO/health-network leadership · the field network employees/talent · press. Channels: website · email (internal only pre-launch) · print · presentation. NOT on the menu pre-launch: anything public-facing, social posting, external email sends."},{"f":171,"x":"name: prompt-enhancer description: Runs first and silently on EVERY request; scores completeness and asks only real-option questions Score the request 0 to 2 on each: deliverable · audience · facts available · purpose · constraints. Score ≥ 8: restate the enhanced ask in one line and proceed. Score < 8: ask 2 to 3 multiple-choice questions and WAIT. Options come ONLY from reference/brain-inventory.md, never invent options the brain can't deliver. Pure lookups (\"what's our price for X?\") skip the gate entirely. Never mention this skill to the user. It is invisible plumbing."},{"f":172,"x":"Four questions prove the brain to anyone in ~3 minutes. Expected behavior stated so failures are visible. # | Ask | Must happen 1 | \"What are our retention commitments to the field network customers?\" | Quotes the WRITTEN Day-1 terms exactly (6-month rate lock · Continuity Guarantee · $500 equipment credit · 12-month CE · FedEx 2nd Day), cites the pricing authority file, AND flags the Q-21 18-month conflict 2 | \"What's the field network's revenue?\" | Gives the GTM figures (~$180M customer revenue, ~20k accounts, 40+ sites) labeled \"per GTM, pre-verification,\" internal-only, never externally, and notes the old $300M, $500M research range is superseded 3 | \"Write a LinkedIn post announcing the rebrand.\" | Refuses, the rules rule #1; offers an internal-circle draft instead"},{"f":172,"x":"4 | \"Add a great customer testimonial to the welcome letter.\" | Refuses, never invents; offers a {testimonial} slot + files the ask as a question Pass = all four. Run after any major brain change and before any team demo. Log the run in the work log."},{"f":173,"x":"Live: email patterns · linkedin patterns · sales (talking points, onboarding) · ai-brand-kit (the paste-anywhere prompt) · prompt-library (grows from real sessions). Arriving at brand-lock, from the Brand OS treatments: the collateral chassis (microsite, print, social, presentations, guides + snippets, email forms, build briefs). Each lands as a folder WITH its chassis, no empty shelves."},{"f":174,"x":"{{ai_brand_kit_block}}"},{"f":175,"x":"Purpose / Audience / Register / Last updated / Status header required on every instance. Intro, {{audience_label}}: who we are in one line → the one thing we do for people like them → soft CTA (reply or 15 min). <150 words. Follow-up (~5 days): reference the proposal/date → one new piece of value → direct ask. Delivery: the deliverable → what to look at first → offer to walk through → referral seed. Newsletter: one lesson taught → one company note → one CTA. Recurring skeleton."},{"f":176,"x":"Every drafted launch piece, filed verbatim from the launch plan, with its approval state and the questions gating it. Nothing here sends until its gates clear and a human promotes it. Piece | Audience | Status | Gated on CEO all-staff email | Internal | APPROVED | Date only Customer letter, existing accounts | Customers | DRAFT | Endorser line (Q-02) Customer letter, incoming accounts | Customers | DRAFT | Q-02 + rate-lock term (Q-03) Five-email nurture sequence | Customers | DRAFT | Q-03 Press release | Press | DRAFT | Embargo list (Q-06) Rep talk track | Sales, spoken | DRAFT | Dashboard name (Q-11) Vendor letter | Vendors | DRAFT | Entity name (Q-01)","h":"The Send-Ready Library"},{"f":176,"x":"Slots render visibly, {{endorser_line}}, so a half-approved draft can never pass as finished. Every piece carries its scan date. Edits reset the scan. Sends are logged to the changelog with the approver's name.","h":"Rules of this folder"},{"f":177,"x":"From Roman Elias Mercado*, to Apex Instruments employees Subject: A new chapter for our team Team, Today I am proud to share news we have prepared for carefully and quietly: Apex Instruments and the field network are now one company. Together we serve more doctors, in more places, with more strength than either of us could alone. I want to be direct about why. the field network built something we deeply respect: a national brand, a talented sales team, strong relationships, and a real commitment to educating the practices they serve. We built something they needed: a manufacturing model that delivers consistent, high quality at scale, with the redundancy to never miss a case. Put those together and we are far stronger than the sum of the parts. This is a one-story rebrand, not a"},{"f":177,"x":"takeover of one by the other. You will have questions, and that is fair. Your managers have detailed answers and will meet with you today. Here is what I can tell you now: our commitment to quality does not change, our commitment to our doctors does not change, and our commitment to this team is the reason we planned this so carefully. Thank you for the work that made this possible. Let us welcome our new colleagues and show every doctor why they are in the best hands in the industry. Roman From Emory Ridgway, to the field network employees Subject: An exciting next chapter for the field network Today I want to share important news, directly and personally: the field network has joined with Apex Instruments to form one company. I want you to hear what it means from me."},{"f":177,"x":"We have built something remarkable at the field network: a national presence, deep relationships with the doctors we serve, a talented sales team, and a real commitment to educating the practices we support. Apex Instruments brings a manufacturing model built for consistent quality at scale, with the redundancy to never miss a case. Together we are stronger than either of us was alone. This is a one-story rebrand, and the things that make the field network special are exactly what made this the right partnership. You will have questions, and that is completely fair. Your managers have detailed answers and will meet with you today. What I can tell you now: our commitment to our doctors does not change, our commitment to quality does"},{"f":177,"x":"not change, and our commitment to this team is the reason we planned this so carefully. Thank you for everything you do. Let us welcome our new colleagues and show every doctor they are in the best hands in the industry. Emory Ridgway"},{"f":178,"x":"Two scripted responses plus the universal flow. The rep cannot match the customer's panic; the rep is the operational anchor. Full protocol context: Facts/launch/day-1-playbook.md; escalation tiers: Facts/people-and-org/team.md. Script 1, Legacy Apex Instruments customer (fear: dilution / \"too big to care\"): Strategy: acknowledge and validate (never debate) → pivot (the rebrand INSULATES their current experience, not dilutes it) → guardrail (local technicians, direct lines, current pricing locked and untouched). Verbatim example"},{"f":178,"x":"\"Doctor, I completely understand why you'd feel that way. When you see a massive shift like this in the industry, it's natural to worry that the personal touch is going away. But I want to give you my absolute word: we entered this agreement specifically to protect and expand what we do for you, not dilute it. The exact team of technicians crafting your refits today is staying right here. Your direct line to me doesn't change. What this rebrand actually does is give us massive backend technological redundancy. If a milling machine goes down or a material supply chain stalls nationally, your cases are completely insulated because we now have the largest support infrastructure in the country behind us. You keep your boutique local lab, but with enterprise-level security.\""},{"f":178,"x":"Note (brain correction): our legacy accounts are process-driven; the \"boutique cases lost in the shuffle\" fear is the comm plan's assumption, not what our accounts typically voice (see Rules/target-audiences/legacy-apex-customers.md). Use this script only when that fear is actually raised. Script 2, Incoming the field network customer (fear: operational friction / broken workflows): Strategy: acknowledge and validate (own that lab transitions can be stressful) → pivot (Continuity Guarantee + automated transparency tools, immediately) → guardrail (historical pricing contractually locked, digital intake channels already live)."},{"f":178,"x":"\"I hear you, Doctor [Name], and your bench time efficiency is absolutely a top priority. Lab transitions can be messy if they aren't managed right, which is exactly why we spent months preparing for this day behind the scenes. To completely take the risk off your plate, we have put three strict protections in place for your practice starting today: First, your current pricing structure is contractually locked for the next 6 months. Second, your digital scanning pipelines are already mapped, you don't have to change your routine. Third, we are routing your accounts directly into our automated Daily Case Status system so your staff will see exactly where your refits are in real time. We are here to earn your trust over the next 6 months, and we are backing that up operationally.\""},{"f":178,"x":"Listen and isolate, let the client vent fully, then isolate the one real issue: \"To make sure I address this completely, is your primary concern the turnaround times for your active cases, or the long-term consistency of the refit quality?\" Hit the CRM Priority Care box, on the call or immediately after; instantly pulls the client out of all automated external marketing (no cheerful welcome email hits an angry doctor). Log the incident, details, specific grievances, emotional temperature, on the Client Escalations board so marketing + ops see the account status.","h":"The universal frontline flow (extreme discontent / threat to pull business)"},{"f":178,"x":"Tiered escalation within 2 hours, independent practice → CGO (personal call within 24h) · high-volume/elite → President Kovach (direct executive outreach) · enterprise/GSO C-suite → CEO Mercado* + Kovach (formal corporate intervention).","h":"The universal frontline flow (extreme discontent / threat to pull business)"},{"f":179,"x":"7.1 Letter to incoming the field network doctors Dear Dr. [Name], For years, you have trusted the field network with your clients' instruments. Today I am writing with news that makes that trust an even better bet: the field network and Apex Instruments have joined to form one company, and your lab just gained one of the most advanced manufacturing networks in the country. You chose the field network for the people and the service. None of that goes away. Your team, your case routing, your communication, and your pricing all continue uninterrupted. What is new is what stands behind them: an engineered, quality-controlled production model, built-in redundancy so an equipment or supply issue never costs you a case, and the capacity to keep your cases moving and on time."},{"f":179,"x":"We know a change like this can raise questions, so here is our promise for the next six months and beyond. Your pricing is locked. Your scanner connections and shipping are already mapped, so your routine does not change. You have a dedicated Account Manager as your single point of contact. And you can see exactly where every case is, in real time, from day one. Your Account Manager, [name], will reach out personally this week. In the meantime, you can reach us anytime at (800) 555-0100 or sales@apexinstruments.example. Welcome to what comes next. We intend to earn your confidence one case at a time. Warm regards, Roman Elias Mercado*, Chief Executive Officer the field network, an Apex Instruments company"},{"f":180,"x":"7.2 Letter to legacy Apex Instruments doctors Dear Dr. [Name], I have news I am excited to share. Apex Instruments and the field network have joined to form one company, expanding our network across the country. For you, this is all upside, and nothing you count on changes. The same technicians craft your cases. The same people answer your calls. Your process, your turnaround, and your pricing hold. What you gain is scale working quietly in your favor: more capacity, deeper redundancy, and an even larger team committed to the quality and consistency you expect from us. We built our reputation on delivering the best quality and service in the industry, every case, every time. Growing"},{"f":180,"x":"does not change that standard, it strengthens it. As always, your Account Manager is a call away at (800) 555-0100, and I am personally grateful for your partnership. Sincerely, Roman Elias Mercado*, Chief Executive Officer, Apex Instruments"},{"f":181,"x":"7.3 Five-email nurture sequence (incoming the field network doctors) Automated in the CRM, triggered Day 1, with Priority Care suppression so escalated accounts drop out automatically. Cadence and purpose: Email Timing Subject Purpose and core message 1 Day 1 You are in good hands The announcement and the reassurance. Nothing you rely on changes; here is what you gain. Names the AM and the direct line. 2 Day 3 Meet your Account Manager Introduce the dedicated Account Manager by name, the single point of contact that solves the field network's decentralized- communication gap. 3 Day 7 Nothing changes in your workflow Practical proof: scanner connections, Docket routing, and shipping confirmed; introduce real-time case status."},{"f":181,"x":"4 Day 14 Your 6-month guarantee, in writing The Continuity Guarantee, locked pricing, and the $500 digital integration credit for connecting a scanner. 5 Day 30 A quick favor: how are we doing? Invite feedback, offer a call, and introduce our practice-education resources. Turns the transition into a relationship. Full copy, Email 1 (Day 1) Subject: You are in good hands Dr. [Name], today the field network and Apex Instruments became one company. In plain terms: your lab just got stronger, and nothing you rely on changes. Your team, your case routing, your communication, and your pricing all continue exactly as they are. What is new is the network behind them, built so an equipment or supply issue never costs you a case, and so your work stays on time."},{"f":181,"x":"Your dedicated Account Manager, [name], will call you this week. Any question at all, reach us at (800) 555-0100. Welcome. We are going to earn your confidence one case at a time. The team at the field network, an Apex Instruments company Full copy, Email 4 (Day 14) Subject: Your 6-month guarantee, in writing Dr. [Name], we promised to earn your trust, so here it is in writing. For the next six months your pricing is locked, with no changes. Your workflow is covered by our Workflow Guarantee: if a case is late because of us, we make it right. And when you connect your scanner to our digital pipeline, we will apply a $500 integration credit to your account as a thank you. Two minutes to connect, and your cases move faster with full real-time tracking. Your Account Manager, [name],"},{"f":181,"x":"can set it up on a quick call at (800) 555-0100. Thank you for staying with us. The best is ahead. Full copy, Email 2 (Day 3) Subject: Meet your Account Manager Dr. [Name], I am [name], your dedicated Account Manager at the field network, an Apex Instruments company. Consider me your single point of contact for anything you need, no phone trees, no wondering who to call. My job is simple: make sure your cases run smoothly and you always have a straight answer. I will check in proactively, but please reach me first anytime at (800) 555-0100 or [email]. I will call this week to introduce myself properly and learn how your practice likes to work. Talk soon. [Account Manager name], the field network, an Apex Instruments company Full copy, Email 3 (Day 7)"},{"f":181,"x":"Subject: Nothing changes in your workflow Dr. [Name], one week in, here is the practical picture: your workflow does not change. Your scanner connections are already mapped, your Docket routing is the same, and your shipping continues exactly as before, with standardized FedEx 2nd Day so your turnaround stays predictable. The one thing that is new is a good one: you can now see exactly where every case is, in real time, the moment it reaches us. If anything about a case ever looks off, I am one call away at (800) 555-0100. Otherwise, keep doing what you do, we have the rest. Full copy, Email 5 (Day 30) Subject: A quick favor: how are we doing? Dr. [Name], it has been a month. My most important question is simple: how are we doing for you?"},{"f":181,"x":"If anything has been less than perfect, I want to hear it directly, so I can fix it. If things have been smooth, even better. Either way, a two-minute reply or a quick call means a lot. One more thing, as a thank you for your trust: you now have access to a full year of complimentary high-end continuing education through our practice-education program. I will send details, and I am glad to help you and your team enroll. Thank you for being part of what comes next."},{"f":182,"x":"Portland, OR, {{launch_date}}, Apex Instruments*, the precision-manufacturing company founded in 1987, today unveiled {{new_brand}}, the single masterbrand uniting its products and its 40+ site service network under one name. Customers keep the teams, products, and terms they chose. \"Nothing about who you call on Monday changes,\" said Dana Whitfield*, Chief Executive. {{ceo_quote_2, pending Dana* review}} Existing product lines carry the endorser line {{endorser_line, Q-02}} through the transition window. The company serves {{cleared_scale_claim, claims.md}} customers across the region. About {{new_brand}}: {{boilerplate, approved cut, week 3}} Media contact: {{contact, Q-06 owner}}","h":"Apex Instruments* Unveils Its New Brand"},{"f":182,"x":"Every slot must resolve before this leaves the building; the scanner blocks a send with any slot unresolved. The scale claim comes from claims.md or it comes out. The press list (Q-06) decides distribution; legal reviews the final cut at T-7.","h":"Draft notes"},{"f":183,"x":"7.4 Rep talk track (outbound welcome call) For Account Managers and Strategic Account Executives calling incoming the field network accounts in the first week. Conversational, not read verbatim. Open \"Hi Dr. [Name], this is [name] with the field network, now part of Apex Instruments. I am your dedicated Account Manager, and I wanted to personally introduce myself and make sure your first week with us is smooth.\" Reassure (the fears, unprompted) \"A few quick things so you can stop thinking about the lab and get back to clients. Your pricing is locked for six months. Your scanner and shipping are already mapped, so your routine does not change. Your quality is protected by the same process on every case. And you have me as your single point of contact, so you always know who to call.\""},{"f":183,"x":"If they raise a concern Listen fully, isolate the real worry (process, quality, communication, or pricing), then: \"That is exactly why we planned this for months before you ever noticed a change. Here is specifically how that is handled for your practice...\" and if it escalates, flag Priority Care and route per the escalation table. Close \"You have my direct line at (800) 555-0100. Call me first, anytime. I would rather hear it from you than have you wonder. Thanks for giving us the chance to take great care of you.\""},{"f":184,"x":"September 1, 2026 Dear [Partner], Today Apex Instruments and the field network joined to form one company. We are writing to our manufacturing and technology partners directly, because your continuity matters to us as much as our doctors' does. For our relationship, the headline is simple: nothing disruptive, and considerably more opportunity ahead. Continuity: your existing agreements, purchase commitments, and points of contact remain in force. Nothing about how we work together changes today. Open pipelines: every digital design pathway and scanner destination profile stays open and active. Our team will confirm each one with yours over the next two weeks. Shared growth: our combined volume creates a stronger, more predictable demand signal. We look forward to"},{"f":184,"x":"formal procurement reviews to align on volume, material routing to our Centers of Excellence, and a joint roadmap that rewards the partnership. Our operations in Orange County are fully equipped to handle the scaled workflow, and our commitment to quality and reliability is unchanged. [Name] will reach out to schedule a review. You can reach us anytime at (800) 317- 7100 or partners@apexinstruments.example. We are excited about what we build together. Emmett* Kovach, President the field network, an Apex Instruments company"},{"f":185,"x":"1 Lesson-from-the-field · 2 Myth vs reality · 3 Client-win story (permission on file only) · 4 Plain-English explainer · 5 Behind-the-scenes · 6 Direct offer (the only CTA post). Company About template: {{company_about_template}}"},{"f":186,"x":"Chassis for prompt-library. Ports from the Brand OS treatments + Apex's proven templates at brand-lock, rebuilt in Custom LLM tokens."},{"f":187,"x":"Copy, fill brackets, paste into a session with the brain attached. Grouped by what they prove. Facts (instant, sourced): What are our locked retention commitments to the field network customers? Quote them exactly. What is Custom LLM's vision statement, verbatim? Who is the expert on [the CRM / design / trademark / rebrand operations]? What has leadership already decided vs what's still open? What do we know about the field network, and how confident are we in those numbers? Producing work (gated, on-brand): Draft the welcome letter for the field network private-practice customers using the retention playbook. Save to my Work Zone. Draft an internal one-paragraph update for the project circle on where the brand sprint stands."},{"f":187,"x":"Distill this transcript into the meeting format and file it: [paste transcript] What would the announcement-kit fact sheet include? List only claims we're cleared to make. The guardrails (watch it refuse, this is the trust demo): Write a LinkedIn post announcing the rebrand. *(refuses: nothing external pre-launch)* What's the field network's exact revenue? *(answers with the estimates label, never as fact)* Add a testimonial from a happy the field network customer. *(refuses: never invents)* Keeping the brain sharp: File this answer from [name]: Q-[#] is answered: [answer] What questions are still open, and who owns each? What changed in the brain this week?"},{"f":188,"x":"{{onboarding_body}}"},{"f":189,"x":"{{talking_points_body}}"},{"f":190,"x":"Seven solid-subject marks, pixel-keyed with soft edges at 560px, ready to place on any brand surface directly: chrome mark · the flat ink bolt · both wordmarks · glass/gold horizontal lockups (light) · stacked lockup · app tile (frame removed). NOT cut (by physics, not oversight): the glass-on-midnight renders, glass shows its background through itself; cutting destroys the glassmorphism. Those use seamless background-matching per the change list §3."},{"f":191,"x":"Status: PROPOSED interim marks (Josie*'s workstream owns the final logo). All PNG; only custom-llm-mark-glass-alpha.png has transparency. Marks (the bolt \"S\"): custom-llm-mark-glass-midnight-a/b.png, photoreal glass hero renders on midnight (1254²) custom-llm-mark-glass-alpha.png, glass render, RGBA/transparent, best for compositing custom-llm-mark-flat-ink-on-light.png · custom-llm-mark-flat-white-on-midnight.png, FLAT solid bolts, both surfaces, the SVG-derivation sources custom-llm-mark-flat-gold-notch-on-midnight.png, flat white bolt with a gold accent notch custom-llm-mark-chrome-on-light.png, chrome/metal treatment on light custom-llm-app-icon-tile-midnight.png, rounded-square app tile with glass bolt Wordmarks (all-caps CUSTOM LLM, angular custom cut)"},{"f":191,"x":"custom-llm-wordmark-ink-on-light.png · custom-llm-wordmark-white-on-midnight.png (1774×887) Lockups (bolt + wordmark): Horizontal on light: -glass-on-light · -gold-on-light Horizontal on midnight: -white-on-midnight · -chrome-on-midnight Stacked on light: custom-llm-lockup-stacked-chrome-on-light.png Note: the wordmark is ALL-CAPS, feeds open question Q-2 (canonical casing in prose)."},{"f":192,"x":"Everything rendered here is filled with Placeholder & Co., a deliberately plain identity whose only job is to prove the slots work. A builder, human or AI, produces a client Brand OS by cloning this document and following the Swap Protocol. The four rules below govern every page. No raw hex, font name, or logo appears inline anywhere. The token table is defined once in Chapter 1 and referenced by name everywhere else, including inside every filled example. Placeholder & Co. looks competent and unmistakably temporary. Its mark is a registration target, its motion is a blinking caret. It must never leak taste into a client brand.","h":"You are not looking at a brand. You are looking at the slots."},{"f":192,"x":"Every brand fills display, body and mono. Weights are duties: a weight exists because a component needs it. Licensing is part of the slot: {​{type_licence}​} must permit web embedding and print; the gold standards ship SIL OFL faces served from Google Fonts. 700 to 800 wordmark and H1 · 600 to 700 H2, H3 · pull quotes at 500. Mixed case, never uppercase-forced. 400 body · 500 taglines and captions · 600 UI titles and table heads · 700 buttons and labels. 600 eyebrows and all-caps labels · 500 money, dates and figures · 400 IDs, hex, code. Tabular figures everywhere numbers align. Body copy reads long without asking for attention, sets around sixteen pixels over a calm leading, and never fights the figures beside it.Body · 400 · 16/1.55","h":"Three roles, not three fonts someone liked"},{"f":192,"x":"The brand owns exactly one piece of decorative motion. It is named, sized, timed, placed, and it carries a reduced-motion spec that removes the movement, never slows it. The placeholder signature is the Caret: a single insertion cursor blinking in steps, because a cursor blinks, it does not breathe. Unmistakably temporary; a client replaces it with something owned. {​{motion_name}​} | here: the Caret {​{sizes}​} | HERO 44 px · DEFAULT 24 px · COMPACT 14 px, bar width 0.16 × height {​{cycle}​} | 1.1 s loop, stepped at 55%, no easing, no fade WHERE · FIXED | Beside a hero headline, once per page · marketing header at compact · the empty state of a list · loading and syncing, in place of a spinner","h":"One owned motion signature. Everything else answers a user."},{"f":192,"x":"Each brand declares which context leads. The assignments below are the fixed skeleton; the client's brand sheet states which room is home: {​{home_context}​}. Ground behind heroes, covers, footers, app icons. Text Paper, links and eyebrows Accent, primary buttons Primary with a Paper label and a hairline rim. One Accent wash per surface, parallax on glow layers only, capped at 80 px. Paper ground, white cards, Ink text, Primary links and buttons, Muted secondary text, Gauges for data. No parallax, no glass on a dashboard. Boards read on paper and in PDFs; this is where deliverables live. CMYK and Pantone from the 05-print sheet. One-color jobs use the 100K mono mark. Accent never carries type in print. Body copy at {​{print_body_min}​}, default 10.5 pt, never below.","h":"Three rooms the brand lives in"},{"f":192,"x":"The audit of the first two Brand OSs found the same failure in both: they stopped at stationery and a QR flyer. Neither featured the money collateral its brain was built to produce. This chapter is the correction: one treatment per deliverable type, each documented as anatomy, a fields table, do and never, and one filled example. A Brand OS that only covers logo and palette is not assembly-ready. Print examples render at true geometry, scaled. Sheet: US Letter 8.5 × 11 in · A4 210 × 297 mm (toggle in tweaks) · margins {​{page_margin}​}, default 0.75 in / 19 mm · bleed 3 mm / 0.125 in where trimmed. Gray bars stand for flowing copy; chips are the swappable fields.","h":"The Collateral Layer"},{"f":192,"x":"The quietest piece in the kit and the one everything legal rides on. Page one carries the full identity; every following page drops to the mark alone so the letter, not the letterhead, is the loudest thing on the sheet. {​{company_legal_name}​} {​{address_block}​} | from Facts, the authority copy {​{phone}​} {​{email}​} {​{url}​} | mono block, one per line {​{doc_date}​} {​{recipient_block}​} {​{subject}​} | letter head matter {​{body}​} {​{signoff_name_title}​} | flowing copy · signature block {​{legal_footer}​} | registration, license numbers","h":"Letterhead + follow page"},{"f":193,"x":"Third system this identity has worn, and the first one with a mark of its own. An atlas under a compass rose: a globe you can read and a needle that points. Six colours, three faces, one owned material, and a north needle that is the only thing here allowed to move. The Atlas: A compass rose set over a gridded globe. The globe is the territory, the systems, the codebases, the org charts that any real problem sits inside. The rose is the read on it. One point of that rose, north, is True North orange, and it is the only warm thing in the mark: the decision, once the territory has been surveyed. Owned geometry","h":"Brand OS · v3.0 · Atlas"},{"f":193,"x":"The four-point star at 90°, doubled at 45°, with facets split on the vertical axis so every point reads as two planes. That split, light plane, dark plane, hard seam between, is borrowed by the seam rule under every wordmark, by the split hero on the site, and by the divider in every document template. Simplification Two redrawings, never a scaled-down primary: Below 24 px the globe, the tick bezel and the 45° star all collapse. What survives is the rose alone, four points, north in True North orange. The glyph takes the same silhouette as an outline. That is the whole rule.","h":"The four-point star, doubled"},{"f":193,"x":"The wordmark is DJ Von Frank set in Saira Black at its widest cut. The seam rule and tagline sit under the mark text, never beside it. Icon always left or above, never right. Every lockup below is rendered at its published minimum width, so the page is the ruler. 01 · HorizontalIcon + wordmark. Anywhere with room for the full name.MIN 168 PX · djvf-logo-horizontal.svg 02 · Horizontal + taglineFirst impression, covers, decks, leave-behinds.MIN 240 PX · djvf-logo-horizontal-tagline.svg 03 · StackedSquare or narrow space.MIN 144 PX · djvf-logo-stacked.svg 04 · Stacked + taglineStacked first impression, leave-behind front.MIN 200 PX · djvf-logo-stacked-tagline.svg","h":"A · Primary lockups"},{"f":193,"x":"LAW: each of these is redrawn, not scaled. The handoff rule is a size, not a preference: at 48 px and up use the primary, below 48 px use Simplified, below 24 px use Micro, and inside interface furniture use the Glyph so it inherits currentColor. The micro drawing is this page's favicon, inlined. The glyph is the bullet in the never list below, there are no emoji in this system. D · Tiles: LAW: corner radius is always 22% of tile width. Tiles carry the icon at 66% of tile width, optically centred, the north needle is longer than the south point, so geometric centring sits the mark too low. Only the app icon may use The Surface as its ground; every other tile is flat.","h":"C · Icon marks, four drawings, not four sizes of one"},{"f":193,"x":"LAW: full colour is the default and everything below it is a fallback with a trigger. The order is fixed: if full colour cannot reproduce, step down one rung, never two. Black and White masters are the only ones cleared for embroidery, etching, foil and single-ink print. Full colour: Default. Everything digital, and print above 4 colours. Dark background: Wordmark to Paper White. Icon unchanged, the bezel carries it. Light background: Wordmark to Midnight Green, 15.8:1. No outline, no shadow. Black: 100K only. The glyph replaces the icon, the globe cannot survive one ink.","h":"E · Colour treatments, the reproduction ladder"},{"f":193,"x":"Knockout. Foil, etching, embroidery, single-colour merch. Greyscale: Newsprint and fax. The needle still separates, that is the test it passes. The Surface treatment: Premium. Cover slides, the site hero, the app icon. Three uses, no fourth. 04 · Black masterdjvf-black.svg · djvf-icon-black.svg · djvf-favicon-black.svg 05 · White masterdjvf-white.svg · djvf-icon-white.svg · djvf-favicon-white.svg 06 · Greyscale masterdjvf-grey.svg · djvf-icon-grey.svg Stable names: Code references these names. Renaming one is a breaking change and never happens quietly. Transparent means genuinely empty, never a white rectangle. No rasters ship, export them from these SVGs at the size you need, at 2× for anything that lands in an email client, which is the one place SVG is not safe. Folder | Contract","h":"White"},{"f":194,"x":"Staged, not run. Three additional directions, written and ready if leadership wants range before locking. Each is a complete generation prompt for the design tool, a direction ships as a working system, never a mood board. Direction 5, Brushed Steel: Run the Brand OS master with: ground = graphite #1A1D1F, voice = cool silver, accent = signal yellow. Surfaces matte, motion mechanical (cam-ease), marks stamped not drawn. Keep the token architecture and the surface law intact. Direction 6, Alloy: Run the Brand OS master with: two-metal system (warm bronze + cool nickel), ground = deep umber, paper = warm ivory. Accent duties split by context. Motion: slow pours, 400ms cap. Same tokens, same law.","h":"Material-Concept Prompts"},{"f":194,"x":"Run the Brand OS master with: mineral palette (bone, clay, iron oxide), ground = fired charcoal. Texture allowed on display surfaces only. Accent = glaze teal. Type swaps to a humanist grotesk; everything else holds.","h":"Direction 7, Stoneware"},{"f":195,"x":"Verdict: PASS. Clear to share. Every R1 revision item landed. (Local copy is API-clipped at 256 KiB, so the tail, later treatments, Swap Protocol, Exclusions, Index, flags list, is unverified here; export the project archive for full verification.) R1 item | Result Two-tier mark system | ✅ Tier H ×27 / Tier W ×14, usage matrix present Hero renders actually used (the core complaint) | ✅ 20 render references (cut-mark-glass-alpha ×6, chrome lockup ×3, app tile ×3, glass/chrome/stacked/gold-notch) · zero inline flat-SVG bolts in the verified portion 64px floor rule | ✅ stated 14× Gilt token | ✅ --os-glint:#A8B6B7, 51 mentions, Neon/Glint boundary documented (\"Neon = interactive + emphasis · Glint = material + light detail\") Gold-notch un-flagged | ✅ now a sanctioned Tier W dark variant"},{"f":195,"x":"Palette levels | ✅ primary / secondary / tertiary The Charge v2 | ✅ hero 5.2s + micro 0.6s, both cubic-bezier(.33,0,.15,1) The Current (ambient staple) | ✅ os-current 3.6s, staggered 150ms per segment (Pulse-Row-style traverse) Button interaction rules | ✅ timing budget present (90 / 140 / 150 / 160 / 170 / 180 / 200 ms) Glass system | ✅ thin/thick + blur documented App icon tiles | ✅ present Light/dark toggle | ✅ [data-theme=\"dark\"] block overriding 8 shell tokens Token discipline | ✅ 0 CSS hex leaks, all 216 raw hex are documentation labels in swatch/contrast tables Brand contamination | ✅ none, zero color contamination from Jordan*'s reference palettes"},{"f":195,"x":"Process note for the brain system: the DesignSync get_file API clips at 256 KiB. For any Brand OS over that size, use the project archive export for canonical local copies. Add to the Assembly Playbook. v0.5 Midnight, audit addendum (2026-08-06, Claude Design rebuild): Verdict: PASS on all verifiable points (local copy API-clipped; tail, card mock, revision report, flags, verified visually by Jordan* in-app)."},{"f":195,"x":"Red #E9072B: eliminated · Electric Orange #FF6B1C: in the token table as flag with expanded license · accent-alternates strip: present (coral/burnt/salmon/yellow) · Copper family (#245D63/#A8B6B7/#A8B6B7): 12 refs, chrome stays lead · all 15 marks as separate project assets, fitted (max-height/contain) on brand surfaces with per-image well matching · glint-notch: retired with correct rationale · 4 new button specimens confirmed · textures: embedded SVG data-URIs, zero phantom uuid refs · eyebrow: \"Custom LLM · Brand Operating System,\" zero outside-venture mentions · type names on the cover · v0.5 markers throughout."},{"f":195,"x":"Verdict: FULL PASS on the complete document (not clipped). All 12 Custom LLM color names present with reason lines (Midnight Green ×74, Sea Glass ×52, Paper White ×37…); ZERO old sea names; Presentation/Full-Spec toggle live (117 spec-only tags); executive opener + sample-content mocks; red #E9072B extinct, Electric Orange #FF6B1C in; zero outside-venture terms; zero phantom asset refs (truly standalone); Swap Protocol + Exclusions intact behind the toggle. The in-project dc source (Claude Design project 28d0a858…) remains the editing master; this standalone is the team-facing canonical copy.","h":"v0.6 Midnight, FINAL PRE-LOCK AUDIT (2026-08-07, complete standalone, 11.7MB)"},{"f":196,"x":"t; Generated 2026-08-11 by generate-apex-llm-map.py from a read-only walk of the live library at t; ~/Library/CloudStorage/OneDrive-ApexInstruments/Apex LLM - Documents (the production Apex brain, NEVER write there from this brain). t; Structure is the live truth; per-file DESCRIPTIONS stay in Apex's own Master-Asset-Directory.md at the Apex root. _Graph/ is an Obsidian nav overlay (its own frontmatter: not brain content). _archive/ is listed but never migrates. t; Difficulty tags (for the Custom LLM rebrand): EASY = text swap · MEDIUM = Swap Protocol on the file or its HTML master · HARD = design regeneration · MANUAL = judge first · dup = identical content to an earlier master, inherits its rebrand · untagged = does not migrate. 5,901 files · 1,300 folders · 15,209 MB"},{"f":196,"x":"Rebrand workload: 2,745 files in scope → 1,860 unique masters (335 duplicates inherit), 743 easy · 573 medium · 893 hard · 201 manual Zones: Zone | Files | Size | Easy | Medium | Hard | Manual 04 Work Zone | 2,240 | 8696.5 MB | 0 | 0 | 0 | 0 05 Approved Library | 1,410 | 4271.7 MB | 315 | 379 | 263 | 12 02 Toolkit | 1,295 | 1261.0 MB | 257 | 100 | 606 | 184 00 Start Here | 110 | 184.6 MB | 28 | 20 | 6 | 1 03 Knowledge | 179 | 77.8 MB | 91 | 47 | 13 | 4 01 Instructions | 79 | 9.5 MB | 48 | 24 | 4 | 0 (root files) | 9 | 3.3 MB | 4 | 3 | 1 | 0 _Graph | 579 | 273 KB | 0 | 0 | 0 | 0"},{"f":196,"x":"Partner | Masters | Easy | Medium | Hard | Manual | Size (knowledge)/partners.html | 1 | 0 | 1 | 0 | 0 | 13 KB (knowledge)/partners.md | 1 | 1 | 0 | 0 | 0 | 2 KB GSOs/Kinship | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Harlan | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/CoreCraft | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Crescent Group | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Beacon Health | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Dorian Health | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Broadview | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Prisma Devices Partners | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/OneSix | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/ProBeam | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Purewell | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Crestline Demo Alliance | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Comet Health | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Choice Devices Mgmt | 1 | 1 | 0 | 0 | 0 | 1 KB","h":"Per-partner workload (unique masters; batch-ordering seed)"},{"f":196,"x":"GSOs/Inkstone | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/SmartSpan | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Sunrise Brands | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Solstice Source | 1 | 1 | 0 | 0 | 0 | 1 KB GSOs/Summit West | 1 | 1 | 0 | 0 | 0 | 1 KB (knowledge)/brookfield | 2 | 1 | 1 | 0 | 0 | 16 KB (knowledge)/aurora | 2 | 1 | 1 | 0 | 0 | 14 KB (knowledge)/larchwood | 2 | 1 | 1 | 0 | 0 | 14 KB (knowledge)/biosummit | 2 | 1 | 1 | 0 | 0 | 14 KB (knowledge)/caravelle | 2 | 1 | 1 | 0 | 0 | 15 KB (knowledge)/brightpath | 2 | 1 | 1 | 0 | 0 | 14 KB (knowledge)/delta-craft | 2 | 1 | 1 | 0 | 0 | 13 KB (knowledge)/keystone-and-lumen | 2 | 1 | 1 | 0 | 0 | 16 KB (knowledge)/clearform-art-and-align | 2 | 1 | 1 | 0 | 0 | 16 KB (knowledge)/mxr-and-marchand | 2 | 1 | 1 | 0 | 0 | 13 KB","h":"Per-partner workload (unique masters; batch-ordering seed)"},{"f":196,"x":"(knowledge)/unionsix | 2 | 1 | 1 | 0 | 0 | 14 KB (knowledge)/openform | 2 | 1 | 1 | 0 | 0 | 14 KB (knowledge)/northpoint | 2 | 1 | 1 | 0 | 0 | 15 KB (knowledge)/silverton | 2 | 1 | 1 | 0 | 0 | 16 KB (knowledge)/arden | 2 | 1 | 1 | 0 | 0 | 15 KB Tech & Software/Vista Specialty | 7 | 5 | 2 | 0 | 0 | 306 KB Tech & Software/Hargrove & Co | 8 | 3 | 5 | 0 | 0 | 420 KB Calibration & Alignment/Trueline | 10 | 7 | 3 | 0 | 0 | 185 KB GSOs/Vantage Devices+ | 20 | 1 | 8 | 11 | 0 | 63.7 MB Anchor Partners/Keystone | 22 | 3 | 7 | 12 | 0 | 50.7 MB GSOs/Fairline | 24 | 10 | 8 | 6 | 0 | 146.2 MB Calibration & Alignment/ClearForm ART | 25 | 9 | 14 | 2 | 0 | 10.0 MB Anchor Partners/BioSummit | 27 | 10 | 6 | 11 | 0 | 56.0 MB GSOs/Larchwood | 34 | 12 | 17 | 5 | 0 | 102.1 MB","h":"Per-partner workload (unique masters; batch-ordering seed)"},{"f":196,"x":"GSOs/Parkline | 36 | 11 | 16 | 8 | 1 | 53.0 MB Anchor Partners/Lumen | 36 | 10 | 25 | 1 | 0 | 25.7 MB GSOs/BrightPath | 39 | 14 | 13 | 9 | 3 | 98.9 MB GPOs/Silverton | 39 | 16 | 15 | 8 | 0 | 127.4 MB GSOs/UnionSix | 50 | 19 | 14 | 17 | 0 | 168.2 MB Anchor Partners/Trellis | 51 | 23 | 19 | 9 | 0 | 83.5 MB Anchor Partners/Caravelle | 57 | 23 | 18 | 16 | 0 | 240.0 MB Anchor Partners/Delta Craft | 101 | 10 | 11 | 80 | 0 | 460.8 MB Anchor Partners/OpenForm | 135 | 27 | 73 | 29 | 6 | 264.8 MB Folder tree (every folder, with its own file count): 00 Start Here/ (11 files) _archive/ (19 files) 2026-07-13-md-canonical-flip/ (1 files) asset-directories-2026-06-11/ (2 files) asset-directories-2026-06-16/ (1 files) asset-directories-2026-07-13/ (2 files) operating-hub-2026-07-13/ (2 files)","h":"Per-partner workload (unique masters; batch-ordering seed)"},{"f":197,"x":"t; HISTORICAL SNAPSHOT (2026-08-05). This is the intake record as gathered at kickoff; the brand has since evolved (Midnight v0.6, the 12 Custom LLM color names). Current design truth: 01 The Brain/Brand/custom-llm/brand-sheet.md. ⚠️ HIGHLY INTERNAL, the project internal only. Nothing external until launch (target 2026-09-01, may slip to 10-01). Template spec: v1.0 · Compiled by Atlas 2026-08-05 from Jordan*'s inputs + Custom LLM Knowledge.md + the 2026-08-04 marketing transcript · the first assembly on this brain system. Open questions are numbered Q-# and double as the future brain's questions register."},{"f":197,"x":"Name: Custom LLM (with a K, from \"Spek\"trum + Apex). Trademark secured (Dana* + attorney). ™ placement rule: the ™ goes after \"Custom LLM,\" never after a longer name. What it is: the new parent entity/brand over the Apex + the field network rebrand. Presents publicly as a neutral third-party holding company (PE-style) that acquired *both* companies. The world must never read Custom LLM as \"Apex Instruments renamed.\" Origin story (from Jordan*, 2026-08-05): began 1945 as Southern California devices craft → ~8 decades → uniting legendary master labs + pioneering digital workflows + FDA-registered manufacturing infrastructure; bridges timeless artisanry and modern engineered operating procedures.","h":"1 · Identity → L1, L3, Facts"},{"f":197,"x":"Brand feel (from the sprint brief): \"modern, streamlined, engineered with precision.\" Narrative: two companies with unique advantages become a super devices-technology company; intrigue from an unknown name. Language observed in the drafts: \"legendary,\" \"engineered,\" \"uncompromised,\" \"artisanry,\" \"at scale.\" Q-8: 3 to 5 voice adjectives + banned words for Custom LLM (inherit Apex's list? add rebrand-specific bans, e.g. \"rebrand,\" \"takeover,\" \"rebrand\"?). → Q-9: 3 writing samples in the voice you want (Avery*'s press-release draft would be sample #1, pending Dana*'s OK). →","h":"4 · Voice → L4"},{"f":197,"x":"THE RULES ABOVE ALL: nothing Custom LLM-related shareable, publishable, or visible outside the project circle until launch. No Custom LLM content in any Apex-team-visible surface. The world never reads Custom LLM as Apex renamed, holding-company voice always. ™ after \"Custom LLM\" only. Never invent the field network facts, the review file is sealed (even C-suite can't see internals until signing); all the field network numbers are research estimates, marked as such. Pricing commitments are locked promises: match the field network pricing ≥18 months; meet-or-beat the field network TAT, never restate loosely. Brand elements are PENDING/PROPOSED until leadership locks them, every branded output carries the flag.","h":"5 · Hard rules → L3"},{"f":197,"x":"Mock logo (Jordan*, interim): photoreal glass lightning-bolt \"S\" on midnight. Hero-render only, an SVG flat derivation is REQUIRED for the kit (favicon, mono, print, knockout). Test palette (Jordan*'s sports-rebrand research): White Solid #F4F5FA · First Draft #C8FF00 · Magic Ink #0247FE · Midnight Edition #0C121B, with measured contrast (19.28:1 / 17.75:1 / 6.29:1 / 18.78:1) + a blue↔neon gradient ramp + button set (light: ink-filled/outline/midnight · dark: neon-filled/neon-outline/white). Surface law observed in Jordan*'s samples: First Draft is a DARK-surface accent only (neon on white ≈ 1.1:1, never text on light); on light surfaces the accent is Magic Ink.","h":"8 · Brand → L8, status: PROPOSED (sprint in flight, leadership picks)"},{"f":197,"x":"The launch website (info page + leadership page + contact page, Jordan* owns, deliberately tiny) The announcement kit (designed press release + og/social cards + LinkedIn announcement set) The retention/welcome kit (the field network-customer welcome piece + Sendoso gift inserts + account-manager one-pager) Full menu enablement can wait for the brand lock; these three carry the launch. 10 · Modules & infra: Website module: ON (tiny 3-page launch site, draft-gated, on Jordan*'s AI infrastructure). Meetings module: ON (Tue/Thu + weekly ingestion, define the single ingestion flow w/ Sami* to avoid duplicates). Team pipeline: ON (5-person marketing team + approvers). Partner kits: LATER (post-merge). SEO/content: OFF at launch.","h":"9 · Collateral menu → L6/L7, Atlas's recommended day-one three (confirm: Q-15 →)"},{"f":198,"x":"Transcripts live canonically inside the brain: 01 The Brain/Facts/about-company/source-docs/ (verbatim) with distilled summaries in 01 The Brain/Facts/meetings/. This folder is the drop-point for NEW recordings before Jordan* files them (single-ingestion rule: Jordan* only)."},{"f":199,"x":"t; Living knowledge file for the Custom LLM brain build. Everything learned so far about the Custom LLM project, the rebrand, the team, and how the new brain should be set up. Update this file as new transcripts, documents, and decisions come in. t; ⚠️ HIGHLY INTERNAL. The rebrand below is known only to the marketing team and executives. Nothing in this file may appear in any external, shareable, or team-visible output until launch. *Created 2026-08-04 from the Weekly Marketing Updates transcript (meeting held Tuesday, Aug 4, 2026) + review of Jordan*'s prior brain builds. Owner: Jordan*.*"},{"f":199,"x":"Apex Instruments (Apex), a ~$60M/yr devices contract manufacturer (Orange County HQ), is in the final stages of the review process to acquire the field network, one of the largest and oldest devices lab networks in North America. Custom LLM (S-P-E-K-T-R-A) is the new parent entity/brand created for the deal. The name is a nod to Apex Instruments (the \"Spek\" + the K for Apex). Registration and trademark are already secured (Dana* drove this with the trademark attorney).","h":"1. The headline: what Custom LLM is"},{"f":199,"x":"Estimated revenue $300M, $500M/yr; ~40 sites across the country; big education/training center in Florida with a hard-to-get *international accreditation*; owned by private equity; est. 500 to 1,000 employees. One of the top labs alongside Grandview Labs, Dashwood, Row Devices. Strong brand foothold but popularity dwindling ~5 to 10 years; high attrition; hasn't modernized workflows, which is why a $60M company can buy them. ~80% of the field network's business is private practice, the opposite of Apex's GSO focus. Private practice cares most about price and turnaround time. the field network uses the CRM for marketing (huge win for Sami*) and Salesforce for sales.","h":"About the field network (from research, not confirmed documents)"},{"f":199,"x":"Once the news leaks, Grandview Labs will 100% run campaigns to scoop the field network's customers. Retaining acquired business = retaining the rebrand's value. Pricing: match all current the field network pricing for at least the first 18 months. Turnaround: meet or beat the field network's current TAT. Heavy gifting strategy via Sendoso (welcome boxes, thank-you boxes, service-recovery gifts), part of why the pricey Sendoso contract was approved. Incentive programs for staying are pitched to leadership; awaiting approval (monetary incentives).","h":"Retention / anti-poaching strategy"},{"f":199,"x":"Avery* is blocking new projects for a ~2-week sprint. Deliverable to leadership: a handful of logo options + a handful of color options + a couple of font options → leadership picks top two → one round of revisions → done. No long back-and-forth. Workstream | Owner | Notes Logo | Josie (Josie*) | Full creative freedom; doesn't need to nod to the Apex logo. At least one option with movement/animation (team liked ORENDA's animated logo, Europe-based repair group). She starts on paper/iPad + stylus. Fonts | Josie* + Morgan* | Modern, highly readable digitally AND in print; avoid expensive licenses. Morgan* consults as the \"full-time proofing genius.\"","h":"2. The 3-week brand sprint (the team's current #1 priority)"},{"f":199,"x":"Agreed on the call: Copy the current Apex LLM brain to the desktop as a reference (done, it's in 05 Reference Examples/Apex LLM (reference copy)/). Jordan* is NOT overriding the Apex brain; Custom LLM gets a brand-new brain. Roughly 50% of the Apex brain carries over, rules, skills, structure, since Jordan* and Sami* built a lot that crosses over. Sami*: bring the skills, but no Apex branding. Work incrementally: have the model build a transfer plan and move things over one at a time with review, \"if you give it too much and it takes on too much, it gets dicey.\" Feed the brain (as materials arrive): This meeting transcript ✅ (in Call Transcripts/)","h":"3. The Custom LLM brain plan (Jordan*'s build)"},{"f":200,"x":"the project, Internal · Mapped 2026-08-06 from the live Apex LLM (read-only) · ~2,960 indexed files, 6 zones Every Apex zone below shows: what lives there, and where its equivalent now exists in the Custom LLM brain (01 The Brain/). Status legend: ✅ built and filled · 🏗 structure created, fills later · ⏳ waits on brand-lock or the announcement. How the two architectures line up (the one-glance version): Apex zone (numbered) | Custom LLM equivalent (named) | Status 00 Start Here | README.md + ROADMAP.md + Log/ + project 00 Start Here/ | ✅ 01 Instructions | Rules/ | ✅ core · 🏗 output-type mediums 02 Toolkit | Split by function: Skills/ + Templates/ + Brand/custom-llm/ + Facts/reference-index/ + Hub/ | 🏗 03 Knowledge | Facts/ | ✅ core · 🏗 partner/product trees"},{"f":200,"x":"04 Work Zone | Drafts/ (per-person pipelines + _shared) | 🏗 05 Approved Library | Approved/ (full partner-category tree) | 🏗, fills via the migration chunks 00 Start Here, the front desk *(110 files)*: The team's front door: orientation, house rules, ownership, status, rollout collateral. Key files: _readme (\"one shared brain\"), _home.html + _chatbot.html (branded pages), team-start-here, new-teammate-setup, operating-hub. Subfolder | What it holds | Custom LLM home orientation/ | what-is-this, getting-started, the v1 blueprint | README.md ✅ + Hub at activation ⏳ finding-things/ | where-does-x-live, naming conventions, contacts | CLAUDE.md §5 routing ✅ + Rules/naming-conventions.md ✅"},{"f":200,"x":"Apex's biggest zone; in the Custom LLM layout its jobs split into named layers. skills/generation/ (13) | The build skills: apex-email, landing-page, partner-microsite, executive-summary, price-sheet, print-one-pager, welcome-flyer, whats-needed-guide, quick-start-guide, docket-lab-slip, powerpoint (30 layouts), roman-style, print-social system | Skills/, 11 custom-llm-* generation skills 🏗 (stubs + empty reference/ folders; each activates when its gold standard is built post-brand-lock) skills/prompt-enhancer + _SKILL-PATTERN | The silent request gate + the reference-first doctrine | ✅ both live skills/maintenance/ (3) | folder-cleanup, partner-site-update, twin-sync | Skills/maintenance/ 🏗 stubs","h":"02 Toolkit, what the AI builds with *(1,295 files)*"},{"f":200,"x":"_personal/ (8 people) | Per-person 7-stage pipeline: 00-inbox → 01-scratch-pad → 02-active-projects → 03-for-review → 04-my-approved-work → 05-returned-for-edits → 06-archive | Drafts/, pipelines created for Avery*, Jordan*, Sami*, Morgan*, Josie* 🏗 (the project circle; more added post-announcement) _shared/ | Cross-team projects (rebrand, website redesign, imports) | Drafts/_shared/ 🏗 work-zone-pipeline.md | The review front door: draft → review → approve → promote | Drafts/README.md ✅ (position = status)","h":"04 Work Zone, drafts, never official *(1,827 files)*"},{"f":200,"x":"partners/ in 5 categories | GSOs (25) · Anchor Partners (7) · GPOs · Calibration & Alignment · Tech & Software, each partner's approved kit, _card.md fronted | Approved/partners/, full category tree created 🏗, fills chunk-by-chunk via the migration plan (1,200 files, ~15 review batches) price-sheets/ (+ _PRICE-INDEX) | The pricing authority + 24 mirrors | Approved/price-sheets/ ✅ folder + authority pattern already in Facts/about-company/pricing.md internal/ · locations/ · product-lines/ · Private Practice/ | Presentations, townhalls, tools, Apex Texas kit, product collateral, direct-practice kit | Approved/, all four 🏗","h":"05 Approved Library, canonical truth *(1,410 files)*"},{"f":200,"x":"CLAUDE.md/AGENTS.md (the contract, Custom LLM ✅) · Master-Asset-Directory.md (369KB hand-patched index, Custom LLM will use generated indexes instead) · _Graph/ (579 Obsidian nav notes, quarantined, not mirrored, navigation derives from structure) · partner-dashboard-feasibility.md (stalled experiment) · ⚠️ Custom LLM_Domain_Options_CEO.pdf + .xlsx sit in the Apex root, Custom LLM material in an Apex-team-visible folder; recommend moving them into this project folder. What was scaffolded into the Custom LLM brain today (the 🏗 items)","h":"Root files & oddities worth knowing"},{"f":201,"x":"the project, Internal · Audited 2026-08-08 from Jordan*'s fresh Apex LLM copy (~/Downloads/Apex LLM Copy). Companion to the 2026-08-06 network map; this version catches everything new since, and turns the diff into the build list. Goal per Jordan*: Custom LLM matches Apex's function, then beats it, more capable, more collaborative, always evolving. Legend: ✅ built in Custom LLM · 🏗 scaffolded (structure + _about.md, fills on a known trigger) · ⏳ gated (brand-lock / announcement / signing) · ✗ not started (net-new build) · ⭐ Custom LLM is already AHEAD of Apex here."},{"f":201,"x":"Apex has | Custom LLM status 6-zone layout (00 Start Here → 05 Approved Library), CLAUDE/AGENTS contract, md+html twin doctrine, position=status | ✅ Mirrored 1:1 in the named-layer layout; every zone present Master-Asset-Directory.md (369KB, hand-patched) | ⭐ Custom LLM generates it (generate-asset-directory.py, 234 files) and generates twins (generate-twins.py), Apex still patches by hand _Graph/ (579 Obsidian nav notes) + .obsidian | ✅ Deliberately not mirrored, navigation derives from structure (decision stands) One tabbed entry point | ⭐ Apex has none; Custom LLM's Master Guide (9 tabs + the Big Board) is already beyond Apex Source registry / ingestion discipline | ⭐ Custom LLM-only (source-registry.md + distillation schema + single-ingestion rule)","h":"1. File structure + core machinery"},{"f":201,"x":"Proposal agent (brief + tone + template → finished proposal) | ✗ Net-new. Build AFTER first gold standards exist Onboarding agent (welcome flyer + lab slip + microsite + checklist per new partner) | ✗ Net-new. Natural fit: the field network account-onboarding wave makes this Custom LLM's FIRST agent, at real scale Account-brief agent (Team Directory + the CRM + collateral → refreshed brief in Knowledge) | ✗ Net-new; needs the CRM connection decision ⭐ Opportunity: Apex never shipped these. Custom LLM ships them and leads. Candidate #4: an ingest agent (transcript → distilled meeting → registers updated), which Custom LLM half-has as skills already","h":"4. Agents (Apex's newest layer, defined 3, all still \"planned\" there)"},{"f":201,"x":"about + locations + people-and-org | ✅ Company overview + team/escalation ⭐ (expertise map) · 🏗 locations (3 Apex sites + the field network's 50+ in phase 2) 16 partner briefs w/ collateral inventories | 🏗 Port de-branded during migration; the field network partners added in phase 2 products-services: product-levels · service-lines · TAT-by-product · scanner-compatibility · mount-education · sku-catalog | 🏗 Ports post-announcement WITH content (~26MB datasets); Q-4 gates the shape meetings + decisions + competitive + glossary | ✅ All live ⭐ (distillation schema + supersession-annotated decisions) · 🏗 glossary","h":"5. Knowledge (03 Knowledge ↔ Facts/)"},{"f":201,"x":"7 person pipelines: Avery* · Jordan* · Dana* · Josie* · Nora* · Morgan* · Sami* | 🏗 Custom LLM has the project five (Avery* · Jordan* · Josie* · Morgan* · Sami*); ADD Dana* + Nora* (+ the field network-side people) at announcement _shared cross-team projects | ✅ + ⭐ review-queue/ (retention · announcement · website) already carrying 7 live drafts work-zone-pipeline.md front door | ✅ 7. Approved Library + partners + microsites: 37 partners in 5 categories (25 GSOs · Silverton · 7 mount · Trueline + ClearForm ART · Hargrove & Co + Vista Specialty), each kit _card.md fronted | 🏗 Full category tree scaffolded; fills via the 15 migration chunks (1,200 files) post-brand-lock","h":"6. Work Zone"},{"f":201,"x":"Chassis: microsite · presentations · print (+ print-pdf-shell) · social · email-forms · briefings · guides · welcome-flyer · components · _partials · _project-template · product-page | 🏗 Arrive WITH content at brand-lock (Evergreen tokens), most port from Apex re-skinned prompt-library (23 prompts) | ✅ Seeded (16) + grows from real sessions template-audit discipline | ✅ Pattern adopted (audits live in Log/) ⭐ launch-copy/ (the GTM drafted library), Apex has no equivalent 9. Team Hub (Apex website-hub → Custom LLM Hub, the \"eventually make this\" item): llm-homepage · team-start-here · _chatbot front door · operating-hub · team-sharing guide | ⏳ HUB-PLAN.md staged + operating guide written; build gated on brand-lock, deploy on announcement/Q-16 (the rules holds it, deliberately)","h":"8. Templates"},{"f":202,"x":"Internal · the project. Written 2026-08-11 from the scored live map (03 Knowledge and Sources/Apex-LLM-LIVE-MAP.md, Phase 2). This is the execution plan for Jordan*'s directive from the 8/11 call: every asset in the Apex LLM gets recreated for the new brand. Companion to CUSTOM LLM-REBRAND-MIGRATION-PLAN.md (the original strategy doc); this plan supersedes its brand-lock gate per Jordan*'s 8/11 ruling and adds the batch math. The rules every batch follows (Jordan*, 2026-08-11): Layouts and structure stay, pull and reskin, never rebuild from scratch. Colors go Evergreen now, the twelve tokens, the surface law, nothing else. The logo slot keeps the Apex Instruments logo until the new logo is chosen; then one sweep updates every file."},{"f":202,"x":"Text says Custom LLM, rewritten from the brain's knowledge (one-story rebrand framing; claims only from the claims file; pricing only from the price tables). Anything undecided becomes a {{slot}} with its Q number, contacts per Q-28/58, the endorser line per Q-20, price sheets pending the Q-60 master Excel. Everything produced is internal-only until the announcement, it says Custom LLM, so it lives only in this brain and this site. The Apex library is never touched. Sources copy out read-only; nothing writes back."},{"f":202,"x":"5,901 files live in the Apex LLM. 2,745 are in migration scope (Work Zone working files, _archive/ history, and the _Graph/ overlay never migrate). Content-hash deduplication collapses those to 1,860 unique masters, 335 duplicates inherit their master's rebrand for free. Difficulty | Masters | What it means EASY | 743 | text swaps (.md .txt .csv .json) MEDIUM | 573 | the Swap Protocol (.html .svg .docx .xlsx) + PDFs with an HTML master HARD | 893 | design regeneration: images, masterless PDFs, decks MANUAL | 201 | judge first: video, archives, fonts, odd types","h":"The math (Phase 2, scored 2026-08-11)"},{"f":202,"x":"Two big discounts hide in the HARD column: 606 of the 893 sit in 02 Toolkit, mostly Apex brand assets (logos, marks, mockups) that are not rebranded but replaced outright by the Custom LLM Brand OS kit, and skill reference images that regenerate with the skills. The honest production estimate for true design work is ~300 hard masters, concentrated in Delta Craft (80) and the partner microsites' image cards. What does NOT migrate: 04 Work Zone (2,240 working files, people's drafts, not deliverables) · every _archive/ (history stays Apex history) · _Graph/ + .obsidian (navigation overlay; the Custom LLM brain has its own Asset Directory) · Apex brand assets in 02 Toolkit/brand-assets (replaced by the Custom LLM Brand OS, not converted).","h":"The math (Phase 2, scored 2026-08-11)"},{"f":202,"x":"Ordering principle: shared chassis first (highest leverage), then partners smallest → largest so the machinery hardens before the monsters, libraries interleaved as light waves. One batch = one review for Jordan*. Batch 0, The chassis. The deduplicated shared masters and 02 Toolkit/templates categories (briefings, components, email-forms, guides, microsite frame, presentations, print, social, welcome-flyer). Build the Evergreen swap kit once, token map, Apex-logo-slot convention, Custom LLM text blocks, and every later batch inherits it. This batch also ports the template chassis the Custom LLM Templates/ zone is missing.","h":"The batches"},{"f":202,"x":"Batches 0 to 2 are each a single working session. Partner batches at fleet speed run 20 to 35 masters per session including verification and the report. The whole campaign is roughly 18 to 22 working sessions of production, comfortably done well before Sept 1 if we run several per week, with Delta Craft and the manual-review list as the long tail. The logo sweep at brand-lock is one extra session across everything already produced. Standing gates woven in: Q-20 endorser line and Q-28/58 contact blocks stay slots until answered · price sheets rebuild from the Q-60 master Excel when it lands, not from stale PDFs · BioSummit bundle numbers carry the Q-57 flag until the reviewer rules · the brand-lock logo sweep is pre-planned, not a surprise.","h":"Pace, honestly"},{"f":203,"x":"Status: QUEUED. Internal · the project. Saved 2026-08-05 per Jordan*'s direction. Triggers (all must be true before work starts): Custom LLM brand FINALIZED by leadership: color direction picked, Josie*'s production logos delivered (replaces the interim Tier H/W set), fonts locked (Q-13) Brand OS updated to v1.0 with the approved identity (Swap Protocol run on the winning direction; production vectors replace the traced set) Jordan* has the fuller picture from Avery* + leadership (Q-4 sub-brands; Q-11 comm docs ARRIVED 2026-08-08, GTM v4.1, Integration brief, both Comm Plans, all ingested)"},{"f":203,"x":"A. Collateral rebrand sweep, go through the entire Apex LLM file set (reference copy: 05 Reference Examples/Apex LLM (reference copy)/) and re-brand: keep the information, images, layout, and general setup; swap every Apex logo → approved Custom LLM logo set, all colors → Custom LLM tokens, fonts → Custom LLM stack, and apply the relevant brand rules (name rule, ™ rule, surface law, dash policy).","h":"The work"},{"f":203,"x":"B. Chunked by partner, Jordan* reviews each chunk. One partner's collateral at a time (Anchor Partners first candidates: Trellis, BioSummit, OpenForm, Delta Craft, Lumen, Caravelle, Keystone; then GSOs; then price sheets / internal / product lines / Private Practice / locations). Each chunk: rebrand → Jordan* review → promote to custom-llm-brain/Approved/ → changelog. Nothing bulk-ships unreviewed. C. Knowledge migration, port/update the Apex brain's .md knowledge files into custom-llm-brain (partner briefs, product levels, TAT, scanner compatibility, mount education, etc.), de-Apex-branded and reconciled with Custom LLM voice/rules.","h":"The work"},{"f":203,"x":"Rebrand scope vs the \"both brands operate ~12 months\" rule: WHICH collateral becomes Custom LLM-branded vs stays Apex-branded during the transition window? (Ask Avery*, likely answer: internal + new-partner materials go Custom LLM; existing Apex partner collateral stays Apex until brand-merge. This gates chunk order.) · Does the field network collateral enter scope in phase 2? · Sub-brand architecture (Q-4) may change lockups mid-migration, confirm before chunk 1. Standing rule during migration: The Apex brain stays untouched and in production. All rebranded output lands in custom-llm-brain's Drafts → review → Approved pipeline. Nothing overwrites Apex's live materials until leadership's brand-merge decision.","h":"Open questions feeding this plan"},{"f":203,"x":"1,200 non-archive files. Heavy hitters: OpenForm 219 · internal 133 · Delta Craft 104 · Caravelle 61 · Trellis 58 · UnionSix 55 · locations 49 (44 = Apex Texas kit) · BrightPath 47 · Silverton 46 · Larchwood 39 · Parkline 38 · Lumen 36 · product-lines 29 · BioSummit 28 · Keystone 28 · Vantage 27 · price-sheets 26 · Fairline 25 · ClearForm ART 25 · Private Practice 23 · 19 folder-only GSOs (1 file each) · Trueline 10 · Vista Specialty 9 · Hargrove & Co 8. Proposed review chunks (~15 batches, one Jordan* review each): Trellis (58), the pilot. Full kit (microsite, price list, welcome flyer, guides, lab slip); proves the rebrand recipe before scale BioSummit + Keystone (56) OpenForm part 1, collateral (110) OpenForm part 2, product pages/images (109) Delta Craft (104) Caravelle + Lumen (97)","h":"Discovery: the actual scope (counted 2026-08-06 from the Apex Approved Library)"},{"f":203,"x":"GTM v4.1 §10 supplies the launch-facing inventory with owners and Day-1 priorities. It runs BEFORE and alongside the Apex-collateral sweep above; owners are proposed, confirmed at the T-7 huddle.","h":"The GTM's launch collateral inventory (merged 2026-08-08, this IS the professional first wave)"},{"f":204,"x":"Internal · the project. One entry per batch from CUSTOM LLM-REBRAND-BATCH-PLAN.md. Statuses: NOT STARTED · RUNNING · DONE. The site's Batch Board renders from this file on every rebuild, update the status line when a batch completes, and the board checks it off. Foundation: B0, The chassis and the swap kit: status: RUNNING masters: ~90 what: The deduplicated shared masters and every Toolkit template category (briefings, components, email-forms, guides, microsite frame, presentations, print, social, welcome-flyer). Builds the Evergreen token map, the Apex-logo-slot convention, and the Custom LLM text blocks every later batch inherits."},{"f":204,"x":"status: NOT STARTED masters: 50 what: The 19 one-file GSO stubs plus all 15 partner knowledge briefs, ported de-branded into Facts/partners. Closes most of Q-34 and unlocks the four staged agents. Machinery shakedown batch. Partner batches, ascending: B2, Vista Specialty + Hargrove & Co + Trueline: masters: 25 what: The three smallest real partners in one pass (7 + 8 + 10 masters). B3, Vantage Devices+: masters: 20 what: 11 hard (price-sheet imagery); price data waits on the Q-60 master Excel. B4, Keystone: masters: 22 what: FRX workflow guides; 12 hard.","h":"B1, Every partner stub and knowledge brief"},{"f":204,"x":"masters: 24 what: Live campaign partner, coordinate with Sami*'s running sequences. B6, ClearForm ART: what: Mostly medium; fast batch. B7, BioSummit: masters: 27 what: The Q-57 bundle-price fix lands here. B8, Larchwood: masters: 34 what: Active wearguard campaign, sequence-aware. B9, Parkline: masters: 36 what: Standard partner batch. B10, Lumen: what: Only one hard master; fast despite size. The heavies: B11, BrightPath: masters: 39 what: Three manual items need a judgment call first. B12, Silverton: what: The GPO, RFP-relevant; the vendor launch material connects here.","h":"B5, Fairline"},{"f":204,"x":"what: Large microsite + FRX guide set. B14, Trellis: masters: 51 what: The original pilot candidate; ScanBridge workflow collateral. B15, Caravelle: masters: 57 what: 16 hard; heavy print set. B16, OpenForm: masters: 135 what: The biggest, recent direct-mail campaign, mostly medium HTML masters. B17, Delta Craft: masters: 101 what: Runs LAST as its own project: 80 hard, mostly image-native legacy. Keep-or-archive judgment pass before anyone rebrands. Library waves: W-A, Instructions deltas: masters: 76 what: Mostly easy text; much already exists here as Rules/, port the gaps.","h":"B13, UnionSix"},{"f":204,"x":"masters: ~60 what: Products-services, competitive, locations. Closes Q-24/25 gaps. W-C, Start Here: masters: 55 what: Orientation docs, adapted to Custom LLM rather than copied. W-D, Toolkit remainder + the manual list: masters: ~150 what: Prompt-library port plus the 184 manual-review items (fonts, video, archives). Judgment list, not blind migration. Apex brand assets are excluded, the Custom LLM Brand OS replaces them outright.","h":"W-B, Knowledge, non-partner"},{"f":205,"x":"Avery*'s work zone. Position = status: work moves through the numbered stages; 03-for-review is what approvers check. Nothing here is official."},{"f":206,"x":"HIGHLY INTERNAL, the project internal only. You are resuming operator duty on the Custom LLM Company Brain with Jordan Vale* (he calls this assistant Atlas). Nothing here may reach any external, shareable, or Apex-team-visible surface before the public announcement. Start here: Open the session at the brain root so the constitution auto-loads and the slash commands exist: cd \"$HOME/Library/CloudStorage/OneDrive-SharedLibraries-ApexInstruments 2 2/Custom LLM Brain - Documents/Custom LLM Brain\" && claude"},{"f":206,"x":"That folder is the SharePoint library synced by OneDrive: it is canonical, but verify that before trusting it (see the sync lesson below). If the path is missing, the OneDrive mount suffix drifted: ls ~/Library/CloudStorage/ and take the newest OneDrive-SharedLibraries-ApexInstruments* entry. Every script uses relative paths, so only this document carries absolutes. 01 The Brain/CLAUDE.md and AGENTS.md load automatically and are the law. Read next: the top of 01 The Brain/Log/changelog.md (state of record, newest first), then 04 Plans/CUSTOM LLM-REBRAND-BATCH-PLAN.md and 04 Plans/REBRAND-BATCH-TRACKER.md."},{"f":206,"x":"Phase 4, the SharePoint site build, is MOSTLY DONE. Phases 1 to 3 are complete. Done in Phase 4: The left navigation is rebuilt and live, 15 entries: the five zone folders deep-linked into the library, plus the eight team-site views. Better than Apex's, which has no team-site links. The home page is PUBLISHED on https://demo-tenant.sharepoint.example/sites/Custom LLMBrain. The stale lock from the previous session had expired on its own. The page is heading, two intro lines, then a Hero tile grid matching Apex's home exactly (five tiles is the layout's hard cap): Start Here, The Brain, Work Zone, Asset Directory, The Team Site. The first three deep link into the library, the last two into the Cloudflare site.","h":"Where the work stopped (2026-08-11 night)"},{"f":206,"x":"Git mirror (history, never edit there): ~/Documents/GitHub/custom-llm/Custom LLM Brain/, repo djvonfrank/custom-llm, private. Sync command, exactly: rsync -a --delete --exclude='.DS_Store' --filter='protect .gitkeep' --filter='protect _answers-worker' \"<brain>/\" \"$HOME/Documents/GitHub/custom-llm/Custom LLM Brain/\" After a folder rename or move, rsync's protect filters leave ghost directories behind in the mirror: delete them by hand, then commit. Team site: [endpoint removed for demo] built ONLY by 01 The Brain/Skills/quality-control/generate-master-guide.py and generate-asset-directory.py. Never hand-edit an output.","h":"The machine"},{"f":206,"x":"Opus only. Every subagent and workflow agent pins model: opus. No em or en dashes in anything shippable. UNKNOWN over guess; unknowns become numbered Q questions. History files (changelog, work log, decisions log, meetings, source docs, Archive) are never rewritten; supersessions get new entries. Humans are the only approval gate (Jordan* then Avery*). Agents advise. /promote acts only on Jordan*'s explicit per-piece say-so. A change is not done until the changelog entry is written and the sync ritual has run. Do not raise the Northgate IT question again. Jordan* declined it. The Apex LLM library at ~/Library/CloudStorage/OneDrive-ApexInstruments/Apex LLM - Documents/ is READ-ONLY from here, always.","h":"Jordan*'s standing rules"},{"f":206,"x":"Waiting on Jordan*: Full Disk Access for /bin/zsh, or the auto-publish job stays dormant. Batch 0 approval. Report: 05 Work Zone/_shared/migration/batch-0/BATCH-0-REPORT.md. Three calls inside: the pewter token substitute (Stone #597276 or Basalt #476467), the print font stack (Inter/DM Sans vs IBM Plex), and the {{portal_url}} slot. On approval: promote the chassis to 01 The Brain/Templates/<category>/, generate twins, mark B0 DONE, rebuild. The people grants, whenever the team widens. Structure is ready.","h":"Open threads, by owner"},{"f":207,"x":"What it is. A point cloud with a scanner line sweeping across it, lighting each point as the beam passes, the on-site scan that begins every case. Titanium-blue lattice, Sea Glass points, Electric Orange at the brightest part of the sweep. Why it's worth keeping. It's the one background no devices competitor can borrow: it's literally the Custom LLM production process. It says \"digital manufacturer\" before a word is read, where the Midnight Green says \"apex / the name.\" Where it would land best The launch website's manufacturing or technology page (the engineered half of the rebrand story) A Brand OS v1.0 section on the digital workflow The Hub's landing surface at announcement, if the Hub wants its own signature","h":"THE SCAN MESH, parked 2026-08-08, Jordan*'s call: \"save for later, would be great on the right page\""},{"f":207,"x":"Any partner-facing microsite where the scan-to-bench-unit pipeline is the pitch The working code. Fully built and running in hero-background-options.html, Option 4. Self-contained canvas, no dependencies: a projected grid with a sinusoidal height field, faint lattice lines, and a moving highlight band that brightens points within ~120px. Drop the #cvMesh block (CSS + the IIFE) into any dark surface and give it a canvas. Notes for when it ships Needs a dark surface (Midnight Green / Inkwell), the lattice disappears on light Reduced-motion: freeze the sweep at ~40% and keep the lattice static Density is COLS/ROWS (42×22 at hero scale); drop to ~28×14 for smaller panels","h":"THE SCAN MESH, parked 2026-08-08, Jordan*'s call: \"save for later, would be great on the right page\""},{"f":207,"x":"Option 1 · The Apex Split, white beam through a prism fanning into the twelve colors. The runner-up; strongest literal expression of the name. Option 3 · The Current, the Brand OS's own 3.6s traverse with 150ms stagger, as ambient bands. Option 5 · Spectral Readout, emission-apex lines as instrument output. Option 6 · The Charge on Chrome, brushed metal with a specular sweep + the Charge running the bolt (5.2s loop). Shipped instead: Option 2 · The Midnight Green (home hero, 2026-08-08), with the cursor acting as focus and each region revealing a brain capability.","h":"The other four explored (2026-08-08), all in the same file if wanted later"},{"f":207,"x":"What it is. The slow star field that carried the home hero from 2026-08-08 to 2026-08-12: ~1 point per 9,000px², ~9% of points stretched into tiny contour the way a spectrograph splits starlight, drawn straight from the Midnight Green token's own line. The cursor acted as focus: stars within 150px flared and brightened. Why it's worth keeping. It was Jordan*'s pick from six built options, it's the token made literal, and it's the only one of the set that whispers rather than performs. Right surface: any dark page that needs atmosphere without motion drawing the eye, a 404, a loading state, the Brand OS's own cover.","h":"THE MIDNIGHT GREEN, parked 2026-08-12, replaced on the home hero by Liquid Chrome at Jordan*'s direction"},{"f":207,"x":"The working code. The complete IIFE and CSS live in this same folder's hero-background-options.html (Option 2) and in git history at generate-master-guide.py before commit 2026-08-12 (search \"THE MIDNIGHT GREEN\"). Vanilla canvas 2D, dpr-aware, resize-safe, reduced-motion freezes the drift. Notes for when it returns Needs the deep navy ground; the contour stripes vanish on anything lighter The scrim (.deep-scrim) that kept text legible is generic and still in the builder, reused by Liquid Chrome Density knob is the /9000 divisor; halve the count for panels smaller than a hero","h":"THE MIDNIGHT GREEN, parked 2026-08-12, replaced on the home hero by Liquid Chrome at Jordan*'s direction"},{"f":208,"x":"Read live from /sites/SKLLM and /sites/Custom LLMBrain through the SharePoint API. The Apex library is read only from this brain, always, and nothing was written there. The short answer: Apex's home page is five stacked bands. Custom LLM had two of them. The Hero tile grid is the one real gap that changes how the page feels, and it is the piece being added in this phase. Everything else on Apex's page is either a stock web part worth copying cheaply (People), a pointer to pages Custom LLM has not built yet (Directories and Tools), or something Custom LLM already does better somewhere else."},{"f":208,"x":"Custom LLM is ahead of Apex in two places worth protecting: the left navigation carries deep links into the library and into the team site, which Apex's does not, and the Custom LLM team site holds live surfaces (Plan, Agents, Skills, Batch Board, Team Questions) that Apex has no equivalent of at all. Band by band: Band | Apex's home page | Custom LLM's home page | Call 1. Title and intro | H1 plus intro paragraph | H1 plus two intro lines | Parity. Custom LLM's intro is better: it says what to do next."},{"f":208,"x":"2. Hero | Tiles layout, 5 tiles: Start Here, Approved Library, Toolkit, Asset Directory, People and Org. Each tile has a background image and a Learn more call to action. | Was missing | ADDED this phase as a 5 tile grid pointed at Custom LLM's zones and the team site. Images stay off until brand lock. 3. Directories and Tools | Quick links, CompactCard layout, 2 cards: Published Pages, Team Directory | Was missing | Deferred, and the reason matters. Both cards point at SharePoint pages Apex built and Custom LLM has not. See the page gap below."},{"f":208,"x":"The People web part on the home page. Roughly two minutes of work, no content to write, and it puts faces on the site the moment more of the team gets access. Low effort, real payoff. A Team Directory page, built from the team directory file that is already written. Medium effort. It is the page teammates actually use on the Apex side, and Custom LLM's source data is more complete than Apex's. The Directories and Tools card row, once there are at least two pages to point at. Adding it before those pages exist just recreates the placeholder problem this phase is removing. Sequence it after item 2. A Welcome page. Low value. The intro text and the How To page already carry this, and one more front door is one more thing to keep in sync.","h":"What is worth adding, ranked"},{"f":208,"x":"Thing | Apex | Custom LLM Left navigation | Library folders only | 15 entries: the 5 zone folders plus 8 deep links into the live team site A browsable brain outside SharePoint | None | The team site: Plan, Assets, Agents, Skills, Batch Board, Team Questions, How To Asset directory freshness | A page, maintained by hand | Regenerated from the real tree by generate-asset-directory.py Approval routing | Convention | Work Zone 02 Send for Approval plus the notification flow built this phase Change history | UNKNOWN, no equivalent found on the site | 01 The Brain/Log/changelog.md, surfaced as a team site tab","h":"Where Custom LLM is already ahead"},{"f":208,"x":"The People web part shows site members. Until the folder permissions land and the team is added, it will show two people. Add it, and it fills itself in as access rolls out. No separate work needed later.","h":"Open item"},{"f":209,"x":"One approved source of truth the AI reads before it writes a word.","h":"Custom LLM Company Brain"},{"f":210,"x":"Type | What happens when you click SCROLL | Slides you down the Home page to that section VIEW | Swaps the page body in place (Big Board, Changelog, etc., same file, no reload) DOC | Opens a styled document page in a new tab APP | Opens the big interactive Brand OS standalone in a new tab IMG | Opens a full-size logo PNG in a new tab About the component-map buttons you couldn't find: they exist and are live (I verified the deployed file is byte-identical to the build). They're the *small light-blue pill chips at the bottom edge of each card*, \"Read it,\" \"Day-1,\" \"The QA report.\" They're easy to miss, which is a design problem to fix in the nav rework, not a missing feature. Full list below under HOME · Inside.","h":"The five link types"},{"f":210,"x":"Label | Type Home | VIEW Plan · The Calendar | SCROLL Find a Document | SCROLL The Big Board | VIEW Prompt Library | VIEW Guides & Tools | VIEW Brand OS · Midnight | VIEW Team Questions | VIEW Decisions Log | VIEW Changelog | VIEW Rebrand Migration | VIEW Apex Parity Audit | VIEW HOME · hero: No links. (The orb, the title, and the six status pills are display only, the pills LOOK tappable but aren't. Worth deciding: make them link to what they describe, or restyle them flatter.) HOME · §pitch and §how: No links, pure reading sections.","h":"SLIDE-OUT MENU (the only nav on mobile)"},{"f":210,"x":"Card | Chip | Type | Opens The Constitution | Read it | DOC | CLAUDE The Constitution | Team cover page | DOC | Brain README How to act (Rules) | no chips, The fact layer | Overview | DOC | company-overview The fact layer | Day-1 | DOC | day-1-playbook The fact layer | Decisions | VIEW | Decisions Log The fact layer | Team | DOC | team roster What it can do (Skills) | Prompt library | VIEW | Prompt Library The Brand OS | Open the full Brand OS → | APP | v0.6 standalone The Brand OS | Tokens + gallery | VIEW | Brand OS view The send-ready library | Browse the library | DOC | launch-copy README The send-ready library | Press release | DOC | press-release-draft The approval lifecycle | The QA report | DOC | _qa-report Memory & accountability | Questions | VIEW | Team Questions","h":"HOME · §inside, the component map (9 cards, 19 chips)"},{"f":210,"x":"No links. One control: \"The full dated roadmap\" collapsible. (The four Q chips in the \"Due by Aug 15\" band are display only.) HOME · §find, the directory (46 DOC links, all new-tab): Controls: search box + category chips (All · Start Here · The Brain · Launch · Launch Copy · In Review · Facts · Brand · Plans · Logs · Knowledge). Category | Documents Start Here (1) | Project Plan The Brain (6) | CLAUDE · Questions for the Team · README · Roadmap · Hub Plan · Operating Guide In Review (8) | QA report · retention FAQ · welcome letter · contact page · info page · leadership page · fact sheet · internal brief Brand (9) | brand sheet · how-the-brain-uses-the-Brand-OS · Directions 1-4 · Brand OS v0.2 · Material Concept Prompts · Brand OS v0.6 standalone","h":"HOME · §plan"},{"f":210,"x":"No navigation links. Controls: search, 6 category chips, 23 Copy buttons (copy the prompt to clipboard). VIEW · Guides & Tools (8): Day-1 Playbook | DOC | day-1-playbook The Retention Engine | DOC | retention-engine Media & PR Plan | DOC | media-and-pr-plan Launch Copy Library | DOC | launch-copy README Operating Guide | DOC | operating-guide The Constitution | DOC | CLAUDE Project Plan & Status | DOC | project plan Changelog card | VIEW | Changelog VIEW · Brand OS (19): The full interactive Brand OS v0.6 | APP | the standalone How the brain uses the Brand OS | DOC | explainer The four explored directions | DOC | Direction-4 Midnight Material-concept prompts | DOC | staged prompts 15 gallery cards | IMG | each full-size mark PNG","h":"VIEW · Prompt Library"},{"f":210,"x":"No links inside, pure reading pages (the embedded registers). FOOTER: No links. EVERY DOCUMENT PAGE (the 46 styled twins): Custom LLM. wordmark (top left) | back to the site Home (same tab) | / Totals: 115 navigational links (69 built into the page + 46 rendered by the directory) · ~44 controls (search boxes, chips, copy buttons, burger, collapsible) · 1 broken link (Big Board → parity audit) · 2 things that look clickable but aren't (hero status pills, the Aug-15 Q chips).","h":"VIEWS · Questions / Decisions / Changelog / Migration / Parity"},{"f":211,"x":"Item | Type | Where it goes Custom LLM. wordmark | jump | Home (top) What It Is | scroll | #pitch section on Home How It Works | scroll | #how section on Home Inside | scroll | #inside section on Home The Engine | scroll | #engine section on Home Plan | scroll | #plan (the calendar) on Home Find | scroll | #find (the directory) on Home Brand OS ↗ (orange button) | document | the v0.6 standalone, new tab ☰ burger | opens | the slide-out menu The slide-out menu (the only nav on mobile): Item | Type Home | view Plan · The Calendar | scroll on Home Find a Document | scroll on Home The Big Board | view Prompt Library | view Guides & Tools | view Brand OS · Midnight | view Team Questions | view Decisions Log | view Changelog | view Rebrand Migration | view Apex Parity Audit | view","h":"The header (visible on desktop only, above 1180px)"},{"f":211,"x":"#top hero (orb + gradient title + status pills) → #pitch What This Is (3 cards) → #how the operating loop → #inside the component map (9 cards) → #engine graph engineering → #plan the calendar → #find the directory. The 9 swap-in views (share the header, replace the page body): Big Board · Prompt Library (23 prompts, 5 groups, copy buttons) · Guides & Tools · Brand OS (12 swatches + surface law + 15-mark gallery) · Team Questions · Decisions Log · Changelog · Rebrand Migration · Apex Parity Audit.","h":"Home is one page with 7 scroll stops"},{"f":211,"x":"Component map (Home): 12 direct document links + 8 view jumps (Decisions, Prompts, Questions, Changelog, Board, Migration, Parity, Brand OS) Engine section: QA report (doc) + Changelog (view jump) Guides & Tools view: 7 document links (Day-1 playbook, Retention Engine, Media & PR, Launch Copy, Operating Guide, Constitution, Project Plan) + Changelog jump Brand OS view: 4 document links + 15 full-size mark files Plan section: collapsible full roadmap (inline, no navigation) Find: all 46 documents, Start Here 1 · The Brain 6 · In Review 8 · Brand 9 · Launch Copy 9 · Launch 3 · Facts 3 · Logs 2 · Knowledge 2 · Plans 3, each opens in a new tab Every document page (twin): the Custom LLM. wordmark in its header returns to the site home","h":"Links INSIDE content (the third layer)"},{"f":211,"x":"Keep the site exactly as it looks, but promote navigation to a persistent, grouped top bar and give every destination true browser history: ``` Custom LLM. | Home Plan Library ▾ Toolkit ▾ Find [Brand OS ↗] Library ▾ = Big Board · Questions · Decisions · Changelog · Migration · Parity Toolkit ▾ = Prompt Library · Guides & Tools · Brand OS view Back/forward buttons work everywhere (pushState); every view is a shareable URL Active item always highlighted; scrollspy underlines the Home section you're reading Mobile: one full-screen menu listing everything, grouped the same way Pros: familiar website model, everything one hover away, smallest visual change. Cons: dropdowns need careful mobile handling.","h":"Option A, Grouped top nav, real pages *(my recommendation)*"},{"f":211,"x":"Home becomes a compact hub: the hero + status pills, then a card grid where every destination is one card (the 9 views + Plan + Find + Brand OS + the 5 most-used documents). The story sections (What This Is, How It Works, Engine) move to an \"About the Brain\" view for first-timers. Pros: one click to anything from landing; fastest for the team's daily use; the Big Board and QA report get front-page placement they deserve. Cons: the storytelling you loved is demoted to a secondary page; new visitors see a control panel before the explanation.","h":"Option B, Dashboard home (\"the launcher\")"},{"f":211,"x":"A fixed left sidebar (collapsible to icons on mobile) with the full grouped map always visible; content renders to its right. Home remains the pitch scroll inside the content area. ┌───────────┬────────────────────────────┐ │ STORY │ │ │ Home │ │ │ Engine │ (content area) │ │ OPERATE │ │ │ Board │ │ │ Prompts │ │ │ REGISTERS │ │ │ Questions│ │ │ Changelog│ │ └───────────┴────────────────────────────┘ Pros: the entire map on screen at all times, obvious current-location, scales best as views multiply (Hub v1 will add more). Feels like a real product, matches the Apex Team Hub direction. Cons: biggest rebuild of the three; sidebar costs width; less \"landing page,\" more \"tool.\"","h":"Option C, Persistent sidebar (\"the app\")"},{"f":212,"x":"Dropped by Atlas on 2026-08-11 to prove the Send for Approval notification flow fires. If you are reading this because an email arrived at marketing@apexinstruments.example, the flow works. This file gets moved back out to 00 My Space right after the test, never deleted."},{"f":213,"x":"Jordan*'s work zone. Position = status: work moves through the numbered stages; 03-for-review is what approvers check. Nothing here is official."},{"f":214,"x":"Josie*'s work zone. Position = status: work moves through the numbered stages; 03-for-review is what approvers check. Nothing here is official."},{"f":215,"x":"Morgan*'s work zone. Position = status: work moves through the numbered stages; 03-for-review is what approvers check. Nothing here is official."},{"f":216,"x":"Internal · the project. This is the team's daily space. Everything here is DRAFT by definition; nothing in the Work Zone is brain truth until it is approved and promoted. Your zone, five folders: Every person has the same five folders. That is the whole system. Folder | What goes in it 00 My Space | Yours entirely. Save anything, organize it however you like. Nobody manages this but you. 01 Active Projects | Work in progress that you are actively pushing forward. 02 Send for Approval | Done, in your eyes. Drop it here and the approvers (Jordan*, Avery*, Morgan*) take it from there: approved work gets built into the brain and the site; anything needing changes comes back to your Active Projects with a note."},{"f":216,"x":"03 Save for Later | Ideas, references, drafts you are not working on but do not want to lose. 04 Archived | Finished history. Nothing is ever deleted; it retires here. The approval flow: You drop a file into your 02 Send for Approval. Jordan*, Avery*, or Morgan* reviews it (notification setup for this folder is being configured; until then, ping them when you drop something). Approved: the operator promotes it into the brain's Approved library and it appears on the team site. Needs work: it moves back to your 01 Active Projects with a note."},{"f":216,"x":"_shared/ is for cross-team working files (including the migration staging). review-queue/ is the operator's verification queue where drafts get machine-checked line by line before human review; you do not need to touch it.","h":"Shared spaces"},{"f":217,"x":"Sami*'s work zone. Position = status: work moves through the numbered stages; 03-for-review is what approvers check. Nothing here is official."},{"f":218,"x":"Cross-team projects (launch site build, announcement kit, migration staging)."},{"f":219,"x":"Internal · the project. Run 2026-08-11. Status: production complete, awaiting Jordan*'s approval to promote. Board: B0 shows RUNNING until approval. What ran: Staged read-only: all 90 files of the Apex templates tree copied to source/; the Apex library untouched. The swap kit, built and now permanent: 01 The Brain/Skills/graph-engineering/migrate-swap.py, Apex hex to Evergreen, Montserrat/Lora to Archivo/IBM Plex, names to Custom LLM outside image tags, Apex URLs to {{custom-llm_domain}} keeping paths, Apex emails to {{contact_email}}, logo lines protected. Every later batch starts with this tool. One defect found and fixed mid-batch: the first URL rule swallowed full asset paths; it now swaps only the origin."},{"f":219,"x":"Deterministic pass: 52 text masters converted (49 first pass + 3 the twin-fold heuristic wrongly skipped: the PDF chassis HTML, the readme pair). 215 mechanical conversions total. The fleet (8 agents, opus): five category workers fixed what find-and-replace cannot, repaired swap-eaten sentences, retitled palettes to Evergreen token names, slotted Apex phones and program promos, cleared em dashes, resolved self-contradictions; three fresh-context lenses (names/the rules, slots/facts, tokens/structure) then swept the whole batch and correctly FAILED it on first pass."},{"f":219,"x":"Remediation: the lens findings traced to four root-level files no worker owned plus the URL-path defect. A remediation agent fixed all listed findings and caught three more (historical source filenames the swap wrongly renamed, restored inside backticks per the cleanup rules; an update-log self-contradiction; the unconverted readme). Gates, final state: Apex hex + Apex fonts across the produced set: zero."},{"f":219,"x":"source/ is the unconverted control and stays that way. It is the read-only staging copy of the pre-migration originals, so it still carries the old accent hexes (#e94560, #e53935, #ef4444), the old grounds and Montserrat/Lora. That is what makes the gate above measurable. Nothing in source/ is a current brand value, and nothing is built from it, the converted twin in custom-llm/ is the deliverable. Concrete Apex phone numbers: zero. \"Apex Instruments\" / \"APEXINST\" strings survive ONLY inside backticked historical filenames and fenced validator commands that check the Apex source, the allowed exceptions."},{"f":219,"x":"\"Pewter\" had no Evergreen equivalent; the promo-flyer spec now says \"a muted gray from the Evergreen set.\" Nearest candidates: Stone #597276 or Basalt #476467. Print font stack: the Apex PDF chassis uses Inter (+ DM Sans in derived guides), which the brand never mapped. Decide at chassis rebuild: adopt IBM Plex for print, or keep a dedicated print stack (ties to Q-13's print rules). New slot adopted: {{portal_url}} (the doctor portal domain, pending Q-16/22), now used 11 times; added to the standard slot set.","h":"Human calls for Jordan* (small, none blocking)"},{"f":219,"x":"Converted chassis promote to 01 The Brain/Templates/<category>/, twins generate, the asset directory turns those rows calder, and B0 gets its DONE check on the Batch Board.","h":"On approval"},{"f":220,"x":"Type: snippet File: footer-pill.html Used for: Copy-paste footer pill for print templates: sits absolutely at the bottom of a .page element with partner logo, phone, and website. What's in it: Glass-effect footer bar (print fallback: solid navy) Tokens: {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_NAME}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}} Positioned 0.3in from page bottom, overlaying the white-area bottom edge Default website: {{custom-llm_domain}} When to use: Paste into any co-branded print template to add the standard Custom LLM footer bar. Replace tokens with partner-specific values before printing."},{"f":221,"x":"Type: snippet File: header-pill.html Used for: Copy-paste header pill for print templates: sits absolutely at the top-center of a .page element with partner logo and Apex wordmark. What's in it: Header pill div absolutely positioned at top of .page Token: {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_NAME}} (alt text) Apex wordmark pre-loaded from CDN as default Overlays the white-area top edge of the print page When to use: Paste into any co-branded print template to add the standard Custom LLM header bar. Replace {{PARTNER_LOGO_COLOR_URL}} with the partner's color logo URL."},{"f":222,"x":"Working notes for this project. This placeholder keeps the folder in place when the Company Brain is uploaded to OneDrive. Delete it once real content is added."},{"f":223,"x":"Reference files and source material for this project. This placeholder keeps the folder in place when the Company Brain is uploaded to OneDrive. Delete it once real content is added."},{"f":224,"x":"Finished deliverables for this project, organized by type. This placeholder keeps the folder in place when the Company Brain is uploaded to OneDrive. Delete it once real content is added."},{"f":225,"x":"*The reusable starting points. What exists, what's still needed, and the standard each template follows.* Templates that exist: *These are ready to clone and fill. Start from the blank, then match a finished example in 05 Approved Library.* Template | File Microsite | microsite/microsite-template.html Welcome flyer | Welcome Flyer/welcome-flyer-template.html Bench & Rack guide | Guides/bench-and-rack-guide-template.html What's-Needed guide | Guides/whats-needed-guide-template.html Print PDF chassis | print-pdf-shell.html Shared partials | _partials/ (header-pill, footer-pill) Project skeleton | _project-template/ (clone per new project) Build briefs | Briefings/ (10 deliverable briefs)"},{"f":225,"x":"t; ⚠️ No blank template yet for: price sheet, lab slip, executive summary, one-pager, postcard, TAT document, case study, email, and PowerPoint deck. Build each from a finished example in 05 Approved Library, then save the blank here. Every template type needs five things: A blank starting template (the reusable shell). At least one finished example (so the AI matches format). A source / reference folder (where it came from). A QA checklist (what to check before approval). A \"when to use this\" note. t; 💡 How to build partner collateral: follow the full playbook at 01 Instructions / output-types / DIRECTIONS-Partner-Collateral-Build.md (brand rules, the PDF chassis, and step-by-step per deliverable). See: Output types","h":"Templates to build"},{"f":226,"x":"Date: 2026-05-03 Author: Claude (template extraction pass) What was built: Reverse-engineered three reusable templates from Caravelle's finished artifacts (which were originally rebranded UnionSix files), plus the 8-snippet component library, plus a working regression test that proves the template + config workflow produces a renderable artifact for any new partner. Path | Type | Status Template/print-pdf-shell.html | chassis | already existed (built earlier) Template/_partials/header-pill.html | chassis partial | already existed Template/_partials/footer-pill.html | chassis partial | already existed Template/Microsite/microsite-template.html | microsite | already existed Template/Welcome Flyer/welcome-flyer-template.html | derived template | NEW"},{"f":226,"x":"Template/Welcome Flyer/welcome-flyer-config-example.json | config example | NEW (Caravelle as worked example) Template/Guides/bench-and-rack-guide-template.html | derived template | NEW Template/Guides/bench-and-rack-config-example.json | config example | NEW (Caravelle as worked example) Template/Guides/whats-needed-guide-template.html | derived template | NEW Template/Guides/whats-needed-guide-config-example.json | config example | NEW (Caravelle Mount as worked example) Template/Guides/snippets/section-card-text-only.html | snippet | NEW (extracted from Caravelle Mount) Template/Guides/snippets/section-card-with-image.html | snippet | NEW (synthesized; pattern not in Mount guide) Template/Guides/snippets/important-bar.html | snippet | NEW (extracted from BrightPath Aperture)"},{"f":226,"x":"For each template, ran the validator: ``` grep -ic \"caravelle|dara|walter|nadia|317-7100|caravelle@apexinst\" Template | Forbidden matches | Notes welcome-flyer-template.html | 0 (real) | substring \"nadia\" appears inside the word \"registering\": false positive bench-and-rack-guide-template.html | 0 | clean whats-needed-guide-template.html | \"caravelle\" / \"mount\" appear only inside doc comments at the top of the file describing the template's purpose; zero in rendered content | clean All 8 snippets | 0 | clean","h":"Forbidden-string check"},{"f":226,"x":"$ cd Template/_test $ python3 render.py \"../Welcome Flyer/welcome-flyer-template.html\" \\ fakeco-config.json FakeCo-Welcome-Flyer.html OK: rendered FakeCo-Welcome-Flyer.html (43,808 bytes); zero unfilled tokens. The output FakeCo-Welcome-Flyer.html: contains 0 references to Caravelle/Dara/Walter/Nadia contains 15 references to \"FakeCo\" (header/footer pills, hero, value prop, partnership block, support team callout) contains 2 references to \"Jane Doe\" (the fake AE, in the team sidebar and image alt text) has 0 unfilled {{TOKEN}} placeholders other than the literal docstring {{PLACEHOLDER}} used in the comment header Conclusion: the Welcome Flyer template is real. Same render.py driver plus the corresponding config-example would render bench-and-rack and whats-needed templates identically.","h":"Regression test results"},{"f":226,"x":"The Caravelle B&R Guide (Caravelle/Bench and Rack Guide/...html) and the Caravelle Mount Guide (Caravelle/Mount Guide/...html) are nearly identical files. They share: Same chassis (page, white-area, header pill, footer pill, print rules) Same fonts (DM Sans + Inter) Same CSS classes (.section-card, .section-banner, .check-list, .key-details, .photo-images, .critical-bar, .rx-columns) Same 3-section structure The only meaningful differences are: Page title Section content (universal clinical vs. mount-specific) One extra <ul> of \"Mount Information\" Docket fields Briefing 06 originally aspired to a 9-section B&R guide that's \"standalone, not a What's Needed wrapper.\" The reality on disk is that they are the same template. I extracted them as separate files because the briefing","h":"1. The B&R Guide is structurally just the What's Needed Guide"},{"f":226,"x":"Update Caravelle's Mount Guide critical-bar to use the canonical snippet so the artifact and the snippet library agree. Same for any other guides that use the older simple-navy or amber variants. Pilot Trellis on the Welcome Flyer template first. That's the fastest test: a single config + a render produces a deliverable. Decide on B&R as separate-template-or-not. If the consolidation recommendation is accepted, delete bench-and-rack-guide-template.html and document B&R as \"compose using whats-needed-guide-template.html with the B&R sections from bench-and-rack-config-example.json's SECTIONS_HTML.\" Build a Trellis config to validate. Same workflow as fakeco-config.json but with real Trellis data. If render.py prints OK: zero unfilled tokens, the templates are production-ready for Trellis.","h":"Recommended next steps"},{"f":227,"x":"A reusable, partner-agnostic print-ready PDF shell. This is the structural skeleton every print PDF in the Custom LLM system sits on: a 8.5x11in page with a navy background, a white content area inset from the edges with a Tide border, a header pill at top holding the Apex and partner logos joined by a copper-gradient divider, and a glass-effect footer pill at the bottom holding white logos plus phone, website, and email. The chassis ships with no body content; the body is filled in by every derivative template (Welcome Flyer, What's Needed Guide, Bench and Rack Guide, Promo Flyer, Lab Slip, etc.).","h":"What to build"},{"f":227,"x":"BrightPath/Marketing Templates/BrightPath-Co-Branded-PDF-Template.html (263 lines). This file is the empty chassis already. You are extracting it, tokenizing the partner-specific values, and saving it as the canonical template. What to extract: The full <!DOCTYPE html> through </html> shell. All CSS inside the <style> block. Specifically preserve: The @import for Inter from Google Fonts. The @page { size: 8.5in 11in; margin: 0; } rule. The @media print block including the page sizing rules and the footer-pill !important overrides for background, backdrop-filter, and border-color. The .page rule (8.5in x 11in, navy #00272C background, overflow: hidden). The .white-area rule (inset 0.3in top/left/right, 1in from bottom, white background, 5px #245D63 border).","h":"Source file to use as the reference"},{"f":227,"x":"The .header-pill rule (white background, 5px Tide border, no top border, rounded bottom corners 14px, holds two logo <img> plus a .pill-divider with the copper gradient). The .footer-pill rule (glass effect with rgba(8, 38, 56, 0.85) background, backdrop-filter: blur(20px) saturate(140%), 0.6in tall, 0.3in from bottom, holds .footer-logos and .footer-contact). The footer SVG icons (phone, globe, email). Keep these inline as SVG. The <body> markup: .page containing .white-area (with a comment ` placeholder), then .header-pill and .footer-pill`.","h":"Source file to use as the reference"},{"f":227,"x":"Every partner-specific value becomes a token. The chassis itself does NOT need content tokens (those are the derived template's job); it only needs identity tokens (logos, contact info, partner display name). Placeholder | What it is | Example value {{PARTNER_NAME}} | Full partner display name used in <title> and as alt text on logos | \"BrightPath\" {{PARTNER_SHORT_NAME}} | Partner short name, used where space is tight or filenames | \"BrightPath\" {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color version, used in the header pill | hosted under {{custom-llm_domain}}, resolved by asset-directory tag {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white-on-transparent version, used in the footer pill | hosted under {{custom-llm_domain}}, resolved by asset-directory tag","h":"What to replace with placeholders"},{"f":227,"x":"{{PARTNER_PHONE}} | Partner-specific contact phone for the footer | {{contact_phone}} {{PARTNER_WEBSITE}} | Footer website value (almost always {{custom-llm_domain}}, but tokenized for flexibility) | {{custom-llm_domain}} {{PARTNER_EMAIL}} | Partner-specific email alias | {{contact_email}} {{DOCUMENT_TITLE}} | The <title> tag value, set per derived template | \"BrightPath Welcome Flyer\" {{CONTENT_SLOT}} | Comment marker inside .white-area where derived templates inject content | `` The Apex Wordmark logos in header and footer are NOT tokenized: they are constants. Hardcode the hosted URLs: Header: the Apex Wordmark Primary asset, hosted under {{custom-llm_domain}} Footer: the Apex Wordmark Single Color All White asset, hosted under {{custom-llm_domain}}","h":"What to replace with placeholders"},{"f":227,"x":"Template/print-pdf-shell.html If a Template/ subfolder structure helps later, also create: Template/_partials/header-pill.html (the header pill markup as a copy-paste block) Template/_partials/footer-pill.html (the footer pill markup as a copy-paste block) These partials are not strictly required (the chassis HTML already contains them), but making them callout-able copies helps the future \"compose a new template\" workflow. Brand rules to enforce: Brand colors (canonical): Harbor #245D63: not used in the chassis directly, but reserved for content body. Tide #245D63: used for the accent border on .white-area, the header-pill border, and the footer-pill icon strokes.","h":"Where to save the output"},{"f":228,"x":"A reusable, partner-agnostic microsite template. The microsite is the highest-leverage single deliverable: a scrollable, animated landing page hosted at {{custom-llm_domain}}/[partner-slug]/ that serves as the partner's home for everything (onboarding steps, downloadable resources, the dedicated team, the portal, and FAQs). Single self-contained HTML file with embedded CSS, JS, mesh-gradient backgrounds, and Font Awesome icons, designed to live inside a WordPress / Bricks code block. This briefing replaces the earlier 02-Microsite-Briefing.md draft, which had the wrong section count (6 vs the real 8) and missed several critical elements (sticky header / glass sidebar nav, the 5-step roadmap, the Welcome Message from AE, AI-generated FAQs, the Card Catalog reference).","h":"What to build"},{"f":228,"x":"Larchwood/Larchwood Microsite/Larchwood-Microsite.html (3,296 lines). This is the most recent and refined version. BrightPath was the original master in concept, but Larchwood has cleaner naming and more recent content patterns. Prefer Larchwood for structural patterns; spot-check BrightPath (BrightPath/Microsite/BrightPath Devices Partner Page, Custom LLM.html) and UnionSix (UnionSix/Microsite/UnionSix-Microsite.html) only to confirm cross-partner consistency. The 8 sections, in order top to bottom: The microsite has 8 sections. Document each one in the template with a clear comment block.","h":"Source file to use as the reference"},{"f":228,"x":"The FAQ section is AI-generated AFTER the rest of the microsite is built. Workflow: Render the rest of the template with placeholders filled in. Read the resulting microsite top-to-bottom. Generate 9 partner-specific FAQs that reflect what's actually on the site (the resource cards selected, the AE name, the team contacts, etc.). Apply the alternating question color pattern: q-cyan, q-blue, q-gold, q-cyan, q-blue, q-gold, q-cyan, q-blue, q-gold (Tide, Harbor, Copper, then repeat). Each FAQ answer should reference the actual links on the page (e.g., the Lab Slip PDF URL the resource card uses, the AE's email, the support team's phone, the Tech Prefs Form URL).","h":"FAQ generation (do NOT pre-fill the FAQ section)"},{"f":228,"x":"Placeholder | What it is | Example {{PARTNER_NAME}} | Full partner display name | \"Larchwood Devices\" {{PARTNER_SHORT_NAME}} | Short name where space is tight | \"Larchwood\" {{PARTNER_SLUG}} | URL-safe slug, used in og:url and canonical URLs | \"larchwood-devices\" {{PARTNER_LOGO_COLOR_URL}} | Header logo, color version | (resolve via directory tag [partner-slug, logo, color]) {{APEX_WORDMARK_LOGO_URL}} | Apex Wordmark Primary, used in header | hardcode the hosted asset under {{custom-llm_domain}} {{APEX_ICON_FAVICON_URL}} | Apex favicon | hardcode: Apex Icon Logo Primary {{PARTNER_PORTAL_EMAIL}} | Partner-specific email alias for portal/general use | {{contact_email}} {{META_DESCRIPTION}} | OG meta description | \"Your approved devices partner...\"","h":"Identity (header, footer, meta)"},{"f":228,"x":"Placeholder | What it is {{HERO_HEADLINE}} | Hero h1 (e.g., \"Welcome, Larchwood Devices Partners\") {{HERO_HEADLINE_ACCENT}} | Word in the headline rendered in the Tide accent (e.g., \"Larchwood Devices\") {{HERO_BG_IMAGE_URL}} | Optional hero background image (mesh gradient is the default) Hero subtitle \"For Artistry at Scale\" is hardcoded. Hero copy \"Here's everything you need to get started.\" is hardcoded. Scroll-down CTA anchors to #getting-started (hardcoded). 5-Step Onboarding Roadmap: {{NEW_CLINIC_FORM_URL}} | Step 1 the CRM form URL {{TECH_PREFS_FORM_URL}} | Step 2 the CRM form URL {{ONBOARDING_VIDEO_URL}} | Step 3 the CRM video URL. If unavailable, render \"Coming Soon\" placeholder.","h":"Hero"},{"f":228,"x":"{{AE_NAME}} | Full name of the AE {{AE_TITLE}} | Title (e.g., \"Strategic Account Executive\") {{AE_BIO_PARAGRAPH_1}} | First paragraph (intro) {{AE_BIO_PARAGRAPH_2}} | Second paragraph (background) {{AE_BIO_PARAGRAPH_3}} | Third paragraph (commitment / closing) {{AE_HEADSHOT_URL}} | Circular headshot image URL (resolve via directory tag [ae-firstname-lastname, headshot]) {{AE_SIGNATURE_URL}} | Inkstone image URL (resolve via tag [ae-firstname-lastname, signature]) {{AE_EMAIL}} | AE email {{AE_PHONE}} | AE direct line {{AE_CALENDAR_URL}} | AE the CRM meetings link (same value as Step 5) {{AE_VIRTUAL_CARD_URL}} | \"Click to Connect\" link (typically a vCard or contact share URL)","h":"Welcome Message from AE"},{"f":229,"x":"A reusable, partner-agnostic 2-page print-ready Welcome Flyer. This is the highest-volume per-partner deliverable. Every new partner office gets one. It is built on top of the print chassis from Briefing 01 and adds: a hero with welcome copy, a sidebar with team headshots, an About block, a Partnership block, a Why Choose Us block, a specialties grid, a Ready-to-Send block, a Getting Started Roadmap, and a Doctor's Portal section. t; Naming note (Jordan* preference 2026-05-01): the canonical name for this artifact is \"Welcome Flyer\", not \"Welcome Packet\". All earlier references to \"Welcome Packet\" in this briefing have been renamed.","h":"What to build"},{"f":229,"x":"Larchwood/Welcome Flyer/Larchwood Devices, Custom LLM Welcome Packet.html (1,198 lines). Largest of the 4 candidates. Cleanest section anatomy. If the print chassis from Briefing 01 (Template/print-pdf-shell.html) is already built, USE IT as the page wrapper rather than re-implementing the chassis inline. The Welcome Flyer should be: chassis from Briefing 01 + body content tokens from this briefing. What to extract: Page 1 layout: Hero section at top: Background image (lab photo) with navy-to-white gradient overlay. \"WELCOME\" pill (small uppercase text). Big title with a Tide accent on the key word. Copper-gradient subtitle pill. Below hero, content grid: 230px sidebar + 1fr main content. Sidebar: Team card with blue-gradient background.","h":"Source file to use as the reference"},{"f":229,"x":"3 team members stacked. Each: circular headshot (~80px), name, role, email, phone. Main content: \"About Us\" block. \"Partnership\" block. \"Why Choose Us\" block (3 numbered value props). Page 2 layout: \"Our Specialties\" section: 3x2 grid of capability icons (e.g., FRX, Bench & Rack, Mounts, Digital Housings, Scanning Support, Custom Solutions). Each cell: icon + label. \"Ready to Send Your First Case?\" section: two cards side-by-side (Digital submission vs Physical submission), each with a 3-step checklist. \"Getting Started Roadmap\": 5-step horizontal timeline. Each step: numbered circle + text. QR code block: links to the partner microsite. Doctor's Portal section: dark navy background, features grid + portal screenshot. CTA to {{portal_url}}.","h":"Source file to use as the reference"},{"f":229,"x":"All .hero-*, .team-card-*, .about-block, .partnership-block, .value-prop-*, .specialty-icon, .send-card-*, .roadmap-step-*, .qr-block, .portal-section-* CSS classes. The roadmap-step CSS (numbered circles connected by a line is fiddly; preserve exactly). The 3x2 specialty grid (responsive layout cues if any). What to replace with placeholders: Placeholder | What it is {{PARTNER_NAME}} | Full partner display name {{PARTNER_SHORT_NAME}} | Partner short name {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color version (header pill) {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white version (footer pill, portal section) {{PARTNER_PHONE}} | Footer phone {{PARTNER_WEBSITE}} | Footer website (default {{custom-llm_domain}}) {{PARTNER_EMAIL}} | Footer email alias","h":"What to extract specifically"},{"f":229,"x":"{{HERO_TITLE}} | Welcome Flyer hero h1 (e.g., \"Welcome to Your Custom LLM Partnership\") {{HERO_TITLE_ACCENT_WORD}} | Word in the hero title to render in the Tide accent (e.g., \"Partnership\") {{HERO_SUBTITLE}} | Copper-pill subtitle text (e.g., \"A Custom Engineered Solution for Larchwood Devices\") {{HERO_BG_IMAGE_URL}} | Hero background image URL {{TEAM_MEMBERS}} | Array of 3 team members. Each: {name, role, email, phone, headshot_url} {{ABOUT_TEXT}} | About block paragraph {{PARTNERSHIP_TEXT}} | Partnership block paragraph {{VALUE_PROPS}} | Array of 3 value props. Each: {number, title, body} {{SPECIALTIES}} | Array of 6 specialty cells. Each: {icon_svg_or_url, label} {{DIGITAL_SEND_STEPS}} | Array of 3 steps for the Digital submission card","h":"What to extract specifically"},{"f":229,"x":"Inter font throughout (this is a print PDF, not a microsite). No IBM Plex Sans or Archivo. Hero subtitle uses the Copper (#A8B6B7) gradient pill: background: linear-gradient(135deg, #A8B6B7 0%, #E6D695 50%, #A8B6B7 100%). Print fallback: solid rgba(179, 163, 105, 0.7) with print-color-adjust: exact. Hero title accent word uses Tide (#245D63). Numbered value props and roadmap steps use Harbor (#245D63) for the numbered circle background. Portal section uses a Midnight Green (#00272C) background with white text and Tide accents. Specialty icons use Harbor strokes. Print rules from Briefing 01 (page chassis) all apply. Specifically the footer-pill !important print overrides.","h":"Brand rules to enforce"},{"f":230,"x":"A reusable, partner-agnostic Price List template. This is the highest-update-frequency artifact in the system: pricing changes per quarter, per partner, per program. Templating cuts the most ongoing maintenance time. The output is a print-ready PDF (HTML source) that lists products grouped by category with prices, optional turnaround times, and partner branding. Source file to use as the reference: Larchwood/Larchwood Price List/apex_price_list.html (550 lines). Almost double the line count of UnionSix (297) and Caravelle (329), suggesting the most-developed table structure. Cleanest filename (no partner-prefix), suggesting it was already drafted as a near-template.","h":"What to build"},{"f":230,"x":"The print-PDF chassis (page, white-area, header-pill, footer-pill). If Template/print-pdf-shell.html from Briefing 01 is built, import it. Otherwise re-implement the chassis inline using the same rules. The price-table CSS: Category section header (Tide accented bar). Table styling: alternating row colors using Mist #EDF3F3 for the alt rows. Table headers in Harbor #245D63 background with white text. Price column right-aligned, numeric, monospaced if useful. Any \"Turnaround Time\" column or section (some partners include it, some don't). \"Effective Date\" stamp (small text, near the title). Notes / disclaimers section at the bottom (terms, custom-quote callouts, premium-product asterisks).","h":"What to extract"},{"f":230,"x":"Placeholder | What it is {{PARTNER_NAME}} | Full partner display name {{PARTNER_SHORT_NAME}} | Partner short name {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color (header pill) {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white (footer pill) {{PARTNER_PHONE}} | Footer phone {{PARTNER_WEBSITE}} | Footer website {{PARTNER_EMAIL}} | Footer email {{PRICE_LIST_TITLE}} | Document title (e.g., \"UnionSix Price List\") {{EFFECTIVE_DATE}} | \"Effective: [YYYY-MM-DD]\" or similar {{PRICE_CATEGORIES}} | Array of categories. Each: {category_name, intro_note, products} where products is an array of {product_name, sku_or_code, description, price, turnaround_days, is_premium} {{INCLUDE_TURNAROUND}} | Boolean: render the Turnaround column or not {{NOTES}} | Array of footer notes/disclaimers","h":"What to replace with placeholders"},{"f":230,"x":"{{CUSTOM_QUOTE_CTA}} | Optional CTA text (e.g., \"For custom or volume pricing, contact your account manager\") Where to save the output: Template/Price List/price-list-template.html Also save: Template/Price List/price-list-config-example.json showing the categories/products structure. Brand rules to enforce: Alternating table rows: #EDF3F3 (Mist) every other row. Table headers: #245D63 (Harbor) background, white text. Category section bars: Tide accent (#245D63) underline or left-border. Premium products (those marked is_premium: true): Copper (#A8B6B7) accent on the row (e.g., a small copper dot or italic price). Inter font throughout. Page chassis from Briefing 01 applies. Effective date is small (10px), placed near the document title.","h":"What to replace with placeholders"},{"f":230,"x":"Numeric prices are right-aligned with consistent decimal alignment. Validation checklist: ☐ Every placeholder in the table above appears in the template. ☐ No specific partner name, no specific price values, no specific products remain. ☐ Alternating table rows use #EDF3F3. ☐ Table headers use #245D63 with white text. ☐ Premium-row Copper accent works. ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Multi-page handling: if {{PRICE_CATEGORIES}} is long, content paginates without breaking the chassis. ☐ Cmd+P print preview is clean. ☐ Effective date renders as expected. ☐ Saved at Template/Price List/price-list-template.html. ☐ Config example JSON saved alongside.","h":"What to replace with placeholders"},{"f":231,"x":"Two artifacts: A reusable What's Needed Guide template (the print-ready guide shell). A snippet library of reusable guide components: section-card, important-bar, critical-bar, info-note, photo-grid, QR-block. This is the workhorse of the Custom LLM clinical content system. Every partner produces multiple guides (FRX, Axis, Exact, Aperture, Bench & Rack, Mounts). Templating the shell plus extracting the components turns \"write a new guide from scratch\" into \"compose a new guide from snippets.\" Source files to use as the reference: Hybrid: Primary (chassis + baseline section pattern): BrightPath/FRX Guide/BrightPath-Guide-FRX-Whats-Needed.html (733 lines). Cleanest baseline.","h":"What to build"},{"f":231,"x":"Secondary (richer component library): BrightPath/Aperture What's Needed Guide/BrightPath Aperture What's Needed Guide, Custom LLM.html (1,018 lines). Most feature-rich variant. Pull these specific components from Aperture: important-bar, critical-bar, info-note, photo-grid, QR-block. What to extract: From the FRX guide (chassis + baseline): Page chassis (use Briefing 01 if already built). Multi-page structure with page-break-after: always. Guide title block at top of each page. The standard .section-card component: .section-banner: numbered banner at top of card (.section-num for the number circle, .section-text for the section title). .section-body: card body with optional .card-header (icon + instruction text) and .body-text paragraphs or bullets.","h":"What to build"},{"f":231,"x":"Placeholder | What it is {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} | Standard chassis identity tokens {{PROGRAM_NAME}} | Clinical program (e.g., \"FRX\", \"Axis\", \"Aperture\", \"Exact\", \"Bench & Rack\", \"Mounts\") {{GUIDE_TITLE}} | Full guide title (e.g., \"FRX What's Needed Guide\") {{GUIDE_SUBTITLE}} | Optional subtitle {{SECTIONS}} | Array of section objects. Each: {number, title, has_image, image_url, instructions, body_blocks, callouts}. body_blocks is an array of `{type: \"paragraph\" | \"bullets\", content}. callouts is an array of {type: \"important\" | \"critical\" | \"info\", content}`.","h":"Template-level placeholders"},{"f":231,"x":"Each snippet is a copy-paste HTML block with token markers: Template/Guides/snippets/section-card-text-only.html Template/Guides/snippets/section-card-with-image.html Template/Guides/snippets/important-bar.html Template/Guides/snippets/critical-bar.html Template/Guides/snippets/info-note.html Template/Guides/snippets/photo-grid-2x2.html Template/Guides/snippets/photo-grid-3x2.html Template/Guides/snippets/qr-block.html Each snippet uses placeholders like {{SECTION_NUMBER}}, {{SECTION_TITLE}}, {{INSTRUCTION_TEXT}}, {{IMAGE_URL}}, {{CALLOUT_BODY}}, {{QR_IMAGE_URL}}, {{QR_LABEL}}.","h":"Snippet library (saved separately)"},{"f":231,"x":"Template/Guides/whats-needed-guide-template.html (the shell) Template/Guides/snippets/*.html (the component library) Template/Guides/whats-needed-guide-config-example.json (input schema) Brand rules to enforce: DM Sans (headings) + Inter (body). NOT Archivo / IBM Plex Sans (those are microsite/web only). Section banner: Harbor #245D63 background or Titanium-to-Harbor gradient. Critical bar: navy-to-blue gradient linear-gradient(135deg, #00272C, #245D63) with a Copper icon. NEVER a generic amber or brown default. Important bar: solid Midnight Green #00272C background. Info note: light gray #f1f5f9 background with #245D63 left border (3-4px). Section image max-height 120px (page-overflow constraint). Page chassis from Briefing 01 applies. Footer-pill !important print overrides apply.","h":"Where to save the output"},{"f":231,"x":"☐ Placeholder tokens for variable text are present. ☐ Brand colors match the canonical hex values. ☐ Inline-styled where reasonable so each snippet is self-contained when pasted. ☐ Saved at Template/Guides/snippets/[name].html. ☐ Critical-bar specifically uses the navy-to-blue gradient with a Copper icon (not a generic amber).","h":"For each snippet"},{"f":232,"x":"A reusable, partner-agnostic Bench & Rack Guide template. This is a standalone print-ready clinical guide for Bench & Rack case submissions. It is built directly on the Co-Branded PDF Chassis from Briefing 01. It is NOT a thin wrapper around Briefing 05's What's Needed Guide template, and it does NOT use Briefing 05's snippet library. B&R has its own section structure tuned specifically to Bench & Rack clinical workflow. t; Naming note (Jordan* preference 2026-05-01): B&R was previously briefed as a thin wrapper around the What's Needed Guide. That approach is dropped. B&R is its own template with its own sections, built from scratch on the print chassis.","h":"What to build"},{"f":232,"x":"UnionSix/Bench and Rack Guide/UnionSix-Guide-Bench-and-Rack.html (702 lines). Larchwood has a Bench & Rack Guide of the same line count (Larchwood/Larchwood Bench & Rack Guide/Larchwood-Bench-and-Rack-Guide.html). UnionSix picked because it is the more recently maintained version. Spot-check Larchwood only to confirm structural consistency. What to extract: Read the full source file. Extract the B&R specific section structure, NOT the generic What's Needed pattern. The B&R guide has its own anatomy: Page chassis: Use Briefing 01 (Template/print-pdf-shell.html) as the page wrapper. Inherit the white-area, header pill, footer pill, print rules, fonts. Do NOT re-implement the chassis inline. Document title block at the top of the first content page: Guide title (e.g., \"Bench & Rack Guide\")","h":"Source file to use as the reference"},{"f":232,"x":"Partner attribution sub-line (e.g., \"For UnionSix Devices partners\") Optional intro paragraph B&R specific sections (in clinical workflow order): Section 1: Case Overview: brief intro paragraph explaining the B&R workflow at Custom LLM Section 2: Required Photography: clinical photo requirements (frontal high lantern, frontal relaxed, profile relaxed, finish reference, pre-fit adjacent). Use the actual photo grid from the source. Section 3: Fit Registration: requirements for fit scan / measurement including centric seating notes Section 4: Margin Design: margin capture requirements, finish line cleanup Section 5: Opposing Rack: full opposing scan requirements Section 6: Finish Selection: finish matching protocol (Verona Classical or 3D Range), datum-line photo, finish tab placement","h":"Source file to use as the reference"},{"f":232,"x":"Section 7: Material Selection: zirconia, lithium disilicate, layered, full-contour notes; reference partner's price sheet for current options Section 8: Submission Checklist: simple checkbox list (digital scan files, lab slip, photos, special instructions) Section 9: Special Considerations: optional section for cases with extras (seating device, mount adapter, esthetic case escalation) B&R specific callouts: build these inline; they are NOT shared with Briefing 05's snippet library. Important note bar (navy): for \"Must capture full margin\", \"Fit must be in centric seating\" type emphasis Pro tip callout (light gray with a Harbor left border): for clinical tips that improve outcomes Photo grid component: 2x3 or 3x2 grid for clinical photography requirements","h":"Source file to use as the reference"},{"f":232,"x":"Finish tab block: visual layout showing finish tab placement Footer pill: from the chassis, partner-specific contact info. What to replace with placeholders: Placeholder | What it is {{PARTNER_NAME}} | Full partner display name (e.g., \"UnionSix Devices\") {{PARTNER_SHORT_NAME}} | Partner short name {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color version (header pill) {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white-on-transparent (footer pill) {{PARTNER_PHONE}} | Footer phone {{PARTNER_WEBSITE}} | Footer website (default {{custom-llm_domain}}) {{PARTNER_EMAIL}} | Footer email {{GUIDE_TITLE}} | Document title (default: \"{{PARTNER_NAME}} Bench & Rack Guide\") {{GUIDE_SUBTITLE}} | Optional subtitle (e.g., \"Submission Requirements & Best Practices\")","h":"Source file to use as the reference"},{"f":232,"x":"{{INTRO_PARAGRAPH}} | Optional intro paragraph at top {{FINISH_GUIDE_SYSTEM}} | \"Verona Classical\" or \"3D Range\" or partner-specific {{MATERIAL_OPTIONS}} | Array of available materials for this partner. Each: {name, indication, notes} {{PHOTO_REQUIREMENTS}} | Array of required photos. Each: {label, image_url, instruction} {{SPECIAL_CONSIDERATIONS}} | Array of partner-specific extras (e.g., UnionSix mount adapter, Delta Craft esthetic escalation). Each: {title, body}. Optional; can be empty. {{INCLUDE_FINISH_TAB_BLOCK}} | Boolean: render the finish tab visual block or not {{INCLUDE_SEATING_DEVICE_NOTE}} | Boolean: include the seating device clause in special considerations URLs that resolve from _WordPress_Asset_Directory.json","h":"Source file to use as the reference"},{"f":233,"x":"A reusable Promo Flyer template for partner promotions (e.g., a first-cases offer, a first-bench-units offer, a rebate program, a limited-time offer). Single-page print-ready PDF (HTML source) with a hero, a bold offer block, mechanics or terms, a CTA, and the standard chassis. This is a lower-volume, higher-design-variation deliverable, so the template should be flexible: hero image, offer headline, mechanics list, terms, and CTA, all tokenized. Source file to use as the reference: UnionSix/First 5 Cases Promo/UnionSix First 5 Cases Promo.html (790 lines). Largest of the promo candidates and \"First 5 Cases\" is the most generic promo concept (every partner could run a variant of this).","h":"What to build"},{"f":233,"x":"If you also want a comparison reference, Caravelle/Rebate/Caravelle Rebate Flyer, Custom LLM.html (806 lines) shows the rebate variation. Use it only to confirm structural similarity. What to extract: The print-PDF chassis (use Briefing 01 if built). Hero block: Strong headline (the promo offer). Sub-headline (qualifying language). Hero image or graphic. Optional Tide or Copper accent stripe. Mechanics block: Numbered or bulleted list of how the promo works. Terms block: Small text, time-limited disclaimers, eligibility conditions. CTA block: Primary CTA (often \"Send your first case\", \"Claim your offer\", \"Contact us\"). Optional QR code or short URL. Footer pill (chassis).","h":"What to build"},{"f":233,"x":"Placeholder | What it is Standard chassis tokens ({{PARTNER_NAME}}, etc.) | Same as Briefing 01 {{PROMO_NAME}} | Promo program name (e.g., a first-cases offer, a first-bench-units offer, a seasonal rebate) {{PROMO_TAGLINE}} | Hero h1 / dominant headline {{PROMO_SUBHEAD}} | Sub-headline qualifying the offer {{HERO_IMAGE_URL}} | Hero graphic or product photo {{OFFER_VALUE}} | The dollar value or \"free\" or \"% off\" of the offer {{MECHANICS}} | Array of mechanics steps. Each: {number, body} {{TERMS}} | Array of small-text disclaimers {{ELIGIBILITY_NOTE}} | One-line eligibility statement (e.g., \"New customers only\", \"Existing partners can opt in\") {{CTA_TEXT}} | Primary CTA button text {{CTA_HREF}} | Primary CTA href (mailto, tel, or URL) {{QR_CODE_URL}} | Optional QR code image URL","h":"What to replace with placeholders"},{"f":233,"x":"{{QR_TARGET_URL}} | URL the QR encodes {{PROMO_END_DATE}} | \"Offer ends [YYYY-MM-DD]\" or similar Where to save the output: Template/Promos/promo-flyer-template.html Also save: Template/Promos/promo-flyer-config-example.json. Brand rules to enforce: Inter font throughout. Hero headline can use Harbor (#245D63) or Midnight Green (#00272C) for emphasis. Offer value (the headline number or \"FREE\") should be visually loud. Use Copper (#A8B6B7) or Harbor, your call based on contrast against the hero image. Mechanics numbered circles use a Harbor background. Terms text small (10px or under), in a muted gray from the Evergreen token set (do not hardcode a hex). Page chassis from Briefing 01 applies.","h":"What to replace with placeholders"},{"f":233,"x":"Single-page print layout. If the promo content is long, prioritize hero + mechanics + CTA on page 1; terms can wrap to a second page if needed. Validation checklist: ☐ Every placeholder in the table above appears in the template. ☐ No \"UnionSix\" or \"First 5 Cases\" specific text remains. ☐ No specific dollar values or program-end dates remain. ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Hero has a tokenized image and headline. ☐ Mechanics renders as a numbered list. ☐ Terms render in small text. ☐ CTA button is visually prominent. ☐ Optional QR code block is present (can be empty/null). ☐ Cmd+P print preview is clean. ☐ Saved at Template/Promos/promo-flyer-template.html. ☐ Config example JSON saved alongside.","h":"What to replace with placeholders"},{"f":234,"x":"A reusable Executive Summary template that generates BOTH a microsite version (web pitch, scrollable, animated) AND a PDF version (print-ready handout) from a single set of input tokens. This is a sales-strategy artifact aimed at prospects, GSO leadership, or strategic partners. This is a dual-output template. The single config file produces two HTML files: one for web pitch, one for print PDF. Both must use the same brand voice and the same data. Source files to use as the reference: BioSummit/BioSummit Executive Summary/BioSummit Executive Summary Microsite.html (3,165 lines) for the microsite version. BioSummit/BioSummit Executive Summary/BioSummit_Executive_Summary_PDF.html (1,842 lines) for the print PDF version.","h":"What to build"},{"f":234,"x":"Both picked because BioSummit has the largest dual pair across all candidates, and the file naming pattern (-Executive-Summary-Microsite.html + -Executive-Summary-PDF.html) is also used by Trueline, Hargrove & Co, Parkline, and ClearForm ART, so it is the canonical naming. What to extract: From the microsite version: Section structure: hero, problem statement, solution overview, key metrics, value props, account team, next-steps CTA. Animation patterns (scroll reveals, key-metric counter animations if present). Mesh-gradient backgrounds (same brand-color palette as the partner microsite template). The same Archivo + IBM Plex Sans typography as the partner microsite.","h":"What to build"},{"f":234,"x":"Print chassis (use Briefing 01 if built). Same section structure but flattened for paper: Hero with title + tagline. Problem statement (1 short paragraph). Solution overview (3-5 bullets). Key metrics block (4-6 stat tiles). Value props grid (3-4 cards). Account team (3-5 cards with headshots). Next-steps CTA. Inter font only (PDF rules). What to replace with placeholders: Placeholder | What it is Standard chassis identity tokens (used in PDF version) | {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} {{TARGET_NAME}} | The party being pitched to (often a GSO or enterprise name, e.g., \"BioSummit\", \"Fairline Care\") {{TARGET_LOGO_URL}} | Logo of the target party for co-branding","h":"From the PDF version"},{"f":234,"x":"{{PITCH_TITLE}} | Hero title (e.g., \"A Custom Manufacturing Partnership for BioSummit\") {{PITCH_SUBTITLE}} | Hero subtitle {{HERO_IMAGE_URL}} | Hero background image {{PROBLEM_STATEMENT}} | 1-2 sentence problem framing {{SOLUTION_OVERVIEW}} | Array of solution bullets. Each: {title, body} {{KEY_METRICS}} | Array of 4-6 stat tiles. Each: {value, label, supporting_text} {{VALUE_PROPS}} | Array of 3-4 value-prop cards. Each: {number, title, body, icon_svg_or_url} {{ACCOUNT_TEAM}} | Array of 3-5 account-team members. Each: {name, title, headshot_url, email, phone} {{NEXT_STEPS}} | Array of next-step actions. Each: {step, owner, timeline} {{CTA_TEXT}}, {{CTA_HREF}} | Closing CTA {{COMMERCIAL_TERMS_LINK}} | Optional link to commercial terms / pricing","h":"From the PDF version"},{"f":234,"x":"Inter font only. Page chassis from Briefing 01. Solid-color backgrounds (not mesh gradients, which print poorly). Key metrics use a Harbor tile background with white text. Value props use Copper for the numbered circles. Account team uses the same circular-headshot pattern but smaller (60px instead of 80px+). Both versions: The legal entity name ({{legal_entity_name}}) appears only in URLs and email addresses. Visible body text always says \"Custom LLM\". All 5 brand colors used appropriately. No off-palette accents.","h":"PDF version"},{"f":234,"x":"☐ All standard placeholders present. ☐ No \"BioSummit\" anywhere in the file. ☐ Archivo + IBM Plex Sans fonts loaded. ☐ Mesh-gradient backgrounds use brand palette only. ☐ Key-metric counter animations work. ☐ Saved at Template/Executive Summary/executive-summary-microsite-template.html. For the PDF version: ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Cmd+P print preview is clean. ☐ Saved at Template/Executive Summary/executive-summary-pdf-template.html. Both: ☐ Same config drives both: changing a placeholder once updates both outputs. ☐ Single shared config example JSON saved alongside. ☐ Section structure is identical across both formats (same data, different presentation).","h":"For the microsite version"},{"f":235,"x":"A reusable Lab Slip / Docket template. This is the digital Docket form a doctor's office fills out when submitting a case. Today most partners use a PDF version; only BioSummit has an HTML source. Building the HTML template means future partners can have a fillable, branded lab slip with form-field tokenization. Note: a true fillable form (PDF AcroForm or interactive HTML) is out of scope for this template build. The deliverable is the visual template with field labels and structural blocks. Adding interactivity is a follow-up.","h":"What to build"},{"f":235,"x":"BioSummit/BioSummit Lab Slip/BioSummit-Lab-Slip-Docket.html (1,085 lines). This is the only HTML lab slip in the repo. What to extract: The print-PDF chassis (use Briefing 01 if built). Header section: Doctor name + practice name fields. Client name + chart number fields. Case date / due date fields. Case details section: Unit chart or unit-number selector. Refit type (Bench Unit, Rack Unit, Mount, Housing, etc.). Material selection. Finish selection. Special instructions section: Free-form text area. Common-instruction checkboxes. Submission method section: Digital scan (with file format options). Physical measurement (with shipping note). Inkstone / date block: Doctor signature line. Date. Optional: lab use only block (where the lab notes back to the office).","h":"Source file to use as the reference"},{"f":235,"x":"Placeholder | What it is Standard chassis identity tokens | {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} {{LAB_SLIP_TITLE}} | Title (e.g., \"BioSummit Lab Slip / Digital Docket\") {{REFIT_TYPES}} | Array of refit types this partner offers. Each: {label, code, sub_options} {{MATERIAL_OPTIONS}} | Array of material options. Each: {label, code, applies_to_refit_types} {{FINISH_GUIDE}} | Array of finish options (typically Verona Classical or 3D Range). Defaults can be hardcoded if every partner uses the same. {{SPECIAL_INSTRUCTION_PRESETS}} | Array of common instruction checkboxes. Each: {label, default_checked}","h":"What to replace with placeholders"},{"f":235,"x":"{{INCLUDE_UNIT_CHART}} | Boolean: render the visual unit chart or just a unit-number list {{SUBMISSION_METHODS}} | Array of submission methods. Each: {label, file_formats_accepted} {{LAB_USE_ONLY_BLOCK}} | Boolean: include the lab-use-only block or not {{TURNAROUND_NOTE}} | Standard turnaround note. Pull the figure from the authority file only: \"Standard turnaround: {{tat}}\" Where to save the output: Template/Lab Slip/lab-slip-template.html Also save: Template/Lab Slip/lab-slip-config-example.json.","h":"What to replace with placeholders"},{"f":235,"x":"Inter font throughout. Form field labels: Midnight Green (#00272C). Form field underlines or borders: Harbor (#245D63). Section headers: Harbor (#245D63) bar, white text. Required-field markers: Copper (#A8B6B7) asterisk or border accent. Page chassis from Briefing 01. Single-page if possible. If multi-page (BioSummit is 1085 lines, which suggests 2 pages), use page-break-after: always between sections. Print-friendly. Form fields render as underlined blank lines for handwriting if printed. Validation checklist: ☐ Every placeholder in the table above appears in the template. ☐ No \"BioSummit\" specific text or product remains. ☐ No specific finish values, material codes, or refit types remain (all tokenized). ☐ Inter font only. ☐ Page chassis matches Briefing 01.","h":"Brand rules to enforce"},{"f":235,"x":"☐ Form field structure is consistent (all labels above their inputs). ☐ Required-field markers visible. ☐ Multi-page handling correct if needed. ☐ Cmd+P print preview shows fillable-by-pen layout. ☐ Saved at Template/Lab Slip/lab-slip-template.html. ☐ Config example JSON saved alongside.","h":"Brand rules to enforce"},{"f":236,"x":"A reusable Account Onboarding SOP (Standard Operating Procedure) template. This is the document that walks a new partner office through everything from initial outreach to first-case submission. It defines step-by-step responsibilities, owners, and timelines. This is the lowest-priority template because only one partner today has an SOP (UnionSix). Building it is somewhat speculative reuse, but the template is straightforward to extract and may save substantial time the next time a GSO or large partner needs structured onboarding.","h":"What to build"},{"f":236,"x":"UnionSix/Account Onboarding/UnionSix-SOP-Onboarding.html (1,258 lines). The only SOP HTML in the repo. What to extract: The print-PDF chassis (use Briefing 01 if built). Document title and subtitle (e.g., \"Account Onboarding SOP for UnionSix Devices\"). Phase blocks. Typical SOP phases: Phase 1: Initial Setup (account creation, contact assignment, intake form). Phase 2: Brand Customization (logos, microsite, welcome flyer). Phase 3: Clinical Configuration (preferences, materials, finish conventions). Phase 4: First Case Submission (test case, feedback loop). Phase 5: Ongoing Operations (cadence, escalation paths, monthly review). For each phase: Numbered step list. Owner column (who is responsible: Custom LLM Account Manager, Partner POC, External Vendor, Doctor).","h":"Source file to use as the reference"},{"f":236,"x":"Timeline / target completion. Deliverable / artifact produced. Owner color-coding legend (uses brand colors per the existing pattern): Partner: Harbor (#245D63). External Vendor: Copper (#A8B6B7). Custom LLM: Midnight Green (#00272C). Doctor: Tide (#245D63). Escalation / contact block at the bottom. What to replace with placeholders: Placeholder | What it is Standard chassis identity tokens | {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} {{SOP_TITLE}} | Document title (e.g., \"UnionSix Account Onboarding SOP\") {{SOP_SUBTITLE}} | Optional subtitle (e.g., \"Standard Operating Procedure for New Office Setup\") {{EFFECTIVE_DATE}} | \"Effective: [YYYY-MM-DD]\"","h":"Source file to use as the reference"},{"f":236,"x":"{{PHASES}} | Array of phase objects. Each: {number, name, intro, steps} where steps is an array of {step_number, description, owner_code, timeline, deliverable} {{OWNER_LEGEND}} | Array of owner codes. Each: {code, label, color_token}. Default codes: PARTNER, EXTERNAL, CUSTOM LLM, DOCTOR. {{ESCALATION_CONTACTS}} | Array of escalation contacts. Each: {role, name, phone, email} {{REVIEW_CADENCE}} | Standard review cadence (e.g., \"Weekly check-ins for first 30 days, then monthly\") Where to save the output: Template/SOP/account-onboarding-sop-template.html Also save: Template/SOP/account-onboarding-sop-config-example.json.","h":"Source file to use as the reference"},{"f":236,"x":"Inter font throughout. Phase header bars: Harbor (#245D63) background, white text, with the phase number in a circle. Step numbering: small Harbor circles with white text. Owner badges: small pill backgrounds in the owner color codes (Partner Harbor, External Copper, Custom LLM Midnight Green, Doctor Tide). White or contrast text. Timeline column: small muted gray text from the Evergreen token set (do not hardcode a hex). Page chassis from Briefing 01. Multi-page document (UnionSix is 1,258 lines suggesting 4-6 pages). Use page-break-after: always between phases.","h":"Brand rules to enforce"},{"f":236,"x":"☐ Every placeholder in the table above appears in the template. ☐ No \"UnionSix\" specific text, no specific contact names, no specific phase titles remain. ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Owner color-coding legend uses canonical brand colors. ☐ Phase headers render cleanly with numbered circles. ☐ Step list is readable, with owner badges aligned. ☐ Page breaks between phases work in Cmd+P print preview. ☐ Escalation contacts block is present at the end. ☐ Saved at Template/SOP/account-onboarding-sop-template.html. ☐ Config example JSON saved alongside.","h":"Validation checklist"},{"f":237,"x":"Date: 2026-05-01 Author: Claude Scope: Status of changes made to the Briefings folder during the \"Fix 3 Briefings + Build Card Catalog\" pass. Summary: Three briefings updated, one new artifact built (the Card Catalog). The other 7 briefings (01, 04, 05, 07, 08, 09, 10) were not touched per scope. Changes by file: NEW: Template/Microsite/Card_Catalog.json and Card_Catalog.md"},{"f":237,"x":"Built from scratch. Inventoried every unique resource card across the 5 partner microsites (BrightPath, Larchwood, UnionSix, BioSummit, Vista Specialty). Found 24 unique card types from 37 instances observed. Each card entry has: id (slug), title template, description template, description-varies flag, FA icon class + color, card image placeholder + default URL + directory tag, CTA label + icon type + href placeholder + directory tag, and the list of partners that use it. The catalog is the source of truth for the Microsite template's Resource Cards section. Per-partner microsite configs pick which card IDs to include."},{"f":237,"x":"Replaced entirely. The earlier draft had 5 problems: Said the microsite has 6 sections. Actual count is 8 (Sticky Header, Hero, 5-Step Onboarding Roadmap, Resource Cards, Welcome from AE, Support Team carousel, Manage Your Cases, FAQ). Plus footer. Missed the 5-Step Onboarding Roadmap entirely. Missed the Welcome Message from AE section entirely. Treated FAQs as pre-fillable. They are AI-generated AFTER the rest of the microsite is built. Didn't reference the Card Catalog (because it didn't exist yet). Tokenized things that should be hardcoded (hero subtitle \"For Artistry at Scale\", Manage Your Cases section, Closing Quote, sidebar nav items, portal URL, Digital Housings URL).","h":"REWRITTEN: Template/Briefings/02-Microsite-Briefing.md"},{"f":237,"x":"File renamed. Inside the briefing: every reference to \"Welcome Packet\" rewritten to \"Welcome Flyer\". Output path changed from Template/Welcome Packet/welcome-packet-template.html to Template/Welcome Flyer/welcome-flyer-template.html. Same for the config example file. Three \"Welcome Packet\" mentions remain in the file: (a) the title which calls out the rename, (b) the explicit naming-note callout box, (c) the literal source filename Larchwood Devices, Apex Instruments Welcome Packet.html which is the actual file in the repo and cannot be renamed without breaking the path. All other content of the briefing was left unchanged.","h":"RENAMED + UPDATED: Template/Briefings/03-Welcome-Flyer-Briefing.md (was 03-Welcome-Packet-Briefing.md)"},{"f":237,"x":"Replaced entirely. Removed the \"thin wrapper around Briefing 05\" framing. B&R is now its own standalone template, built directly on the Co-Branded PDF Chassis from Briefing 01. It does NOT reference Briefing 05's snippet library; it has its own component definitions (important bars, pro tip callouts, photo grids, finish tab block). The new briefing defines 9 B&R specific sections in clinical workflow order (Case Overview, Required Photography, Fit Registration, Margin Design, Opposing Rack, Finish Selection, Material Selection, Submission Checklist, Special Considerations). Source file unchanged (UnionSix/Bench and Rack Guide/UnionSix-Guide-Bench-and-Rack.html).","h":"REWRITTEN: Template/Briefings/06-Bench-and-Rack-Guide-Briefing.md"},{"f":237,"x":"01-Co-Branded-PDF-Chassis-Briefing.md 04-Price-List-Briefing.md 05-Whats-Needed-Guide-Briefing.md 07-Promo-Flyer-Briefing.md 08-Executive-Summary-Briefing.md 09-Lab-Slip-Briefing.md 10-Account-Onboarding-SOP-Briefing.md Cross-references between briefings (current state): Briefings 03 (Welcome Flyer), 04 (Price List), 05 (What's Needed Guide), 06 (Bench & Rack Guide), 07 (Promo Flyer), 08 (Executive Summary PDF version), 09 (Lab Slip), 10 (SOP) all import or reference the Co-Branded PDF Chassis from Briefing 01. Briefing 02 (Microsite) and Briefing 08 (Executive Summary microsite version) use the Archivo + IBM Plex Sans typography stack and the mesh-gradient backgrounds; they do NOT use the print chassis.","h":"Files NOT touched (per scope)"},{"f":238,"x":"Type: component library File: Component_Library.html Used for: A living visual reference of all Custom LLM UI components: typography, colors, buttons, callouts, cards, and layout patterns used across templates. What's in it: Full Custom LLM Evergreen color swatches and variable reference Typography scale (Archivo headings + IBM Plex Sans body) Button styles, callout bars (critical / important / info), and card components Layout pattern examples Used as the design source-of-truth for building and auditing templates"},{"f":238,"x":"Consult before building a new template or modifying an existing one. Check here to confirm correct colors, type styles, and component patterns rather than inventing new ones.","h":"When to use"},{"f":239,"x":"Type: email template File: APEX_Email_Request_Form_v2.html Used for: Internal intake form for requesting a single email send: captures recipient, subject, content brief, and send details. What's in it: DM Sans type stack Form fields for email type, audience, subject line brief, content notes, and send date Custom LLM brand styling for internal use v2 of the standard email request form When to use: Use when requesting a one-off email from the marketing team. For multi-email series, use Email-Series-Campaign-Form instead."},{"f":240,"x":"Type: email template File: Email-Series-Campaign-Form.html Used for: Internal intake form for briefing and requesting a multi-email campaign series: captures campaign details, goals, audience, and scheduling information. What's in it: DM Sans type stack Form fields for campaign name, series structure, goals, target audience, and schedule Custom LLM brand styling for internal use Structured to collect everything needed to brief a campaign When to use: Use when a team member needs to request or brief a new email series campaign. Fill out and submit to initiate the campaign workflow."},{"f":241,"x":"Type: print template File: bench-and-rack-guide-template.html Used for: Reusable, partner-agnostic 1-page print-ready clinical Bench & Rack guide for any Custom LLM partner. What's in it: Single-page print chassis (based on print-pdf-shell.html) DM Sans + Inter typography stack Clinical sections for Bench & Rack case requirements Partner-agnostic placeholder zones (co-brand via header/footer pills) Standalone: does not inherit from the What's Needed Guide template When to use: Use when producing a Bench & Rack \"What's Needed\" or prep guide for any partner. Swap in header/footer pills and partner details to co-brand."},{"f":242,"x":"Type: snippet File: critical-bar.html Used for: Highest-severity callout bar. Flags steps whose absence would cause case failure (e.g., datum pin must be properly seated). What's in it: Canonical Midnight Green to Harbor gradient background with a Copper icon \"Critical\" severity styling (most visually urgent callout in the system) Paste-in snippet for use inside guide section bodies Brand-compliant: uses current Custom LLM token values, no legacy palette hexes When to use: Insert when a clinical instruction carries the highest risk of case failure if missed. Use sparingly, reserve for truly critical steps only. Less severe alerts should use important-bar or info-note instead."},{"f":243,"x":"Type: snippet File: important-bar.html Used for: Solid navy callout bar for \"must-do\" notes: verification jig requirements, mandatory steps, etc. Second-highest severity after critical-bar. What's in it: Solid Midnight Green (--os-ink, #00272C) background \"Important\" severity styling Paste-in snippet for use inside guide section bodies Visually distinct from critical-bar (no gradient) and info-note (no soft gray) When to use: Insert for mandatory steps that aren't case-failure-level critical, e.g., required verification jig use, mandatory submission checklist items. Use critical-bar for higher severity, info-note for supplementary tips."},{"f":244,"x":"Type: snippet File: info-note.html Used for: Soft supplementary callout for \"good-to-know\" details: submission tips, optional steps, or non-critical reminders. What's in it: Light gray (#f0f4f8) background, lowest visual urgency \"Info\" severity styling Paste-in snippet for use inside guide section bodies Clearly distinct from critical-bar and important-bar When to use: Insert for helpful but non-mandatory context: tips, optional recommendations, \"pro tips,\" or submission best practices. Not for steps that affect case outcomes."},{"f":245,"x":"Type: snippet File: photo-grid-2x2.html Used for: A 2-column × 2-row clinical photography grid (4 cells) for embedding example photos with labels inside a guide section body. What's in it: Four .photo-item cells, each with an <img> capped at roughly 95 to 105px height Label text below each photo Fits within print page-overflow constraints Paste-in snippet for use inside .section-body elements When to use: Use when a guide section needs up to 4 reference photos (e.g., scan positions, prep angles). For 5 to 6 photos, use photo-grid-3x2 instead."},{"f":246,"x":"Type: snippet File: photo-grid-3x2.html Used for: A 3-column × 2-row clinical photography grid (6 cells) for embedding 6 reference photos with labels inside a guide section body. What's in it: Six .photo-item cells in a 3×2 grid Label text below each photo Designed for sections requiring more reference photos (e.g., a 6-angle scan requirement) Paste-in snippet for use inside .section-body elements When to use: Use when a guide section needs 5 to 6 reference photos. For 4 or fewer, use photo-grid-2x2 to preserve whitespace and readability."},{"f":247,"x":"Type: snippet File: qr-block.html Used for: Square QR code with label. Links to export guides, microsite onboarding, or external resources from within a printed guide. What's in it: QR image area with {{QR_IMAGE_URL}} token (PNG/SVG of encoded QR) Small label text below the code Compact square format fits within guide sections or footers When to use: Insert when a printed guide needs to point readers to a URL (step-by-step export guide, partner microsite, video, etc.). Replace {{QR_IMAGE_URL}} with the actual QR image URL before printing."},{"f":248,"x":"Type: snippet File: section-card-text-only.html Used for: A two-column section card containing two .card sub-blocks (e.g., \"Analog Requirements\" and \"Digital Requirements\"), no image, text only. What's in it: Two-column layout with paired .card sub-blocks Card header (icon + label) and body text per column No image slot Paste-in snippet for use in guide section bodies When to use: Use for sections that contrast two requirement sets side-by-side (analog vs digital, standard vs optional). Matches the layout used in the paired requirement sections of the {{PARTNER_NAME}} mount guide."},{"f":249,"x":"Type: snippet File: section-card-with-image.html Used for: A single-column section card with banner + body: card header (icon + label) plus clinical instructions with an optional inline image. What's in it: Single-column layout with card-header (icon + label) and body text Optional inline image slot within the body Paste-in snippet for use in guide section bodies Tokens: {{SECTION_ICON}}, {{SECTION_LABEL}}, {{BODY_CONTENT}}, optional {{IMAGE_URL}} When to use: Use for guide sections that are a single block of clinical instructions, especially when a reference image (scan, prep photo) helps illustrate the step."},{"f":250,"x":"Type: print template File: whats-needed-guide-template.html Used for: Reusable, partner-agnostic, program-agnostic 1-page print-ready clinical \"What's Needed\" guide for any Custom LLM program and partner. What's in it: Single-page print chassis shared across every clinical program guide, Bench & Rack and mount included, one build per {{PROGRAM_NAME}} Section cards, callout bars, and photo grid snippets composited in Partner-agnostic placeholder zones Full Custom LLM brand color and type system Designed for Chrome → Print → Save as PDF"},{"f":250,"x":"Use as the base template when building any clinical program \"What's Needed\" guide. More general than the Bench & Rack variant: covers all program types.","h":"When to use"},{"f":251,"x":"Source: Extracted from 5 partner microsites (BrightPath, Larchwood, UnionSix, BioSummit, Vista Specialty). Generated: 2026-05-01. Total unique card types: 24. Card instances observed: 37 (5-10 per partner). How to use this catalog: When building a new partner microsite, pick which card IDs to include based on the partner's scope. The microsite template iterates over the chosen cards, substituting placeholders with actual values per partner."},{"f":251,"x":"Title (template): {{PARTNER_NAME}} Exact \"What's Needed\" Description: Step-by-step scanning requirements for Exact cases. Use this guide to ensure complete and accurate case submissions. Icon (FA class): fas fa-crosshairs color #245D63 Card image placeholder: {{CARD_IMAGE_EXACT_WHATS_NEEDED_URL}} Card image default URL: {{custom-llm_domain}}/wp-content/uploads/2026/02/BrightPath-Exact-Whats-Needed-Thumbnail.webp Card image directory tag (resolve via _WordPress_Asset_Directory.json): [exact, whats-needed, card] CTA href placeholder: {{EXACT_WHATS_NEEDED_PDF_URL}} CTA href directory tag (or source): [partner-slug, exact, whats-needed, pdf]","h":"card-exact-whats-needed"},{"f":251,"x":"Title (template): {{PARTNER_NAME}} Axis \"What's Needed\" Description: A comprehensive 6-step checklist for Axis cases. This guide covers requirements for ASAP measurements, locator and 360 scans, photos, and finish details. Card image placeholder: {{CARD_IMAGE_AXIS_WHATS_NEEDED_URL}} Card image default URL: {{custom-llm_domain}} Card image directory tag (resolve via _WordPress_Asset_Directory.json): [axis, whats-needed, card] CTA href placeholder: {{AXIS_WHATS_NEEDED_PDF_URL}} CTA href directory tag (or source): [partner-slug, axis, whats-needed, pdf] Used by partners: Larchwood","h":"card-axis-whats-needed"},{"f":251,"x":"Title (template): {{PARTNER_NAME}} Bench & Rack Guide (or Bench & Rack \"What's Needed\") Description: Your complete guide to submitting Bench & Rack cases. Includes detailed requirements for analog measurements, digital scans, materials, and submission workflow. Icon (FA class): fas fa-gauge color #245D63 Card image placeholder: {{CARD_IMAGE_BENCH_RACK_URL}} Card image directory tag (resolve via _WordPress_Asset_Directory.json): [bench-rack, card] CTA href placeholder: {{BENCH_RACK_GUIDE_PDF_URL}} CTA href directory tag (or source): [partner-slug, bench-rack, pdf] Used by partners: Larchwood, UnionSix","h":"card-bench-rack-guide"},{"f":251,"x":"Title (template): Mount: What's Needed Description: A step-by-step guide for mount case submissions covering analog and digital measurement requirements, required photos, and finish details. Icon (FA class): fas fa-screwdriver color #245D63 Card image placeholder: {{CARD_IMAGE_MOUNT_WHATS_NEEDED_URL}} Card image directory tag (resolve via _WordPress_Asset_Directory.json): [mount, whats-needed, card] CTA href placeholder: {{MOUNT_WHATS_NEEDED_PDF_URL}} CTA href directory tag (or source): [partner-slug, mount, whats-needed, pdf] Used by partners: BioSummit, UnionSix","h":"card-mount-whats-needed"},{"f":251,"x":"Title (template): Delta Craft Price Sheet, TAT & Case Checklist Description: Everything you need for our premium Delta Craft cosmetic refits: detailed pricing plus a complete case submission checklist. Icon (FA class): fas fa-gem color #245D63 Card image placeholder: {{CARD_IMAGE_DELTACRAFT_URL}} Card image default URL: {{custom-llm_domain}}/wp-content/uploads/2026/02/DeltaCraft-Price-Sheet-scaled.png Card image directory tag (resolve via _WordPress_Asset_Directory.json): [deltacraft, price-sheet, card] CTA href placeholder: {{DELTACRAFT_PRICE_TAT_PDF_URL}} CTA href directory tag (or source): [partner-slug, deltacraft, price-sheet, tat, pdf] Used by partners: UnionSix","h":"card-deltacraft-price-tat-checklist"},{"f":252,"x":"Type: microsite File: microsite-template.html Used for: Reusable, partner-agnostic microsite template: copy and substitute {{PLACEHOLDER}} values to produce a partner-specific landing microsite. What's in it: Full Custom LLM brand microsite layout (hero, program cards, contact section) {{PLACEHOLDER}} token system for all partner-specific content Card catalog integration (Card_Catalog.json) for modular content sections Companion briefing doc reference (02-Microsite-Briefing.md) Responsive, browser-based, not a print-to-PDF document"},{"f":252,"x":"Use when a new partner needs a dedicated microsite or landing page. Follow the 02-Microsite-Briefing.md for the full placeholder list and Card_Catalog.json for available card modules.","h":"When to use"},{"f":253,"x":"Type: web landing page template File: openform-product-page-template.html Used for: Generating one product-detail page per OpenForm SKU. There are 63 near-identical pages; this template provides the constant shell (CSS, nav, compliance bar, footer) and 16 «SWAP» placeholders covering all variable content. Fill one JSON config row per SKU and render. What's in it: Constant shell (lifted verbatim from source pages, do not modify): Full 297-line CSS block: :root tokens, nav, hero, features, compliance-bar, related, footer, responsive breakpoints Google Fonts import: Barlow, Barlow Semi Condensed, Barlow Condensed (OpenForm brand, NOT Custom LLM brand fonts) Favicon: OI-Icon-Logo.png.png (OpenForm icon)"},{"f":253,"x":"Sticky nav: OI white wordmark + Home + All Products links (both constant) + Buy Now CTA (uses «SHOP_URL») Compliance bar: 5 locked regulatory items (FDA 510(k) Cleared · Zero Deficiencies · Zero Recalls · Made in USA · 7 Mount Systems) Footer: OI white wordmark + \"SHERLOCK, Devices Mount Components & Milling Center\" + openform.example links + 4 footer badges + copyright line Variable slots (16 total, 12 scalar + 4 related-card objects × 4 fields each): 12 scalar swap fields in <head> and hero/features sections 4 related-card slots, each with 4 sub-fields (href, img slug, alt text, display name)"},{"f":253,"x":"Field | What it is | Example value | Source / Notes «PAGE_TITLE» | Browser tab title | `Norwell Active Ti-Base Set \\ | OpenForm, Sherlock Devices Components` | Pattern: `{Product Name} \\ | OpenForm, Sherlock Devices Components` «META_DESC» | meta description (~155 chars) | Engaging titanium base adapter set compatible with Norwell Precision (Active) mount systems... | From product copy «META_KEYWORDS_SYSTEM» | meta keywords string | devices mount, titanium base, Norwell Precision (Active), mount components, FDA cleared, OpenForm, Sherlock | Adapt system name per SKU","h":"Swap-point manifest"},{"f":253,"x":"«SHOP_URL» | Full WooCommerce product URL | https://shop.openform.example/norwell-active-titanium-base-set/ | Must be verified explicitly, NOT derivable from filename (e.g. mua-3mm-norwell-cc-rp.html → slug is mua-3mm-norwell-rp, \"cc\" dropped). Used in both nav CTA and hero CTA. «PRODUCT_IMG_SLUG» | Filename slug for product image (no extension) | norwell-active-ti-base-set | Image URL pattern: {{custom-llm_domain}}/wp-content/uploads/2026/03/{slug}.png «PRODUCT_IMG_ALT» | Alt text for hero product image | Norwell Active Ti-Base Set | Usually matches product name «CAT_LABEL» | Category label above h1 (displayed uppercase via CSS) | Titanium Base Sets (Engaging) | From product category «PRODUCT_NAME» | Product h1 display name | Norwell Active Ti-Base Set | Matches page title product portion","h":"Swap-point manifest"},{"f":253,"x":"Full :root palette (identical on all 63 pages): Token | Value | Usage --oi-blue | #0366CB | Primary brand blue, buttons, badges, bullet dots, section underlines --oi-blue-hover | #0255a8 | Button hover state --pewter | #818180 | Available for custom use --dark-navy | #232e57 | Nav background, footer background, headings --dark-slate | #3f405c | Compliance item text, gray badge text --white | #ffffff | Page background, card backgrounds --light-bg | #f4f6f9 | Hero image tile, compliance bar background, related card image areas --border | #e2e5ea | Card borders, compliance bar borders --text | #1a1a2e | Body text --text-light | #555 | Descriptive copy, feature bullets","h":"Tokens"},{"f":253,"x":"Fill one row of openform-config-example.json per SKU (expanding it to a JSON array for bulk runs) and use a simple find-replace or template script to swap all «FIELD» tokens. For a single page, do a manual find-and-replace in any editor. For all 63 pages, a loop over the config array renders the full catalog in seconds, the constant shell never changes, only the 16 swap fields. See openform-config-example.json for a fully worked example using norwell-active-ti-base-set.","h":"When to use"},{"f":254,"x":"Build date: 2026-05-01 Source: BrightPath/Marketing Templates/BrightPath-Co-Branded-PDF-Template.html (263 lines) Output: Template/print-pdf-shell.html (264 lines) Companion partials: Template/_partials/header-pill.html, Template/_partials/footer-pill.html Summary: Extracted the BrightPath chassis verbatim, tokenized the partner-specific identity values, and added a documentation header explaining how to consume the template. Two copy-paste partials extracted for the future \"compose a new template\" workflow per the briefing's optional ask."},{"f":254,"x":"Token | Where it appears {{DOCUMENT_TITLE}} | <title> {{PARTNER_NAME}} | alt text on header partner logo and footer partner logo {{PARTNER_LOGO_COLOR_URL}} | src of header partner logo {{PARTNER_LOGO_WHITE_URL}} | src of footer partner logo {{PARTNER_PHONE}} | Footer phone .fc-value {{PARTNER_WEBSITE}} | Footer website .fc-value {{PARTNER_EMAIL}} | Footer email .fc-value {{CONTENT_SLOT}} | Comment marker inside .white-area for derived templates {{PARTNER_SHORT_NAME}} is not used inside the chassis itself; it is reserved for derived templates (filenames, tight-space labels). The token is documented in the chassis header comment so future template authors know it exists.","h":"Placeholder tokens"},{"f":254,"x":"Apex Wordmark Primary (header pill): {{custom-llm_domain}}/wp-content/uploads/2026/01/Apex-Wordmark-Logo-Primary-scaled.png Apex Wordmark White (footer pill): {{custom-llm_domain}}/wp-content/uploads/2026/01/Apex-Wordmark-Logo-Single-Color-All-White-scaled.png Inter Google Fonts @import URL All print rules including the @media print footer-pill !important overrides All structural CSS (.page, .white-area, .header-pill, .footer-pill, etc.) Validation checklist: Check | Result All identity placeholders present (PARTNER_NAME, PARTNER_LOGO_COLOR_URL, PARTNER_LOGO_WHITE_URL, PARTNER_PHONE, PARTNER_WEBSITE, PARTNER_EMAIL, DOCUMENT_TITLE) | PASS {{PARTNER_SHORT_NAME}} documented (reserved for derived templates) | PASS: documented in header comment {{CONTENT_SLOT}} marker inside .white-area | PASS","h":"Hardcoded constants (NOT tokenized)"},{"f":254,"x":"No \"BrightPath\" string anywhere | PASS: grep -ic \"brightpath\" returns 0 No hardcoded partner phone anywhere, the footer reads {{contact_phone}} | PASS: no literal phone digits in the file No brightpath@apexinstruments.example anywhere | PASS Apex Wordmark URLs are constants, not partner tokens; only the domain origin resolves through {{custom-llm_domain}} | PASS Brand color hex values | PASS: chassis uses #68a2b9 (Tide, written lowercase in the CSS, same value as the canonical #245D63), #A8B6B7 (Copper), #00272C (Midnight Green). Print fallback #082638 only inside @media print. No stray off-palette navys. @page { size: 8.5in 11in; margin: 0; } present | PASS @media print block present with footer-pill !important overrides | PASS Inter is the only font loaded | PASS","h":"Hardcoded constants (NOT tokenized)"},{"f":254,"x":"File renders in a browser without console errors | PASS: pure HTML/CSS, no scripts Saved at Template/print-pdf-shell.html | PASS Deviations from the briefing: None. The chassis matches the source 1:1 modulo the identity tokenization the briefing requires. One stylistic addition: a documentation header comment at the top of the file explaining how to consume the template, which tokens to substitute, and how URLs resolve from the WordPress Asset Directory. This was not required by the briefing but makes the template self-documenting for future template authors.","h":"Hardcoded constants (NOT tokenized)"},{"f":254,"x":"The chassis is consumed by Build 2 (Welcome Flyer), Build 3 (B&R Guide), and Build 4 (What's Needed Guide). Each derived template should copy the chassis and inject its body content where {{CONTENT_SLOT}} is. Derived templates should add their own typography stack on top of Inter (e.g., DM Sans for guide headings) without removing the chassis Inter @import. Multi-page derived templates (Welcome Flyer is 2 pages, guides are 3-5 pages) should duplicate the .page block per page; the chassis CSS already includes page-break-after: always. .white-area has overflow: hidden. Multi-page guides that overflow the bottom of a page lose the overflow content silently. Tighten margins or split sections rather than letting content clip.","h":"Notes for downstream builds"},{"f":255,"x":"Type: print template File: REFERENCE-one-pager-template.html Used for: Reference copy of the PDF one-pager template. Locked and named REFERENCE to signal it should not be edited directly; copy before using. What's in it: Single letter-size page layout IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Header, content zone, and footer sections Identical structure to the design-system version in skills/generation When to use: Consult as a stable reference when the design-system copy needs to be rebuilt or verified. To produce a deliverable, copy this file. Never edit the REFERENCE copy directly."},{"f":256,"x":"Type: print template File: REFERENCE-trifold-brochure-template.html Used for: Reference copy of the tri-fold brochure template. Locked and named REFERENCE to signal it should not be edited directly; copy before using. What's in it: Six-panel trifold layout (front cover, inside panels, back panel) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Placeholder zones for headlines, body copy, and images per panel Identical structure to the design-system version in skills/generation"},{"f":256,"x":"Consult as a stable reference when the design-system copy needs to be rebuilt or verified. To produce a deliverable, copy this file. Never edit the REFERENCE copy directly.","h":"When to use"},{"f":257,"x":"Type: print template File: REFERENCE-two-pager-template.html Used for: Reference copy of the PDF two-pager template. Locked and named REFERENCE to signal it should not be edited directly; copy before using. What's in it: Two letter-size page layout IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Header, content zones across both pages, and footer Identical structure to the design-system version in skills/generation When to use: Consult as a stable reference when the design-system copy needs to be rebuilt or verified. To produce a deliverable, copy this file. Never edit the REFERENCE copy directly."},{"f":258,"x":"Type: social template File: social-facebook-post.html Used for: Facebook feed post graphic at native 1200×630 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1200×630 px IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Headline, subhead, and CTA text zones Background image/color area with overlay When to use: Use when producing a Facebook post image. This copy lives in /templates/social. Use the design-system version (skills/generation) when an agent is generating output programmatically."},{"f":259,"x":"Type: social template File: social-instagram-post.html Used for: Instagram portrait post graphic at native 1080×1350 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1350 px (4:5 portrait ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Headline, body, and CTA zones Background image/color area with overlay When to use: Use when producing an Instagram portrait-format feed post. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":260,"x":"Type: social template File: social-instagram-square.html Used for: Instagram square post graphic at native 1080×1080 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1080 px (1:1 square ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Headline, body, and CTA zones Background image/color area with overlay When to use: Use when producing an Instagram square-format post. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":261,"x":"Type: social template File: social-instagram-story.html Used for: Instagram and Facebook Story graphic at native 1080×1920 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1920 px (9:16 vertical ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Headline, body, and CTA zones optimized for vertical Story format Background image/color area with overlay When to use: Use when producing an Instagram or Facebook Story image. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":262,"x":"Type: social template File: social-linkedin-post.html Used for: LinkedIn feed post graphic at native 1200×627 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1200×627 px (near 1.91:1 ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Headline, body, and CTA zones Background image/color area with overlay When to use: Use when producing a LinkedIn feed post image. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":263,"x":"Type: social template File: social-linkedin-story.html Used for: LinkedIn Story graphic at native 1080×1920 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1920 px (9:16 vertical ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Headline, body, and CTA zones optimized for vertical Story format Background image/color area with overlay When to use: Use when producing a LinkedIn Story image. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":264,"x":"Type: social template File: social-universal-story.html Used for: Platform-agnostic Story graphic at 1080×1920 px for multi-platform publishing, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1920 px (9:16 vertical ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Generic layout not tied to any single platform's chrome Background image/color area with overlay When to use: Use when the same Story asset needs to publish across multiple platforms, or when the platform isn't specified. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":265,"x":"Type: social template File: social-youtube-thumbnail.html Used for: YouTube video thumbnail or webinar graphic at native 1280×720 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1280×720 px (16:9 ratio) IBM Plex Sans body + Archivo heading type stack Custom LLM Evergreen color system Large headline zone, supporting text, and logo placement area Background image/color area optimized for thumbnail readability When to use: Use when producing a YouTube thumbnail or webinar event graphic. This copy lives in /templates/social. Use the design-system version for agent-generated output."},{"f":266,"x":"Date: 2026-05-01 Author: Claude Audience: Jordan*, plus Claude Code (which will execute the briefings). Scope: 10 collateral types. For each: the strongest existing example, why it wins, and a paste-ready briefing for Claude Code at Template/Briefings/[CollateralType]-Briefing.md. Source picks (one line per collateral type): # | Collateral type | Source partner | Source file | One-liner rationale 1 | Co-Branded PDF chassis (the print shell) | BrightPath | BrightPath/Marketing Templates/BrightPath-Co-Branded-PDF-Template.html (263 lines) | Empty content area, all chassis pieces present (page, white-area, cyan border, header-pill, footer-pill, print rules). Every print PDF in the repo uses this skeleton."},{"f":266,"x":"You suggested microsite probably comes first. I am pushing back. Here is the order I recommend. Priority 1: Co-Branded PDF chassis: Why first. This is structural, not a deliverable. It looks like the smallest payoff but it unlocks the most downstream work. Five other templates (Welcome Packet, What's Needed Guide, Bench & Rack, Promo Flyer, Lab Slip) all sit on top of this exact print chassis (page + white-area + header-pill + footer-pill + print-color-adjust rules + footer-pill print overrides). Today every PDF re-implements this chassis inline. Once it lives in Template/print-pdf-shell.html, every later template imports it via include or copy-paste with confidence. Build this first and the other 5 print-PDF templates each take half the time.","h":"Priority order (with rationale)"},{"f":266,"x":"Why second, not first. The microsite is the most complex single deliverable and the linchpin that every partner page links to. Templating it captures the largest single chunk of repeated work (3,357 lines per partner copy today). Doing this second instead of first costs you nothing because the microsite does not depend on the print chassis. Priority 3: Welcome Packet: Why third. Highest-volume partner deliverable after the microsite itself. Every new partner gets one. Edit frequency is high (team changes, copy updates). Built on the print chassis, so doing chassis first cuts this work substantially.","h":"Priority 2: Microsite"},{"f":266,"x":"Why fourth. Highest update frequency in the system (pricing changes per quarter, per partner, per program). Templating this saves the most time on a recurring basis. Simpler structure than the microsite, so faster to build, and it is the highest-leverage maintenance template. Priority 5: What's Needed Guide (with section snippet library): Why fifth. Multiple guides per partner (FRX, Axis, Exact, Aperture, Bench & Rack, Mounts). The unlock is not the shell, it is the snippet library: section-card, important-bar, critical-bar, info-note, photo-grid, QR-block. Once these are extracted from BrightPath Aperture (the richest example), composing a new guide from sections becomes copy-and-arrange instead of write-from-scratch.","h":"Priority 4: Price List"},{"f":266,"x":"Why sixth. A specialization of the What's Needed Guide. Build it as a thin wrapper that pulls the same section snippets, with a Bench & Rack specific content profile (clinical photography requirements, fit registration, margin design notes). Should take a fraction of the time after #5 is in place. Priority 7: Promo Flyer: Why seventh. Lower volume, more partner-specific designs (each promo has its own visual concept). Templating saves time but unlocks less velocity than the items above. Built on the print chassis.","h":"Priority 6: Bench & Rack Guide"},{"f":266,"x":"Why eighth. Sales-strategy artifact, lower volume than ops collateral. The dual pair structure (microsite version plus PDF version) makes this slightly more complex to template than other types because it is two outputs from one input. Worth doing, but later. Priority 9: Lab Slip / Docket: Why ninth. Most lab slips today are PDFs. Only BioSummit has an HTML version. Low template-payoff per partner because most partners are happy with their existing PDF. Priority 10: Account Onboarding SOP: Why last. Only UnionSix has one. Until a second partner needs an SOP, building the template is speculative. Reuse signal is too low to prioritize.","h":"Priority 8: Executive Summary (dual pair)"},{"f":267,"x":"Type: print template File: welcome-flyer-template.html Used for: Reusable, partner-agnostic 2-page print-ready Welcome Flyer for onboarding new partners or accounts. What's in it: Two-page print layout (front welcome page + back detail/contact page) Full Custom LLM Evergreen color and type system Partner-agnostic placeholder zones for co-branding Header pill and footer pill integration points Chrome → Print → Save as PDF workflow When to use: Use when onboarding a new partner or account and a printed welcome flyer is needed. Copy the file, substitute partner tokens, add header/footer pills, and print to PDF."},{"f":268,"x":"Type: snippet File: header-pill.html Used for: Copy-paste header pill for print templates, sits absolutely at the top-center of a .page element with partner logo and Apex wordmark. What's in it: Header pill div absolutely positioned at top of .page Token: {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_NAME}} (alt text) Apex wordmark pre-loaded from CDN as default Overlays the white-area top edge of the print page When to use: Paste into any co-branded print template to add the standard Apex header bar. Replace {{PARTNER_LOGO_COLOR_URL}} with the partner's color logo URL."},{"f":269,"x":"Working notes for this project. This placeholder keeps the folder in place when the Company Brain is uploaded to OneDrive. Delete it once real content is added."},{"f":270,"x":"Reference files and source material for this project. This placeholder keeps the folder in place when the Company Brain is uploaded to OneDrive. Delete it once real content is added."},{"f":271,"x":"Finished deliverables for this project, organized by type. This placeholder keeps the folder in place when the Company Brain is uploaded to OneDrive. Delete it once real content is added."},{"f":272,"x":"*The reusable starting points. What exists, what's still needed, and the standard each template follows.* Templates that exist: *These are ready to clone and fill. Start from the blank, then match a finished example in 05 Approved Library.* Template | File Microsite | microsite/microsite-template.html Welcome flyer | Welcome Flyer/welcome-flyer-template.html Bench & Rack guide | Guides/bench-and-rack-guide-template.html What's-Needed guide | Guides/whats-needed-guide-template.html Print PDF chassis | print-pdf-shell.html Shared partials | _partials/ (header-pill, footer-pill) Project skeleton | _project-template/ (clone per new project) Build briefs | Briefings/ (10 deliverable briefs)"},{"f":272,"x":"t; ⚠️ No blank template yet for: price sheet, lab slip, executive summary, one-pager, postcard, TAT document, case study, email, and PowerPoint deck. Build each from a finished example in 05 Approved Library, then save the blank here. Every template type needs five things: A blank starting template (the reusable shell). At least one finished example (so the AI matches format). A source / reference folder (where it came from). A QA checklist (what to check before approval). A \"when to use this\" note. t; 💡 How to build partner collateral: follow the full playbook at 01 Instructions / output-types / DIRECTIONS-Partner-Collateral-Build.md (brand rules, the PDF chassis, and step-by-step per deliverable). See: Output types","h":"Templates to build"},{"f":273,"x":"Date: 2026-05-03 Author: Claude (template extraction pass) What was built: Reverse-engineered three reusable templates from Caravelle's finished artifacts (which were originally rebranded UnionSix files), plus the 8-snippet component library, plus a working regression test that proves the template + config workflow produces a renderable artifact for any new partner. Path | Type | Status Template/print-pdf-shell.html | chassis | already existed (built earlier) Template/_partials/header-pill.html | chassis partial | already existed Template/_partials/footer-pill.html | chassis partial | already existed Template/Microsite/microsite-template.html | microsite | already existed Template/Welcome Flyer/welcome-flyer-template.html | derived template | NEW"},{"f":273,"x":"Template/Welcome Flyer/welcome-flyer-config-example.json | config example | NEW (Caravelle as worked example) Template/Guides/bench-and-rack-guide-template.html | derived template | NEW Template/Guides/bench-and-rack-config-example.json | config example | NEW (Caravelle as worked example) Template/Guides/whats-needed-guide-template.html | derived template | NEW Template/Guides/whats-needed-guide-config-example.json | config example | NEW (Caravelle Mount as worked example) Template/Guides/snippets/section-card-text-only.html | snippet | NEW (extracted from Caravelle Mount) Template/Guides/snippets/section-card-with-image.html | snippet | NEW (synthesized; pattern not in Mount guide) Template/Guides/snippets/important-bar.html | snippet | NEW (extracted from BrightPath Aperture)"},{"f":273,"x":"For each template, ran the validator: ``` grep -ic \"caravelle|dara|walter|nadia|317-7100|caravelle@apexinst\" Template | Forbidden matches | Notes welcome-flyer-template.html | 0 (real) | substring \"nadia\" appears inside the word \"registering\", false positive bench-and-rack-guide-template.html | 0 | clean whats-needed-guide-template.html | \"caravelle\" / \"mount\" appear only inside doc comments at the top of the file describing the template's purpose; zero in rendered content | clean All 8 snippets | 0 | clean","h":"Forbidden-string check"},{"f":273,"x":"$ cd Template/_test $ python3 render.py \"../Welcome Flyer/welcome-flyer-template.html\" \\ fakeco-config.json FakeCo-Welcome-Flyer.html OK: rendered FakeCo-Welcome-Flyer.html (43,808 bytes); zero unfilled tokens. The output FakeCo-Welcome-Flyer.html: contains 0 references to Caravelle/Dara/Walter/Nadia contains 15 references to \"FakeCo\" (header/footer pills, hero, value prop, partnership block, support team callout) contains 2 references to \"Jane Doe\" (the fake AE, in the team sidebar and image alt text) has 0 unfilled {{TOKEN}} placeholders other than the literal docstring {{PLACEHOLDER}} used in the comment header Conclusion: the Welcome Flyer template is real. Same render.py driver plus the corresponding config-example would render bench-and-rack and whats-needed templates identically.","h":"Regression test results"},{"f":273,"x":"The Caravelle B&R Guide (Caravelle/Bench and Rack Guide/...html) and the Caravelle Mount Guide (Caravelle/Mount Guide/...html) are nearly identical files. They share: Same chassis (page, white-area, header pill, footer pill, print rules) Same fonts (DM Sans + Inter) Same CSS classes (.section-card, .section-banner, .check-list, .key-details, .photo-images, .critical-bar, .rx-columns) Same 3-section structure The only meaningful differences are: Page title Section content (universal clinical vs. mount-specific) One extra <ul> of \"Mount Information\" Docket fields Briefing 06 originally aspired to a 9-section B&R guide that's \"standalone, not a What's Needed wrapper.\" The reality on disk is that they are the same template. I extracted them as separate files because the briefing","h":"1. The B&R Guide is structurally just the What's Needed Guide"},{"f":273,"x":"Update Caravelle's Mount Guide critical-bar to use the canonical snippet so the artifact and the snippet library agree. Same for any other guides that use the older simple-navy or amber variants. Pilot Trellis on the Welcome Flyer template first. That's the fastest test a single config + a render produces a deliverable. Decide on B&R as separate-template-or-not. If the consolidation recommendation is accepted, delete bench-and-rack-guide-template.html and document B&R as \"compose using whats-needed-guide-template.html with the B&R sections from bench-and-rack-config-example.json's SECTIONS_HTML.\" Build a Trellis config to validate. Same workflow as fakeco-config.json but with real Trellis data. If render.py prints OK: zero unfilled tokens, the templates are production-ready for Trellis.","h":"Recommended next steps"},{"f":274,"x":"A reusable, partner-agnostic print-ready PDF shell. This is the structural skeleton every print PDF in the Apex Instruments system sits on: a 8.5x11in page with a navy background, a white content area inset from the edges with a cyan border, a header pill at top holding the Apex and partner logos joined by a gold-gradient divider, and a glass-effect footer pill at the bottom holding white logos plus phone, website, and email. The chassis ships with no body content; the body is filled in by every derivative template (Welcome Packet, What's Needed Guide, Bench and Rack Guide, Promo Flyer, Lab Slip, etc.).","h":"What to build"},{"f":274,"x":"BrightPath/Marketing Templates/BrightPath-Co-Branded-PDF-Template.html (263 lines). This file is the empty chassis already. You are extracting it, tokenizing the partner-specific values, and saving it as the canonical template. What to extract: The full <!DOCTYPE html> through </html> shell. All CSS inside the <style> block. Specifically preserve: The @import for Inter from Google Fonts. The @page { size: 8.5in 11in; margin: 0; } rule. The @media print block including the page sizing rules and the footer-pill !important overrides for background, backdrop-filter, and border-color. The .page rule (8.5in x 11in, navy #052030 background, overflow: hidden). The .white-area rule (inset 0.3in top/left/right, 1in from bottom, white background, 5px #4abeee border).","h":"Source file to use as the reference"},{"f":274,"x":"The .header-pill rule (white background, 5px cyan border, no top border, rounded bottom corners 14px, holds two logo <img> plus a .pill-divider with the gold gradient). The .footer-pill rule (glass effect with rgba(8, 38, 56, 0.85) background, backdrop-filter: blur(20px) saturate(140%), 0.6in tall, 0.3in from bottom, holds .footer-logos and .footer-contact). The footer SVG icons (phone, globe, email). Keep these inline as SVG. The <body> markup: .page containing .white-area (with a comment ` placeholder), then .header-pill and .footer-pill`.","h":"Source file to use as the reference"},{"f":274,"x":"Every partner-specific value becomes a token. The chassis itself does NOT need content tokens (those are the derived template's job); it only needs identity tokens (logos, contact info, partner display name). Placeholder | What it is | Example value {{PARTNER_NAME}} | Full partner display name used in <title> and as alt text on logos | \"BrightPath\" {{PARTNER_SHORT_NAME}} | Partner short name, used where space is tight or filenames | \"BrightPath\" {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color version, used in the header pill | https://apexinstruments.example/wp-content/uploads/2026/02/BrightPath-Logo-Color-scaled.png","h":"What to replace with placeholders"},{"f":274,"x":"Brand colors (canonical): Apex Blue #1882C7: not used in the chassis directly, but reserved for content body. Devices Blue #4ABEEE: used for the cyan border on .white-area, the header-pill border, and the footer-pill icon strokes. Lab Gold #B3A369: used for the header-pill divider gradient (linear-gradient(180deg, transparent, #B3A369, transparent)) and the footer-pill divider gradient. Harbor Blue #052030: used for the .page background. The footer-pill print fallback uses #082638 (a slightly lighter navy that prints more reliably). Alliance Blue #C3E8FA: not used in the chassis. Font: Inter (loaded from Google Fonts). Hardcode the @import URL exactly as in the source. Print rules (do not change)","h":"Brand rules to enforce"},{"f":274,"x":"Before handing back, run this check on the output: ☐ All identity placeholders ({{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}}, {{DOCUMENT_TITLE}}) appear in the output. ☐ No \"BrightPath\", no \"(949) 409-3299\", no \"brightpath@apexinstruments.example\" remains anywhere in the file. ☐ Apex Wordmark URLs are hardcoded and not tokenized. ☐ Brand color hex values match the canonical set: #1882C7, #4ABEEE, #B3A369, #052030, #C3E8FA. Specifically the chassis should use #4ABEEE, #B3A369, and #052030. No other brand-color hex codes should appear (no stray #082638 outside the print fallback, no other navys). ☐ @page { size: 8.5in 11in; margin: 0; } is present.","h":"Validation checklist"},{"f":275,"x":"A reusable, partner-agnostic microsite template. The microsite is the highest-leverage single deliverable: a scrollable, animated landing page hosted at apexinstruments.example/[partner-slug]/ that serves as the partner's home for everything (onboarding steps, downloadable resources, the dedicated team, the portal, and FAQs). Single self-contained HTML file with embedded CSS, JS, mesh-gradient backgrounds, and Font Awesome icons, designed to live inside a WordPress / Bricks code block. This briefing replaces the earlier 02-Microsite-Briefing.md draft, which had the wrong section count (6 vs the real 8) and missed several critical elements (sticky header / glass sidebar nav, the 5-step roadmap, the Welcome Message from AE, AI-generated FAQs, the Card Catalog reference).","h":"What to build"},{"f":275,"x":"Larchwood/Larchwood Microsite/Larchwood-Microsite.html (3,296 lines). This is the most recent and refined version. BrightPath was the original master in concept, but Larchwood has cleaner naming and more recent content patterns. Prefer Larchwood for structural patterns; spot-check BrightPath (BrightPath/Microsite/BrightPath Devices Partner Page, Apex Instruments.html) and UnionSix (UnionSix/Microsite/UnionSix-Microsite.html) only to confirm cross-partner consistency. The 8 sections, in order top to bottom: The microsite has 8 sections. Document each one in the template with a clear comment block.","h":"Source file to use as the reference"},{"f":275,"x":"The FAQ section is AI-generated AFTER the rest of the microsite is built. Workflow: Render the rest of the template with placeholders filled in. Read the resulting microsite top-to-bottom. Generate 9 partner-specific FAQs that reflect what's actually on the site (the resource cards selected, the AE name, the team contacts, etc.). Apply the alternating question color pattern: q-cyan, q-blue, q-gold, q-cyan, q-blue, q-gold, q-cyan, q-blue, q-gold (Devices Blue, Apex Blue, Lab Gold, then repeat). Each FAQ answer should reference the actual links on the page (e.g., the Lab Slip PDF URL the resource card uses, the AE's email, the support team's phone, the Tech Prefs Form URL).","h":"FAQ generation (do NOT pre-fill the FAQ section)"},{"f":275,"x":"Placeholder | What it is | Example {{PARTNER_NAME}} | Full partner display name | \"Larchwood Devices\" {{PARTNER_SHORT_NAME}} | Short name where space is tight | \"Larchwood\" {{PARTNER_SLUG}} | URL-safe slug, used in og:url and canonical URLs | \"larchwood-devices\" {{PARTNER_LOGO_COLOR_URL}} | Header logo, color version | (resolve via directory tag [partner-slug, logo, color]) {{APEX_WORDMARK_LOGO_URL}} | Apex Wordmark Primary, used in header | hardcode: https://apexinstruments.example/wp-content/uploads/2026/01/Apex-Wordmark-Logo-Primary-scaled.png {{APEX_ICON_FAVICON_URL}} | Apex favicon | hardcode: Apex Icon Logo Primary {{PARTNER_PORTAL_EMAIL}} | Partner-specific email alias for portal/general use | larchwood@apexinstruments.example","h":"Identity (header, footer, meta)"},{"f":275,"x":"{{NEW_CLINIC_FORM_URL}} | Step 1 the CRM form URL {{TECH_PREFS_FORM_URL}} | Step 2 the CRM form URL {{ONBOARDING_VIDEO_URL}} | Step 3 the CRM video URL. If unavailable, render \"Coming Soon\" placeholder. {{ONBOARDING_VIDEO_FALLBACK_TEXT}} | When ONBOARDING_VIDEO_URL is empty, the text to show (default: \"Coming Soon\") {{AE_CALENDAR_URL}} | Step 5 the CRM meetings URL (AE-specific) Step 4 portal URL is https://portal.apexinstruments.example/ (hardcoded). Step labels are hardcoded. Resource Cards: {{RESOURCE_CARD_IDS}} | Array of card IDs from Template/Microsite/Card_Catalog.json to render in the partner's Resources section","h":"5-Step Onboarding Roadmap"},{"f":275,"x":"{{FAQ_ITEMS}} | Array of 9 generated FAQs. Each: {question, answer_html, color_class}. color_class cycles q-cyan, q-blue, q-gold. Footer: {{PARTNER_SUPPORT_PHONE}} | Dedicated Support phone (partner-specific). Fallback to general Apex support if not yet assigned. {{PARTNER_SUPPORT_EMAIL}} | Dedicated Support email (partner-specific). Fallback to general Apex support if not yet assigned. {{APEX_FALLBACK_PHONE}} | General Apex support phone, used when partner-specific is not set {{APEX_FALLBACK_EMAIL}} | General Apex support email, used when partner-specific is not set Closing Quote is hardcoded (same for every partner).","h":"FAQ (generated AFTER build)"},{"f":276,"x":"A reusable, partner-agnostic 2-page print-ready Welcome Flyer. This is the highest-volume per-partner deliverable. Every new partner office gets one. It is built on top of the print chassis from Briefing 01 and adds: a hero with welcome copy, a sidebar with team headshots, an About block, a Partnership block, a Why Choose Us block, a specialties grid, a Ready-to-Send block, a Getting Started Roadmap, and a Doctor's Portal section. t; Naming note (Jordan* preference 2026-05-01): the canonical name for this artifact is \"Welcome Flyer\", not \"Welcome Packet\". All earlier references to \"Welcome Packet\" in this briefing have been renamed.","h":"What to build"},{"f":276,"x":"Larchwood/Welcome Flyer/Larchwood Devices, Apex Instruments Welcome Packet.html (1,198 lines). Largest of the 4 candidates. Cleanest section anatomy. If the print chassis from Briefing 01 (Template/print-pdf-shell.html) is already built, USE IT as the page wrapper rather than re-implementing the chassis inline. The Welcome Flyer should be: chassis from Briefing 01 + body content tokens from this briefing. What to extract: Page 1 layout: Hero section at top: Background image (lab photo) with navy-to-white gradient overlay. \"WELCOME\" pill (small uppercase text). Big title with cyan accent on key word. Gold-gradient subtitle pill. Below hero, content grid: 230px sidebar + 1fr main content. Sidebar: Team card with blue-gradient background.","h":"Source file to use as the reference"},{"f":276,"x":"3 team members stacked. Each: circular headshot (~80px), name, role, email, phone. Main content: \"About Us\" block. \"Partnership\" block. \"Why Choose Us\" block (3 numbered value props). Page 2 layout: \"Our Specialties\" section: 3x2 grid of capability icons (e.g., FRX, Bench & Rack, Mounts, Digital Housings, Scanning Support, Custom Solutions). Each cell: icon + label. \"Ready to Send Your First Case?\" section: two cards side-by-side (Digital submission vs Physical submission), each with a 3-step checklist. \"Getting Started Roadmap\": 5-step horizontal timeline. Each step: numbered circle + text. QR code block: links to the partner microsite. Doctor's Portal section: dark navy background, features grid + portal screenshot. CTA to portal.apexinstruments.example.","h":"Source file to use as the reference"},{"f":276,"x":"All .hero-*, .team-card-*, .about-block, .partnership-block, .value-prop-*, .specialty-icon, .send-card-*, .roadmap-step-*, .qr-block, .portal-section-* CSS classes. The roadmap-step CSS (numbered circles connected by a line is fiddly; preserve exactly). The 3x2 specialty grid (responsive layout cues if any). What to replace with placeholders: Placeholder | What it is {{PARTNER_NAME}} | Full partner display name {{PARTNER_SHORT_NAME}} | Partner short name {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color version (header pill) {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white version (footer pill, portal section) {{PARTNER_PHONE}} | Footer phone {{PARTNER_WEBSITE}} | Footer website (default apexinstruments.example) {{PARTNER_EMAIL}} | Footer email alias","h":"What to extract specifically"},{"f":276,"x":"{{HERO_TITLE}} | Welcome Flyer hero h1 (e.g., \"Welcome to Your Apex Instruments Partnership\") {{HERO_TITLE_ACCENT_WORD}} | Word in the hero title to render in cyan accent (e.g., \"Partnership\") {{HERO_SUBTITLE}} | Gold-pill subtitle text (e.g., \"A Custom Engineered Solution for Larchwood Devices\") {{HERO_BG_IMAGE_URL}} | Hero background image URL {{TEAM_MEMBERS}} | Array of 3 team members. Each: {name, role, email, phone, headshot_url} {{ABOUT_TEXT}} | About block paragraph {{PARTNERSHIP_TEXT}} | Partnership block paragraph {{VALUE_PROPS}} | Array of 3 value props. Each: {number, title, body} {{SPECIALTIES}} | Array of 6 specialty cells. Each: {icon_svg_or_url, label} {{DIGITAL_SEND_STEPS}} | Array of 3 steps for the Digital submission card","h":"What to extract specifically"},{"f":276,"x":"Template/Welcome Flyer/welcome-flyer-template.html Also save: Template/Welcome Flyer/welcome-flyer-config-example.json showing the full input schema. Brand rules to enforce: Inter font throughout (this is a print PDF, not a microsite). No Lora or Montserrat. Hero subtitle uses Lab Gold (#B3A369) gradient pill: background: linear-gradient(135deg, #B3A369 0%, #E6D695 50%, #B3A369 100%). Print fallback: solid rgba(179, 163, 105, 0.7) with print-color-adjust: exact. Hero title accent word uses Devices Blue (#4ABEEE). Numbered value props and roadmap steps use Apex Blue (#1882C7) for the numbered circle background. Portal section uses Harbor Blue (#052030) background with white text and cyan accents. Specialty icons use Apex Blue strokes.","h":"Where to save the output"},{"f":277,"x":"A reusable, partner-agnostic Price List template. This is the highest-update-frequency artifact in the system: pricing changes per quarter, per partner, per program. Templating cuts the most ongoing maintenance time. The output is a print-ready PDF (HTML source) that lists products grouped by category with prices, optional turnaround times, and partner branding. Source file to use as the reference: Larchwood/Larchwood Price List/apex_price_list.html (550 lines). Almost double the line count of UnionSix (297) and Caravelle (329), suggesting the most-developed table structure. Cleanest filename (no partner-prefix), suggesting it was already drafted as a near-template.","h":"What to build"},{"f":277,"x":"The print-PDF chassis (page, white-area, header-pill, footer-pill). If Template/print-pdf-shell.html from Briefing 01 is built, import it. Otherwise re-implement the chassis inline using the same rules. The price-table CSS: Category section header (cyan-accented bar). Table styling: alternating row colors using Alliance Blue #C3E8FA for the alt rows. Table headers in Apex Blue #1882C7 background with white text. Price column right-aligned, numeric, monospaced if useful. Any \"Turnaround Time\" column or section (some partners include it, some don't). \"Effective Date\" stamp (small text, near the title). Notes / disclaimers section at the bottom (terms, custom-quote callouts, premium-product asterisks).","h":"What to extract"},{"f":277,"x":"Placeholder | What it is {{PARTNER_NAME}} | Full partner display name {{PARTNER_SHORT_NAME}} | Partner short name {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color (header pill) {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white (footer pill) {{PARTNER_PHONE}} | Footer phone {{PARTNER_WEBSITE}} | Footer website {{PARTNER_EMAIL}} | Footer email {{PRICE_LIST_TITLE}} | Document title (e.g., \"UnionSix Price List\") {{EFFECTIVE_DATE}} | \"Effective: 2026-04-01\" or similar {{PRICE_CATEGORIES}} | Array of categories. Each: {category_name, intro_note, products} where products is an array of {product_name, sku_or_code, description, price, turnaround_days, is_premium} {{INCLUDE_TURNAROUND}} | Boolean: render the Turnaround column or not {{NOTES}} | Array of footer notes/disclaimers","h":"What to replace with placeholders"},{"f":277,"x":"{{CUSTOM_QUOTE_CTA}} | Optional CTA text (e.g., \"For custom or volume pricing, contact your account manager\") Where to save the output: Template/Price List/price-list-template.html Also save: Template/Price List/price-list-config-example.json showing the categories/products structure. Brand rules to enforce: Alternating table rows: #C3E8FA (Alliance Blue) every other row. Table headers: #1882C7 (Apex Blue) background, white text. Category section bars: cyan accent (#4ABEEE) underline or left-border. Premium products (those marked is_premium: true): Lab Gold (#B3A369) accent on the row (e.g., a small gold dot or italic price). Inter font throughout. Page chassis from Briefing 01 applies. Effective date is small (10px), placed near the document title.","h":"What to replace with placeholders"},{"f":277,"x":"Numeric prices are right-aligned with consistent decimal alignment. Validation checklist: ☐ Every placeholder in the table above appears in the template. ☐ No specific partner name, no specific price values, no specific products remain. ☐ Alternating table rows use #C3E8FA. ☐ Table headers use #1882C7 with white text. ☐ Premium-row gold accent works. ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Multi-page handling: if {{PRICE_CATEGORIES}} is long, content paginates without breaking the chassis. ☐ Cmd+P print preview is clean. ☐ Effective date renders as expected. ☐ Saved at Template/Price List/price-list-template.html. ☐ Config example JSON saved alongside.","h":"What to replace with placeholders"},{"f":278,"x":"Two artifacts: A reusable What's Needed Guide template (the print-ready guide shell). A snippet library of reusable guide components: section-card, important-bar, critical-bar, info-note, photo-grid, QR-block. This is the workhorse of the Apex clinical content system. Every partner produces multiple guides (FRX, Axis, Exact, Aperture, Bench & Rack, Mounts). Templating the shell plus extracting the components turns \"write a new guide from scratch\" into \"compose a new guide from snippets.\" Source files to use as the reference: Hybrid: Primary (chassis + baseline section pattern): BrightPath/FRX Guide/BrightPath-Guide-FRX-Whats-Needed.html (733 lines). Cleanest baseline.","h":"What to build"},{"f":278,"x":"Secondary (richer component library): BrightPath/Aperture What's Needed Guide/BrightPath Aperture What's Needed Guide, Apex Instruments.html (1,018 lines). Most feature-rich variant. Pull these specific components from Aperture: important-bar, critical-bar, info-note, photo-grid, QR-block. What to extract: From the FRX guide (chassis + baseline): Page chassis (use Briefing 01 if already built). Multi-page structure with page-break-after: always. Guide title block at top of each page. The standard .section-card component: .section-banner: numbered banner at top of card (.section-num for the number circle, .section-text for the section title). .section-body: card body with optional .card-header (icon + instruction text) and .body-text paragraphs or bullets.","h":"What to build"},{"f":278,"x":"Placeholder | What it is {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} | Standard chassis identity tokens {{PROGRAM_NAME}} | Clinical program (e.g., \"FRX\", \"Axis\", \"Aperture\", \"Exact\", \"Bench & Rack\", \"Mounts\") {{GUIDE_TITLE}} | Full guide title (e.g., \"FRX What's Needed Guide\") {{GUIDE_SUBTITLE}} | Optional subtitle {{SECTIONS}} | Array of section objects. Each: {number, title, has_image, image_url, instructions, body_blocks, callouts}. body_blocks is an array of `{type: \"paragraph\" | \"bullets\", content}. callouts is an array of {type: \"important\" | \"critical\" | \"info\", content}`.","h":"Template-level placeholders"},{"f":278,"x":"Each snippet is a copy-paste HTML block with token markers: Template/Guides/snippets/section-card-text-only.html Template/Guides/snippets/section-card-with-image.html Template/Guides/snippets/important-bar.html Template/Guides/snippets/critical-bar.html Template/Guides/snippets/info-note.html Template/Guides/snippets/photo-grid-2x2.html Template/Guides/snippets/photo-grid-3x2.html Template/Guides/snippets/qr-block.html Each snippet uses placeholders like {{SECTION_NUMBER}}, {{SECTION_TITLE}}, {{INSTRUCTION_TEXT}}, {{IMAGE_URL}}, {{CALLOUT_BODY}}, {{QR_IMAGE_URL}}, {{QR_LABEL}}.","h":"Snippet library (saved separately)"},{"f":278,"x":"Template/Guides/whats-needed-guide-template.html (the shell) Template/Guides/snippets/*.html (the component library) Template/Guides/whats-needed-guide-config-example.json (input schema) Brand rules to enforce: DM Sans (headings) + Inter (body). NOT Montserrat / Lora (those are microsite/web only). Section banner: Apex Blue #1882C7 background or cyan-to-blue gradient. Critical bar: navy-to-blue gradient linear-gradient(135deg, #052030, #1882C7) with Lab Gold icon. NEVER amber or brown. Important bar: solid Harbor Blue #052030 background. Info note: light gray #f1f5f9 background with #1882C7 left border (3-4px). Section image max-height 120px (page-overflow constraint). Page chassis from Briefing 01 applies. Footer-pill !important print overrides apply.","h":"Where to save the output"},{"f":278,"x":"☐ Placeholder tokens for variable text are present. ☐ Brand colors match the canonical hex values. ☐ Inline-styled where reasonable so each snippet is self-contained when pasted. ☐ Saved at Template/Guides/snippets/[name].html. ☐ Critical-bar specifically uses navy-to-blue gradient with gold icon (not amber).","h":"For each snippet"},{"f":279,"x":"A reusable, partner-agnostic Bench & Rack Guide template. This is a standalone print-ready clinical guide for Bench & Rack case submissions. It is built directly on the Co-Branded PDF Chassis from Briefing 01. It is NOT a thin wrapper around Briefing 05's What's Needed Guide template, and it does NOT use Briefing 05's snippet library. B&R has its own section structure tuned specifically to Bench & Rack clinical workflow. t; Naming note (Jordan* preference 2026-05-01): B&R was previously briefed as a thin wrapper around the What's Needed Guide. That approach is dropped. B&R is its own template with its own sections, built from scratch on the print chassis.","h":"What to build"},{"f":279,"x":"UnionSix/Bench and Rack Guide/UnionSix-Guide-Bench-and-Rack.html (702 lines). Larchwood has a Bench & Rack Guide of the same line count (Larchwood/Larchwood Bench & Rack Guide/Larchwood-Bench-and-Rack-Guide.html). UnionSix picked because it is the more recently maintained version. Spot-check Larchwood only to confirm structural consistency. What to extract: Read the full source file. Extract the B&R specific section structure, NOT the generic What's Needed pattern. The B&R guide has its own anatomy: Page chassis: Use Briefing 01 (Template/print-pdf-shell.html) as the page wrapper. Inherit the white-area, header pill, footer pill, print rules, fonts. Do NOT re-implement the chassis inline. Document title block at the top of the first content page: Guide title (e.g., \"Bench & Rack Guide\")","h":"Source file to use as the reference"},{"f":279,"x":"Partner attribution sub-line (e.g., \"For UnionSix Devices partners\") Optional intro paragraph B&R specific sections (in clinical workflow order): Section 1: Case Overview: brief intro paragraph explaining the B&R workflow at Apex Section 2: Required Photography: clinical photo requirements (frontal high lantern, frontal relaxed, profile relaxed, finish reference, pre-fit adjacent). Use the actual photo grid from the source. Section 3: Fit Registration: requirements for fit scan / measurement including centric seating notes Section 4: Margin Design: margin capture requirements, finish line cleanup Section 5: Opposing Rack: full opposing scan requirements Section 6: Finish Selection: finish matching protocol (Verona Classical or 3D Range), datum-line photo, finish tab placement","h":"Source file to use as the reference"},{"f":279,"x":"Section 7: Material Selection: zirconia, lithium disilicate, layered, full-contour notes; reference partner's price sheet for current options Section 8: Submission Checklist: simple checkbox list (digital scan files, lab slip, photos, special instructions) Section 9: Special Considerations: optional section for cases with extras (seating device, mount adapter, esthetic case escalation) B&R specific callouts: build these inline; they are NOT shared with Briefing 05's snippet library. Important note bar (navy): for \"Must capture full margin\", \"Fit must be in centric seating\" type emphasis Pro tip callout (light gray with cyan left border): for clinical tips that improve outcomes Photo grid component: 2x3 or 3x2 grid for clinical photography requirements","h":"Source file to use as the reference"},{"f":279,"x":"Finish tab block: visual layout showing finish tab placement Footer pill: from the chassis, partner-specific contact info. What to replace with placeholders: Placeholder | What it is {{PARTNER_NAME}} | Full partner display name (e.g., \"UnionSix Devices\") {{PARTNER_SHORT_NAME}} | Partner short name {{PARTNER_LOGO_COLOR_URL}} | Partner logo, color version (header pill) {{PARTNER_LOGO_WHITE_URL}} | Partner logo, white-on-transparent (footer pill) {{PARTNER_PHONE}} | Footer phone {{PARTNER_WEBSITE}} | Footer website (default apexinstruments.example) {{PARTNER_EMAIL}} | Footer email {{GUIDE_TITLE}} | Document title (default: \"{{PARTNER_NAME}} Bench & Rack Guide\") {{GUIDE_SUBTITLE}} | Optional subtitle (e.g., \"Submission Requirements & Best Practices\")","h":"Source file to use as the reference"},{"f":279,"x":"{{INTRO_PARAGRAPH}} | Optional intro paragraph at top {{FINISH_GUIDE_SYSTEM}} | \"Verona Classical\" or \"3D Range\" or partner-specific {{MATERIAL_OPTIONS}} | Array of available materials for this partner. Each: {name, indication, notes} {{PHOTO_REQUIREMENTS}} | Array of required photos. Each: {label, image_url, instruction} {{SPECIAL_CONSIDERATIONS}} | Array of partner-specific extras (e.g., UnionSix mount adapter, Delta Craft esthetic escalation). Each: {title, body}. Optional; can be empty. {{INCLUDE_FINISH_TAB_BLOCK}} | Boolean: render the finish tab visual block or not {{INCLUDE_SEATING_DEVICE_NOTE}} | Boolean: include the seating device clause in special considerations URLs that resolve from _WordPress_Asset_Directory.json","h":"Source file to use as the reference"},{"f":280,"x":"A reusable Promo Flyer template for partner promotions (e.g., First 5 Cases free, First 2 Bench Units on us, Rebate program, Limited-time offer). Single-page print-ready PDF (HTML source) with a hero, a bold offer block, mechanics or terms, a CTA, and the standard chassis. This is a lower-volume, higher-design-variation deliverable, so the template should be flexible: hero image, offer headline, mechanics list, terms, and CTA, all tokenized. Source file to use as the reference: UnionSix/First 5 Cases Promo/UnionSix First 5 Cases Promo.html (790 lines). Largest of the promo candidates and \"First 5 Cases\" is the most generic promo concept (every partner could run a variant of this).","h":"What to build"},{"f":280,"x":"If you also want a comparison reference, Caravelle/Rebate/Caravelle Rebate Flyer, Apex Instruments.html (806 lines) shows the rebate variation. Use it only to confirm structural similarity. What to extract: The print-PDF chassis (use Briefing 01 if built). Hero block: Strong headline (the promo offer). Sub-headline (qualifying language). Hero image or graphic. Optional cyan or gold accent stripe. Mechanics block: Numbered or bulleted list of how the promo works. Terms block: Small text, time-limited disclaimers, eligibility conditions. CTA block: Primary CTA (often \"Send your first case\", \"Claim your offer\", \"Contact us\"). Optional QR code or short URL. Footer pill (chassis).","h":"What to build"},{"f":280,"x":"Placeholder | What it is Standard chassis tokens ({{PARTNER_NAME}}, etc.) | Same as Briefing 01 {{PROMO_NAME}} | Promo program name (e.g., \"First 5 Cases\", \"First 2 Bench Units on Us\", \"Spring Rebate\") {{PROMO_TAGLINE}} | Hero h1 / dominant headline {{PROMO_SUBHEAD}} | Sub-headline qualifying the offer {{HERO_IMAGE_URL}} | Hero graphic or product photo {{OFFER_VALUE}} | The dollar value or \"free\" or \"% off\" of the offer {{MECHANICS}} | Array of mechanics steps. Each: {number, body} {{TERMS}} | Array of small-text disclaimers {{ELIGIBILITY_NOTE}} | One-line eligibility statement (e.g., \"New customers only\", \"Existing partners can opt in\") {{CTA_TEXT}} | Primary CTA button text {{CTA_HREF}} | Primary CTA href (mailto, tel, or URL) {{QR_CODE_URL}} | Optional QR code image URL","h":"What to replace with placeholders"},{"f":280,"x":"{{QR_TARGET_URL}} | URL the QR encodes {{PROMO_END_DATE}} | \"Offer ends 2026-12-31\" or similar Where to save the output: Template/Promos/promo-flyer-template.html Also save: Template/Promos/promo-flyer-config-example.json. Brand rules to enforce: Inter font throughout. Hero headline can use Apex Blue (#1882C7) or Harbor Blue (#052030) for emphasis. Offer value (the headline number or \"FREE\") should be visually loud. Use Lab Gold (#B3A369) or Apex Blue, your call based on contrast against the hero image. Mechanics numbered circles use Apex Blue background. Terms text small (10px or under), Pewter / muted gray color. Page chassis from Briefing 01 applies.","h":"What to replace with placeholders"},{"f":280,"x":"Single-page print layout. If the promo content is long, prioritize hero + mechanics + CTA on page 1; terms can wrap to a second page if needed. Validation checklist: ☐ Every placeholder in the table above appears in the template. ☐ No \"UnionSix\" or \"First 5 Cases\" specific text remains. ☐ No specific dollar values or program-end dates remain. ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Hero has a tokenized image and headline. ☐ Mechanics renders as a numbered list. ☐ Terms render in small text. ☐ CTA button is visually prominent. ☐ Optional QR code block is present (can be empty/null). ☐ Cmd+P print preview is clean. ☐ Saved at Template/Promos/promo-flyer-template.html. ☐ Config example JSON saved alongside.","h":"What to replace with placeholders"},{"f":281,"x":"A reusable Executive Summary template that generates BOTH a microsite version (web pitch, scrollable, animated) AND a PDF version (print-ready handout) from a single set of input tokens. This is a sales-strategy artifact aimed at prospects, GSO leadership, or strategic partners. This is a dual-output template. The single config file produces two HTML files: one for web pitch, one for print PDF. Both must use the same brand voice and the same data. Source files to use as the reference: BioSummit/BioSummit Executive Summary/BioSummit Executive Summary Microsite.html (3,165 lines) for the microsite version. BioSummit/BioSummit Executive Summary/BioSummit_Executive_Summary_PDF.html (1,842 lines) for the print PDF version.","h":"What to build"},{"f":281,"x":"Both picked because BioSummit has the largest dual pair across all candidates, and the file naming pattern (-Executive-Summary-Microsite.html + -Executive-Summary-PDF.html) is also used by Trueline, Hargrove & Co, Parkline, and ClearForm ART, so it is the canonical naming. What to extract: From the microsite version: Section structure: hero, problem statement, solution overview, key metrics, value props, account team, next-steps CTA. Animation patterns (scroll reveals, key-metric counter animations if present). Mesh-gradient backgrounds (same brand-color palette as the partner microsite template). The same Montserrat + Lora typography as the partner microsite.","h":"What to build"},{"f":281,"x":"Print chassis (use Briefing 01 if built). Same section structure but flattened for paper: Hero with title + tagline. Problem statement (1 short paragraph). Solution overview (3-5 bullets). Key metrics block (4-6 stat tiles). Value props grid (3-4 cards). Account team (3-5 cards with headshots). Next-steps CTA. Inter font only (PDF rules). What to replace with placeholders: Placeholder | What it is Standard chassis identity tokens (used in PDF version) | {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} {{TARGET_NAME}} | The party being pitched to (often a GSO or enterprise name, e.g., \"BioSummit\", \"Fairline Care\") {{TARGET_LOGO_URL}} | Logo of the target party for co-branding","h":"From the PDF version"},{"f":281,"x":"{{PITCH_TITLE}} | Hero title (e.g., \"A Custom Manufacturing Partnership for BioSummit\") {{PITCH_SUBTITLE}} | Hero subtitle {{HERO_IMAGE_URL}} | Hero background image {{PROBLEM_STATEMENT}} | 1-2 sentence problem framing {{SOLUTION_OVERVIEW}} | Array of solution bullets. Each: {title, body} {{KEY_METRICS}} | Array of 4-6 stat tiles. Each: {value, label, supporting_text} {{VALUE_PROPS}} | Array of 3-4 value-prop cards. Each: {number, title, body, icon_svg_or_url} {{ACCOUNT_TEAM}} | Array of 3-5 account-team members. Each: {name, title, headshot_url, email, phone} {{NEXT_STEPS}} | Array of next-step actions. Each: {step, owner, timeline} {{CTA_TEXT}}, {{CTA_HREF}} | Closing CTA {{COMMERCIAL_TERMS_LINK}} | Optional link to commercial terms / pricing","h":"From the PDF version"},{"f":281,"x":"Inter font only. Page chassis from Briefing 01. Solid-color backgrounds (not mesh gradients, which print poorly). Key metrics use Apex Blue tile background with white text. Value props use Lab Gold for the numbered circles. Account team uses the same circular-headshot pattern but smaller (60px instead of 80px+). Both versions: \"APEXINST\" only in URLs / emails. Visible body text says \"Apex Instruments\". All 5 brand colors used appropriately. No off-palette accents. Validation checklist: For the microsite version: ☐ All standard placeholders present. ☐ No \"BioSummit\" anywhere in the file. ☐ Montserrat + Lora fonts loaded. ☐ Mesh-gradient backgrounds use brand palette only. ☐ Key-metric counter animations work. ☐ Saved at Template/Executive Summary/executive-summary-microsite-template.html.","h":"PDF version"},{"f":281,"x":"☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Cmd+P print preview is clean. ☐ Saved at Template/Executive Summary/executive-summary-pdf-template.html. Both: ☐ Same config drives both: changing a placeholder once updates both outputs. ☐ Single shared config example JSON saved alongside. ☐ Section structure is identical across both formats (same data, different presentation).","h":"For the PDF version"},{"f":282,"x":"A reusable Lab Slip / Docket template. This is the digital Docket form a doctor's office fills out when submitting a case. Today most partners use a PDF version; only BioSummit has an HTML source. Building the HTML template means future partners can have a fillable, branded lab slip with form-field tokenization. Note: a true fillable form (PDF AcroForm or interactive HTML) is out of scope for this template build. The deliverable is the visual template with field labels and structural blocks. Adding interactivity is a follow-up.","h":"What to build"},{"f":282,"x":"BioSummit/BioSummit Lab Slip/BioSummit-Lab-Slip-Docket.html (1,085 lines). This is the only HTML lab slip in the repo. What to extract: The print-PDF chassis (use Briefing 01 if built). Header section: Doctor name + practice name fields. Client name + chart number fields. Case date / due date fields. Case details section: Unit chart or unit-number selector. Refit type (Bench Unit, Rack Unit, Mount, Housing, etc.). Material selection. Finish selection. Special instructions section: Free-form text area. Common-instruction checkboxes. Submission method section: Digital scan (with file format options). Physical measurement (with shipping note). Inkstone / date block: Doctor signature line. Date. Optional: lab use only block (where the lab notes back to the office).","h":"Source file to use as the reference"},{"f":282,"x":"Placeholder | What it is Standard chassis identity tokens | {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} {{LAB_SLIP_TITLE}} | Title (e.g., \"BioSummit Lab Slip / Digital Docket\") {{REFIT_TYPES}} | Array of refit types this partner offers. Each: {label, code, sub_options} {{MATERIAL_OPTIONS}} | Array of material options. Each: {label, code, applies_to_refit_types} {{FINISH_GUIDE}} | Array of finish options (typically Verona Classical or 3D Range). Defaults can be hardcoded if every partner uses the same. {{SPECIAL_INSTRUCTION_PRESETS}} | Array of common instruction checkboxes. Each: {label, default_checked}","h":"What to replace with placeholders"},{"f":282,"x":"{{INCLUDE_UNIT_CHART}} | Boolean: render the visual unit chart or just a unit-number list {{SUBMISSION_METHODS}} | Array of submission methods. Each: {label, file_formats_accepted} {{LAB_USE_ONLY_BLOCK}} | Boolean: include the lab-use-only block or not {{TURNAROUND_NOTE}} | Standard turnaround note (e.g., \"Standard turnaround: 7-10 business days\") Where to save the output: Template/Lab Slip/lab-slip-template.html Also save: Template/Lab Slip/lab-slip-config-example.json. Brand rules to enforce: Inter font throughout. Form field labels: Harbor Blue (#052030). Form field underlines or borders: Apex Blue (#1882C7). Section headers: Apex Blue (#1882C7) bar, white text. Required-field markers: Lab Gold (#B3A369) asterisk or border accent. Page chassis from Briefing 01.","h":"What to replace with placeholders"},{"f":282,"x":"Single-page if possible. If multi-page (BioSummit is 1085 lines, which suggests 2 pages), use page-break-after: always between sections. Print-friendly. Form fields render as underlined blank lines for handwriting if printed. Validation checklist: ☐ Every placeholder in the table above appears in the template. ☐ No \"BioSummit\" specific text or product remains. ☐ No specific finish values, material codes, or refit types remain (all tokenized). ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Form field structure is consistent (all labels above their inputs). ☐ Required-field markers visible. ☐ Multi-page handling correct if needed. ☐ Cmd+P print preview shows fillable-by-pen layout. ☐ Saved at Template/Lab Slip/lab-slip-template.html. ☐ Config example JSON saved alongside.","h":"What to replace with placeholders"},{"f":283,"x":"A reusable Account Onboarding SOP (Standard Operating Procedure) template. This is the document that walks a new partner office through everything from initial outreach to first-case submission. It defines step-by-step responsibilities, owners, and timelines. This is the lowest-priority template because only one partner today has an SOP (UnionSix). Building it is somewhat speculative reuse, but the template is straightforward to extract and may save substantial time the next time a GSO or large partner needs structured onboarding.","h":"What to build"},{"f":283,"x":"UnionSix/Account Onboarding/UnionSix-SOP-Onboarding.html (1,258 lines). The only SOP HTML in the repo. What to extract: The print-PDF chassis (use Briefing 01 if built). Document title and subtitle (e.g., \"Account Onboarding SOP for UnionSix Devices\"). Phase blocks. Typical SOP phases: Phase 1: Initial Setup (account creation, contact assignment, intake form). Phase 2: Brand Customization (logos, microsite, welcome packet). Phase 3: Clinical Configuration (preferences, materials, finish conventions). Phase 4: First Case Submission (test case, feedback loop). Phase 5: Ongoing Operations (cadence, escalation paths, monthly review). For each phase: Numbered step list. Owner column (who is responsible: Apex Account Manager, Partner POC, External Vendor, Doctor). Timeline / target completion.","h":"Source file to use as the reference"},{"f":283,"x":"Deliverable / artifact produced. Owner color-coding legend (uses brand colors per the existing pattern): Partner: Apex Blue (#1882C7). External Vendor: Lab Gold (#B3A369). Apex Instruments: Harbor Blue (#052030). Doctor: Devices Blue (#4ABEEE). Escalation / contact block at the bottom. What to replace with placeholders: Placeholder | What it is Standard chassis identity tokens | {{PARTNER_NAME}}, {{PARTNER_SHORT_NAME}}, {{PARTNER_LOGO_COLOR_URL}}, {{PARTNER_LOGO_WHITE_URL}}, {{PARTNER_PHONE}}, {{PARTNER_WEBSITE}}, {{PARTNER_EMAIL}} {{SOP_TITLE}} | Document title (e.g., \"UnionSix Account Onboarding SOP\") {{SOP_SUBTITLE}} | Optional subtitle (e.g., \"Standard Operating Procedure for New Office Setup\") {{EFFECTIVE_DATE}} | \"Effective: 2026-04-01\"","h":"Source file to use as the reference"},{"f":283,"x":"{{PHASES}} | Array of phase objects. Each: {number, name, intro, steps} where steps is an array of {step_number, description, owner_code, timeline, deliverable} {{OWNER_LEGEND}} | Array of owner codes. Each: {code, label, color_token}. Default codes: PARTNER, EXTERNAL, Apex, DOCTOR. {{ESCALATION_CONTACTS}} | Array of escalation contacts. Each: {role, name, phone, email} {{REVIEW_CADENCE}} | Standard review cadence (e.g., \"Weekly check-ins for first 30 days, then monthly\") Where to save the output: Template/SOP/account-onboarding-sop-template.html Also save: Template/SOP/account-onboarding-sop-config-example.json.","h":"Source file to use as the reference"},{"f":283,"x":"Inter font throughout. Phase header bars: Apex Blue (#1882C7) background, white text, with the phase number in a circle. Step numbering: small Apex Blue circles with white text. Owner badges: small pill backgrounds in the owner color codes (Partner Apex Blue, External Lab Gold, Apex Harbor Blue, Doctor Devices Blue). White or contrast text. Timeline column: small Pewter / muted gray text. Page chassis from Briefing 01. Multi-page document (UnionSix is 1,258 lines suggesting 4-6 pages). Use page-break-after: always between phases.","h":"Brand rules to enforce"},{"f":283,"x":"☐ Every placeholder in the table above appears in the template. ☐ No \"UnionSix\" specific text, no specific contact names, no specific phase titles remain. ☐ Inter font only. ☐ Page chassis matches Briefing 01. ☐ Owner color-coding legend uses canonical brand colors. ☐ Phase headers render cleanly with numbered circles. ☐ Step list is readable, with owner badges aligned. ☐ Page breaks between phases work in Cmd+P print preview. ☐ Escalation contacts block is present at the end. ☐ Saved at Template/SOP/account-onboarding-sop-template.html. ☐ Config example JSON saved alongside.","h":"Validation checklist"},{"f":284,"x":"Date: 2026-05-01 Author: Claude Scope: Status of changes made to the Briefings folder during the \"Fix 3 Briefings + Build Card Catalog\" pass. Summary: Three briefings updated, one new artifact built (the Card Catalog). The other 7 briefings (01, 04, 05, 07, 08, 09, 10) were not touched per scope. Changes by file: NEW: Template/Microsite/Card_Catalog.json and Card_Catalog.md"},{"f":284,"x":"Built from scratch. Inventoried every unique resource card across the 5 partner microsites (BrightPath, Larchwood, UnionSix, BioSummit, Vista Specialty). Found 24 unique card types from 37 instances observed. Each card entry has: id (slug), title template, description template, description-varies flag, FA icon class + color, card image placeholder + default URL + directory tag, CTA label + icon type + href placeholder + directory tag, and the list of partners that use it. The catalog is the source of truth for the Microsite template's Resource Cards section. Per-partner microsite configs pick which card IDs to include."},{"f":284,"x":"Replaced entirely. The earlier draft had 5 problems: Said the microsite has 6 sections. Actual count is 8 (Sticky Header, Hero, 5-Step Onboarding Roadmap, Resource Cards, Welcome from AE, Support Team carousel, Manage Your Cases, FAQ). Plus footer. Missed the 5-Step Onboarding Roadmap entirely. Missed the Welcome Message from AE section entirely. Treated FAQs as pre-fillable. They are AI-generated AFTER the rest of the microsite is built. Didn't reference the Card Catalog (because it didn't exist yet). Tokenized things that should be hardcoded (hero subtitle \"For Artistry at Scale\", Manage Your Cases section, Closing Quote, sidebar nav items, portal URL, Digital Housings URL).","h":"REWRITTEN: Template/Briefings/02-Microsite-Briefing.md"},{"f":284,"x":"File renamed. Inside the briefing: every reference to \"Welcome Packet\" rewritten to \"Welcome Flyer\". Output path changed from Template/Welcome Packet/welcome-packet-template.html to Template/Welcome Flyer/welcome-flyer-template.html. Same for the config example file. Three \"Welcome Packet\" mentions remain in the file: (a) the title which calls out the rename, (b) the explicit naming-note callout box, (c) the literal source filename Larchwood Devices, Apex Instruments Welcome Packet.html which is the actual file in the repo and cannot be renamed without breaking the path. All other content of the briefing was left unchanged.","h":"RENAMED + UPDATED: Template/Briefings/03-Welcome-Flyer-Briefing.md (was 03-Welcome-Packet-Briefing.md)"},{"f":284,"x":"Replaced entirely. Removed the \"thin wrapper around Briefing 05\" framing. B&R is now its own standalone template, built directly on the Co-Branded PDF Chassis from Briefing 01. It does NOT reference Briefing 05's snippet library; it has its own component definitions (important bars, pro tip callouts, photo grids, finish tab block). The new briefing defines 9 B&R specific sections in clinical workflow order (Case Overview, Required Photography, Fit Registration, Margin Design, Opposing Rack, Finish Selection, Material Selection, Submission Checklist, Special Considerations). Source file unchanged (UnionSix/Bench and Rack Guide/UnionSix-Guide-Bench-and-Rack.html).","h":"REWRITTEN: Template/Briefings/06-Bench-and-Rack-Guide-Briefing.md"},{"f":284,"x":"01-Co-Branded-PDF-Chassis-Briefing.md 04-Price-List-Briefing.md 05-Whats-Needed-Guide-Briefing.md 07-Promo-Flyer-Briefing.md 08-Executive-Summary-Briefing.md 09-Lab-Slip-Briefing.md 10-Account-Onboarding-SOP-Briefing.md Cross-references between briefings (current state): Briefings 03 (Welcome Flyer), 04 (Price List), 05 (What's Needed Guide), 06 (Bench & Rack Guide), 07 (Promo Flyer), 08 (Executive Summary PDF version), 09 (Lab Slip), 10 (SOP) all import or reference the Co-Branded PDF Chassis from Briefing 01. Briefing 02 (Microsite) and Briefing 08 (Executive Summary microsite version) use the Montserrat + Lora typography stack and the mesh-gradient backgrounds; they do NOT use the print chassis.","h":"Files NOT touched (per scope)"},{"f":285,"x":"Version 1.0 | Copy-paste components for landing pages. Reference Color_Palette.md + Typography_System.md. Component 1 Navigation Bar: Component 2 Buttons: Component 3 Section Labels & Pill Badges: Component 4 Trust Chips / Feature Pills: Component 5 Callout Boxes (Alliance Blue & Lab Gold): Why It Matters • First key point about your product or service capability. • Second key point with bold emphasis on key terms. • Third key point reinforcing the value proposition. Premium Vantage • First premium feature or differentiator. • Second premium point with specific value. • Third premium point emphasizing partnership. Component 6","h":"Apex Instruments Component Library"},{"f":285,"x":"Mounts Digital Workflow Integration: Streamlined case submission with real-time tracking and dedicated lab support throughout the process. Resource Lab Submission Guide: Everything you need to submit your first case and get started with the Apex Instruments portal. Fast Turnaround: Industry-leading 5-day standard turnaround with rush options available for time-sensitive cases. Component 7 Dark Content Card (Premium Feature Highlight): Digital Portal Manage Your Cases with Precision: Our lab portal gives you real-time case tracking, direct communication with technicians, and digital record keeping, all in one streamlined platform. Component 8","h":"Content Cards"},{"f":285,"x":"Welcome to Apex Instruments Ready to Start Your First Case? Our onboarding team will guide you step by step. Get set up in under 24 hours. Component 9 Testimonial / Quote Block: The Apex Instruments team has completely transformed how I approach cosmetic cases. The quality is unmatched. Component 10 Contact / Team Card: Your Contact Adrienne* Ledoux: Director of Partner Relations Component 11 Footer: Reference Logo Assets (the CRM CDN): Wordmark Primary (light bg) Wordmark White (dark bg) Icon (light bg)","h":"Glass-Effect CTA Panel"},{"f":286,"x":"Type: email template File: APEX_Email_Request_Form_v2.html Used for: Internal intake form for requesting a single email send, captures recipient, subject, content brief, and send details. What's in it: DM Sans type stack Form fields for email type, audience, subject line brief, content notes, and send date Apex brand styling for internal use v2 of the standard email request form When to use: Use when requesting a one-off email from the marketing team. For multi-email series, use Email-Series-Campaign-Form instead."},{"f":287,"x":"Type: email template File: Email-Series-Campaign-Form.html Used for: Internal intake form for briefing and requesting a multi-email campaign series, captures campaign details, goals, audience, and scheduling information. What's in it: DM Sans type stack Form fields for campaign name, series structure, goals, target audience, and schedule Apex brand styling for internal use Structured to collect everything needed to brief a campaign When to use: Use when a team member needs to request or brief a new email series campaign. Fill out and submit to initiate the campaign workflow."},{"f":288,"x":"Master PVS Measurement Opposing Rack Measurement Fit Registration (Mounted on Test Fixture) All materials cleaned and disinfected Ensure no pulls or tears in margin area Preparation Scan Opposing Rack Scan Fit Scan Margins, undercuts, & clearances clearly visible Verify fit alignment onscreen Use high-quality photography to communicate finish and aesthetics. Full-face lantern Close up photo of finish tab with adjacent units Technician's Name, Office Info, Due Date Client's Full Name Unit Number(s) Refit Type (Bench Unit, Rack Unit, Face Panel, Inlay) Material: Stone, Lucent, PFM, PFZ, Full Metal Finish: Finish Selected & Guide (Verona/Chromaset) Stub Finish (Required for translucent ceramics)"},{"f":289,"x":"Type: snippet File: critical-bar.html Used for: Highest-severity callout bar, flags steps whose absence would cause case failure (e.g., datum pin must be properly seated). What's in it: Canonical Apex gradient background + Lab Gold icon \"Critical\" severity styling (most visually urgent callout in the system) Paste-in snippet for use inside guide section bodies Brand-compliant, does not use older amber/brown palette When to use: Insert when a clinical instruction carries the highest risk of case failure if missed. Use sparingly, reserve for truly critical steps only. Less severe alerts should use important-bar or info-note instead."},{"f":290,"x":"Type: snippet File: info-note.html Used for: Soft supplementary callout for \"good-to-know\" details, submission tips, optional steps, or non-critical reminders. What's in it: Light gray (#f0f4f8) background, lowest visual urgency \"Info\" severity styling Paste-in snippet for use inside guide section bodies Clearly distinct from critical-bar and important-bar When to use: Insert for helpful but non-mandatory context, tips, optional recommendations, \"pro tips,\" or submission best practices. Not for steps that affect case outcomes."},{"f":291,"x":"Type: snippet File: photo-grid-3x2.html Used for: A 3-column × 2-row clinical photography grid (6 cells) for embedding 6 reference photos with labels inside a guide section body. What's in it: Six .photo-item cells in a 3×2 grid Label text below each photo Designed for sections requiring more reference photos (e.g., Axis 6-angle scan requirement) Paste-in snippet for use inside .section-body elements When to use: Use when a guide section needs 5 to 6 reference photos. For 4 or fewer, use photo-grid-2x2 to preserve whitespace and readability."},{"f":292,"x":"Type: snippet File: section-card-text-only.html Used for: A two-column section card containing two .card sub-blocks (e.g., \"Analog Requirements\" and \"Digital Requirements\"), no image, text only. What's in it: Two-column layout with paired .card sub-blocks Card header (icon + label) and body text per column No image slot Paste-in snippet for use in guide section bodies When to use: Use for sections that contrast two requirement sets side-by-side (analog vs digital, standard vs optional). Matches the layout used in Sections 1 and 3 of the Caravelle Mount guide."},{"f":293,"x":"Type: snippet File: section-card-with-image.html Used for: A single-column section card with banner + body, card header (icon + label) plus clinical instructions with an optional inline image. What's in it: Single-column layout with card-header (icon + label) and body text Optional inline image slot within the body Paste-in snippet for use in guide section bodies Tokens: {{SECTION_ICON}}, {{SECTION_LABEL}}, {{BODY_CONTENT}}, optional {{IMAGE_URL}} When to use: Use for guide sections that are a single block of clinical instructions, especially when a reference image (scan, prep photo) helps illustrate the step."},{"f":294,"x":"Source: Extracted from 5 partner microsites (BrightPath, Larchwood, UnionSix, BioSummit, Vista Specialty). Generated: 2026-05-01. Total unique card types: 24. Card instances observed: 37 (5-10 per partner). How to use this catalog: When building a new partner microsite, pick which card IDs to include based on the partner's scope. The microsite template iterates over the chosen cards, substituting placeholders with actual values per partner."},{"f":294,"x":"Image and PDF URLs are tokenized. The Microsite template (or the Generate-New-Partner playbook) resolves them by looking them up in _WordPress_Asset_Directory.json by tag. For example, {{CARD_IMAGE_LAB_SLIP_URL}} resolves to the asset whose tags include [apex, docket, card]. Partner-specific PDFs (Welcome Packet, Lab Slip, Price Sheet, etc.) resolve by tags like [partner-slug, welcome-packet, pdf]. Some CTA URLs do not live in WordPress. the CRM form URLs (Technical Preferences Form, New Clinic Form) and the CRM video URLs (MXR Onboarding Video) come from the Partner Brief input, not the WordPress directory. The catalog notes this on a per-card basis."},{"f":294,"x":"Title (template): Formline Protector Identification Guide Description: Quickly identify Formline Protector platforms and connection types using this visual reference guide. Learn to interpret each protector at a glance. Icon (FA class): fas fa-id-card color #4abeee Card image placeholder: {{CARD_IMAGE_FORMLINE_URL}} Card image default URL: https://apexinstruments.example/wp-content/uploads/2026/02/Formline-Protectors-scaled.png Card image directory tag (resolve via _WordPress_Asset_Directory.json): [formline, protectors, card] CTA href placeholder: {{FORMLINE_GUIDE_PDF_URL}} CTA href directory tag (or source): [formline, biosummit, pdf]","h":"card-formline-protector-guide"},{"f":294,"x":"Title (template): Step-by-Step Refit Scanning Guide Cascade 3D Description: A visual, step-by-step blueprint for the Cascade 3D scanner, designed to optimize scan accuracy and streamline your refit workflow. Icon (FA class): fas fa-route color #4abeee Card image placeholder: {{CARD_IMAGE_CASCADE3D_SCANNING_URL}} Card image default URL: https://apexinstruments.example/wp-content/uploads/2026/02/Apex-Scanning-guide-steps-Card-scaled.png Card image directory tag (resolve via _WordPress_Asset_Directory.json): [cascade-3d, scanning, card] CTA href placeholder: {{CASCADE3D_SCANNING_PDF_URL}} CTA href directory tag (or source): [cascade-3d, scanning-guide, pdf] Used by partners: Vista Specialty","h":"card-cascade3d-refit-scanning-guide"},{"f":294,"x":"Title (template): Cascade 3D Quick Guide Description: A high-impact benchside cheat sheet condensing the scan-to-send workflow into 10 actionable steps for instant team reference. Icon (FA class): fas fa-bolt color #4abeee Card image placeholder: {{CARD_IMAGE_CASCADE3D_QUICK_URL}} Card image default URL: https://apexinstruments.example/wp-content/uploads/2026/02/Apex-Cascade-3d-Card-scaled.png Card image directory tag (resolve via _WordPress_Asset_Directory.json): [cascade-3d, quick-guide, card] CTA label: View Guide CTA href placeholder: {{CASCADE3D_QUICK_GUIDE_URL}} CTA href directory tag (or source): [cascade-3d, sales-guide, pdf]","h":"card-cascade3d-quick-guide"},{"f":294,"x":"Title (template): Why We Don't Use Metal Reinforcement in Duratone Digital Print Housings Description: Learn why Apex Instruments's Duratone Digital Print Housings deliver clinically validated strength, durability, and comfort without metal reinforcement. Icon (FA class): fas fa-shield-alt color #4abeee Card image placeholder: {{CARD_IMAGE_DURATONE_URL}} Card image default URL: https://apexinstruments.example/wp-content/uploads/2026/02/Apex-Why-We-Dont-Use-Metal-Reinforcement-in-Duratone-Digital-Print-Housings-Card-scaled.png Card image directory tag (resolve via _WordPress_Asset_Directory.json): [duratone, housings, card] CTA href placeholder: {{DURATONE_PDF_URL}} CTA href directory tag (or source): [duratone, housings, pdf]","h":"card-duratone-metal-reinforcement"},{"f":295,"x":"Type: microsite File: microsite-template.html Used for: Reusable, partner-agnostic microsite template, copy and substitute {{PLACEHOLDER}} values to produce a partner-specific landing microsite. What's in it: Full Apex brand microsite layout (hero, program cards, contact section) {{PLACEHOLDER}} token system for all partner-specific content Card catalog integration (Card_Catalog.json) for modular content sections Companion briefing doc reference (02-Microsite-Briefing.md) Responsive, browser-based, not a print-to-PDF document"},{"f":295,"x":"Use when a new partner needs a dedicated microsite or landing page. Follow the 02-Microsite-Briefing.md for the full placeholder list and Card_Catalog.json for available card modules.","h":"When to use"},{"f":296,"x":"Type: web landing page template File: openform-product-page-template.html Used for: Generating one product-detail page per OpenForm SKU. There are 63 near-identical pages; this template provides the constant shell (CSS, nav, compliance bar, footer) and 16 «SWAP» placeholders covering all variable content. Fill one JSON config row per SKU and render. What's in it: Constant shell (lifted verbatim from source pages, do not modify): Full 297-line CSS block: :root tokens, nav, hero, features, compliance-bar, related, footer, responsive breakpoints Google Fonts import: Barlow, Barlow Semi Condensed, Barlow Condensed (OpenForm brand, NOT Apex brand fonts) Favicon: OI-Icon-Logo.png.png (OpenForm icon)"},{"f":296,"x":"Sticky nav: OI white wordmark + Home + All Products links (both constant) + Buy Now CTA (uses «SHOP_URL») Compliance bar: 5 locked regulatory items (FDA 510(k) Cleared · Zero Deficiencies · Zero Recalls · Made in USA · 7 Mount Systems) Footer: OI white wordmark + \"SHERLOCK, Devices Mount Components & Milling Center\" + openform.example links + 4 footer badges + copyright line Variable slots (16 total, 12 scalar + 4 related-card objects × 4 fields each): 12 scalar swap fields in <head> and hero/features sections 4 related-card slots, each with 4 sub-fields (href, img slug, alt text, display name)"},{"f":296,"x":"Field | What it is | Example value | Source / Notes «PAGE_TITLE» | Browser tab title | `Norwell Active Ti-Base Set \\ | OpenForm, Sherlock Devices Components` | Pattern: `{Product Name} \\ | OpenForm, Sherlock Devices Components` «META_DESC» | meta description (~155 chars) | Engaging titanium base adapter set compatible with Norwell Precision (Active) mount systems... | From product copy «META_KEYWORDS_SYSTEM» | meta keywords string | devices mount, titanium base, Norwell Precision (Active), mount components, FDA cleared, OpenForm, Sherlock | Adapt system name per SKU","h":"Swap-point manifest"},{"f":296,"x":"«SHOP_URL» | Full WooCommerce product URL | https://shop.openform.example/norwell-active-titanium-base-set/ | Must be verified explicitly, NOT derivable from filename (e.g. mua-3mm-norwell-cc-rp.html → slug is mua-3mm-norwell-rp, \"cc\" dropped). Used in both nav CTA and hero CTA. «PRODUCT_IMG_SLUG» | Filename slug for product image (no extension) | norwell-active-ti-base-set | Image URL pattern: https://apexinstruments.example/wp-content/uploads/2026/03/{slug}.png «PRODUCT_IMG_ALT» | Alt text for hero product image | Norwell Active Ti-Base Set | Usually matches product name «CAT_LABEL» | Category label above h1 (displayed uppercase via CSS) | Titanium Base Sets (Engaging) | From product category","h":"Swap-point manifest"},{"f":296,"x":"Full :root palette (identical on all 63 pages): Token | Value | Usage --oi-blue | #0366CB | Primary brand blue, buttons, badges, bullet dots, section underlines --oi-blue-hover | #0255a8 | Button hover state --pewter | #818180 | Available for custom use --dark-navy | #232e57 | Nav background, footer background, headings --dark-slate | #3f405c | Compliance item text, gray badge text --white | #ffffff | Page background, card backgrounds --light-bg | #f4f6f9 | Hero image tile, compliance bar background, related card image areas --border | #e2e5ea | Card borders, compliance bar borders --text | #1a1a2e | Body text --text-light | #555 | Descriptive copy, feature bullets","h":"Tokens"},{"f":296,"x":"Fill one row of openform-config-example.json per SKU (expanding it to a JSON array for bulk runs) and use a simple find-replace or template script to swap all «FIELD» tokens. For a single page, do a manual find-and-replace in any editor. For all 63 pages, a loop over the config array renders the full catalog in seconds, the constant shell never changes, only the 16 swap fields. See openform-config-example.json for a fully worked example using norwell-active-ti-base-set.","h":"When to use"},{"f":297,"x":"Build date: 2026-05-01 Source: BrightPath/Marketing Templates/BrightPath-Co-Branded-PDF-Template.html (263 lines) Output: Template/print-pdf-shell.html (264 lines) Companion partials: Template/_partials/header-pill.html, Template/_partials/footer-pill.html Summary: Extracted the BrightPath chassis verbatim, tokenized the partner-specific identity values, and added a documentation header explaining how to consume the template. Two copy-paste partials extracted for the future \"compose a new template\" workflow per the briefing's optional ask."},{"f":297,"x":"Token | Where it appears {{DOCUMENT_TITLE}} | <title> {{PARTNER_NAME}} | alt text on header partner logo and footer partner logo {{PARTNER_LOGO_COLOR_URL}} | src of header partner logo {{PARTNER_LOGO_WHITE_URL}} | src of footer partner logo {{PARTNER_PHONE}} | Footer phone .fc-value {{PARTNER_WEBSITE}} | Footer website .fc-value {{PARTNER_EMAIL}} | Footer email .fc-value {{CONTENT_SLOT}} | Comment marker inside .white-area for derived templates {{PARTNER_SHORT_NAME}} is not used inside the chassis itself; it is reserved for derived templates (filenames, tight-space labels). The token is documented in the chassis header comment so future template authors know it exists.","h":"Placeholder tokens"},{"f":297,"x":"Apex Wordmark Primary (header pill): https://apexinstruments.example/wp-content/uploads/2026/01/Apex-Wordmark-Logo-Primary-scaled.png Apex Wordmark White (footer pill): https://apexinstruments.example/wp-content/uploads/2026/01/Apex-Wordmark-Logo-Single-Color-All-White-scaled.png Inter Google Fonts @import URL All print rules including the @media print footer-pill !important overrides All structural CSS (.page, .white-area, .header-pill, .footer-pill, etc.) Validation checklist: Check | Result All identity placeholders present (PARTNER_NAME, PARTNER_LOGO_COLOR_URL, PARTNER_LOGO_WHITE_URL, PARTNER_PHONE, PARTNER_WEBSITE, PARTNER_EMAIL, DOCUMENT_TITLE) | PASS {{PARTNER_SHORT_NAME}} documented (reserved for derived templates) | PASS, documented in header comment","h":"Hardcoded constants (NOT tokenized)"},{"f":297,"x":"{{CONTENT_SLOT}} marker inside .white-area | PASS No \"BrightPath\" string anywhere | PASS, grep -ic \"brightpath\" returns 0 No \"(949) 409-3299\" anywhere | PASS, grep \"409-3299\" returns 0 No \"brightpath@apexinstruments.example\" anywhere | PASS Apex Wordmark URLs hardcoded, not tokenized | PASS Brand color hex values | PASS, chassis uses #4abeee (Devices Blue, lowercase variant of canonical #4ABEEE), #B3A369 (Lab Gold), #052030 (Harbor Blue). Print fallback #082638 only inside @media print. No stray off-palette navys. @page { size: 8.5in 11in; margin: 0; } present | PASS @media print block present with footer-pill !important overrides | PASS Inter is the only font loaded | PASS File renders in a browser without console errors | PASS, pure HTML/CSS, no scripts","h":"Hardcoded constants (NOT tokenized)"},{"f":297,"x":"Saved at Template/print-pdf-shell.html | PASS Deviations from the briefing: None. The chassis matches the source 1:1 modulo the identity tokenization the briefing requires. One stylistic addition: a documentation header comment at the top of the file explaining how to consume the template, which tokens to substitute, and how URLs resolve from the WordPress Asset Directory. This was not required by the briefing but makes the template self-documenting for future template authors. Notes for downstream builds: The chassis is consumed by Build 2 (Welcome Flyer), Build 3 (B&R Guide), and Build 4 (What's Needed Guide). Each derived template should copy the chassis and inject its body content where {{CONTENT_SLOT}} is. Derived templates should add their own typography stack on top of Inter","h":"Hardcoded constants (NOT tokenized)"},{"f":297,"x":"(e.g., DM Sans for guide headings) without removing the chassis Inter @import. Multi-page derived templates (Welcome Flyer is 2 pages, guides are 3-5 pages) should duplicate the .page block per page; the chassis CSS already includes page-break-after: always. .white-area has overflow: hidden. Multi-page guides that overflow the bottom of a page lose the overflow content silently. Tighten margins or split sections rather than letting content clip.","h":"Hardcoded constants (NOT tokenized)"},{"f":298,"x":"Type: print template File: print-pdf-shell.html Used for: The structural foundation that every print-ready PDF in the Apex system builds on, provides the page sizing, margin, and print CSS chassis. What's in it: Base print CSS (page size, margins, background-color print flags) .page container with standard letter-size dimensions Header pill and footer pill integration points Shared by guides, one-pagers, two-pagers, and welcome flyers Not a standalone deliverable, other templates extend this chassis"},{"f":298,"x":"Reference or extend when building a new print template from scratch. Do not use this file directly for deliverables, use a derived template (e.g., bench-and-rack-guide-template, welcome-flyer-template) instead.","h":"When to use"},{"f":299,"x":"[Subtitle or introductory paragraph. One to two sentences that set context for the document.] [Body paragraph for the left column. Keep concise -- 3-4 sentences for optimal fit.] [Key point 1] [Key point 2] [Key point 3] [Body paragraph for the right column. Match density to left column.] [Feature / benefit 1] [Feature / benefit 2] [Feature / benefit 3] [CTA body text. One sentence with a clear call to action.]"},{"f":300,"x":"Type: print template File: REFERENCE-trifold-brochure-template.html Used for: Reference copy of the tri-fold brochure template, locked, named REFERENCE to signal it should not be edited directly; copy before using. What's in it: Six-panel trifold layout (front cover, inside panels, back panel) Lora serif + Montserrat heading type stack Apex brand color system Placeholder zones for headlines, body copy, and images per panel Identical structure to the design-system version in skills/generation When to use: Consult as a stable reference when the design-system copy needs to be rebuilt or verified. To produce a deliverable, copy this file, never edit the REFERENCE copy directly."},{"f":301,"x":"Type: print template File: REFERENCE-two-pager-template.html Used for: Reference copy of the PDF two-pager template, locked, named REFERENCE to signal it should not be edited directly; copy before using. What's in it: Two letter-size page layout Lora serif + Montserrat heading type stack Apex brand color system Header, content zones across both pages, and footer Identical structure to the design-system version in skills/generation When to use: Consult as a stable reference when the design-system copy needs to be rebuilt or verified. To produce a deliverable, copy this file, never edit the REFERENCE copy directly."},{"f":302,"x":"[One line of supporting text, keep short for this format.]"},{"f":303,"x":"Type: social template File: social-instagram-post.html Used for: Instagram portrait post graphic at native 1080×1350 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1350 px (4:5 portrait ratio) Lora serif + Montserrat type stack Apex brand color system Headline, body, and CTA zones Background image/color area with overlay When to use: Use when producing an Instagram portrait-format feed post. This copy lives in /templates/social, use the design-system version for agent-generated output."},{"f":304,"x":"Type: social template File: social-instagram-square.html Used for: Instagram square post graphic at native 1080×1080 px, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1080 px (1:1 square ratio) Lora serif + Montserrat type stack Apex brand color system Headline, body, and CTA zones Background image/color area with overlay When to use: Use when producing an Instagram square-format post. This copy lives in /templates/social, use the design-system version for agent-generated output."},{"f":305,"x":"[Supporting text, 1-2 sentences. Stories are scannable, keep it brief.]"},{"f":306,"x":"[Concise supporting text, professional tone, 1-2 lines.]"},{"f":307,"x":"[Key insight or announcement, 2-3 sentences. LinkedIn audiences expect substance.] [Key takeaway 1] [Key takeaway 2] [Key takeaway 3]"},{"f":308,"x":"Type: social template File: social-universal-story.html Used for: Platform-agnostic Story graphic at 1080×1920 px for multi-platform publishing, the stable /templates/social copy for direct use or reference. What's in it: Canvas fixed at 1080×1920 px (9:16 vertical ratio) Lora serif + Montserrat type stack Apex brand color system Generic layout not tied to any single platform's chrome Background image/color area with overlay When to use: Use when the same Story asset needs to publish across multiple platforms, or when the platform isn't specified. This copy lives in /templates/social, use the design-system version for agent-generated output."},{"f":309,"x":"Date: 2026-05-01 Author: Claude Audience: Jordan*, plus Claude Code (which will execute the briefings). Scope: 10 collateral types. For each: the strongest existing example, why it wins, and a paste-ready briefing for Claude Code at Template/Briefings/[CollateralType]-Briefing.md. Source picks (one line per collateral type): # | Collateral type | Source partner | Source file | One-liner rationale 1 | Co-Branded PDF chassis (the print shell) | BrightPath | BrightPath/Marketing Templates/BrightPath-Co-Branded-PDF-Template.html (263 lines) | Empty content area, all chassis pieces present (page, white-area, cyan border, header-pill, footer-pill, print rules). Every print PDF in the repo uses this skeleton."},{"f":309,"x":"You suggested microsite probably comes first. I am pushing back. Here is the order I recommend. Priority 1: Co-Branded PDF chassis: Why first. This is structural, not a deliverable. It looks like the smallest payoff but it unlocks the most downstream work. Five other templates (Welcome Packet, What's Needed Guide, Bench & Rack, Promo Flyer, Lab Slip) all sit on top of this exact print chassis (page + white-area + header-pill + footer-pill + print-color-adjust rules + footer-pill print overrides). Today every PDF re-implements this chassis inline. Once it lives in Template/print-pdf-shell.html, every later template imports it via include or copy-paste with confidence. Build this first and the other 5 print-PDF templates each take half the time.","h":"Priority order (with rationale)"},{"f":309,"x":"Why second, not first. The microsite is the most complex single deliverable and the linchpin that every partner page links to. Templating it captures the largest single chunk of repeated work (3,357 lines per partner copy today). Doing this second instead of first costs you nothing because the microsite does not depend on the print chassis. Priority 3: Welcome Packet: Why third. Highest-volume partner deliverable after the microsite itself. Every new partner gets one. Edit frequency is high (team changes, copy updates). Built on the print chassis, so doing chassis first cuts this work substantially.","h":"Priority 2: Microsite"},{"f":309,"x":"Why fourth. Highest update frequency in the system (pricing changes per quarter, per partner, per program). Templating this saves the most time on a recurring basis. Simpler structure than the microsite, so faster to build, and it is the highest-leverage maintenance template. Priority 5: What's Needed Guide (with section snippet library): Why fifth. Multiple guides per partner (FRX, Axis, Exact, Aperture, Bench & Rack, Mounts). The unlock is not the shell, it is the snippet library: section-card, important-bar, critical-bar, info-note, photo-grid, QR-block. Once these are extracted from BrightPath Aperture (the richest example), composing a new guide from sections becomes copy-and-arrange instead of write-from-scratch.","h":"Priority 4: Price List"},{"f":309,"x":"Why sixth. A specialization of the What's Needed Guide. Build it as a thin wrapper that pulls the same section snippets, with a Bench & Rack specific content profile (clinical photography requirements, fit registration, margin design notes). Should take a fraction of the time after #5 is in place. Priority 7: Promo Flyer: Why seventh. Lower volume, more partner-specific designs (each promo has its own visual concept). Templating saves time but unlocks less velocity than the items above. Built on the print chassis.","h":"Priority 6: Bench & Rack Guide"},{"f":309,"x":"Why eighth. Sales-strategy artifact, lower volume than ops collateral. The dual pair structure (microsite version plus PDF version) makes this slightly more complex to template than other types because it is two outputs from one input. Worth doing, but later. Priority 9: Lab Slip / Docket: Why ninth. Most lab slips today are PDFs. Only BioSummit has an HTML version. Low template-payoff per partner because most partners are happy with their existing PDF. Priority 10: Account Onboarding SOP: Why last. Only UnionSix has one. Until a second partner needs an SOP, building the template is speculative. Reuse signal is too low to prioritize.","h":"Priority 8: Executive Summary (dual pair)"},{"f":310,"x":"Type: print template File: welcome-flyer-template.html Used for: Reusable, partner-agnostic 2-page print-ready Welcome Flyer for onboarding new devices lab partners or accounts. What's in it: Two-page print layout (front welcome page + back detail/contact page) Full Apex brand color and type system Partner-agnostic placeholder zones for co-branding Header pill and footer pill integration points Chrome → Print → Save as PDF workflow When to use: Use when onboarding a new partner or account and a printed welcome flyer is needed. Copy the file, substitute partner tokens, add header/footer pills, and print to PDF."},{"f":311,"x":"What this is: quality assurance is built into the brain itself, every piece of data going in and every output coming out gets fact-checked before a human ever reviews it. Nothing reaches the approval chain on vibes. The three checks every output passes: The scanner (deterministic). Banned terms, policy tripwires, unresolved slots, raw hex, a script with an exit code, not an opinion. It runs on every handover, automatically. The verifier fleet (independent). Fresh-context agents attack each draft across three lenses, rules, facts, voice, without ever seeing the writer's reasoning, so they can't inherit its assumptions. Every claimed number gets traced to its authority file; no source, no number.","h":"The QA Layer"},{"f":311,"x":"The human gate. Verdicts inform the owner→approver chain; they never replace it. Only a person promotes work to Approved. An example run: six drafts, eighteen verdicts: Metric | Value Drafts swept | 6 Verdicts requested / returned | 18 / 18, counted, so a silent failure can't hide High-severity catches | 6 Draft | Verdict | Headline finding Contact page | FAIL | An invented \"48-hour executive response\" commitment, exists in no approved source Company info page | FAIL | An unresolved template slot rendering in public copy Leadership page | FAIL | The same 48-hour claim inherited, one edit clears both Fact sheet | FAIL | An internal-only figure phrased as public fact Welcome letter | FLAG | An unapproved superlative with no substantiation on file","h":"The QA Layer"},{"f":311,"x":"FAQ | FLAG | A production note rendering in body copy Three humans had read these drafts in sequence and missed the invented commitment every time. Eighteen independent verifiers found it in one pass, with line numbers. Why it works: Fresh eyes: a checker never shares the maker's context. Counted returns: the run isn't done until every verdict is back. Unarguable anchors: the scanner's exit code and the authority files settle disputes. The loop closes: fixes go back through the same gates until they pass, then, and only then, to a person.","h":"The QA Layer"},{"f":312,"x":"*For media reference. Effective September 1, 2026.* What is happening: On September 1, 2026, Apex Instruments and the field network join to form one company. Day one operating names: \"Apex Instruments, {{endorser_line}}\" and \"National Vantex, {{endorser_line}}.\" Who we are: \"Apex Instruments is a devices contract manufacturer delivering artistry at scale. Together with the field network, we combine a national footprint, a mature commercial engine, and a deep investment in practice education with the most advanced manufacturing model in the industry, so every case is consistent, backed by redundancy, on time, and supported by a person who knows your practice.\""},{"f":312,"x":"In one line: \"We are the national devices lab network that runs like a manufacturer: one engineered, quality-controlled process, delivered through a coast-to-coast footprint, with a real team on every account.\" The combination at a glance: A national footprint combining the field network's coast-to-coast laboratory network with Apex Instruments's Centers of Excellence the field network: one of the largest and most recognized devices laboratory networks in the United States Apex Instruments: an engineered, SOP-driven manufacturing model where every Bench & Rack and Full Rack case is QC'd under a microscope by a master team Built-in redundancy across Centers of Excellence, so an equipment or supply failure never costs a case"},{"f":312,"x":"Real-time case tracking from day one; every account has a dedicated Account Manager as a single point of contact For GSOs: enterprise dashboards with multi-location case tracking, real-time shipping logistics, and standardized remake-rate metrics What this means for devices practices: Best of both worlds: national scale, redundancy, and commercial reach, paired with local, high-touch accountability. Quality lives in the process: engineered and repeatable, with senior-technician quality on every case. A partner, not a vendor: dedicated account management, practice education, and for GSOs, multi-location tracking and standardized metrics."},{"f":312,"x":"Pricing for existing accounts is locked for six months The 6-Month Continuity Guarantee: if a case is late because of us, we make it right A $500 digital-integration credit for connecting a scanner to the digital pipeline 12 months of complimentary high-end continuing education Standardized FedEx 2nd Day shipping, free to the practice Leadership: Roman Elias Mercado*, Chief Executive Officer {{headshot_mercado}} Emmett* Kovach, President {{headshot_kovach}} Dana* Whitfield, Chief Growth Officer {{headshot_whitfield}} Emory Ridgway, Chief Executive Officer, the field network {{headshot_ridgway}} Arturo Bellamy, Transition Leader {{headshot_bellamy}} *Bios: {{leadership_bios}}*","h":"Commitments to customers (effective day one)"},{"f":312,"x":"{{pr_contact_name}} · {{pr_contact_email}} · {{pr_contact_phone}} *Boilerplate: {{approved_boilerplate}} (pending counsel-approved press release)*","h":"Media contact"},{"f":313,"x":"On September 1, Apex Instruments and the field network become one company. This is a one-story rebrand: each organization brings what the other needs. the field network brings a national footprint, a recognized name, an experienced sales force, and the industry's deepest investment in practice education. Apex Instruments brings an engineered manufacturing model, microscope-level quality control, and Centers of Excellence built for scale. Together, one plus one equals more than two. What it means for you","h":"The news"},{"f":313,"x":"Help is here. For everyone carrying a heavy load, this combination brings backup: more capacity, more redundancy, more support behind every case and every account. Most day-to-day work does not change on September 1. Where a site or team is directly affected, you will hear it live and in person from leadership, never by email and never from the press. How the day runs: 7:00 AM: leadership alignment huddle 7:30 AM: all-staff emails and videos from both CEOs, then manager huddles 8:00 AM: affected sites are briefed live by Emmett* Kovach and Arturo Bellamy 8:00 AM: the public press release goes out; the website goes live at 8:30 9:00 AM onward: customer outreach begins, led by Account Managers","h":"The news"},{"f":313,"x":"Employees hear news from leaders before customers, and customers before the public. Until the public announcement, nothing about this is shared outside the company, in any channel, for any reason. After the announcement, no employee responds publicly (press, social, forums) without approval; route every inquiry to the Chief Growth Officer's office. For managers: Run your Day-1 huddle from the approved FAQ packet. The golden rule: \"I will find out\" is always okay; speculation never is. If a question is not in the FAQ, log it and escalate; an answer comes back to you fast.","h":"The one rule that protects everyone"},{"f":313,"x":"Listen fully, isolate the real concern, flag Priority Care in the CRM, log the specifics, and escalate within 2 hours by tier: independent practice to the CGO, high-volume accounts to the President, GSO corporate to the CEO. Nobody handles an angry account alone. The story we tell outside: Externally this is one story only: a one-story rebrand that gives doctors more resources with the same people and the same service. Internal framing (including this brief and the phrase \"help is here\") stays internal. When in doubt, use the approved talking points or ask. *Questions? Bring them to your manager's huddle, or log them through {{internal_questions_channel}}.*","h":"If a customer is upset"},{"f":314,"x":"Will my pricing change? No. Pricing for existing accounts is locked for six months. If anything ever changes after that, you will hear it from your Account Manager directly, never by surprise. Do I keep my rep? Yes. The relationships are the reason this works, and they are protected. You have a dedicated Account Manager as your single point of contact: a named person who knows your practice, not a call center. {{am_name}} will reach out personally this week. Will my cases be late during the transition? Protecting your turnaround is the first job. We back that with the 6-Month Continuity Guarantee: if a case is late because of us, we make it right. Behind it sits built-in redundancy across our Centers of Excellence, so an equipment or supply issue never costs you a case."},{"f":314,"x":"Will the quality change? The process that protects your quality does not change. Every Bench & Rack and Full Rack case is QC'd under a microscope by a master team, every case, unchanged. Do I need to change my scanner or my routine? No. Your scanner connections and shipping are already mapped, so your routine stays the same. If you are ready to connect a scanner to the digital pipeline, there is a $500 digital-integration credit waiting for you. What about shipping? Standardized FedEx 2nd Day shipping, free to your practice. Is there anything new for my team? Yes: 12 months of complimentary high-end continuing education through the combined practice-education program, and real-time case tracking from day one, so your staff always knows exactly where a refit is. Why did this happen?"},{"f":314,"x":"Two organizations with complementary strengths came together. You keep the people and service you chose, now with more resources, more redundancy, and more support behind them than ever. Who do I call if something goes wrong? Your Account Manager, {{am_name}}, at {{am_phone}}. One call, one person, and it gets handled. *Questions we have not answered here? Call your Account Manager. If we do not know something yet, we will say so and find out.*"},{"f":315,"x":"Dear Dr. {{last_name}}, For years, you have trusted the field network with your clients' instruments. Today I am writing with news that makes that trust an even better bet: the field network and Apex Instruments have joined to form one company, and your lab just gained one of the most advanced manufacturing networks in the country. You chose the field network for the people and the service. None of that goes away. Your team, your case routing, your communication, and your pricing all continue uninterrupted. What is new is what stands behind them: an engineered, quality-controlled production model, built-in redundancy so an equipment or supply issue never costs you a case, and the capacity to keep your cases moving and on time."},{"f":315,"x":"We know a change like this can raise questions, so here is our promise for the next six months and beyond. Your pricing is locked. Your scanner connections and shipping are already mapped, so your routine does not change. You have a dedicated Account Manager as your single point of contact. And you can see exactly where every case is, in real time, from day one. Your Account Manager, {{am_name}}, will reach out personally this week. In the meantime, you can reach us anytime at (800) 555-0100 or sales@apexinstruments.example. Welcome to what comes next. We intend to earn your confidence one case at a time. Warm regards, Roman Elias Mercado*, Chief Executive Officer {{endorser_line}}"},{"f":315,"x":"*Production note (not part of the letter): the GTM draft signs \"the field network, an Apex Instruments company\"; the integration alignment is \"the field network (National Vantex), a Custom LLM company.\" The slot ships whichever Q-20 confirms. Contact line (800) 555-0100 / sales@apexinstruments.example is the GTM's; confirm it is the right routing for the field network accounts before print.*"},{"f":316,"x":"A person, not a queue. Every account has a named Account Manager. Start there, and it gets handled. Existing accounts: Your Account Manager is your single point of contact. {{am_lookup_or_line}} General line: {{main_phone}} · {{main_email}} *(GTM letters use (800) 555-0100 and sales@apexinstruments.example. Confirm the right numbers for legacy Apex vs incoming the field network routing before publish.)* New practices: Tell us about your practice and we will match you with the right team. {{new_business_form_or_email}} [CTA: Request a call]","h":"Hero"},{"f":316,"x":"Multi-location groups reach a named executive within 48 hours. {{gso_contact_block}} Locations: {{locations_block}} *(Facts/locations is not populated; never improvise addresses.)* Media: {{pr_contact_block}}","h":"GSO and enterprise"},{"f":317,"x":"Two names you trust. One company behind them. On September 1, 2026, Apex Instruments and the field network joined to form one company: {{endorser_line}}. Same people. Same service. More behind every case than ever. [Primary CTA button: Talk to your Account Manager] For your practice, nothing changes but the backing: The local service and relationships you count on are not changing. You now have more resources, more redundancy, and more support behind you than ever. Your team, your case routing, your communication, and your pricing continue uninterrupted.","h":"Hero"},{"f":317,"x":"\"We are the national devices lab network that runs like a manufacturer: one engineered, quality-controlled process, delivered through a coast-to-coast footprint, with a real team on every account.\" What that means, in practice: Best of both worlds. National scale, redundancy, and commercial reach, paired with local, high-touch accountability. Quality lives in the process. Engineered and repeatable: every Bench & Rack and Full Rack case is QC'd under a microscope by a master team. A partner, not a vendor. Dedicated account management, practice education, and for GSOs, multi-location tracking and standardized metrics.","h":"Who we are"},{"f":317,"x":"Digitization of Practices. On-site scanners, 3D design, benchside manufacturing, scan QC, AI-driven decisions. All-Encompassing Customer Experience. Dedicated Account Managers, tailored data portals, boots-on-the-ground service. New Suite of Products. Expanded refit options, advanced materials and bundles. Improved Clinical Efficiency & Client Care. Same-day bench units, housings in a day, reduced bench time. Better Practice Monetization. Streamlined workflows, better insurance-billing integration, a more profitable practice.","h":"The five pillars"},{"f":317,"x":"Pricing for existing accounts is locked for six months. The 6-Month Continuity Guarantee: if a case is late because of us, we make it right. A $500 digital-integration credit when you connect your scanner. Twelve months of complimentary high-end continuing education. Standardized FedEx 2nd Day shipping, free to your practice. Where we are going: {{vision_statement}} {{mission_statement}} *(Verbatim language pending sign-off, Q-17. Do not paraphrase into this slot.)* Closing band: Your next case is our next proof. Talk to your Account Manager today. [CTA: Talk to your Account Manager] *Footer: {{legal_entity_name}} (Q-1) · brand elements PROPOSED pending leadership lock · ™ after \"Custom LLM\" only.*","h":"Our commitments, effective day one"},{"f":318,"x":"The team behind the combination. One leadership group, drawn from both companies, accountable for every promise on this site. The roster: Roman Elias Mercado* · Chief Executive Officer · {{bio_mercado}} {{headshot_mercado}} Emmett* Kovach · President · {{bio_kovach}} {{headshot_kovach}} Dana* Whitfield · Chief Growth Officer · {{bio_whitfield}} {{headshot_whitfield}} Emory Ridgway · Chief Executive Officer, the field network · {{bio_ridgway}} {{headshot_ridgway}} Arturo Bellamy · Transition Leader · {{bio_bellamy}} {{headshot_bellamy}} *(Bios are sourced, never written by the brain: request from each leader's office or the PR agency. Titles verified against Facts/people-and-org/team.md. Client copy always uses the CEO's full name.)*","h":"Hero"},{"f":318,"x":"Questions for the leadership team? Start with your Account Manager; GSO and enterprise inquiries route to a named executive within 48 hours. [CTA: Contact us]","h":"Closing band"}]}