Interactive · local-only · no external calls
The site is part of the argument.
Most portfolios claim engineering. This page runs it. The queue is real IndexedDB, the replay is a real second delivery, and the service worker actually caches this route. The AI pipeline is a deterministic simulation of the MediVault decision logic; nothing is sent to a model.
01 / Local-first queue
0 queuedWrite locally. Sync when the network returns.
Intake is written to IndexedDB before anything else happens. Cut the network, queue two records, then drain. The queue preserves order and replays are deduplicated by the server contract.
Opening local database…
Demo data only. The “server” is a second IndexedDB store on this device, used to model the idempotency contract. Nothing leaves your browser.
02 / AI fallback
idleFail over without failing the patient.
The extractor has two providers, two timeouts and one rule: below 90% confidence, a human reviews the field before it enters the record. Turn a provider off and run the pipeline.
Deterministic simulation. Latencies are illustrative; the decision logic and the 90% review gate match the case study.
03 / Offline shell
checkingA service worker scoped to this page.
The worker caches /lab and its static assets, then serves the page from cache when the network is gone. Its scope is the lab — not the rest of the site.
After the first visit, turn off your network and reload this page. If the lab shell appears, the cache is doing its job. Clear it any time.
/lab; the rest of the site stays out of its cache. All demo state can be cleared with the reset button or by clearing site data. No analytics, no third-party requests, no server round trip.