curbitoOPERATIONS DEMOCity workflow

SYNTHETIC BUSINESS PILOT

Know the curb
before the crew rolls.

Property teams see verified work near every managed address. Dispatchers check a destination and arrival window before assigning a vehicle. Drivers receive only the alert tied to their current assignment—never an employee movement feed.

MULTI-PROPERTY BOARD

Three sites. One action queue.

Sample data only
7:00 AM tomorrow · North Minneapolis shopGarbage and organics pickup

Place carts at the collection point

Assigned
Move by 5:00 PM Fri · Uptown rentalTemporary event no parking

Notify tenant and clear the curb

Assigned
Planning only · Northeast storefrontNearby utility project

Not assigned—exact impact is unverified

Context
PROPERTY INPUTExact addressencrypted at rest
FLEET INPUTStop windownot continuous tracking
WEAK EVIDENCEContext onlynever assigned as work
URGENT ROUTEDriver + dispatchshift-aware contract

IMPLEMENTED API CONTRACT

One engine for resident and fleet decisions.

The protected operations endpoint accepts a destination window or normalized property events. It returns proceed, provider checkout, reroute, do-not-dispatch, confirm-permit, or verify-on-arrival—plus a least-data receipt identifying the controlling source, policy, time, freshness, authority and geometry match.

POST /api/partner/operations/plan
Authorization: Bearer partner-key
x-curbito-role: dispatcher
x-curbito-actor-ref: demo-dispatcher-01

{
  "mode": "pre_dispatch",
  "stop": {
    "vehicleRef": "truck-07",
    "destinationRef": "job-42",
    "use": "loading",
    "arrivalAt": "...",
    "departureAt": "..."
  }
}

→ outcome: "reroute"
→ receipt.verification: "verified"
→ receipt.evidence: source + rule + trust state
→ storesTripTrail: false
→ auditId: least-data receipt

Additional modes:
fleet_manifest · scenario_compare · queue_export (JSON/CSV)

Fleet manifests evaluate up to 50 ordered stop windows
and can produce an explicit, provider-neutral handoff.
No coordinates, plates, drivers, or trip trail are exported.
01Roles plus an audit receipt

Owners, property managers, site staff, dispatchers, drivers, and viewers receive only the capabilities needed for their work. Every successful queue, plan, comparison and export records a least-data audit ID.

02Only verified work is assigned

Stale, nearby, or incomplete events remain context. They cannot create a dispatch instruction or an operational all-clear.

03Plan a route—without worker trails

Authorized dispatchers can evaluate a bounded multi-stop manifest, review conflicts in priority order, and prepare a route-provider-neutral handoff. The result never claims invented savings or builds an employee-location history.