Aether

Every site claims resilience. This one proves it. Open devtools, delete a heading, rewrite a node, strip a class, disable the stylesheet, inject a script. Aether notices, undoes it, and seals what happened into a ledger with the node, the action, and the measured recovery time. No simulated telemetry anywhere: every number is taken in your browser, in your session, and where a browser does not expose a sensor the readout says so instead of inventing a figure.

Three organs. A MutationObserver holding integrity snapshots restores excised nodes as the original object, so listeners survive; foreign scripts and iframes are ejected against a framework-aware allowlist; an idle sweep catches what a drained mutation queue loses, including stylesheets switched off by property rather than attribute. A 4Hz sampler measures real event-loop lag and sheds load when the thread is under pressure — the white-cell field thins as it does, because the visualisation is the instrument. Every event is hash-chained with SHA-256, so editing the record in devtools makes verification name the entry where it broke. Twelve real attack vectors on a proving ground, and a page listing what the system cannot do.

It holds up to being attacked, which is the only test that counts. Testing it also broke it three times: a flood that read as a healthy thread because 200ms bursts aliased against a 250ms sampler, a smoothing filter that never seeded, and a guard that fought React and kept restoring the navigation's stale highlight. All three are fixed and all three are published on the site rather than quietly patched. The limits are published too — it cannot stop a denial-of-service attack, it cannot prevent tampering rather than undo it, and you can switch it off from the console.