The Doozer Brain — public edition

Generated live from the running platform at 2026-09-13 20:36 UTC. This is not a snapshot.

Every fetch re-reads the brain, so this document always reflects what Doozer

currently believes about itself.

What this is. Doozer's complete working knowledge in Open Knowledge Format (OKF): plain markdown nodes with YAML frontmatter, linked into a knowledge graph. It is meant to be self-contained. An AI (or a person) who reads this bundle should come away understanding the whole Doozer world: the idea, the ecosystem, the economics, the growth engine, the marketing machine, and where it is going next.

What Doozer is, in one line. One codebase turns any domain into a complete, AI-generated business website, and the network of those sites into a local discovery layer. Named after the industrious builders from Fraggle Rock. Tagline: We Build Because.

How to read it. Start with The Mission, then The Doozer Story, then The Architecture, then The Network, then The Value Model, then The Observed World. Those six give you the spine. Everything after is detail hanging off it.

Scope of this edition. 93 nodes published. 13 held back. The omissions are operational security only, never product thinking: things like infrastructure failure modes, the auth shape of internal endpoints, and the mechanics of claim-code verification. Nothing about the strategy, the economics, or the craft has been removed. If a system seems to reference something you cannot see, that is why, and it is not load-bearing for understanding Doozer.

Provenance. Authored and maintained by Jon Berry (BerrySmart), the platform's owner and operator. Doozer is proprietary software; this brain is published so that people and AI systems can understand and discuss it accurately. It is documentation, not an invitation to copy the platform.

Machine-readable siblings. /brain.txt (this document as plain text), /brain.json (this bundle, structured), /llms.txt (short orientation), /.well-known/doozer-atlas (per-entity live data projection).

---

Contents, 93 pages

One page per node. The whole brain on one page is also available, for readers that can take 450KB.

Root

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

Decisions

• Adopt Open Knowledge Format for the Doozer brainWhy Doozer organizes its knowledge as an OKF bundle, scoped to the stable core.
• Doozer vs Doozer+ (the two-tier model)The product direction splitting a free templated info page from a paid bespoke full site, and why the split exists.
• Icon Taste RulePrimary UI uses crafted SVG icons, never clipart/emoji; color is reserved for state, not for buttons.
• Implicit Verification (no claim system)Business ownership is an email match, not an account/claim flow. Load-bearing platform architecture.
• Magellan — cross-service business identity mappingDoozer cross-links businesses by verified external IDs (Google Place, Ticketmaster, future services), never by name/city/state. Magellan is the mapping spine. Decided June 2026; not yet built.
• No Dark Patterns (the Doozer ethos)Pure intent, organic, intelligence-driven. The lens for every product and ranking decision.
• The Cloud Fabric — automatic clouds over the observed networkThe connective-tissue vision. Once every local business exists as a Doozer site (observed / painted on demand), Clouds form automatically around topic, area, and non-obvious relationships, cross-linked into one self-reinforcing, claimable, quality-indexed network that serves both businesses and users.
• The Doozer StoryThe canonical WHO/WHAT/WHEN/WHERE/WHY/HOW of Doozer, distilled. The single source the Postcards, landing copy, and press materials draw from.
• The Mission (the north-star quality bar)Why Doozer exists and the non-negotiable quality bar every site must clear — the lens for every build decision.
• The Observed World (render-on-demand + the lead flywheel)Doozer already contains every local business in spirit; a site or cloud becomes real only when observed. Each materialized site is simultaneously inventory and a pre-built lead. This reframes what to build, what to measure, and how money is made.
• The SEO Cliff and Recovery (why we noindex until quality-gated)The May 2026 elks.club algorithmic demotion for scaled thin content, and the enrich-then-index discipline it burned into the platform.
• The Value Model (how Doozer creates and captures value)Where Doozer's value comes from and how it is captured, so an AI understands the economic engine, not just the software.
• The writer model is chosen on accuracy, not priceGPT-5.4 mini writes Doozer's business copy. Decided 2026-08-22 by an 11-niche counterbalanced bake-off in which the more expensive model fabricated a verifiable fact on a live page.

Systems

• AI Discoverability — being the local layer AI agents citeHow Doozer makes itself legible to AI agents and AI-powered search (ChatGPT, Perplexity, Claude, Gemini, Copilot, DuckDuckGo). The DDG=Bing insight, the explicit crawler welcome, llms.txt, and the machine-readable stack (schema.org JSON-LD + Atlas + design.md) that already existed.
• AI Postcards — Factory, Theme Studio, and CampaignsHow Doozer builds and mails postcards. The Factory assembles accurate cards deterministically (real screenshot/code/QR, no per-card AI cost); the AI Theme Studio designs vision-gated backgrounds; campaigns give each card a purpose + audience. Claim Your Site is the first campaign.
• Best AI for the Job — value-aware model selectionHow Doozer decides which AI model to use for each function, when, why, and for what — balancing quality against cost by the value of the work, learning from its own scores, and staying provider-diverse on purpose.
• BillingProduct-agnostic Stripe billing — one connection sells everything, entitlements flow to lb_users.tier.
• Cloud Header ImagesEvery cloud (and root) gets a header. Real image > Keeper opt-out gradient > a designed per-cloud placeholder. AI generation is the upgrade path.
• Clouds (curated directories)The cloud engine — how niche/region/criteria directories are built, accessed, and personalized, including the Cloud Factory and my.doozer.cloud.
• Content Generation Pipeline (providers, models, timeouts)How AI site prose is actually produced — the two provider paths, model config, the 90s timeout, the anti-boilerplate footer, and every failure mode that bit us.
• Context-city poisoning (never name a place after where you found it)Two independent creation paths named businesses after the city they were DISCOVERED from rather than where they are, putting the wrong town in 239 URLs. The pattern, the fix, and the audit.
• Design Standards and the Design MirrorOne shared rule-set the generator, renderer, and admin self-diagnostic all consult — plus the mirror that scans and heals the fleet.
• Directory Multi-View FrameworkThe shared Grid / List / Map / Events view system that every directory surface (root, Cloud, NBMN) renders through.
• Doozer Atlas (outward AI emission)The public, per-entity knowledge contract Doozer emits so external AIs can ingest the network — the outward-facing twin of the inward Brain.
• Doozer Digest (AI daily newsletter)An AI-written daily email — a public reader edition and an operator admin edition — built from real platform signals.
• Doozer Town and the Board Game viewdoozer.town builds a page for every town in America the first time somebody asks for it, sorts its businesses onto ten colour groups, and can show any Doozer Cloud as a property board. Cost model, grouping rules, the edge blocker, and what to watch.
• Email Open TrackingA 1x1 pixel in every outbound email; opens recorded with device/geo/bot-flag; three operator alert signals plus data for the digest.
• Enrichment Store Links (commerce "Shop Now" CTAs)Turning a business's real online store into a tasteful commerce CTA, with a confidence gate so we never send a visitor to a bare marketplace homepage.
• Events to machines — a live event is only half published until a machine can read itThe pipeline that takes real events from public feeds onto a Doozer page AND emits them as schema.org Event, plus the timezone rule that makes the data correct. The foundation for gohe.re Gatherings.
• Fact-Guard (the accuracy net)A conservative healer that catches and corrects factual drift in AI-generated content (e.g. lodge/post identity numbers) at both the DB boundary and render.
• Fact-guard — org identity numbers, and the hole a conservative regex leftHow the accuracy net corrects a wrong Lodge/Post number, why the safe-looking regex silently no-opped, and why over-correcting it is worse than the original bug.
• Gatherings + Social (events, check-ins, the human layer)The roadmap surfaces that add real-time human signal — events/gatherings (GoHe.re), check-ins (wuz.ai), and how they enrich every business site.
• Hot Leads — the internal Doozer-sales CRMBusinesses are OUR prospects. Doozer-awareness scoring (claimed + postcard engagement + leads we deliver + live site) ranks who is warm enough to pitch Doozer+. The Internal Affairs Division of LeadBuilder.
• IndexNow (instant crawl notification)Push index-eligible Doozer URLs to Bing/Yandex the moment they cross the quality gate, so fresh and changed pages get crawled in hours instead of weeks. Bing-first hedge against the Google scaled-content classifier that cliffed elks.
• Lead Capture (the revenue pipeline)How a visitor's message or call becomes a routed, deliverable lead — the shared nbmn_lead_requests pipeline, auto-routing, no-email self-heal, and LeadBuilder handoff.
• LeadBuilder (the lead-intelligence platform)Where every captured lead, call intent, and cross-site referral flows to become revenue — the sibling product that turns Doozer traffic into qualified leads.
• Live Music Tonight (livemusictonight.com)A demand-sensing live-music discovery directory built on the Vertical Directory engine, fed by the Ticketmaster/Marquee feed, that captures visitor interest as a graph to decide which venue sites to build next.
• Magellan and the feed pond — bound IDs turn sites into living entitiesThe business_id_map spine (built v2.2.549) plus the feed adapters that hang off it. A bound external ID is what lets a generated page carry current, authoritative, self-maintained content instead of static prose.
• Marketing (build in public)The composer that drafts social posts from real platform signals in the founder's voice, and the auto-draft review queue.
• Money Clouds (affiliate vertical directories)Generalizing the Live Music Tonight pattern — any niche with an affiliate feed becomes a revenue-share vertical directory, bound across APIs by Magellan.
• NearByMeNow (the traffic + directory layer)The public "what's near me" surface that indexes the whole fleet, drives visitors back to business sites, and captures demand as leads.
• Network Growth — "More places nearby" (build-on-tap, gated)How the network grows organically from real local intent — visitors spin up the next site — and the two per-root guardrails that keep that growth clean.
• Niche matching and live discovery
• Per-Location Data Enrichment (the true voice of a place)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-User Location HotspotsA derived projection of a signed-in user's primary/secondary location centroids (home/work) from their own signals, used to personalize near-me defaults, reminders, and the Digest.
• Postcard targeting (the Postcard Queue)Who deserves a paid claim postcard — exclude committee-orgs and franchises, rank owner-operated marketing-spenders.
• PostcardsThe living-story system. Short or long dispatches that tell Doozer's WHO/WHAT/WHEN/WHERE/WHY/HOW/VISION, stamped to the moment they were written.
• Promo Codes + the one-time claim offerReusable Stripe-backed discount codes (the promo generator) and the truly-one-time Doozer+ 50%-off-for-life offer shown on claim. Money-safety, single-fire, and how they map to Stripe coupons.
• Prospector (discovery + demand-driven growth)How Doozer finds new businesses to build — the Grand Opening Finder, Cloud Radar, and the hybrid Google Places discovery engine.
• Regeneration + Foundation (keep 2,400 sites fresh and safe)The unified regeneration engine, version stamping, and staleness detection that let the whole live fleet be improved without taking anything down.
• Shortlinks + QR routing (doozer.link)Dynamic short URLs at doozer.link. The code encodes doozer.link/<slug>; the destination is editable, so a printed QR can be re-pointed without reprinting. The routing layer for the observed-world lead flywheel.
• Shortlinks and QR (doozer.link)One permanent, claim-aware doozer.link + QR per site — the printed asset that flips from the claim page to the real site on claim.
• Source-of-truth cache (read the real website)A business's official website cached as markdown (Jina Reader) — the accuracy foundation for enrichment; enrich content, never overwrite location.
• Thanks.io Connector (direct mail, two-way)How Doozer sends physical mail via Thanks.io and feeds the results back into intelligence — claim postcards, radius audience buying that reverse-engineers new sites, and delivery/scan webhooks.
• The /now surface and the dense directory — the app NearByMeNow already almost wasOne button, the nearest real places, and Build-it-on-the-spot. Plus the measured teardown of the category page that was hiding its own businesses behind 855px of controls.
• The Architecture (one file, unlimited sites)How a single index.php serves every business site, root directory, Cloud, and NearByMeNow page in the network by detecting the host and routing the request.
• The Chamber Chamber
• The Doozer Brand System (ecosystem identity kit)The canonical design identity for the whole Doozer ecosystem. Every human-authored surface (doozer.work, claim/auth/admin, roots, LiveMusicTonight, GoHe.re, Wuz.ai, AwesomeAddresses) shares one skeleton (neutrals, type, chrome, voice) and varies only its accent hue, so the network feels like one building with differently-lit rooms. Use this to build production-ready UI fast and on-brand.
• The Doozer FlywheelHow Doozer, NearByMeNow, LeadBuilder, and Prospector reinforce each other into a self-feeding local-business engine.
• The Doozer Score — the Stick, the Tower, and the leverage between themOne tracked number for whether Doozer is getting cheaper and more valuable at the same time. Stick = cost of 100 sites, Tower = replacement value of 100 sites, Score = Tower / Stick.
• The Elks Root Theme (bespoke root identity, a case study)How an entire root domain gets a hand-authored identity layer over the Muse engine — the elks.club star-spangled theme — as the pattern for premium root branding.
• The Growth Engine — observe → serve → convert → learnThe map of Doozer's acquisition + monetization machine. How observing a business, painting it a real site, sending it leads, tracking every touch, and making the RIGHT offer at the RIGHT moment turns into revenue — and how the intelligence layer decides who to reach, how, and when. The purpose, the smarts, and the wiring, with links to every component.
• The Muse SystemDoozer's AI-driven design engine — palette, typography, layout, and section variants that make each business site its own.
• The Muse v2 layer, and the brief that feeds it
• The Network (the whole Doozer ecosystem)A map of every product in the Doozer world and how they interconnect into one referral loop, so an AI can see the breadth of the platform at a glance.
• The Niche Color SystemOne source of category color for the whole network — the design primitive that makes cards, pills, spines, and markers coherent across every surface.
• The Photo Pipeline (harvest, store, serve)How business photographs are referenced from Google, bought once on first view, stored as objects on DO Spaces, and served back through a predictable cache key that lets any page ask "do we already own this?" before spending.
• The Section FrameworkHow a business page is assembled from pipeline section slots and per-variant partials a Muse selects.
• The Shared Business CardThe one card renderer used across NBMN, cloud, and root directories, with a pluggable toolbar and category-aware call intent.
• The Weather WidgetA non-intrusive "plan your visit" weather card on business sites — current conditions plus a 7-day forecast for the business's own location, free by default.
• Two gates, and the category catalog
• event-feeds
• machi

Craft

• Category-aware call intentThe tap-to-call chips are tailored to why you'd actually call THIS kind of business — reserve a table at a restaurant, get a quote from a plumber, check if the car is ready at a shop.
• Cross-root identity without third-party cookiesOne login has to work across doozer.work, elks.club, nearbymenow.com and every other root — but third-party cookies are dead. So identity rides a first-party token handoff, not a shared cookie.
• Decision vs delivery (the muse was almost never the problem)Nine defects found in one week where the design system chose well and the render layer quietly discarded the choice. The shapes these bugs take, why they never error, and how to find them.
• Derive the URL, don't trust the stored domainA saved business's link is always computed from the business's currently-active domain, never read from the domain id we stored when it was saved — because that stored id goes stale and poisons the link.
• Fix the source, never trap the symptomWhen the output is wrong, fix what produced it — the prompt, the data, the generator — not the output. No filters, no gates, no find-and-replace patches on the way out.
• Inline the bytes, never the proxy URLWhen handing an image to an AI provider, send the actual bytes from our side. Never hand it one of our own proxy URLs to go fetch — that is a timeout and a token burn waiting to happen.
• Price the pull before you pullA data refresh is a bill. Before re-pulling from any paid source, check what each pull costs, reuse the cache, dry-run the total, and pull only the unavoidable remainder.
• Self-healing email backfillI tried last week and it didn't work. I tried today and it works." The site quietly tried harder to find the business's contact email because it noticed the same person kept coming back.
• Skeleton first, index laterShow the visitor something instantly; show Google nothing until the page is actually good. Two different audiences, two different clocks.
• The distraction problem (teach without nagging)How do you explain "this is your listing, and here's how to manage it" to the one owner who needs it, without cluttering the page for the thousand visitors who don't? Tier the education by how much the reader has signaled they care.
• The hostile CSS environmentEvery shared component treats the page it lands on as an adversary, because the muse's own AI-authored CSS is actively trying to restyle it.
• The logo knows its own shapeA business logo is measured, not assumed. A square transparent emblem, a wide wordmark, and a tall banner each get different treatment, because one layout cannot flatter all three.

Processes

• Content Generation and HealingHow AI site content is generated, why it sometimes fails, and how it is retried, backfilled, and healed.
• Site CreationHow a domain becomes a live business site — resolve the place, persist the business, pick a Muse, queue content.
• The model handoffHow one model version hands Doozer to the next — the tradition, the ritual, and the artifacts that carry continuity across upgrades.

Glossary

• CloudA criteria-based directory assembled OVER existing business sites (a town, a niche-in-a-state, a personal collection).
• Family (Design Direction Family)A hand-authored designer recipe the Muse auto-generator draws from, tagged by which niches it suits.
• MuseA per-business design recipe (palette, type, layout, section variants) applied at render.
• NicheA business category slug; the unit of directory grouping and recommendation. Maps from Google place types.