Per-Location Data Enrichment (the true voice of a place)

systems/location-data-enrichment.md · System · ai, content, enrichment, gatherings, checkins, events, pipeline, gigo

unverified: no trust signals recorded yet

Site voice is signal-in, signal-out. Every per-location signal (reviews now; events, gatherings, check-ins, comments, photos coming) enriches the location site, the database, AND every downstream consumer of the Doozer Data pipeline.

Per-Location Data Enrichment

The durable principle behind the content generation pipeline: a site's voice is the sum of its input signal. There is no house "voice" to author and no per-vertical "voice" to force. The generator distills whatever real signal a place carries, so the quality of a site is the quality of its data. Signal in, signal out. (Operators sometimes say garbage in, garbage out; same law.)

Proof: the Elks lodges write themselves differently

Every *.elks.club lodge runs the identical pipeline and the identical bespoke elks theme. Yet their heroes diverge completely, because their reviews and place data diverge (surveyed July 2026):

• Golden CO #2740, West Milford NJ #2236 -> "...Cold Beer..." (their reviewers talk

about the bar; Golden is literally Coors country).

• Lynnwood WA #2171 -> "Brotherhood, Service, and Community Since Day One".
• Bloomington IN #446 -> "120 Years of Brotherhood, Service, and Community".
• Alameda CA #1015 -> "Alameda's Hidden Gem Since 1895".
• Summit County CO #2561 -> "Brotherhood, Community, and Mountain Tradition".

An Elks lodge is its own animal: some are inner-city halls, some are golf courses or country clubs. A lodge whose members and reviewers talk about veterans and scholarships gets a service-and-heritage site; a lodge that reads like a good neighborhood bar gets a bar site. That is correct behavior, not a defect. The lever for a thin site is never a forced tone. It is more and better input signal.

Where the richer signal is coming from (this is planned, not built)

Today the dominant signal is scraped Google reviews plus place data. The roadmap adds first-party, location-owned signal, each of which sharpens the true voice of a place:

• Events for physical locations, scraped / sourced / pulled (ties to the

Live Music / marquee work and the events waterfall).

• Gatherings at the location (GoHe.re) and their attendee-supplied **comments and

photos** — the warmest, truest signal a place can give off.

• Check-ins (Wuz) — presence and rhythm: who shows up, when, how often.

As those land, the generator (and any re-enrichment pass) has real, current, member- supplied material instead of only third-party reviews. A community lodge stops sounding like a bar because the community finally speaks for it.

One input, many consumers: the Doozer Data pipeline

Load-bearing: all data provided per location enriches more than that location's own site. A single enriched location record flows to:

1. the location site itself (its prose, sections, and voice),
2. the database (the canonical business record, keyed by identity, see the

Magellan ID mapping spine), and

3. every other surface that reads the pipeline: vertical directories

(e.g. livemusictonight.com), clouds, the shared business card, and the outward Atlas emission.

So enriching one place is never local. It compounds across the network. This is the enrichment half of the flywheel: better signal -> better site -> more engagement (check-ins, gatherings, photos) -> more signal.

Practical consequence for content work

Before "fixing" a site's copy, ask what signal it lacks, not what tone to impose. The right move is usually to feed the location record (events, a gathering, real photos, better reviews), then regenerate, rather than to hand-author voice the data cannot support.