The Doozer Brain

index.md · Index · okf, brain, index

unverified: no trust signals recorded yet

Doozer's complete knowledge in Open Knowledge Format — the idea, direction, systems, processes, value, and vocabulary behind the entire platform.

The Doozer Brain

This is Doozer's knowledge in Open Knowledge Format (OKF): plain markdown files with YAML frontmatter, linked to each other to form a knowledge graph. It is the durable "brain" behind the platform, and it is meant to be self-contained: an AI (or a person) reading this bundle should come away understanding the whole Doozer world — the idea, the direction, the processes, and the value. It is additive to MEMORY.md (fast recall) and CLAUDE.md (project instructions); see how to grow this brain.

Just upgraded to a new model? Read NOTES-FOR-NEWEST-MODEL.md (repo root) first — the living handoff letter from the previous model — then follow the reading order below. See The model handoff for the tradition.

New session? Read Start here — working with Jon first — the portable working agreement: how we work, the house style, keeping a brain, the admin skeleton, the dev channel, and the stack that's only a key away. (A verbatim portable copy is at docs/start-here-working-with-jon.md.)

Start here (read in this order)

1. The Mission — why Doozer exists + the non-negotiable

quality bar (trusted / working / accurate / tasteful / useful / good). One loop — the Oct 2026 north star: how every doozer property fits one loop for people (find, go, be there, keep, come back) and one for owners, the order of work, and the guardrails. Read before adding a property, a surface or a money idea.

2. The One Page — **Oct 2026 pivot, read before any page

work:** one uniform, source-cited App Page per business instead of generated look-alike websites; the search → check-in → memory loop; owner-built official sites. Alice — the concierge on The One: one pill that says exactly what her next tap does, predicts the next place from the question, the moment, people's own moves and good sense. Common knowledge — source C: the public record (Wikidata, Wikipedia) and what a kind of place means, at an explicit level (this place / its brand / its kind). Happenings — happy hours, nights out, specials and offers, kept only as verbatim, dated quotes from the place's own website; feeds Town "What's on" and doozer.deals. doozer.deals — the Oct 2026 plan: six kinds of deal (happenings, tickets and experiences, owner deals, the Local Loop, plans, gift cards and online), local first and online honest, commission never in the ranking. The Doozer App — the Oct 2026 kick-off: one native app for the whole ecosystem (find, arrive, keep a Wuz, relive, commerce), LeadBuilder as the data spine. Doozer API v1 — the app's one door (doozer.work/api/v1, live v2.2.666): every route wraps what the web calls, the web's JWT as a bearer, the route map. Visit kind — is it a place people go to? go / comes / office / other plus an interest, per business, from one $0 rule; feeds the app's Nearby (places/near?visit=go). The Wuz — a memory with the place attached: how a check-in becomes one, companions who both agreed, four privacy levels, where you have been kept on the device only. App design — the app's tokens and components, from the Doozer family and The One, for iOS and Android; three contrast findings that also apply to the web. Doozer Games and Doozer Shop — the Oct 2026 plan: games played together inside a place (TV + phones), and buying local (gift cards first). Town Trivia and the Doozer Games menu — the second game, true facts about real places only (Google types confirm kinds), and the TV menu that moves a room between games. Winner stays: Four in a Row and Reversi — the 1-on-1 games and the reusable rule under them: champion, challenger, a line, rematch; a new one is its rules and board. Doozer Games rooms and relay — phones as touchpads: the room code, the TV-authoritative protocol, the interim relay, the Cloudflare Worker, and why it answers 200. The Doozer Story — the origin and the idea. Who built Doozer, and why — Jon Berry, who he is, what he built across the network down to Wuz, and why.

3. The Architecture — one index.php serving unlimited

sites; what a Doozer site actually IS.

4. The Network — every product in the ecosystem and how

they interconnect (the breadth).

5. The Value Model — how value is created and

captured (the economics).

6. The Flywheel — how it all compounds.
7. Doozer vs Doozer+ — the free/paid direction.
8. The Observed World — render-on-demand: every

local business exists once observed, and each materialized site is both inventory and a pre-built lead (the self-funding flywheel).

Organization

• craft/ — the clever parts: the non-obvious details that make

Doozer different, where the interesting thing is the WHY. Category-aware call intent, the hostile CSS environment, skeleton first, index later, self-healing email backfill, price the pull before you pull, fix the source, not the symptom, inline the bytes, not the proxy URL, cross-root identity, derive the URL, don't store it, the logo knows its own shape, the distraction problem, decision vs delivery. A growing genre.

• systems/ — how things work:

Architecture, The Network, NearByMeNow, Network Growth ("More places nearby"), Clouds, Directory multi-view framework, what a directory page costs, Muse System, Design Standards, The Brand System (ecosystem identity kit), content generation pipeline, Best AI for the Job (value-aware model selection), Fact-Guard, per-location data enrichment, Weather Widget, Live Composition (the page reorders for the moment, order only), Jev (the fast decider), The Menu Finder (go get the menu, stage it for review), shared business card, section framework, Lead Capture, LeadBuilder, billing, Money Clouds (affiliate), Prospector, Marketing, Shortlinks + QR (doozer.link), The Growth Engine — the acquisition + monetization map, AI Postcards (Factory + Theme Studio + campaigns), Thanks.io connector (direct mail, two-way), Promo Codes + the one-time claim offer, Hot Leads — internal Doozer-sales CRM, Machi (the marketing brain), Event Feeds (Marquee + the multi-source plan), IndexNow (instant Bing crawl), AI Discoverability (llms.txt + AI-crawler welcome), Admin Tool Inventory (audit + cockpit), Doozer Digest, Email Open Tracking, Identity + Auth, Doozer Comms (Telegram), Regeneration + Foundation, Atlas (outward AI), Gatherings + Social, Live Music Tonight, Niche Color System, Enrichment Store Links, per-user hotspots, Postcards, cloud headers, hosting infrastructure, Admin Health Tools, Dev API + Site Quality Score, free-tier render gotchas, the 521 root cause, shortlinks and QR (doozer.link), source-of-truth cache, postcard targeting, context-city poisoning, and the flywheel.

• processes/ — how we do things: site creation,

content generation and healing, deployment, the model handoff, spotcheck.

• decisions/ — load-bearing calls: the mission,

the value model, Doozer vs Doozer+, the observed world, implicit verification, no dark patterns, icon taste rule, Magellan ID mapping, the SEO cliff and recovery, the Doozer story, OKF adoption.

• glossary/ — the vocabulary: Muse, Cloud,

Family, Niche.

The live network (businesses, niches, clouds, families) is emitted as OKF nodes on demand by includes/okf-engine.php, browsed in Admin → Doozer Brain, and projected outward per-entity as the Atlas. The whole bundle exports as one portable .zip (Admin → Doozer Brain → Export). No secrets live in the brain by design.

• Magellan and the feed pond — bound external IDs (business_id_map) + the gcal and member-registry adapters that make sites living entities.
• Niche matching and live discovery — a niche page matches OUR tag OR Google's types; a niche slug is NOT a place type; the thing you asked for is never junk.
• Two gates, and the category catalog — directory visibility vs index eligibility; the promotion step that was never written; dz nichecatalog.
• The photo pipeline — references are free, bytes are bought once on first view; the cache key is md5(name + w/h) so WIDTH is part of it, and any page can ask "do we already own this?" before spending. dz imgct.
• The Muse v2 layer — the v2 render layer never applied to ANY site (token array passed where a muse row was expected); a muse is only as good as its brief. dz muse do=tokens.
• Events to machines — a live event is only half published until a machine can read it; the schema.org Event pipeline + the timezone rule.
• The Doozer Score — Stick (cost per 100 sites), Tower (value per 100), and the leverage between them.
• The writer model is chosen on accuracy — gpt-5.4-mini, decided by an 11-niche bake-off after the pricier model fabricated a fact.
• The /now surface — one button, the nearest places, Build-it-on-the-spot; plus the measured teardown of the category page.
• Doozer Town and the Board Game view — self-building town clouds on doozer.town (slug = the instruction, $0 from inventory, one gated geocode otherwise), ten colour groups, any cloud as a property board.
• The Chamber Chamber and doozer.world — thechamberchamber.com is Directory Harvest's public face (roster read once, dated, sourced; members connected to their Doozer pages; emails never shown); doozer.world is the two-screen front door with thirteen honestly-labelled doors.