Delivery miles are not total miles.
A driver may travel to the merchant, wait, deliver away from their working zone and then travel back before the next realistic order. CHOPX models that burden instead of pricing only the customer leg.
Layer 03 · Movement · logistics fairness infrastructure
CHOPX makes the real delivery burden visible before the driver says yes.
CHOPX / ChopExpress is a fairness-driven last-mile operating model. It is designed around a simple failure in conventional delivery economics: the customer-facing delivery leg is not the whole job. Pickup travel, store delay, delivery miles, return-zone burden, vehicle operating reality, platform-funded compensation, customer tips, driver consent and field evidence all affect whether an offer is sustainable.
Sprint 5E hardeningFastAPI + React/Vite architectureCompliance / lifecycle testsPre-production
The logistics problem
A delivery offer can look profitable while the driver absorbs the hidden miles and risk.
CHOPX starts from the operating reality of the person doing the delivery. That changes what must be measured before an offer is considered fair.
A tip should not repair platform pay.
Customer generosity is separated from what the platform itself funds. That makes the offer economics legible to the driver and prevents the tip from masking an otherwise weak base offer.
Acceptance must be a real choice.
Safe-decline logic, compliance eligibility and consent/override state are designed so a driver is not silently punished or activated through an ambiguous workflow.
Offer construction
Order → route burden → platform pay → driver decision.
The current architecture is modular: economics, fairness, offer/dispatch, compliance, vehicle-reality, field-session and market-simulation logic are separate concerns rather than one opaque formula.
Receive order context
The order pipeline captures the merchant/customer movement problem and the data required to evaluate the offer. The platform should not invent missing route or timing data.
Calculate practical route burden
The fairness model considers pickup, delivery and return-zone reality. This is the PPEM/economic-mile principle: price the actual work pattern rather than the most convenient mileage slice.
Separate platform pay from tip
The system can show what the platform is funding and what the customer chose to add. Tip value remains driver-owned and does not retroactively convert poor platform economics into a “good” offer.
Check eligibility / compliance state
A driver should only receive/accept actions allowed by the current activation and compliance lifecycle. Sprint 5E specifically hardened legacy activation paths outside local-test conditions.
Present a transparent offer
The offer should expose enough route/economic context for a driver to understand the burden. The design goal is informed consent, not a single unexplained score.
Accept or safely decline
Driver choice and any override path are represented as explicit state. The platform can audit how an outcome was reached instead of treating every dispatch decision as automatic authorization.
Driver protection layer
Fairness is more than the dollar amount on the offer.
The codebase separates compliance, lifecycle, vehicle/operating reality and reserve-planning concepts because driver sustainability is not one variable.
Activation has prerequisites.
Current backend logic includes driver activation, consent and compliance posture. Production-like mutation routes also have API security guardrails. Provider-backed production identity is still a deliberate transition boundary.
The car is part of the economics.
Vehicle, safety, actual-mile and operating-risk logic exists so the system can reason about real delivery burden rather than assuming every mile has the same cost or risk.
Plan for costs without pretending to hold money.
Maintenance, insurance/protection and tax-oriented reserve concepts are planning/accounting logic at this stage. The system must not imply live banking, paycards, insurance underwriting or regulated reserve custody.
Consent should remain observable.
The driver’s decline/accept/override path is part of the audit trail. A fair marketplace should be able to explain why the driver was eligible, what was offered and how consent was captured.
Field evidence
Pickup, delivery and exceptions should not have to be reconstructed from memory.
CHOPX’s field-session architecture is the movement equivalent of the evidence discipline used elsewhere in IZZYAKOS: preserve what happened, who acted and what state changed.
Bind actions to an active driver context.
Field-session routes and lifecycle contracts create a place to associate delivery events with the correct driver/session rather than anonymous client state.
Evidence should support disputes and exceptions.
Pickup, receipt, drop-off, GPS/incident and related evidence concepts are intended to support later audit. Private production evidence storage remains a gate, not a completed claim.
In-memory proof is not enough.
The architecture has explicitly tracked durable field-session evidence persistence as an engineering concern. Public positioning therefore stays at pre-production hardening rather than “live evidence vault.”
Codebase audit finding
The implementation is ahead of some repository status documents.
The current main branch is Sprint 5E, but `PROJECT_STATUS.md` and `ACTIVE_CODE_MAP.md` still describe the Sprint 4C/4D checkpoint. That is documentation drift, not evidence that the code regressed. The IZZYAKOS site now uses the current main-branch posture rather than the stale status label.
AreaCurrent evidenceRemaining gate
Economics / fairnessEconomic-mile, fairness, offer and vehicle-reality architecture exists with regression-test history.Field validation that the model produces sustainable offers for real merchants/drivers.
Identity / complianceAPI security guardrails, driver activation/consent logic and Sprint 5E lifecycle hardening exist.Provider-backed production identity and production authorization.
EvidenceField-session routes/evidence model exist.Private durable production evidence vault, retention and operational acceptance.
Money movementPlanning and terminology for reserves/protection costs exist.No live payroll, banking, paycard, insurance or regulated custody is claimed.