Platform concept

A decision and memory layer—not another driver application.

Deliverd is designed to sit beside the tools an operation already uses. Drivers should not be asked to learn another application, and platforms should not be asked to hand over their workflow.

Conceptual interfaces

Conceptual API

The example below is illustrative only. No real address, API key or live endpoint is shown.

Conceptual interface · not currently a production API

• dispatch_decision
• principal_issue
• required_checks
• vehicle_suitability
• crew_requirement
• handling_equipment
• memory_available
• evidence_state
• unresolved_conflicts
• recipient_confirmation_required

GET /v1/locations/{authorised-location-id}/delivery-memory

{
  "location_id": "authorised-location-reference",
  "access_point": {
    "description": "Second gate after the stone wall",
    "coordinates": "ordinary latitude and longitude"
  },
  "handover_point": "Blue workshop door beside Unit 4",
  "vehicle_constraints": {
    "medium_van": "access confirmed",
    "larger_vehicle": "restricted turning space",
    "state": "unresolved_conflict"
  },
  "evidence": [
    { "type": "photograph", "subject": "entrance", "supplied_by": "recipient" }
  ],
  "provenance": [
    { "date": "12 July", "actor": "recipient", "action": "supplied" },
    { "date": "18 July", "actor": "driver", "action": "confirmed" }
  ],
  "last_confirmed_at": "18 days ago",
  "expires_at": "04 February",
  "permission_scope": "authorised_future_deliveries",
  "unresolved_conflicts": ["vehicle_turning_space"]
}

Conceptual interface · not currently a production API.

One product, four layers

Deliverd decides whether the job is realistically achievable—not merely whether the route exists.

Mission feasibility outputs

Conceptual interface · no production API currently offered

• mission_feasibility
• direct_drive_time
• collection_operational_time
• charging_required
• preferred_charging_stop
• alternative_charging_stop
• charger_fit_state
• charger_status_state
• occupancy_evidence_state
• charging_minutes_required
• planned_break_minutes
• overlapping_minutes
• effective_charging_delay
• realistic_arrival_window
• disrupted_arrival_window
• expected_delivery_charge
• expected_return_charge
• required_reserve
• principal_uncertainty
• required_action

Deliverd does not calculate statutory driving-hours compliance. A user-entered planned break is a planning input only, never a compliance determination.

Operational stop evidence

Where a mission may require charging, Deliverd assesses whether the stop is usable by the described vehicle rather than whether a charger exists. ChargeWise CX is a specialist evidence source inside Deliverd — not a separate product or consumer charging application.

• charging_stop_decision
• bay_length_fit
• cable_reach_state
• current_status_source

Third-party location systems

Delivery Memory would store ordinary geographic coordinates as the underlying location. Human-readable systems such as three-word references could be displayed optionally where appropriately licensed and supported. No partnership or endorsement is implied.

The prospective moat

The software interface can be reproduced. The difficult asset is an authorised history of what was expected, who confirmed it, what happened during the delivery and whether the information remained useful.

Deliverd does not yet claim a proprietary location dataset. The proposed pilot exists to determine whether a governed evidence network can be created responsibly and whether it produces measurable operational value.

Mapping and fleet platform teams: platform integration concept · commercial model