BLUE COLLAR BRANDING — CUSTOM ELLA-MENT INSTRUCTIONS ===================================================== Version: 3.0 Generated: February 12, 2026 Source: 04-ella-ment-map.txt Paste these instructions into Ellavator's custom ella-ment instructions configuration. They tell the AI how each knowledge artifact behaves at runtime — what it controls, when to load it, how it connects to other artifacts, and how to verify it's being used correctly. 28 ella-ments across 4 sections: A (4), B (3), C (6), D (18). D17 (Ride-Along Coaching System) is marked OPTIONAL/SKIP — it's included for completeness but is not active in the standard edition. ================================================================================ SECTION A: COMPANY-LEVEL ARTIFACTS ================================================================================ --- A1: COMPANY POSITIONING & MARKET CONTEXT Tier: REQUIRED GOVERNS: All strategic direction, market positioning, and competitive context. Every play that references "who this company is" or "what makes us different" pulls from this artifact. Controls: company identity statements, values language, market scope definitions, competitive positioning claims. ACTIVATE: Load this ella-ment first in any conversation about brand strategy, positioning, competitive differentiation, company identity, values, or market context. Also load when any downstream ella-ment (C1, C2, C4, D1, D7) is triggered — A1 provides the foundation those artifacts build on. CONNECTS TO: C1 (Brand Clarity Statement uses positioning as foundation), C2 (Brand Character shaped by company values), C4 (Messaging Architecture flows from positioning), A2 (Competitive Analysis frames competitors relative to this position), D1 (CARE Definitions grounded in positioning), D7 (Relevance Matrix uses positioning to define specialization). ENFORCE: Never generate positioning language that contradicts this artifact. If company positioning is not yet completed, guide the user to complete it before producing strategic content. All values language must match the values defined here — no improvising or adding values not in this document. --- A2: COMPETITIVE LANDSCAPE ANALYSIS Tier: REQUIRED GOVERNS: All competitive context, differentiation claims, and market comparison language. Controls: competitor references, competitive advantage statements, market gap identification, and sales talking points that reference other companies. ACTIVATE: Load when the conversation involves competitive positioning, market differentiation, competitor comparisons, or sales messaging. Also load alongside D7 (Relevance Matrix) and any marketing content that claims competitive superiority. CONNECTS TO: D7 (Relevance Matrix defines competitive set), C4 (Messaging emphasizes advantages vs. competitors), C5 (Scripts include competitive differentiation language), A1 (Positioning frames the competitive analysis), B1 (Sub-positioning defined against these competitors). ENFORCE: Never reference competitors not listed in this artifact without flagging it as new information. Never claim competitive advantages not supported by the analysis. Competitive language must be specific and evidence-based, never generic ("we're better" without saying how). --- A3: FIVE DEADLY TRAPS SELF-ASSESSMENT Tier: STRONGLY PREFERRED GOVERNS: Problem diagnosis, urgency framing, and prioritization of brand work. Controls: team motivation messaging, priority sequencing for the roadmap, and language about "why this matters." ACTIVATE: Load when the conversation is about problem diagnosis, team motivation, roadmap prioritization, or answering "why should we do this work." Also load when creating team communication about the importance of brand consistency. CONNECTS TO: D12 (90-Day Roadmap prioritizes based on trap severity), D9 (Training curriculum addresses trap-driven urgency), A4 (Silo Audit provides operational context for traps). ENFORCE: Present traps as diagnostic — not judgmental. Use the severity scores from the assessment, not assumptions. When referencing traps, use the specific impact evidence the owner provided, not generic examples. --- A4: INTERNAL SILO AUDIT Tier: STRONGLY PREFERRED GOVERNS: Alignment diagnosis, office-to-field disconnect identification, and operational gap prioritization. Controls: language about internal communication issues, accountability assignments, and alignment focus areas. ACTIVATE: Load when the conversation involves team alignment, operational consistency, office-field communication, or the Alignment cornerstone of CARE. Also load when building training content that addresses specific operational gaps. CONNECTS TO: D9 (Training addresses gaps identified here), D5 (Service Alignment Checklist operationalizes fixes), D2 (GAPP helps sync office and field), D1 (Alignment definition grounded in actual silos), D12 (Roadmap Alignment phase uses this data). ENFORCE: Reference actual silos identified in the audit, not hypothetical ones. Severity scores and priority rankings from the audit drive all alignment recommendations. Never suggest alignment solutions that don't connect to an identified gap. ================================================================================ SECTION B: CUSTOMER/AUDIENCE PROFILES ================================================================================ --- B1: PRIMARY CUSTOMER PROFILE (6-PACK) Tier: REQUIRED GOVERNS: All customer-facing language, targeting decisions, messaging customization, and service design choices. This is the most-referenced ella-ment — virtually every marketing, sales, training, and experience play pulls from it. Controls: customer pain language, gain language, journey assumptions, emotional triggers, and channel preferences. ACTIVATE: Load in any conversation that produces customer-facing content, marketing materials, sales scripts, service design decisions, or training scenarios involving customer interaction. This should be loaded alongside most plays. CONNECTS TO: Every C-section and D-section ella-ment references B1. Key connections: C3 (PASS Stories tailored to B1), C4 (Messaging addresses B1 pains/gains), C5 (Scripts based on B1 journey), D3 (Journey mapped to B1 expectations), D4 (Moments meaningful to B1), D6 (Alignment maps B1 needs to promises), D13 (Marketing targets B1), D14 (Referral system built for B1). ENFORCE: All customer language must reflect the actual profile, not assumptions. Pain points must use the customer's language, not industry jargon. Decision criteria, emotional states, and journey stages must match the documented profile. If the profile hasn't been completed, guide the user through Brand Foundation playbook first. --- B2: SECONDARY CUSTOMER PROFILE (6-PACK) Tier: STRONGLY PREFERRED GOVERNS: Segmented messaging for the secondary customer type (if the company serves two distinct audiences — e.g., residential homeowners plus property managers). Controls: messaging variations, channel adjustments, and positioning angles for this segment. ACTIVATE: Load when the conversation explicitly involves the secondary customer segment, or when creating marketing content that addresses multiple audiences. Don't load by default — only when segmentation is relevant. CONNECTS TO: B1 (contrasts and complements primary profile), C4 (Messaging has audience variations), D13 (Marketing may split effort across segments). ENFORCE: Keep B2 clearly distinct from B1. Don't blend the two profiles. When generating content for B2, use B2's specific pains, gains, and journey — not B1's with minor tweaks. --- B3: DECISION-MAKER PROFILE Tier: OPTIONAL GOVERNS: Sales approach and negotiation language when the person using the service differs from the person paying for it (e.g., spouse, property manager, HOA board). Controls: objection handling, pricing justification, and authority-based messaging. ACTIVATE: Load only when the conversation specifically involves sales to a distinct decision-maker, or when creating sales training content that addresses financial authority dynamics. CONNECTS TO: B1 (user profile complements decision-maker profile), C5 (Scripts may include decision-maker scenarios). ENFORCE: Only reference this profile when a distinct decision- maker actually exists. Don't assume decision-maker complexity if B1 is also the payer. ================================================================================ SECTION C: BRAND VOICE/IDENTITY ARTIFACTS ================================================================================ --- C1: BRAND CLARITY STATEMENT Tier: REQUIRED GOVERNS: Brand identity language, values expression, and differentiation messaging. This is the "who we are" document that anchors all brand communication. Controls: identity claims, values language, differentiation wording, customer promise language, and team alignment statements. ACTIVATE: Load in any conversation that produces brand-level communication — website copy, team training materials, marketing content, or sales scripts. This is loaded almost as frequently as B1. CONNECTS TO: A1 (Positioning feeds into Brand Clarity), C2 (Character Guide extends Clarity into behavior), C4 (Messaging Architecture builds on Clarity claims), All marketing and team alignment outputs. ENFORCE: All brand identity claims must be consistent with this statement. The customer promise, differentiation language, and values-in-action must match exactly. Never improvise brand identity language — use what's documented here. --- C2: BRAND CHARACTER & BEHAVIOR GUIDE Tier: REQUIRED GOVERNS: How the brand shows up in daily situations — personality, tone, do's and don'ts, and behavioral standards. Controls: voice tone in customer interactions, behavior expectations for field and office teams, and brand personality expression. ACTIVATE: Load when generating customer interaction content, training materials on brand behavior, or any content that describes how the company should "show up." Also load for service recovery scenarios and experience design. CONNECTS TO: C1 (Character extends Clarity into behavior), C5 (Scripts embody character traits), D2 (GAPP behaviors align with character), D4 (Signature Moments express character), D9 (Training teaches character behaviors). ENFORCE: Personality traits must match the defined attributes — no drifting into generic "professional and friendly." Behavioral standards must reflect the specific do's and don'ts documented here. Tone must be consistent with documented patterns. --- C3: PASS STORY SUITE Tier: REQUIRED GOVERNS: Customer narrative and storytelling across all channels. Controls: story structure (Problem-Agitation-Solution-Success), customer transformation language, and proof points used in marketing and sales. ACTIVATE: Load when generating marketing content that uses customer stories, website testimonial sections, sales conversation guides, or team training that involves storytelling. CONNECTS TO: B1 (Stories tailored to primary customer), C4 (Messaging references story themes), A1 (Stories reference company position), D14 (Referral system uses story language). ENFORCE: All customer stories must follow the PASS structure. Stories must be based on real customer scenarios (or realistic composites), not hypothetical. Each story must connect to a specific customer pain from B1 and resolve through the company's unique approach from A1. --- C4: BRAND MESSAGING ARCHITECTURE Tier: REQUIRED GOVERNS: Message hierarchy, value propositions, and communication themes. Controls: primary claims, supporting messages, value pillars, and audience-specific message variations. ACTIVATE: Load when producing any marketing copy, website content, email sequences, social media, advertising, or sales scripts. This is the "what do we say" companion to C1's "who we are." CONNECTS TO: A1 (Messages flow from positioning), C1 (Messages express brand clarity), C3 (Stories reinforce messages), B1 (Messages address customer pains/gains), C5 (Scripts use message hierarchy), D13 (Marketing executes message strategy). ENFORCE: Primary message must appear consistently across all channels. Supporting messages must reinforce (not contradict) the primary claim. Value pillars must map directly to documented customer pains. No freelancing on messaging themes. --- C5: CRITICAL MOMENT SCRIPTS Tier: REQUIRED GOVERNS: Exact language for key customer interactions — what to say, how to say it, and when. Controls: phone scripts, arrival scripts, explanation scripts, pricing scripts, completion scripts, and follow-up scripts. ACTIVATE: Load when generating team training content, customer interaction guides, role-play scenarios, or any content about how field or office staff should communicate with customers. CONNECTS TO: D2 (GAPP behavioral framework guides script tone), C2 (Character defines personality in scripts), B1 (Scripts address B1's concerns and language), D3 (Scripts map to journey touchpoints), D4 (Signature Moments reference scripts). ENFORCE: Scripts must be word-for-word usable (not just guidelines). Language must match the customer's vocabulary level (no jargon). Each script must connect to a specific journey stage and address documented customer concerns. --- C6: TOUCHPOINT EXPRESSION GUIDE Tier: STRONGLY PREFERRED GOVERNS: Brand consistency across channels — website, email, social media, vehicle appearance, uniforms, and printed materials. Controls: channel-specific voice adjustments, visual standards, and format guidelines. ACTIVATE: Load when creating channel-specific content, designing customer communication templates, or auditing brand consistency across touchpoints. CONNECTS TO: C1 (Identity expressed consistently), C2 (Character adapted per channel), C4 (Messages distributed across channels), D3 (Touchpoints map to journey), D13 (Marketing channels follow these guidelines). ENFORCE: Voice must be recognizably consistent across channels while adapting to channel norms. Visual and format standards must be specific enough to execute (not vague guidelines). ================================================================================ SECTION D: DOMAIN-SPECIFIC ARTIFACTS (Home Service Implementation) ================================================================================ --- D1: CARE FRAMEWORK CORNERSTONE DEFINITIONS Tier: REQUIRED GOVERNS: Company-specific interpretation of Clarity, Alignment, Relevance, and Experience. Controls: how each cornerstone is defined, measured, and applied within this specific company. ACTIVATE: Load when explaining the CARE framework, setting strategic priorities, or building any content that references a specific cornerstone. Also load for roadmap planning and quarterly reviews. CONNECTS TO: All downstream D-section ella-ments (each maps to one or more cornerstones), A1 (Positioning roots Clarity), A4 (Silo Audit roots Alignment), D12 (Roadmap structured around cornerstones). ENFORCE: Cornerstone definitions must be company-specific, not generic CARE descriptions. Assessment scores and goals must reference the owner's actual input. Measures of success must be concrete and trackable. --- D2: GAPP FRAMEWORK OPERATIONALIZATION Tier: REQUIRED GOVERNS: Customer interaction philosophy — Guide, Address/ Acknowledge, Prioritize, Partner. Controls: how teams engage customers, behavioral expectations, and interaction quality standards. ACTIVATE: Load when creating training content, customer interaction scripts, service recovery procedures, or any content about how team members should behave with customers. CONNECTS TO: C5 (Scripts embody GAPP behaviors), C2 (Character aligns with GAPP tone), D4 (Signature Moments use GAPP), D5 (Alignment Checklist includes GAPP behaviors), D9 (Training teaches GAPP), D8 (Recovery uses GAPP approach). ENFORCE: All customer interaction guidance must align with GAPP principles. Trade-specific applications must be realistic for the company's actual service type. The team reference card must be concise enough to carry in the field. --- D3: SERVICE JOURNEY MAP & TOUCHPOINTS Tier: REQUIRED GOVERNS: Customer journey structure from first contact through post-service. Controls: phase definitions, touchpoint identification, experience standards, and GAPP applicability at each stage. ACTIVATE: Load when designing customer experiences, creating process checklists, building training scenarios, or mapping marketing to journey stages. CONNECTS TO: D4 (Signature Moments placed within journey), D5 (Checklists organized by journey phase), C5 (Scripts mapped to journey touchpoints), B1 (Journey reflects B1 expectations), D10 (Process Checklists follow journey phases). ENFORCE: Journey phases must reflect how this company's customers actually experience service — not a generic template. Every touchpoint must have defined standards and GAPP applicability noted. --- D4: SIGNATURE MOMENTS PLAYBOOK Tier: REQUIRED GOVERNS: Deliberately designed, repeatable experiences that customers talk about. Controls: moment definitions, execution steps, key phrases, consistency standards, and training materials for each moment. ACTIVATE: Load when creating experience design content, training on memorable moments, or any content about customer experience differentiation. CONNECTS TO: D3 (Moments placed within journey), D2 (GAPP guides moment delivery), C2 (Character expressed through moments), D9 (Training includes moment execution), D5 (Alignment Checklist includes moment delivery). ENFORCE: Each moment must have specific, step-by-step execution instructions. Key phrases must be memorizable. Moments must be realistic for the company's service type and team capability. No generic "exceed expectations" — must be specific. --- D5: SERVICE ALIGNMENT CHECKLIST Tier: REQUIRED GOVERNS: Operational accountability — maps brand promises to field behaviors at each touchpoint. Controls: checklist items, success criteria, accountability assignments, and consistency measurement. ACTIVATE: Load when creating operational standards, quality control processes, training checklists, or performance measurement tools. CONNECTS TO: D3 (Organized by journey phases), C1 (Each item links to a brand promise), D2 (GAPP behaviors included), A4 (Addresses specific silos identified in audit), D10 (Process Checklists extend this concept). ENFORCE: Every checklist item must connect to a specific brand promise. Items must be observable and measurable — not vague intentions. Accountability must be assigned to specific roles. --- D6: CUSTOMER ALIGNMENT PROFILE Tier: STRONGLY PREFERRED GOVERNS: How customer needs map to company strengths and brand promises. Controls: alignment claims, gap identification, and positioning emphasis priorities. ACTIVATE: Load when refining positioning, adjusting messaging emphasis, or analyzing whether the company is delivering on what matters most to customers. CONNECTS TO: B1 (Customer pains mapped), C1 (Brand promises mapped), A1 (Company strengths assessed), D7 (Relevance grounded in alignment reality). ENFORCE: Alignment must be honest — gaps where company promises but doesn't deliver must be acknowledged. Don't inflate alignment scores or ignore documented gaps. --- D7: RELEVANCE MATRIX & SPECIALIZATION PLATFORM Tier: REQUIRED GOVERNS: Specialization strategy — what the company can own in its market. Controls: specialization claims, competitive positioning, market focus decisions, and expansion strategy. ACTIVATE: Load when discussing market positioning, competitive strategy, specialization decisions, or marketing channel selection based on focus areas. CONNECTS TO: A2 (Competitive set defines positioning terrain), A1 (Positioning informs specialization choice), B1 (Customer segment aligns with specialization), D13 (Marketing channels optimized for chosen specialization). ENFORCE: Specialization must be based on the three-circle intersection (capability × market need × ownable position). Claims must be realistic — not aspirational. Competitive positioning must reference actual named competitors from A2. --- D8: SERVICE RECOVERY SYSTEM Tier: STRONGLY PREFERRED GOVERNS: How the company handles service failures and turns them into trust-building opportunities. Controls: recovery scripts, escalation procedures, authority guidelines, and decision trees. ACTIVATE: Load when creating service recovery training, customer complaint handling procedures, or content about turning problems into loyalty opportunities. CONNECTS TO: D2 (GAPP approach to recovery), C2 (Character maintains during recovery), D4 (Recovery can become a Signature Moment), D9 (Training includes recovery scenarios). ENFORCE: Recovery procedures must be specific to the company's trade. Authority guidelines must be clear — field staff need to know what they can decide on the spot vs. what needs escalation. Scripts must demonstrate empathy, not defensiveness. --- D9: BRAND AMBASSADOR TRAINING CURRICULUM Tier: REQUIRED GOVERNS: 12-week phased training program that turns field teams into brand ambassadors. Controls: curriculum structure, session plans, role-play scenarios, and progress measurement. ACTIVATE: Load when building training content, onboarding materials, team development plans, or any content about teaching brand behaviors to field or office staff. CONNECTS TO: D2 (GAPP is core training content), C5 (Scripts are practiced in training), D4 (Signature Moments trained), A4 (Addresses gaps from Silo Audit), D5 (Checklist behaviors taught), D11 (Recognition reinforces training). ENFORCE: Training must follow the 3-phase progression (Foundation → Skill Development → Integration). Sessions must be 60-90 minutes (realistic for trade teams). Content must be practical and field-applicable, not theoretical. --- D10: PROCESS CHECKLISTS BY PHASE Tier: STRONGLY PREFERRED GOVERNS: Step-by-step operational checklists for each phase of customer interaction. Controls: pre-service, protection, quality control, and follow-up phase checklists. ACTIVATE: Load when creating operational documentation, daily execution tools, quality audit instruments, or training materials focused on specific service phases. CONNECTS TO: D3 (Organized by journey phases), D5 (Extends alignment checklist concept), D9 (Used in training exercises). ENFORCE: Checklists must be field-usable — one page per phase, simple language, clear success criteria. Each item must be actionable by the role responsible for it. --- D11: RECOGNITION AND REWARD SYSTEM Tier: STRONGLY PREFERRED GOVERNS: Recognition cadence and reward structure tied to brand values and CARE delivery. Controls: daily/weekly/monthly/ quarterly recognition formats, reward types, and connection to brand behaviors. ACTIVATE: Load when building culture reinforcement systems, team engagement content, performance management frameworks, or content about sustaining brand-aligned behavior. CONNECTS TO: D9 (Recognition reinforces training), D1 (Tied to CARE cornerstones), C2 (Recognizes character-aligned behavior), D4 (Celebrates Signature Moment delivery). ENFORCE: Every recognition event must explicitly connect to a brand value or CARE cornerstone. Rewards must be proportional and sustainable (don't create a system the company can't maintain). Peer recognition must be included, not just top-down. --- D12: 90-DAY IMPLEMENTATION ROADMAP Tier: REQUIRED GOVERNS: Phased, weekly action plan for rolling out the CARE framework company-wide. Controls: phase structure, weekly deliverables, role assignments, and success metrics. ACTIVATE: Load when creating implementation plans, project timelines, accountability frameworks, or any content about "how to actually do this" within 90 days. CONNECTS TO: A3 (Trap severity drives priorities), D1 (Phases map to CARE cornerstones), D9 (Training woven into roadmap), All ella-ments (roadmap sequences their creation). ENFORCE: Roadmap must be achievable by an owner spending 2-5 hours per week on brand work. Weekly deliverables must be specific enough to execute and small enough to complete in a week. Never create a roadmap that requires full-time dedication — this is a working business. --- D13: MARKETING ACTION PLAN Tier: REQUIRED GOVERNS: 90-day revenue-focused marketing plan with channel selection, content calendar, and budget allocation. Controls: marketing goals, channel strategy, content themes, and measurement dashboards. ACTIVATE: Load when creating marketing plans, content calendars, channel strategies, budget allocations, or measurement frameworks for customer acquisition. CONNECTS TO: B1 (Targeting optimized for primary customer), C4 (Messaging executed through marketing), D7 (Channels match specialization focus), D14 (Review/referral feeds marketing), C3 (Stories used in content), C6 (Channel guidelines applied). ENFORCE: Marketing plan must connect to documented customer profile (B1), not assumptions. Channel selection must be realistic for the company's budget and team capacity. Content calendar must be sustainable — don't create a volume the company can't maintain. --- D14: REVIEW REQUEST & REFERRAL SYSTEM Tier: REQUIRED GOVERNS: Systematic process for collecting reviews and generating referrals. Controls: request timing, templates, tracking, incentive structures, and ROI measurement. ACTIVATE: Load when creating growth systems, reputation management content, customer follow-up sequences, or any content about leveraging satisfied customers for growth. CONNECTS TO: B1 (Request timing maps to B1 journey), D3 (Review requests placed at post-service touchpoints), D4 (Satisfied Signature Moment delivery drives reviews), C3 (Story language echoes in review requests), D13 (Referrals feed marketing pipeline). ENFORCE: Review request timing must feel natural within the customer journey — never pushy or transactional. Templates must be personalized (not generic mass emails). Referral incentives must be appropriate for the trade and customer type. --- D15: QUARTERLY BRAND AUDIT WORKBOOK Tier: STRONGLY PREFERRED GOVERNS: Quarterly assessment of brand health and CARE cornerstone progress. Controls: assessment methodology, scoring criteria, benchmarking approach, and improvement prioritization. ACTIVATE: Load when creating audit instruments, progress measurement frameworks, or quarterly planning content. CONNECTS TO: D1 (Scores each CARE cornerstone), A2 (Benchmarks against competitors), B1 (Integrates customer feedback), D12 (Measures roadmap progress), D11 (Feeds recognition data). ENFORCE: Audit must be completable by an owner in 2-3 hours quarterly. Scoring must be honest — not inflated. Action items must be prioritized and specific. Comparison data must reference actual competitors from A2. --- D16: MORNING HUDDLE FORMAT Tier: STRONGLY PREFERRED GOVERNS: Daily team alignment ritual — 5-10 minute morning check-in structure. Controls: agenda template, facilitation tone, frequency guidance, and connection to brand behaviors. ACTIVATE: Load when creating daily team rituals, alignment practices, or team communication frameworks. CONNECTS TO: D4 (Daily Signature Moment practice), D2 (Daily GAPP scenario), D11 (Daily recognition), D9 (Reinforces training between sessions). ENFORCE: Huddle must be 5-10 minutes maximum — no longer. Agenda must fit on one page. Tone must be energizing, not lecturing. Must include at least one brand behavior practice element (GAPP scenario or Signature Moment of the day). --- D17: RIDE-ALONG COACHING SYSTEM Tier: OPTIONAL / SKIP IN STANDARD EDITION GOVERNS: Management observation and coaching for consistent brand delivery in the field. Controls: observation checklist, feedback framework, and coaching cadence. ACTIVATE: Load only when the user specifically requests ride- along or field observation content. This is not active in the standard edition — most companies with 5-50 employees don't have dedicated coaching capacity. CONNECTS TO: D9 (Extends training into field), D5 (Observes checklist compliance), D4 (Evaluates Signature Moment delivery). ENFORCE: If activated, keep the system simple — observation sheet plus feedback conversation. Don't over-engineer for small companies. This is supplementary to D9 training, not a replacement. --- D18: INVISIBILITY GAP ANALYSIS Tier: STRONGLY PREFERRED GOVERNS: Quantification of disconnect between actual service quality and market perception. Controls: perception vs. reality assessment, revenue impact estimates, and perception shift targets. ACTIVATE: Load when discussing brand awareness gaps, revenue impact of invisibility, team motivation around brand investment, or content about "why brand matters financially." CONNECTS TO: A3 (Traps Assessment provides context), A1 (Positioning defines what should be visible), D7 (Relevance strategy addresses the gap), D13 (Marketing closes the gap). ENFORCE: Gap quantification must be realistic — don't overstate revenue impact. Perception data must come from actual sources (reviews, interviews, market research), not assumptions. Frame as opportunity, not failure. ================================================================================ LOADING PRIORITY RULES ================================================================================ These rules tell the system which ella-ments to load first when multiple are relevant: PRIORITY 1 (Always load first): A1 (Company Positioning) — foundation for everything B1 (Primary Customer Profile) — customer context for everything PRIORITY 2 (Load for brand/messaging work): C1 (Brand Clarity) — identity anchor C4 (Messaging Architecture) — communication framework PRIORITY 3 (Load for operations/training work): D2 (GAPP) — behavioral framework D3 (Service Journey) — experience structure D5 (Alignment Checklist) — accountability framework PRIORITY 4 (Load for specific contexts): Load based on conversation topic — see ACTIVATE rules above ================================================================================ DEPENDENCY ENFORCEMENT RULES ================================================================================ The system should enforce these dependencies at runtime: RULE: Before building any C-section ella-ment, verify A1 exists. RULE: Before building any D-section ella-ment, verify C1 and B1 exist. RULE: Before building D4 (Signature Moments), verify D3 exists. RULE: Before building D5 (Alignment Checklist), verify D3 exists. RULE: Before building D7 (Relevance Matrix), verify A2 exists. RULE: Before building D8 (Service Recovery), verify D2 and D4 exist. RULE: Before building D9 (Training), verify D2, C5, and D4 exist. RULE: Before building D12 (Roadmap), verify D1 and A3 exist. RULE: Before building D13 (Marketing), verify C4, D7, and B1 exist. RULE: Before building D14 (Review/Referral), verify D3 and B1 exist. When a dependency is missing, guide the user to complete it first by suggesting the relevant builder play or playbook. ================================================================================ END OF CUSTOM ELLA-MENT INSTRUCTIONS ================================================================================