BLUE COLLAR BRANDING — SYSTEM SETUP GUIDE =========================================== Version: 3.0 Generated: February 12, 2026 Companion to: 07-system-manifest.txt This guide walks you through deploying the Blue Collar Branding system on the Ellavator platform. Follow these steps in order — each step builds on the one before it. ================================================================================ BEFORE YOU START ================================================================================ Make sure you have: - Access to the Ellavator platform with admin permissions - All system files (00 through 09) in your workspace - The Edition Guides/ folder with blue-collar-branding.md - The play-builder and playbook skills installed ================================================================================ STEP 1: UPLOAD KNOWLEDGE FILES ================================================================================ Add these 7 files to the system's knowledge base (general instruction set). Upload them in this exact order: ORDER FILE WHAT IT DOES ───── ────────────────────────────── ────────────────────────────────────── 1 00-system-instructions.txt Master prompt — the brain of the system. Controls all behavior, voice, and decision-making. 2 01-author-voice-profile.txt Brian Sooy's voice profile across 11 dimensions. Controls tone and language patterns system-wide. 3 02-system-job.txt Defines what this system exists to accomplish, who it serves, and how success is measured. 4 03-framework-catalog.txt All 40+ named frameworks from the book. The system references these by name during conversations. 5 04-ella-ment-map.txt All 28 knowledge artifacts across 4 sections. Tells the system what data exists and how it connects. 6 05-play-playbook-specs.txt Architecture blueprint for all 34 plays and 9 playbooks. Defines sequencing, handoffs, and structure. 7 06-edition-guide.txt Domain template for the Home Services edition. Default audiences, channels, tags, and builder adaptations. FILES TO KEEP OUT OF KNOWLEDGE: FILE WHY ────────────────────────────── ────────────────────────────────────── 07-system-manifest.txt Reference for humans, not the AI 08-play-build-queue.txt Build instructions (consumed during play creation, not needed at runtime) 09-playbook-build-queue.txt Build instructions (consumed during playbook creation, not needed at runtime) 10-system-setup-guide.txt This file — setup reference only 11-tag-list.txt Tag configuration reference 12-section-list.txt Section configuration reference 13-custom-ella-ment-instructions Runtime ella-ment behavior rules .txt (paste into system config, see Step 5) ================================================================================ STEP 2: CONFIGURE SYSTEM INSTRUCTIONS ================================================================================ Open the system instructions configuration in Ellavator and paste the full contents of 00-system-instructions.txt. This file contains: - System identity and purpose - 22 behavioral rules (7 ALWAYS + 7 NEVER + 8 WHEN) - 6-context voice cascade - 14+ framework reference entries - Ella-ment loading instructions with dependency enforcement - 7 domain-specific rule categories - Quality assurance checklist Verify after pasting: [ ] System identity section is visible [ ] All 22 behavioral rules are present [ ] Voice cascade has 6 contexts [ ] Framework reference guide is complete ================================================================================ STEP 3: SET UP TAGS ================================================================================ Configure these tags in the platform's tag system. See 11-tag-list.txt for the complete reference with descriptions. CATEGORY: STRATEGY (10 tags) foundation, strategy, diagnosis, clarity, brand, messaging, storytelling, positioning, market-focus, relevance CATEGORY: OPERATIONS (8 tags) operations, customer-experience, training, alignment, delivery, experience, moments, differentiation CATEGORY: GROWTH (7 tags) marketing, growth, revenue, channels, content, customer-intelligence, profiling CATEGORY: ACTIVATION (8 tags) team-activation, culture, motivation, continuous-improvement, implementation, project-management, roadmap, execution TOTAL: 33 unique tags across 4 categories Verify after setup: [ ] All 33 tags created [ ] Tags organized in 4 categories [ ] Tag slugs match exactly (lowercase, hyphenated) ================================================================================ STEP 4: SET UP EDITION SECTIONS ================================================================================ Create these 4 sections in the playbook browser. They organize the 9 playbooks into a logical progression. See 12-section-list.txt for the complete reference. SECTION PLAYBOOKS ───────────────────────────────── ────────────────────────────────── Foundation & Diagnosis Brand Foundation Customer Understanding Internal Alignment & Delivery Strategic Clarity Customer Alignment & Delivery Customer Experience Differentiation Market Positioning & Growth Strategic Relevance Marketing & Growth Operations & Continuous Improvement Team Activation & Brand Ambassador 90-Day Implementation Roadmap Verify after setup: [ ] 4 sections created [ ] Section names match exactly [ ] Each section shows correct playbook count ================================================================================ STEP 5: CONFIGURE CUSTOM ELLA-MENT INSTRUCTIONS ================================================================================ Open the custom ella-ment instructions configuration in Ellavator and paste the contents of 13-custom-ella-ment-instructions.txt. This file contains GOVERNS / ACTIVATE / CONNECTS TO / ENFORCE rules for all 28 active ella-ments. These rules tell the AI: - What each knowledge artifact controls in content output - When to load each artifact into context - How artifacts connect to each other - How to verify the artifact is being used correctly Verify after pasting: [ ] All 28 ella-ment instruction blocks are present [ ] Sections A (4), B (3), C (6), D (18) are complete — note that D17 is marked OPTIONAL/SKIP (not active in standard edition) [ ] Each block has all four fields (GOVERNS, ACTIVATE, CONNECTS TO, ENFORCE) ================================================================================ STEP 6: INSTALL EDITION GUIDE TO WORKSPACE ================================================================================ Copy 06-edition-guide.txt to the workspace location where the play-builder and playbook skills can find it: Edition Guides/blue-collar-branding.md Both builder skills read this file at session start. It tells them: - What audiences exist in this domain - What channels are standard - How to adapt their workflows for home services - What tags, sections, and milestones to use Verify: [ ] File exists at Edition Guides/blue-collar-branding.md [ ] Content matches 06-edition-guide.txt ================================================================================ STEP 7: BUILD STANDALONE PLAYS ================================================================================ Use the play-builder skill with 08-play-build-queue.txt to build the 6 standalone plays. These go into the Plays/ folder. The 6 standalone plays are: 1. Generate PASS Story (Single Customer Narrative) 2. Write Critical Moment Script (Single Scenario) 3. Design One Signature Moment 4. Create Process Checklist (One Phase) 5. Create Brand Messaging One-Pager 6. Build Local Marketing Machine Build method: - Open the play-builder skill - Point it at 08-play-build-queue.txt - Build standalone plays (plays 29-34 in the queue) - Each play saves as a .md file to Plays/ Note: The 28 builder plays in the queue (plays 1-28) are built INSIDE playbooks during Step 8. They do not go in the Plays/ folder. Verify after building: [ ] 6 .md files in Plays/ folder [ ] Each file has ###PLAY SETTINGS### header [ ] Each file has PLAY TITLE and TAGS fields [ ] No builder plays in the Plays/ folder ================================================================================ STEP 8: BUILD PLAYBOOKS ================================================================================ Use the playbook skill with 09-playbook-build-queue.txt to build all 9 playbooks. Each playbook gets its own subfolder in Playbooks/. Build order (follows CARE progression): 1. Brand Foundation → Playbooks/brand-foundation/ 2. Customer Understanding → Playbooks/customer-understanding/ 3. Strategic Clarity → Playbooks/strategic-clarity/ 4. Strategic Relevance → Playbooks/strategic-relevance/ 5. Customer Alignment & Delivery → Playbooks/customer-alignment/ 6. Customer Experience Diff. → Playbooks/experience-differentiation/ 7. Marketing & Growth → Playbooks/marketing-growth/ 8. Team Activation → Playbooks/team-activation/ 9. 90-Day Implementation Roadmap → Playbooks/90-day-roadmap/ Each playbook folder contains: - One wrapper file (-00-playbook-details.txt) - Play files (-01- through -0N-.txt) for each play in the sequence Build method: - Open the playbook skill - Point it at 09-playbook-build-queue.txt - Build playbooks 1-9 in order - Each playbook creates its subfolder automatically Verify after building: [ ] 9 subfolders in Playbooks/ [ ] Each subfolder has a -00-playbook-details.txt wrapper [ ] Each wrapper has ###PLAYBOOK SETTINGS### header [ ] Play files are numbered sequentially [ ] Builder plays have full import headers ================================================================================ STEP 9: RUN VERIFICATION CHECKLIST ================================================================================ KNOWLEDGE FILES [ ] 7 files uploaded (00 through 06) [ ] Files load in correct order [ ] No build scaffolding files in knowledge base SYSTEM CONFIGURATION [ ] System instructions configured from 00 [ ] Custom ella-ment instructions configured from 13 [ ] 33 tags created across 4 categories [ ] 4 edition sections created STANDALONE PLAYS [ ] 6 plays in Plays/ folder [ ] All plays have simplified headers (PLAY TITLE + TAGS) [ ] No builder plays in the Plays/ folder PLAYBOOKS [ ] 9 playbook folders in Playbooks/ [ ] Each has a wrapper file + play files [ ] Total play files across all playbooks: ~41 embedded plays [ ] All wrappers have full Layer 1 content (no placeholders) [ ] All embedded plays have full import headers MILESTONES [ ] 9 playbook-level milestones (1 per playbook) [ ] All milestone titles display correctly [ ] Celebration flags set correctly SYSTEM TEST [ ] Run one play end-to-end (suggested: Brand Foundation Play 1) [ ] Verify voice matches Brian Sooy's profile [ ] Verify ella-ment dependencies are enforced [ ] Verify output format matches play specification ================================================================================ EXPECTED COUNTS (for cross-checking) ================================================================================ ITEM COUNT ────────────────────────────── ───── Knowledge files 7 Build queue files 2 Support files (10-13) 4 Total system files 13 (00-13, skipping none) Tags 33 Tag categories 4 Edition sections 4 Ella-ments (total) 28 Ella-ments (active) 27 (D17 optional/skip in standard) Ella-ment sections 4 (A=4, B=3, C=6, D=18) Builder plays 28 Standalone plays 6 Total plays 34 Playbooks 9 Playbook milestones 9 Frameworks cataloged 40+ Behavioral rules 22 Voice contexts 6 Domain rule categories 7 ================================================================================ TROUBLESHOOTING ================================================================================ ISSUE: System doesn't reference frameworks correctly FIX: Verify 03-framework-catalog.txt is in knowledge base and that 00-system-instructions.txt framework reference section is complete. ISSUE: Voice doesn't match Brian Sooy's style FIX: Verify 01-author-voice-profile.txt is loaded. Check voice cascade in system instructions for correct priority order. ISSUE: Ella-ment dependencies not enforced FIX: Verify 04-ella-ment-map.txt is loaded and ella-ment loading instructions in 00-system-instructions.txt reference dependency chains. ISSUE: Tags not filtering correctly FIX: Verify tag slugs match exactly between play/playbook headers and the platform tag configuration. All slugs are lowercase with hyphens. ISSUE: Playbook plays not appearing in correct order FIX: Check play file numbering (-01-, -02-, etc.) within each playbook subfolder. Import wrapper first, then plays in sequence. ================================================================================ END OF SETUP GUIDE ================================================================================