FROM FEASIBLE DELIVERY TO ACCESS AND RECOVERY
What changes the gap?
Keep the target visible. Wait for improvements to activate.
Recover from a verified checkpoint—without resetting the cold-chain clock.
Audited saved demonstrations from the original Python engine. All acceptance records, positions, resources, project effects and costs here are synthetic assumptions. These examples are separate from the three location cohorts; do not add their beneficiaries.
Loading the bound capability catalog…
WHAT THIS WEBSITE DOES AND DOES NOT DEMONSTRATE
Read the coverage with the result.
| Capability | Website coverage | Boundary |
|---|---|---|
| Daily delivery & pre-dispatch replanning | Saved three-case comparisons + original Python custom-demand computation | Known-before-dispatch conditions; bounded finite search |
| Travel targets & temporary exceptions | Explicit policy, expiry, quota, target attainment and failure examples | Acceptance evidence is synthetic, not field consent |
| Phased outreach / road investment | Four fixed portfolios, three conditions, three operating windows; additional full-failure boundary | Disjoint supplied tasks and stocks; no continuous six-month material flow or lifecycle optimum |
| In-transit recovery | Event checkpoints, transfer/detour, detection delays, original clock, missing evidence and failed resources | Finite sealed-cargo rescue; no live GPS, automatic quality release or partial opened-cargo transfer |
| Simple-rule benchmark | Fixed plan / deterministic road adaptation / V2.7 across saved reference conditions | Same inputs and original audits; not a human dispatcher comparison |
| Operational quality, clinical eligibility and field deployment | Formal input gate and limits are disclosed | Not field validated. Clinical due lists are provider inputs, not inferred from population totals |
| Every possible disruption or global optimality | Search scope and incomplete searches remain visible | No universal recovery guarantee or exhaustive capability claim |
Module data and each downloadable calculation carry SHA-256 bindings to their input, output and unchanged engine-source inventory. These checks establish consistency, not authenticity of field evidence.