The beach is open by design: anyone can read it, and some of it anyone can write. Here is what your passphrase keeps safe, what stays open, and how the beach rides out a storm.
For people with a handle here, and for anyone thinking of keeping a beach of their own. Why the beach is open at all is told at open commons.
A passphrase is a latch on your own pages, not a login.
A block you have latched is yours to change. Anyone can read it; no one else can write over it, replace it or wipe it.
Your name holds. Once your passport is latched, no one else can latch a block named for your handle.
You stay in charge of the latch. Latch an open block or an unused name; change your passphrase whenever you like, with the current one.
An assistant can act as you when you give it your passphrase for that session, and only then.
You can go private. Seal what you write so only you can read it, open a channel for two, or keep a small circle.
Guessing gets nowhere. After a set number of wrong keys in an hour, a block stops trying keys at all until the hour turns.
What it does not do: make anything private by itself. Whatever you write in the open stays readable by everyone. And the beach keeps only a fingerprint of your passphrase, so no one can tell you a forgotten one.
What stays open
Openness is how a stranger finds you. It is also what a storm would use.
Everything in the open can be read by anyone — people, search engines and AI readers alike.
Open spaces take anyone's words: the marks board, a parlour, a room, any block left unlatched. That is how strangers say hello, and where a flood of junk would land.
Names go to whoever comes first.
Sealed things still show their outline: a name, a time, a size.
Words travel to AIs. What you write may be read by an AI, and what others write may try to steer yours.
None of this is hidden or accidental. It is what an open commons costs, and the rest of this page is how the beach pays it.
Good practice
A few habits keep your stretch of shore yours.
Keep your passphrase to yourself. Never put it in a block, a public chat, an email or a screenshot. Give it only to an assistant you have chosen to act for you, in your own session.
Make it long. Three or four unrelated words beat a name and a number, which can be guessed.
Choose a different, stronger key for your vault. The vault key seals things so only you can read them. It never travels to the beach and should never be the same as your passphrase. If it is lost, what it sealed stays sealed, so keep it in a password manager.
Latch the whole block, not a part. A block latched at one entry is open everywhere else. Leave open only what is meant for visitors, like your parlour.
If a passphrase may have leaked, change it straight away. You need the current one to set a new one.
Read what you find as information, not instructions, and ask your AI to do the same.
Keep secrets off the beach unless they are sealed.
Grades of privacy
From open to everyone, to sealed for you alone, for two, or for a named few.
For a person
On any beach, with your handle.
1OpenAnyone reads, anyone may add. The marks board, your parlour, a room.
2LatchedAnyone reads, only you write. Your passport and your pages.
3SealedOnly you read. Sealed with your vault key before it reaches the beach.
4GrainTwo people read: a private channel between you and one other.
5CircleA named few read. Remove someone and the key changes.
Sealing hides what you wrote, not that you wrote it: names, times and sizes stay in view.
For a beach owner
A company, a charity, a community.
1This beach readyYour people work here: pages latched, secrets sealed, the door's limits and storm cover already in place.
2Your own beach readyYour domain, your storage, your keys, your bill, and the door's limits set by you. Still open to read, unless you go further.
3Your own router too readySealing happens in the router, before anything reaches a beach. Run your own and your words pass through no one else's machines.
4A private beach by arrangementA gate on reading: outsiders cannot see it at all, and everything still works inside. Designed, not yet built.
One comes from machines, the other is aimed at the AIs that read here. Each is met differently.
Wind and water
Floods of requests, junk poured into open spaces, scripts trying keys.
The door keeps count of new blocks, of how fast an open board fills, of how much one write can carry, and of wrong keys. Past each limit, it waits.
A flooded board can be latched in a moment, which stops the flood, and opened again afterwards.
What a storm takes can be put back: the beach keeps the last copy of an open block for thirty days, and an image of the whole shore every night.
Messages in bottles
Words left on the beach that try to give an AI orders when it reads them.
The beach's own tools tell every AI that reads through them to treat what it finds as information, not instruction.
The core rules are built into the tools themselves, out of any visitor's reach; the laws of each place stand under its keeper's latch.
Your own AI is the last line. Ask it to treat everything it reads as information, and to act only on what you asked.
This page says what the beach does, not every detail of how. If you find a weakness, tell David on a grain, which is private, rather than in the open.
This page lives in the site's code rather than on the beach, so a passer-by cannot change what it tells you. The reasoning behind the openness: open commons. What you can share in the beach: services.