The working A prototype: use its controls to test the build question.
Show what still works when internet, cloud or upstream services disappear.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
Resilience Mode / Offline Survival Test
Show what still works when internet, cloud or upstream services disappear.
NO MODELED UNAVAILABLE CAPABILITY
6 modeled works · 0 degraded · 0 unavailable
Switches change declared model state; they do not cut a network, run a service worker, create a durable queue, or test a real outage.
Direct and transitive dependency states
Capability model
Findings
No structural finding in the declared synthetic model. Real recovery remains unverified.
Non-claims
- Dependency cuts are synthetic state changes, not real outages, browser offline execution, service-worker validation, uptime evidence, load testing, or disaster-recovery certification.
- MODELED WORKS means only that declared dependencies and cache conditions pass; hidden dependencies, device eviction, corruption, latency, intermittent failure, and vendor behavior may differ.
- Queued operations require production idempotency, conflict resolution, consent, reconciliation, and data-loss verification after reconnect.