HOW TO READ THIS BOARD

Same 395 audited records as the card view, one row each, nothing added.

Dates, venues, attendance ranges, travel class, after-hours read and public-access notes are copied straight from data/events.json. The A–D badge after each name is the evidence grade — D rows are directory-only leads nobody has confirmed. Open any row (▾) for the crowd mix, access rules and the audit notes behind it.

“Curb Appeal” and “Brain Trust” — the joke columns, in full

These two are not data. They are a fixed stereotype about professions, applied by keyword to every row, and they say nothing whatsoever about any individual attendee. Curb Appeal is a grooming-and-dress-code gag (a dermatology conference would score 5; an asphalt trade show scores 1). Brain Trust is a hand-assigned stand-in for how a field's entrance exams tend to rank — invented by hand, not sourced from any score table.

The rubric lives in site/tools/build-table-extras.py and is baked into data/table-extras.json, so every score is reproducible: each event is matched against an ordered list of keyword rules over its title, category, professional mix and tags; the first rule that matches picks the field, and the field picks both numbers.

Saved events live in this browser only (localStorage, key downtownCrowd.interested.v1) — no account, no server, no expiry date, so they survive restarts indefinitely. It is one shared set: ticking a row here and swiping right in swipe mode add to the same list, and the CSV export reads from it. Caveat worth knowing: Safari's storage policy can evict site data after roughly seven days without a visit, so a tick list you want to keep for a year is safest exported to CSV. Filters, sort and theme are remembered the same way.

Export CSV writes the saved events with every column. With nothing saved it writes whatever the current filters leave on screen instead.

build — · rubric —