Current source · Hosted reading copy. Local machine references are omitted. Planning content does not establish launch readiness.
Intended hierarchy — adoption companion to the current shared plan
This additive companion binds existing v9a task acceptance; no duplicate plan, task, owner or production lane is created. The hierarchy instruction is consistent with current Resourcing edition8 and its preserved owner-direction record.
Home Services is the intended parent business. Glean, SimplyTech (also written Simply Tech), and Pitstop Mobile Auto are sibling subsidiaries beneath Home Services. Glean is not the parent of the other two; Pitstop's planned parent is Home Services. This states intended structure, not verified legal formation, registration, ownership transfer or employer status.
Shared dispatch, assistant/coordination, recruiting, finance and marketing may support the three businesses only within evidenced paid capacity. Count each shared position once and allocate its time/cost transparently; do not replicate the hire or assume free spare capacity in each subsidiary. Brand-specific technical authority, qualified delivery, customer obligations and accountability stay explicit. Shared ownership does not establish common booking/invoicing/data permissions or interchangeable technicians. Preserve all existing sales, capacity, funding and release gates; SimplyTech and Pitstop remain unmodeled until their inputs qualify.
| Existing task | Existing owner | Additional adoption evidence |
|---|---|---|
| E03 | Business Portfolio Strategy & Workspace Coordination | Version-bound business plan/entity/brand chart showing Home Services above all three siblings; intended versus legally formed status distinguished. |
| E11 | Resourcing | Current resource chart/roster and finite shared-support allocations, one hire counted once; primary/backup and brand-specific technical accountability retained. |
| E34, E35, E67 | Existing master and its sole financial modeler | Exact financial source-to-model disposition, parent/sibling labels and shared-position allocation; external revenue versus internal charges/eliminations and existing funding/capacity gates preserved; independent same-version receiving. |
| E64 | Define the brands | Exact marketing/strategy/catalog hierarchy and scoped shared support, consistent sibling naming; no implied legal formation, common service qualification or additional staffed capacity. Actual website/code changes remain with Claude. |
| E20 | Assess Tech Savings and Grants | Retain technology/intake accountability; brand hierarchy is supporting input. Shared intake/CRM scope must preserve business-specific permissions and actual paid capacity. |
| E25 | Outline Creatine Social Strategy | Retain existing social/content accountability; apply consistent sibling hierarchy in owned content using brand input, without duplicate staffing or service claims. |
Evidence status at reconciliation
- Resourcing: current edition8 source and owner-direction record explicitly carry the intended hierarchy. The preserved hierarchy review is bounded to its original edition6 source delta; it is supporting history, not a newly issued whole-edition8 review. Current edition8 intake has its separate bounded source review in the already selected packet.
- Business plan, financial model and marketing: the source session reports forwarding the correction. This companion records the required adoption evidence; those downstream artifacts were not freshly inspected here, so neither revision nor acceptance is inferred from message delivery.
- Coordinator: this companion binds the existing acceptance checks. Task states remain nonterminal. No new forecast, staffing assumption, legal assertion or operational release is created.
Next ready set: existing owners return exact revised artifact/version/hash and applicable independent review or source-to-model disposition against these tasks. Unverified downstream adoption stays in progress. No duplicate outreach or forwarding is needed solely because a notification arrived again.
Exact source pins (internal)
- [local source reference] — SHA256 0f95b3a83b0ef5412b6b402606fed3116bf9e443accf461f603ed8885778a18b
- [local source reference] — SHA256 c62e82560aa3cfff95780dec5c72ceac382c6d0095e04f48ff92d6e591392076
- [local source reference] — SHA256 86fe305c90122b5093521850b7bd4a394334d8927308a6f225bde910e96f5ff7
Observed UTC: 2026-10-26T02:46:25.506842+00:00
Master subsequently supplied a source-attributed relay of the same intended hierarchy. This corroborates instruction receipt, not downstream financial adoption:
- [local source reference] — SHA256 fb812ff536854dad9ab1af4105a09c0583ac28be381ab50f1e49e11d366fb515
Selection: this v2 supersedes v1 only to correct exact E20/E25/E64 owner labels and add the master relay pin. v1 is preserved history.