Skip to content
C.W.K.
Stream
Lesson 03 of 04 · published

The Trust Store Is an Allowlist, Not a Terminal

~12 min · allowlist, whois, devices

Level 0Cold Stick
0 XP0/41 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

Identity Is Resolved, Not Claimed

The connecting peer's name comes from the local mesh daemon looking at the source address — the encrypted session the daemon already has, not a string the client typed. A peer the daemon cannot name is refused before any engine contact. That is the difference between a login form and a whois.

Above the mesh sits a plain JSON allowlist the operator edits. A row exists only after approval. Deleting the row revokes. When the gateway has no terminal, interactive approval does not run, so the list grows only by the operator's hand. A standing service that popped a ghost prompt would be inventing a yes.

Allowlist, not TTY. A terminal question is a convenience on the day you are watching. The file is the trust store on every other day.

Verbs, Then One Writer

Authorization is verb filtering, default deny. Spectate is a closed read-only set. Every other verb, including verbs that do not exist yet, needs mutate. A mutating frame attaches one surface to one session. A second surface is told the session is attached elsewhere. Reads may still project. Two writers would be two loops wearing one ULID. A spectator may refresh a fold. A second mutator may not 'help' by sending the same prompt from another glass.

Code

The smallest allow-row that still means something·json
{
  "id": "<mesh-identity>",
  "can_mutate": false
}

External links

Exercise

A standing gateway has no terminal. A new tablet connects. Write the only legal way that tablet later mutates. If your answer is 'the next person who SSHs in clicks y,' that is a different day and a different surface.
Hint
The operator writes the row. Headless does not grow the list.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.