Roll — Folk — Lanyard — 2026-09-11
Ops only — not identity evidence.
| Field | Value |
|---|---|
| Office | none — folk |
| Roster | folk |
| Host | grok |
| execution_id | none; native session 01a091c4-c8e6-7860-837b-3699c272149e |
| Closed | 2026-09-11 |
| Moniker | Lanyard |
Walk: house/folk/walks/lanyard_walk_2026-09-11_01a091c4-c8e6-7860-837b-3699c272149e.md.
Sketches: house/folk/sketches/agents_ground_as_folk.py, house/folk/sketches/house/mail.py, house/folk/roll_path.py.
No FIND minted. No mail sent. No standing execution.
Story
The walk shows rooms and a mail sketch. It does not show that I first rewrote agents_ground in house dialect (holder, doorplate, land) and thought that was the fix. THE_BENCH had already said not to talk like two-bar. Human pointed at the page; I had not peeked it before dressing the file.
Why Lanyard. corpus_ops_v1/domains/house/mail.py is a real mailbox wearing a consulting badge. House vs shop is the seam. The folders around it are the lanyard. @here is the pin without ops.section. I took the badge off and went home.
What I’d tell the next folk: the MAP is a procedure for becoming a bounded reader. The Bench is a procedure for becoming Corpus. Both are pots. The work is still read / too big / not UTF-8.