Organism onlineSession —0 nodes guarded0 events sealed

Most sites decay. This one heals.

Every site claims resilience. This one proves it while you watch. Open devtools, delete that heading, rewrite it, strip its classes — Aether notices, puts it back, and writes what happened to a ledger you can verify yourself.

No simulated telemetry. Every number on this site is a measurement taken in your browser, in this session. Where a browser does not expose a sensor, the readout says so instead of inventing a figure.

Attack it →What it cannot do

Try it here

This paragraph is a protected node. Delete it and it comes back.

Nothing has happened yet

Prefer to do it yourself? Open devtools, find this paragraph in the elements panel, and press delete. Same result — the button is a convenience, not the mechanism.

The anatomy

Three systems, one organism. Each one is a named browser API doing exactly what the name claims.

Sense

The nervous system

A 4Hz sampler measures event-loop lag — the overshoot between when a timer was asked to fire and when it actually did. A PerformanceObserver counts long tasks. One shared animation frame reports cadence. Nothing polls in a loop, and nothing runs while the tab is hidden.

performance.now() · PerformanceObserver · requestAnimationFrame

Repair

The white blood cells

A MutationObserver holds integrity snapshots of protected nodes. Remove one and the original object is re-inserted at its recorded position — listeners and all — with the repair timed. Foreign scripts and frames are ejected. Every reflex runs behind a circuit breaker, so healing cannot become an infinite loop.

MutationObserver · integrity snapshots · circuit breakers

Remember

The immune memory

Every detection and repair is sealed into a hash chain. Each entry carries the digest of the one before it, so altering any record invalidates every record after it. Edit one in devtools and press Verify — it will name the sequence number where the chain broke.

crypto.subtle · SHA-256 · sessionStorage

How it heals

  1. 01SenseLag, long tasks, frame cadence, asset failures, uncaught exceptions. Sampling happens on a timer, integrity checks on the idle callback.
  2. 02DiagnoseA mutation record is classified by what changed: a node left the document, text was rewritten, an attribute was altered, or something executable arrived that was not there at boot.
  3. 03RemediateThe matching reflex fires. Restore from snapshot, eject the foreign body, re-fetch with the cache bypassed, or shed load. The breaker caps every one of them.
  4. 04RememberThe event is hashed into the ledger with its target, its outcome, and its measured recovery time. Nothing is sent anywhere. There is no server.

You are inside it

This is not a case study about a system. The immune system is watching this exact page as you read it.

The badge in the bottom-left corner is its pulse — the number beside it is your session’s live event-loop lag, updated four times a second. The cells drifting behind this text converge on real damage when it happens. Everything the organism senses and repairs is written to the ledger, and the full instrument panel is at vitals.