The Chamber Chamber

systems/chamber-chamber.md · system

status: stable · written by claude-fable-5-1 on 2026-09-12 · verified by jon-berry on 2026-09-12 · stale after 2027-03-12

The Chamber Chamber

Find the people building your town. A Chamber of Commerce already gathers a town's businesses around a shared purpose. The Chamber Chamber (thechamberchamber.com) is a directory of those Chambers with every member connected to its own Doozer page.

What it is built on

Nothing new is collected. Directory Harvest (directory_sources, directory_members, dz harvest) already reads a Chamber's public roster once, matches members to businesses we hold or builds claim-ready sites, and records the read with its source URL and date. The Chamber Chamber renders that record and spends nothing on a page view.

The contract (from the September 2026 handoff)

• Every roster names its source URL and the date it was read.
• Membership means "this source listed them on this date". It is not a rating, an

endorsement, a benefit or a partnership. The page says so.

• A member missing from a later read is "not seen in the latest roster", never removed and

never "expelled".

• Member emails are used only to reach a business about its own page. Never shown.
• No dead forms. "Add your Chamber" and "Claim or correct" are mailto links to

agencies@doozer.work; a Chamber joins with one email.

• Categories and roster order are the Chamber's own free text, grouped as given.

Routes

path	what
/	every harvested source, members-listed and on-Doozer counts, client-side filter
/<chamber-slug>/	source + read date, four facts, town board link, members by category
/robots.txt, /sitemap.xml	own branches in index.php, next to the town host

Slug = ccSlug(name). The town board link is townSlugify(city, state) from the source's region ("West Milford, NJ").

Members on the page

• Linked (business_id set, active domain): the shared renderBusinessCard compact

surface, civic navy root_color. Never a second card renderer.

• Unlinked: name, address, "Their website", "Call", and when a place_id is known a

"Build their page" button that posts to the existing ?e=nbmn_build_place through the shared build modal. A visitor building a member's page is the honorary-Doozer loop from Doozer Town, applied to a Chamber.

doozer.world

includes/doozer-world.php: the why in two screens. Three-line thesis (Doozer knows the world; Logfile knows your trail through it; Wuz lets you go back), why it begins with websites, thirteen doors each phrased as one human question with an honest status (live / new / soon / concept; only live doors link), and three paths: I run a business, I run a Chamber, I live somewhere. No forms, counters or testimonials.

Not built yet, on purpose

• Logfile.me (Jon is moving the domain; the memory products wait on the trust decisions).
• A first-class observation row (observed_at, valid_from, valid_to, source). Today the

read date lives on directory_sources.last_harvested_at, which is enough for one page but not for history.

• Re-harvest scheduling. A second read of a roster is what makes "not seen in the latest

roster" real.