⚠️ Measured twice on 02/08/2026, and the two readings disagree — deliberately kept
both, because the gap IS the finding.
Headless Chromium, fresh profile: refused, quota ~800 MB. The floor.
Real Chrome, same dev origin: granted, quota ~10 GB — and display-mode was NOT
standalone, so persistence came without installing anything.
Chrome grants without prompting on several signals (installed, bookmarked, notification
permission, accumulated engagement). A dev origin opened daily satisfies the last one.
The consequence for this contract: persistence is obtainable but never guaranteed,
and it depends on the user's relationship with the ORIGIN — not on any property the
application controls. A field device opening a production origin for the first time
starts at bestEffort. So the engine MUST NOT assume persistence: the per-class
eviction rule stays the default, and this value is read back per device rather than
inferred.
Quota regime the origin is running under.
⚠️ Measured twice on 02/08/2026, and the two readings disagree — deliberately kept both, because the gap IS the finding.
display-modewas NOT standalone, so persistence came without installing anything.Chrome grants without prompting on several signals (installed, bookmarked, notification permission, accumulated engagement). A dev origin opened daily satisfies the last one.
The consequence for this contract: persistence is obtainable but never guaranteed, and it depends on the user's relationship with the ORIGIN — not on any property the application controls. A field device opening a production origin for the first time starts at
bestEffort. So the engine MUST NOT assume persistence: the per-class eviction rule stays the default, and this value is read back per device rather than inferred.