THE FOLD / RESPAWN / SECOND WIND / THE MANIFEST
THE MANIFEST
installable is not offline
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
“The PWA manifest enables offline use after the first visit.” It does not, and the reason is not a detail. A web app manifest is a JSON file describing name, icons and display mode — it grants installability. Offline capability comes from a service worker, a script that intercepts requests and serves them from a cache it populated earlier. Without one there is no cache, so a second visit with no network has nothing to load from. The two are independent capabilities, and the claim confuses one for the other.
LIT verified live: across the exhaustive four-row table of {manifest, service worker}, every configuration loads online; a manifest with no service worker fails offline while a service worker with no manifest succeeds; so “manifest therefore offline” is false on the table while “service worker therefore offline” holds; a manifest is neither necessary nor sufficient for offline capability, with both directions failing; and a cold second visit with no network serves 100% of 42 assets from a service-worker cache against 0% without one.
LIT verified live: across the exhaustive four-row table of {manifest, service worker}, every configuration loads online; a manifest with no service worker fails offline while a service worker with no manifest succeeds; so “manifest therefore offline” is false on the table while “service worker therefore offline” holds; a manifest is neither necessary nor sufficient for offline capability, with both directions failing; and a cold second visit with no network serves 100% of 42 assets from a service-worker cache against 0% without one.
2 HOW IT WAS WEAVED · AI + HUMAN
David (human) made this the one that fails in his claim table, and its evidence line is the whole argument in a sentence: a manifest grants installability, not offline capability. without a service worker there is no cache to serve a second visit from. Seated at SECOND WIND, because that is literally the claim under test — what happens the second time you arrive.
AVAN (AI) notes the shape of the error, because it recurs far outside web apps. Two capabilities ship together often enough that the correlation gets read as an implication, and the claim then survives on co-occurrence rather than mechanism. Nothing about a manifest touches the cache; the belief was never that it did, only that projects with manifests usually also have service workers. The exhaustive table is worth the small effort here precisely because it breaks the correlation apart — four rows, and the two off-diagonal ones settle it. This page checks the capability logic; it does not test any real browser, and behaviour under a live engine is not something these predicates could establish.
AVAN (AI) notes the shape of the error, because it recurs far outside web apps. Two capabilities ship together often enough that the correlation gets read as an implication, and the claim then survives on co-occurrence rather than mechanism. Nothing about a manifest touches the cache; the belief was never that it did, only that projects with manifests usually also have service workers. The exhaustive table is worth the small effort here precisely because it breaks the correlation apart — four rows, and the two off-diagonal ones settle it. This page checks the capability logic; it does not test any real browser, and behaviour under a live engine is not something these predicates could establish.
3 ONE DIMENSION
Four rows. The two in the middle are the entire argument.
4 TWO DIMENSIONS · INTERACTIVE
Toggle each capability and try the second visit with the network off.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: two independent axes, and the corner people assume is filled.
AVAN’s addition (the inverse-companion): the forward reading is “a manifest is not a service worker.” The inverse is about how the belief formed, because nobody reasoned their way to it. Two things that usually ship together get compressed into one idea, and the compression is invisible from inside — there is no moment at which anyone decides the manifest handles caching. Read backwards, the exhaustive table is not doing logic so much as decorrelation: it manufactures the two configurations the world rarely supplies, and those are exactly the ones carrying the information. Most confused claims are like this, and they need a case that does not naturally occur to break them.
LIT across the exhaustive four-row table of {manifest, service worker}, every configuration loads online; a manifest with no service worker fails offline while a service worker with no manifest succeeds; so 'manifest therefore offline' is false on the table while 'service worker therefore offline' holds; a manifest is neither necessary nor sufficient for offline capability, with both directions failing; and a cold second visit with no network serves 100% of 42 assets from a service-worker cache against 0% without one
FIG The shape of the error recurs far outside web apps: two capabilities ship together often enough that the correlation gets read as an implication, and the claim survives on CO-OCCURRENCE rather than mechanism. The exhaustive table is worth the effort precisely because it breaks the correlation apart — the two off-diagonal rows settle it. This checks capability LOGIC; it does not test any real browser, and live-engine behaviour is not something these predicates could establish.
FIG The shape of the error recurs far outside web apps: two capabilities ship together often enough that the correlation gets read as an implication, and the claim survives on CO-OCCURRENCE rather than mechanism. The exhaustive table is worth the effort precisely because it breaks the correlation apart — the two off-diagonal rows settle it. This checks capability LOGIC; it does not test any real browser, and live-engine behaviour is not something these predicates could establish.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of SECOND WIND · David Lee Wise (ROOT0), with AVAN