═══════════════════════════════════════════════════════════════════════════════ ELLA REAL ESTATE EDITION — SYSTEM SETUP GUIDE ═══════════════════════════════════════════════════════════════════════════════ Master checklist for bringing the Real Estate Edition live in Ellavator AI Complete these steps in order — each depends on the previous SYSTEM: Ella Real Estate Edition DATE: 2026-02-12 ═══════════════════════════════════════════════════════════════════════════════ HOW TO USE THIS GUIDE ═══════════════════════════════════════════════════════════════════════════════ This is the single to-do list for assembling the Real Estate Edition inside Ellavator AI. Work through it top to bottom. Every step tells you what to do, where to find the source material, and how to verify you did it right. Source files referenced below live in the system-scanner/ folder. ═══════════════════════════════════════════════════════════════════════════════ STEP 1: CREATE THE EDITION ═══════════════════════════════════════════════════════════════════════════════ Action: In Ellavator AI, create a new edition named "Real Estate" Details: - Edition name: Real Estate - Primary user: Real estate agents and broker-owners - Tiers: Standard (default), Luxury (premium) Verify: The edition appears in Ellavator's edition list Source: 06-edition-guide.txt, Section 1 (Edition Overview) ═══════════════════════════════════════════════════════════════════════════════ STEP 2: CREATE SECTIONS ═══════════════════════════════════════════════════════════════════════════════ Action: Create the following 4 sections in the edition, in this order: 1. Get Started Purpose: Foundation-building playbooks run early in the user journey 2. Win a Listing Purpose: Playbooks that help agents win and onboard listing clients 3. Promote a Listing Purpose: Playbooks that promote active listings across all channels 4. Market Your Office Purpose: Brokerage-level marketing, recruitment, and relationship building Verify: All 4 sections appear in the edition in the correct order Source: 12-section-list.txt (full section details and playbook assignments) ═══════════════════════════════════════════════════════════════════════════════ STEP 3: CREATE TAGS ═══════════════════════════════════════════════════════════════════════════════ Action: Create all tags from the tag taxonomy. Tags are organized into 6 categories. Create every tag listed below: SITUATION: new-listing, active-listing, pre-listing, off-market, seasonal, recurring, event, milestone-moment AUDIENCE: buyers, sellers, sphere, neighbors, agents, prospects, recruits, general-public OUTPUT TYPE: social-posts, emails, print-materials, landing-pages, video-scripts, plans-calendars, strategy-briefs, checklists, talking-points GOAL: generate-leads, sell-faster, build-brand, recruit-agents, stay-connected, establish-authority EFFORT: quick-win, deep-work, ongoing-series ROLE: agent, office-admin, broker-owner Verify: Count your tags — you should have 37 total across 6 categories Source: 11-tag-list.txt (complete tag reference with descriptions) ═══════════════════════════════════════════════════════════════════════════════ STEP 4: UPLOAD KNOWLEDGE FILES ═══════════════════════════════════════════════════════════════════════════════ Action: Upload the following files as system-level knowledge files in the edition. Upload them in this order: File 1: 01-author-voice-profile.txt What it is: Ella's guide voice — how the system speaks to agents (not the agent's voice) File 2: 02-system-job.txt What it is: The system's job definition, outcomes, and 67 sub-jobs File 3: 03-framework-catalog.txt What it is: All 32 frameworks the system references (philosophical, diagnostic, strategic, tactical) File 4: 04-ella-ment-map.txt What it is: Complete inventory of all 31 ella-ments with schemas, tiers, dependencies, and archetype libraries File 5: 05-play-playbook-specs.txt What it is: Architectural specs for all 9 standalone plays and 27 playbooks File 6: 06-edition-guide.txt What it is: Edition defaults — audience archetypes, channel set, voice cascades, knowledge sourcing, play builder adaptations File 7: 07-system-manifest.txt What it is: Table of contents and build sequence for the entire package Verify: All 7 knowledge files show as uploaded in the edition Note: The system instructions (00) are NOT uploaded as a knowledge file — they go in the system instructions field (see Step 5). Files 08 and 09 are build queues used during construction and don't need uploading. Files 10-13 are human setup guides (this file and its companions) and also don't need uploading. ═══════════════════════════════════════════════════════════════════════════════ STEP 5: SET UP SYSTEM INSTRUCTIONS ═══════════════════════════════════════════════════════════════════════════════ Action: Copy the contents of 00-system-instructions.txt into Ellavator's system instructions field for this edition Details: - This is the master prompt that governs all play execution - It includes: system identity, four-tier context model, behavioral rules, voice cascade architecture, framework reference guide, ella-ment knowledge sourcing instructions, domain-specific rules, knowledge file usage instructions, and output standards - The knowledge file instructions (which tell the system how to use each uploaded knowledge file) are already included in this document Verify: - System instructions field is populated - The instructions reference all 7 knowledge files by name - The instructions include the knowledge file usage instructions section - The instructions include the custom ella-ment instruction reference Source: 00-system-instructions.txt ═══════════════════════════════════════════════════════════════════════════════ STEP 6: CREATE CUSTOM ELLA-MENT INSTRUCTIONS ═══════════════════════════════════════════════════════════════════════════════ Action: For EVERY ella-ment in the system, enter its custom instruction into Ellavator's per-ella-ment custom instruction field Details: - Open 13-custom-ella-ment-instructions.txt - For each ella-ment listed (A1 through CX7), copy the instruction block and paste it into that ella-ment's custom instruction field in Ellavator - Each instruction follows the GOVERNS / ACTIVATE / CONNECTS TO / ENFORCE pattern - Ellavator will automatically substitute {filename} and {companyName} at runtime — leave these template variables as-is Ella-ments requiring instructions (31 active): Section A: A1, A2, A3, A4, A5, A6, A7 Section B: B1, B2, B3, B4, B5, B6 Section C: C1, C2, C3, C4, C5 Section D: D1, D2, D3, D4, D5, D6 Section CX: CX1, CX2, CX3, CX4, CX6, CX7 (CX5 is retired — skip it) Verify: - Every active ella-ment has a custom instruction populated - Count: 30 ella-ments should have instructions (31 active minus CX5 retired) - Spot-check 3-4 instructions to confirm {filename} and {companyName} template variables are present (not hardcoded values) Source: 13-custom-ella-ment-instructions.txt ═══════════════════════════════════════════════════════════════════════════════ STEP 7: IMPORT PLAYS AND PLAYBOOKS ═══════════════════════════════════════════════════════════════════════════════ Action: Import all standalone plays and playbooks into Ellavator Part A — Standalone Plays (9 plays): Source folder: Plays/ Import each .md file as a standalone play Plays to import: 1. agent-market-intel-sharing.md 2. agent-social-post-writer.md 3. buyer-competitive-position-cards.md 4. high-trust-partner-strategy.md 5. listing-social-post.md 6. listing-video-planner.md 7. neighbor-post-sale-value-letter.md 8. property-negotiation-messaging-toolkit.md 9. seller-status-update.md Part B — Playbooks (27 playbooks): Source folder: Playbooks/ Import each playbook folder (wrapper + plays) Playbooks to import (in dependency order): Foundation: 1. agent-voice-print-builder (6 plays) 2. agent-goal-setting (3 plays) 3. content-pillars (2 plays) 4. local-market-intelligence (3 plays) 5. office-foundation (5 plays) 6. content-strategy (2 plays) 7. office-context-refresh (2 plays) Listing Prep: 8. property-bot (4 plays) 9. confirm-the-win (3 plays) 10. property-marketing-plan (3 plays) 11. luxury-listing-presentation-builder (15 plays) 12. white-glove-seller-experience-builder (3 plays) Listing Promotion: 13. 14-day-launch-blitz (3 plays) 14. listing-landing-page (3 plays) 15. listing-launch-momentum (4 plays) 16. new-listing-social-engine (4 plays) 17. open-house-game-plan (5 plays) 18. pre-launch-listing (2 plays) 19. property-website-builder (4 plays) 20. paid-media-campaign-planner (4 plays) Network Building: 21. agent-referral-network (3 plays) Practice & Office: 22. brokerage-talent-attraction (3 plays) 23. lead-nurturing (3 plays) 24. office-pr-planner (3 plays) 25. office-paid-media-planner (3 plays) 26. office-social-post-planner (3 plays) 27. stay-top-of-mind (4 plays) Verify: - 9 standalone plays imported - 27 playbooks imported, each with correct play count - Spot-check section assignments: Agent Voice Print Builder → Get Started, Property Marketing Plan → Win a Listing, 14 Day Launch Blitz → Promote a Listing, Lead Nurturing → Market Your Office - Spot-check tags on 3-4 plays to confirm valid tag slugs Source: Plays/ folder, Playbooks/ folder ═══════════════════════════════════════════════════════════════════════════════ STEP 8: UPLOAD EDITION GUIDE AS RUNTIME COPY ═══════════════════════════════════════════════════════════════════════════════ Action: Place a runtime copy of the edition guide where plays can access it Details: - Copy 06-edition-guide.txt to Edition Guides/real-estate.md - This is the knowledge sourcing copy that plays reference during execution - The original in system-scanner/ is the build-time reference Verify: Edition Guides/real-estate.md exists and matches 06-edition-guide.txt Source: 06-edition-guide.txt ═══════════════════════════════════════════════════════════════════════════════ STEP 9: FINAL VERIFICATION ═══════════════════════════════════════════════════════════════════════════════ Action: Run through this complete checklist to confirm everything is live Edition Setup: □ Edition "Real Estate" exists □ 4 sections created in correct order □ 41 tags created across 6 categories Knowledge & Instructions: □ 7 knowledge files uploaded (01-07) □ System instructions populated from 00-system-instructions.txt □ System instructions include knowledge file usage instructions □ System instructions include custom ella-ment instruction reference □ 30 ella-ment custom instructions entered (all active ella-ments) Content: □ 9 standalone plays imported from Plays/ □ 27 playbooks imported from Playbooks/ □ Edition guide runtime copy at Edition Guides/real-estate.md Functional Test: □ Run one foundation playbook (e.g., Agent Voice Print Builder) to verify knowledge sourcing works □ Check that the system references knowledge files correctly □ Check that the voice cascade operates (D4 → C1 → C3 → default) □ Verify ella-ment custom instructions activate during play execution ═══════════════════════════════════════════════════════════════════════════════ SUMMARY ═══════════════════════════════════════════════════════════════════════════════ Total steps: 9 Total knowledge files to upload: 7 (files 01-07) Total custom ella-ment instructions to enter: 30 Total standalone plays to import: 9 Total playbooks to import: 27 Total sections: 4 Total tags: 37 Total edition tiers: 2 (Standard, Luxury) ═══════════════════════════════════════════════════════════════════════════════ END OF SYSTEM SETUP GUIDE ═══════════════════════════════════════════════════════════════════════════════