Architecture & Operating Design · v0.2

Company operating intelligence, proven in shadow before it is allowed to act.

Implemented in the private src/ TypeScript package (see software modules). Implementer specs live at repo-root specs/ — they are not published on Pages.

Primary objectives

Recommended logical architecture

ServiceTitan / ProBooks / warranty / telephony / maps / pricebook / inventory / media → Integration & MCP Layer → Canonical Event Bus → Operational State Store → Decision Engines → Shadow/Counterfactual Engine → Receipts & Audit → Role Interfaces → Controlled Action Layer.

This portal documents that design. It does not host the event bus or execute engines.

Decision engines (design / stub)

EngineStatus
Booking & Call Intakedesign
Dispatch / Call-Fitdesign
Full-Day Trajectorydesign
Runtime Predictiondesign
Technician Skill & Explorationdesign
Visual/Video QAdesign
Warranty & Callback Classifierdesign
Manager Intervention Predictordesign
Field Advisordesign
Pricebook / Quote / Marginlive-pure
Inventory / van stock / fulfillmentlive-pure
Communications / recognition / mission boardlive-pure
Weather / demandlive-pure
Maintenance / equipment-age routinglive-pure
Revenue & Turnover Attributiondesign
Counterfactual Outcomedesign
Receipt / Audit / Overridedesign

v0.2 software (coded, not a spec dump)

Property Intelligence v1.0 (coded, not a spec dump)

Storage separation

  • Immutable event ledger
  • Operational state store
  • Analytical warehouse / lakehouse
  • Media / object store
  • Feature / skill store
  • Receipt store

North star

The system earns authority by being auditable, adaptable, and repeatedly correct under real operating conditions — not by being more confident than the humans running the business.

Success: any day, call, or disagreement can show what was known, what operations did, what Trades recommended, whether a human changed it, how the day adapted, what happened in the field, and what result followed.