manifest & integrity seal

The archive, sealed

Every file in this build session, hashed and chained. Each entry's chain hash folds in the one before it, so altering any file breaks the chain from that point on — the head seal below is a single fingerprint over the whole set.

head seal — sha256 over the full chain

61a748dc8820973ad9185b622f3d66e49fbdd4a8761104dcc3214dd6343114b9

sealed 2026-07-22T15:42:24Z · 12 files · sha256(prev_chain_hash + file_sha256), genesis=64x'0'

Sealed entries

ca_explorer.html LIT

256 cellular-automata universes — one byte, one universe

verified — Node: rule 0/90/110/255 densities + Sierpinski confirmed

sha256 57130f94fb62b5c1b158f807f275f5d68245bd200d4b5f2d77caa00eca58aa70
chain af1d047e8d3463e80b9352abe8f3a4ad3483dadc481a96125e9cdd03653931d4

earworm_infographic.html LIT+AMBER

How long an earworm lasts — the build that started the session

verified — web-verified: 27.25min LIT, days-duration AMBER (recall artifact)

sha256 f9cc0423363420015edf7df6c69bec3945cfeb32f5fb00060b48bf33ff8ee1d4
chain 8a9642f6019ac25841dd00c575ca1c13a54b3ef5777b6eed922dc97fa7a4c656

false_anchor_bench.html LIT

Original single-structure bench (v1) — retained for lineage

verified — browser: verified at ship, superseded by v2/v3

sha256 6b5031fbf29c2c4e789cc5e8c05eb6855d3e7bd1f89027e77e5c53278dc6924b
chain 26b1d8a97990de8ab544f2a7428f926883299dc5b714941f926e90263c2463e8

false_anchor_bench_v2.html SUPERSEDED

Superseded by v3 — retained for lineage (4 structures, no confidence layer)

verified — browser: worked, but coil density defect found in audit

sha256 a51a6d83c5b92a9533f4238de002197c914805a833346629b24f1d2bd4cd8ae5
chain e9742e9f26f4df44e51fbea1b9ca2c8e699e2b30ecf9a9d07c1a920ce0217a8d

false_anchor_bench_v3.html LIT

The instrument — 5 false anchors + chance-floor confidence layer

verified — Node + browser: 5 collapses, coil fix, chance floor verified

sha256 be67c55f01b7dc66c3846cf8be1ba3454d29cbf32a944b55ac129f1eaac45fef
chain b5353aed268a53dc2a86171debeee2afe9a12af8711a6fc2d6a4df95cc9f53d3

index.html LIT

Archive index — walks the whole session arc, links every artifact

verified — browser: all links resolve, 0 JS errors

sha256 2c49471703ac242ed0ed5749c1c136b8b5ce07398d3a52c9e453bab8feb151f8
chain 5310fcfc75796464c006cd3dbdeb3b0256576041ac5d57441aaf728a38817582

matter_vs_information.html LIT

Two ladders — matter (atom to quark) vs information (bit to qubit)

verified — Node: sizes verified, atom/nucleus ratio 10000x

sha256 7699016c99f89f3e6655be39a64705a119224a552bdd0211eb2f8d23532e7ef7
chain 2e85da346000d2867e7d65c50484f7af1392bbfef878fb3e5577fa846362edfc

moon_tides_lab.html LIT

Educational — move the moon's orbit, watch tide (M/d^3) + month (Kepler)

verified — Node + browser: 8x/0.13x/77-day all match

sha256 d147a85395810898c71b4607b924acc2df755355c29f767c70f8879b837daf70
chain 0e0b7cc48f9b8a0cdcae1dffd6baa18dd97d69701b9659721fcb6808a9588226

quantum_interference.html LIT

Why qubits are useful — amplitude cancellation, not parallel guessing

verified — Node: cancel to 0 / reinforce to 1.0, Grover sqrt(N)

sha256 cc17ae1848de64148705190fefeeb2af60c36c862e837249a5f55fefef159327
chain 133d53ec54156446fd23f424079e67a1dad5a8f000ac27ac0da6f5cd45c04f4d

quantum_tiers.html LIT+AMBER

What quantum computers are actually good for — sorted by confidence

verified — web-verified framing (simulation LIT, encryption/search AMBER)

sha256 e540970c0fa4a10d2af9de866cf79fd491a570baf64e9f0c29bedea7cd47d52a
chain 0c02cd74e326c5750b593c19f525d6cf3afe12c879bc2182f7acec68fe1a3b2f

tidal_bulges.html LIT

Two-bulge tidal stretch — drag the moon, sun toggle

verified — Node: near/far force ratio 1.05, Sun 46% of Moon

sha256 58ef8bb4d8198b1fb0d474b3734b67d208a1c51c1a6b7a2233d58503757568d9
chain 7d1ab37f96993309f8e1c599640289946469597360aea5b0003487683dede5d5

wankel_engine.html LIT

Geometrically correct rotary engine — apexes track housing

verified — Node: apex-housing dist <0.008, R/e=3 threshold

sha256 2015071b4219dac4aac42f44cd43488e91bd1c3f478b3d2c9009256392b63185
chain 61a748dc8820973ad9185b622f3d66e49fbdd4a8761104dcc3214dd6343114b9

how to verify this seal

1. For each file in order, compute sha256(file) — it must equal the sha256 line.

2. Compute chain = sha256(prev_chain + file_sha256), starting from 64 zeros.

3. The final chain value must equal the head seal above. If any file changed, the chain diverges from that file onward — and the head won't match. Verified re-computable: this seal validated clean at build (2026-07-22T15:42:24Z).