How every part of the Empower system actually flows — the suite map, the Evaluator sales pipeline and its recommendation logic, the Sidekick repair workflow and its safety and credential decision trees, the customer Concierge intake, and the shared backend. Cross-referenced to all system and investor documents.
Every diagram uses the same shapes. Follow the arrows top to bottom; diamonds are decisions, and the label on each arrow is the answer it follows.
These charts are the map; the manuals are the territory. Pair them with the Sidekick Field Technician Manual and the Sales Training Manual, and see the full documentation map at the end.
One suite, two staff tools and one public tool, all sharing a single backend. The homeowner reaches us through the public Concierge intake; staff work from the hub into the Evaluator (sales) or Sidekick (service); both call the shared backend, which brokers the AI and data lookups.
The twelve-step survey-to-agreement pipeline. The technician/comfort advisor walks the home; step 8 hands off to the recommendation engine (next page), then pricing, comparison, and a signed Installation Agreement.
How recommendedType() chooses a system class from the home’s existing equipment, fuel, ductwork, and goals. Direct-replacement honors what’s there; otherwise the engine leans toward dual-fuel for gas + ducted homes seeking efficiency, heat-pump/cold-climate where electric or no-gas, and ductless where there are no ducts.
From job type to a signed customer copy. The guided fault tree is measurement-anchored and works offline; the safety tree and the credential gates (next two pages) run throughout.
App-authoritative and non-negotiable. Universal stops are never clearable; the conditional cracked-heat-exchanger stop clears only with the G2 gate plus override and an explicit acknowledgment.
Every repair step runs this check. Baseline work is open to all; gated work is locked unless the tech’s profile holds the credential. This is what keeps a green tech from doing senior work.
The public, no-login customer page. Emergencies short-circuit to a STOP screen before anything else; otherwise AI triage explains likely causes and routes a visit request to the office.
One stateless relay (/api/lookup) behind every app. Public actions (triage, support request) bypass the beta token; everything else requires APP_TOKEN. The backend brokers the AI and data providers so no keys ever live in the apps.
Everything these charts reference, and where each document fits. System docs describe how it’s built; training docs teach people to use it; the investor brief makes the business case.
| Document | What it is & what it covers |
|---|---|
| Master Plan System | The roadmap and the running log of decisions (Open questions & decisions). Start here for what’s built vs. planned. |
| Architecture & Design System | Single-file vs. modular, the public/internal security boundary, data models, and where safety is enforced in app logic. |
| Technical Reference System | The engines: recommendation logic, pricing/margin model, the 15 backend actions, env vars, and deployment. |
| Stage-2 Repair Copilot Spec System | Sidekick’s specification: job types, guided fault trees, the credential model, and the safety hard-stops. |
| User Guide System | End-user how-to across the apps. |
| Sales Training Manual Training | The Evaluator training program: the 12-step walkthrough, glossary, lessons, quizzes, and final test. |
| Sidekick Field Technician Manual Training | Levels, certifications, tools, level-up checklists, the customer-communication playbook, the app how-to, and safety. |
| Residential Service Plans Training | Stewardship / Performance / Signature plans and the service-plan agreement. |
| Investor Brief Investor | Unit economics, per-call AI/data cost, buy-vs-build, margin protection, market & rebate landscape, and the staged rollout. |
This flowcharts document lives in the same training set; link to it from the hub and read it next to the two manuals.