Shadow-mode proof framework · §16 / §21

Proof over autonomy. Authority is earned, not assumed.

The first valuable build is a reliable shadow operating system that can reconstruct calls, Vans, routes, bookings, warranty/membership context, outcomes, and overrides with defensible receipts. This site documents that ladder. It does not claim any rung is live.

Deployment ladder

  1. Observe

    Ingest and normalize data without influencing decisions. Analytics mode name: Watcher.

  2. Shadow

    Produce sealed counterfactual recommendations while humans and existing software operate normally.

  3. Recommend

    Surface decisions to staff with no autonomous execution.

  4. Human Approves

    One-click acceptance / override workflow.

  5. Limited Autonomy

    Narrowly scoped actions with hard constraints and rollback.

  6. Autonomous Operations

    Only after sustained evidence, governance, and operational approval. Not claimed here.

Proof metrics — not revenue alone

Minimum viable shadow system

BYO: the user points this local runtime at their own ServiceTitan and ProBooks read sources. FragGate admits + hashes on that machine. No central dump. Normalize customers, equipment, calls, Vans, bookings, jobs, quotes, parts, turnovers, and sales. Create canonical timestamps and call IDs. Map identities to Van identifiers. Implement Chains A/B/C, baseline Call-Fit and rebasing, role tags and multi-window dashboards, 30-day callback/warranty support, warranty lookup adapters where authorized, media ingest with initial visual QA, reconstructable receipts, and actual-versus-shadow comparison without future information leaking into the original recommendation.