Operating Logic
1. Demand-first routing replaces territory planning
Instead of assigning couriers to fixed zones:
- all items are mapped into a live spatial demand field
- routes are computed as derived objects, not fixed paths
- couriers can be dynamically reassigned mid-shift
Key shift:
territory → real-time optimization surface
2. Upstream staging absorbs uncertainty
All variability is removed from execution:
- sorting, validation, battery checks, and load construction happen upstream
- couriers receive a single linear action stream (not multiple stacks)
- items are delivered as pre-sequenced bundles
This eliminates:
- morning loading chaos
- courier-side sorting
- mid-route reconciliation work
3. Execution agents operate in flow state only
Couriers no longer:
- decide order
- resolve exceptions
- interpret system inconsistencies
- manage multiple item stacks
They only:
- move
- access endpoint
- deposit / retrieve
This minimizes role-switching cost, a major hidden inefficiency.
4. Access-aware routing replaces distance optimization
Routing cost is modeled as:
cost = transport + access friction + geometry + mode constraints
Not just kilometers.
Stops are evaluated by:
- parking proximity
- doorway depth
- scan reliability
- barrier density
- vehicle compatibility
This yields:
- bike-advantage zones
- walk-advantage microclusters
- car-only access penalties
5. Depots become real-time exchange nodes
Instead of bulk warehouses:
- depots function as state transition points
- couriers swap:
- batteries
- cargo modules
- pre-assembled route kits
- system enables continuous replenishment instead of morning loading
6. Endpoints become standardized infrastructure
Receiving points shift from household improvisation to managed protocol:
- carrier defines endpoint geometry and constraints
- AI proposes placement via Pareto optimization (courier efficiency vs resident preference)
- endpoints become service contracts, not personal artifacts
Effect:
removes last-meter negotiation entirely
7. Identity and state are unified system-wide
A key failure mode addressed:
- multiple barcodes / inconsistent tracking states
- courier-side guessing of route placement
- fragmented system knowledge
Solution:
- canonical identity per object
- all scans resolve to single system state
- route placement is immediately shown (no interpretation layer)
8. Logistics becomes bidirectional circulation
Instead of one-way delivery:
- delivery, returns, repair, resale, and redistribution share one network
- objects behave like circulating capabilities, not owned inventory
- “try/return loops” become default behavior
This produces:
- reversible consumption
- minimal storage at endpoints
- continuous material circulation
Pattern Language
batch routes + manual sorting.
A courier receives a single linear route stream, not multiple sorted stacks.
Boundary Conditions
Key boundaries include System risks, Operational risks, and Human/system tensions.