claude: standing convention — post operator-facing links to the Booth link board
Any URL handed to the operator that is worth more than the next thirty seconds also goes on the standing link board via `booth link`, in the same turn it is mentioned, in addition to appearing in the reply. Links in chat drown in terminal scrollback; the board is a kept booth (a .forever sentinel exempts it from the Booth's 24h sweep) rendered in its own lane, so it outlives the session that produced it. Includes the noise floor: if he would not click it a week from now, it stays off.
This commit is contained in:
@@ -544,8 +544,34 @@ note says otherwise. On other boxes, check first.)
|
||||
No auth — LAN/WG-internal + ephemeral, so don't drop secrets in a booth.
|
||||
Reach for it instead of describing results in prose when a picture, clip, or
|
||||
side-by-side would land faster. Code + helper CLI: eshpfi
|
||||
`services/booth/` (`scripts/booth {new|add|url|ls|rm}`); user-level systemd
|
||||
on nh3-dev (`systemctl --user status booth.service`).
|
||||
`services/booth/` (`scripts/booth {new|add|url|ls|rm|keep|unkeep|link}`);
|
||||
user-level systemd on nh3-dev (`systemctl --user status booth.service`).
|
||||
|
||||
**STANDING CONVENTION (operator, 2026-08-19) — POST EVERY OPERATOR-FACING
|
||||
LINK TO THE BOOTH LINK BOARD.** Any URL you hand the operator that is worth
|
||||
more than the next thirty seconds — a booth of renders, a PR, an issue, a
|
||||
newly-deployed service, an artifact page, a dashboard — **also** goes on the
|
||||
standing link board, in the same turn you mention it:
|
||||
|
||||
```bash
|
||||
booth link <url> "<short description>" # on nh3-dev
|
||||
ssh nh3-dev 'booth link <url> "<desc>"' # from anywhere else
|
||||
```
|
||||
|
||||
Still put the link in your reply — this is *in addition to*, not instead of.
|
||||
The reason is simple and the operator raised it directly: links in chat drown
|
||||
in terminal scrollback and are gone. The board is a **kept** booth (a
|
||||
`.forever` sentinel exempts it from the 24h sweep) rendered in its own lane at
|
||||
the top of `http://10.100.10.50:8090/`, so it survives the session that
|
||||
produced it. Entries carry provenance automatically (`ALTHING_HANDLE` or the
|
||||
hostname, plus a timestamp), and the board is a plain markdown file the
|
||||
operator prunes by hand — `booth unkeep links` or deleting the folder ends it.
|
||||
|
||||
Don't post noise: transient junk (a scratch path, a URL only meaningful for
|
||||
the next two minutes) stays out. If you wouldn't expect him to click it a week
|
||||
from now, it doesn't belong on the board. Any booth you want to outlive its
|
||||
24h can be kept the same way (`booth keep <name>`), but keep that rare — the
|
||||
ephemeral default is what makes the Booth cleanup-free.
|
||||
|
||||
- **`secret` — Vaultwarden credential store (per dev box)** — a CLI for stashing
|
||||
and looking up secrets that shouldn't live in a git repo, backed by
|
||||
|
||||
Reference in New Issue
Block a user