Attack the Timeline

Panel 01 · Observe

What you are looking at

This is the last verified projection and its healthy frame chain. Rejected candidates never repaint this world.

Initializing…

head pending

Policy—

Credits—

Consumed—

High-water—

Trusted chain

Healthy frames

Every hand-off names the exact predecessor.

Panel 02 · Attack

Do this

Run the control, choose one attack, or launch Attack All. Each mutation is computed against the current healthy chain, and its expected boundary is named before launch.

Panel 03 · Detect

Watch for

Watch the exact verification layer change state. Green means measured and valid, red means measured and rejected, and gray is unmeasured—never a pass.

Layer	Current signal	What is computed

Panel 04 · Preserve

What this demonstrates

Accepted and rejected attempts share one audit trail: hostile bytes are quarantined while the last verified projection remains visible and unchanged.

Rejected input

Byte quarantine

The candidate is retained for inspection; it is never projected.

Executable claims

Assertions

Every layer must be measured green in the control and observed red under a challenge. Unmeasured is explicitly incomplete.

Scope

A proof of rejection boundaries, not a production trust system.

This page uses canonical JSON and the browser’s real Web Crypto SHA-256. It does not use substitute hashes.
Signatures, identities, distributed transport, persistence, consensus, and key custody are intentionally modeled—not claimed.
The synthetic high-water mark represents trusted durable state. A production system must protect that anchor independently.
Structural validity is not semantic truth. That is why semantics, causality, concurrency, and provenance are separate detectors.
A rejection preserves the last verified projection and retains the submitted bytes for audit. Nothing here silently “repairs” hostile input.

Copyable build prompt

Create one offline, dependency-free HTML laboratory named “Attack the Timeline.” Build a healthy synthetic append-only frame chain using canonical JSON and Web Crypto SHA-256. Add computed attacks for edited past payload, one-frame rehash, frame reorder, consumable-action replay, stale write, rollback, corrupt serialized bytes, older-valid-chain replacement, and forged branch provenance. Verify bytes, payload hash, frame hash, sequence, predecessor, semantics, causality, concurrency/high-water, and provenance separately. Quarantine rejected bytes, preserve the last verified projection, expose control/attack-all/guided/manual/replay/reset controls, and show assertions where unmeasured is never pass. Make it keyboard accessible, responsive at 390px, reduced-motion aware, and light/dark theme compatible.

No network, libraries, fonts, or assets.