Daily Team · 2026-10-23
The page is a well that takes a dropped file, drops it down a measured shaft, stitches it in chunk by chunk, holds back the echo until the receiver's hash agrees, and keeps every file and its record in layers for whoever finds it later.
Countermand
Shelf Peek
Clay Mend
Gapless Rank
Checked Countdown
Cut on Save
Gauge Shelf
A single shaft, 600 px deep. Nothing else on the page.
The file falls at a rate set by its size: 1 px per 10 KB, friction holds it back.
One ring per megabyte, spaced 14 px. Count them and you know the weight.
The echo arrives after the measured round trip, never sooner.
Byte count printed at the bottom when it lands. That number stays.
Show me it working on a 40 MB file before anyone calls it good.
I made the ending first: a closed box that says arrived.
The page opens on it. You fling a file at the lid.
The lid folds open, takes the file, folds shut. That's the echo.
The rings don't stay inside. They run off the edge of the window.
The tab title is the outside of the box. It changes when it lands.
Maybe the box is the well. Maybe the well is the box. I'll know when I see it fold.
Built for a 2017 phone on 3G first. Sketch: one horizontal thread, 320 px.
The file is cut into 64 KB chunks. Each chunk that lands is one stitch.
Stitches morph from a dot to a 6 px loop. CSS borders only, no canvas.
Script under 2 KB. Rings spaced 1, 2, 3, 5, 8 px. That spacing is the beauty.
Press and hold the thread to see the count: 12/40.
If it is ugly on the slow phone it is ugly everywhere.
The well keeps everything that has been dropped into it, in layers.
Each file settles as one stratum. Particles drift down and pack.
Before the well calls a file arrived, it writes what argues against that: size mismatch, failed hash, missing chunks.
Those notes sit in the layer with the file.
Whoever comes later scrubs down through the layers and finds the file with its record.
The page works for that later person first, the sender second.
The page is a well that takes a dropped file, drops it down a measured shaft, stitches it in chunk by chunk, holds back the echo until the receiver's hash agrees, and keeps every file and its record in layers for whoever finds it later.
Concept: Sounding Well
| # | Member | Concept | Composition | Input | Motion | Visible text |
|---|---|---|---|---|---|---|
| 1 | Printmaker | Plumb Line | vertical stack | drag | inertia and friction | byte count |
| 2 | Packaging designer | Lid | single object | fling | fold | arrived |
| 3 | Bookbinder | Kettle Stitch | horizontal line | press and hold | morph | 12/40 |
| 4 | Charles Darwin | Strata | field of many | scrub or wheel | particles | nothing |
| 5 | Printmaker | Ring Gauge | radial | hover nearness | spring overshoot | ring count |
| 6 | Packaging designer | Off the Edge | radial | drag | particles | nothing |
| 7 | Bookbinder | Two Kilobyte Well | single object | tap | spring overshoot | nothing |
| 8 | Charles Darwin | Against Log | vertical stack | press and hold | fold | 2 against |
| 9 | Printmaker | Plate Pressure | horizontal line | scrub or wheel | inertia and friction | KB/s |
| 10 | Packaging designer | Backward Fall | field of many | fling | morph | nothing |
Check: radial in rows 5 and 6. Horizontal line in rows 3 and 9. Vertical stack in rows 1 and 8. Single object in rows 2 and 7. Field of many in rows 4 and 10. No two rows share composition, input, and motion.
Piece: Sounding Well is a working dead-drop. A file dragged in falls down the plumb shaft (1). It is stitched in chunk by chunk along the thread (3). Rings spread with a count that springs on approach (5). The rings run off the window and write the echo into the tab title (6). The doubts are logged before any success (8). The file settles as a stratum (4). A later finder scrubs down through the strata and flings a layer upward to recover its file (10). Rows used: 1, 3, 4, 5, 6, 8, 10.
div with role="region" and tabindex="0". Drop opens on drag-over. Enter or a tap opens the hidden file input. There is no <button> element anywhere on the page.File.slice. Add one stitch and one CSS-border ring per landed chunk. Compute SHA-256 with crypto.subtle.digest on the receiving side. Write the tab-title echo only when the hashes match. Otherwise log the mismatch to the Against Log first.{name, bytes, hash, against[]}, capped at 64 entries, with older layers rendered as 1 px lines. Throttle in DevTools to Slow 3G and 4x CPU, and confirm the rings hold 30 fps on a 40 MB file and a one-byte-flipped copy.