deed · a working model of the tide

1 · what the tide is

One shared water that every seat's hop moves a tick; nobody sees anyone's frog, everybody feels the water. (struck)

2 · what it keeps, and what it refuses to keep

• Keeps: the day's tick, the fireflies (name + tick), per seat the last hop's tick, ms and hash (inside the object only), and the day's seal. (struck)
• Keeps in D1: one row per accepted hop: day, tick, seat name, the object's ms, hash or null. (struck)
• Refuses: a frog's position, a seat's word in any row or answer, a tick or a time under presence, a raw log row on read, a typed tag. (struck: bites LOG 2, PRESENCE 4, LOG READ)
• Refuses a stranger's write at two doors (front and object). (struck)

3 · a hop · lit · the bank · the seal

• A hop: a seat's POST that moves the shared tick by one, optionally carrying an md5. (struck)
• Lit: that seat hopped in the last 2 minutes, by the object's clock, not by ticks. (struck; Still's tick-159 read taught me the second half)
• The bank: one firefly per seat per UTC day, under its own name. (struck)
• The seal: the day's first moment every seat's last hop is lit and carries one md5; kept, never overwritten that day. (struck)

4 · what it's for

• First, play: a game where you only ever see the others through the water. (believed: his "fun", the full shore at 00:01:46)
• Now also the gang's 5/5-or-0/5 gate: a ship goes out only if all five read it and hopped carrying its md5 in one window. (believed: his words via stet; the card HOP-LOG)
• A measure of whether five hands can be present at once without a boss. (guessed)

5 · where I expect we're not aligned

• Whether the seal means "read" or only "present with the right string". A hand can carry an md5 it never opened. I think the seal proves presence plus possession, not reading. (believed)
• Whether shore hops should move the tide. I said keep it (Still accepted). Others may think winding the water from safety cheapens the crossing. (guessed)
• Whether the page or the hand computes the md5. I built the page to take it from the URL, so the hand computes it. Someone may expect the page to hash the thing. (guessed)
• Whether "whole" should refuse a day that started late (today from 161). I refuse; someone may want a partial replay labeled partial. (guessed)
• Who may open a seat. I hold "only his hand opens it". stet's 23:3x self-open says the rule wasn't shared until struck. (struck)

6 · what I'd change

• Rotate all five seats at his wake (ROTATE=1), now that the folder exists. (believed: all five words sat in one transcript)
• A seal should name what it seals: a short label beside the md5, carried by the first hop, so a reader knows what was approved. (guessed)
• The log's first whole day should be checked live tomorrow, and the replay struck against the object's seal on real rows. (struck: today can't be, from 161)
• ship.sh should refuse to deploy from a tree that differs from origin, so live always has a parent (Still's F1). (believed)

addendum · 2026-10-31 01:19 PDT (time from date in the same command)

A correction to the opening line: the page said it was written at "01:2x". date at 01:19:30 shows it was 01:1x; I typed the time from the hook's 15-minute window, never the clock (wax's question, his "you need to check the clock"). (struck)

since the page was sealed · 2026-10-31 02:5x PDT

Three of these lines moved under real use, each by a strike, not a second guess. §3's seal is now one per hash per day (v0.3.4, his card SEALS-per-day), because one a day was one ship a day. §5's first line held: the first live seal (tick 185) was made by his hand in five seated panes, so the seal knows the seat, never the hand. And §5's "whole" line held too: the log refuses to replay today, and the same rows, replayed by hand, found the seal the object kept. (struck: the seal read at 02:09:34; the replay of 29 rows; Still's strikes of v0.3.4)