system
manual

tripbier is a serverless platform for discovering and routing craft breweries. It combines a georeferenced database with generative AI to create personalized experiences — from an interactive map to a narrated itinerary delivered by a beer concierge.

The entire infrastructure runs on Cloudflare (Workers + D1 + KV + R2), with no dedicated servers, global edge latency, and usage-based costs. The data model uses SQLite via D1, distributed across multiple databases by continent.

The system is made up of 6 independent workers, each with a specific responsibility, communicating via internal fetch calls or sharing state through KV.

The radar (tripbier.com/mapa.html) is the heart of the platform — a Leaflet map with 19,900+ pins of breweries across 16 countries, with MarkerCluster for performance and real-time filters.

On load, the map uses the browser's geolocation or the IP (Cloudflare cf.city) to center automatically. Each pin opens a card with rating, address, link to Instagram/site, and a "get directions in Google Maps" button. Award-winning breweries get a distinct marker.

URL parameters accepted by the map:

The tripbier concierge is a pipeline of 6 mini-agents that transforms a text message into a personalized brewery itinerary. Each agent receives a data envelope, enriches it, and passes it to the next.

The concierge is multi-function by design — it is not a menu-driven chatbot. The user writes in natural language and the system automatically detects the intent, without prompting a mode selection:

The Validator detects all 4 modes without any LLM call — pure JavaScript logic. It normalizes abbreviations (poa → Porto Alegre, cwb → Curitiba) before the Extractor runs. The Curator queries databases in cascade: DB Brasil → DB_AMERICAS → DB_EUROPE → DB_ASIA → Serper Discovery as a final fallback.

The tripbier passport is an installable PWA (Progressive Web App) that lets users collect stamps with each visit to partner breweries. It is the platform's gamification and loyalty engine.

User flow: The user visits passaporte.tripbier.com, installs it on their phone (home screen), identifies themselves by name and WhatsApp (no account required), and earns stamps by checking in at breweries on the circuit.

Available circuits: Each partner itinerary has a circuit with N stops. Completing all stops unlocks a reward at the partner brewery (freebie, discount, exclusive experience). The partner dashboard (admin-parceiro) shows in real time who has completed it and allows sending the reward via WhatsApp.

Levels: Curious → Apprentice → Explorer → Master → Sommelier — based on total accumulated stamps.

Itineraries are generated by the Maestro pipeline and automatically saved to D1 with a permanent, unique URL — no login required. The URL can be shared via WhatsApp, included in an email, or bookmarked.

URL format: tripbier.com/roteiros.html?id={slug} — where the slug is generated by the Curator from the city, profile, and selection hash (e.g., variedade-porto-alegre-3d-a1b2).

Each itinerary stores: brewery list (id, name, curator's note), city, chosen profile, number of days, weather at generation time, and the Presenter's narrative.

The social layer allows passport users to interact with each other: share itineraries, comment on breweries, follow other travelers, and build a visit history visible on their public profile.

Identity based on phone number + name (no password). Avatars generated automatically by DiceBear. The activity feed shows recent community visits in each city.

Moderation: an automatic regex detects phone numbers, links, and inappropriate content in comments before saving to D1.

tripbier has active coverage in 16 countries, with a database, editorial city pages, and concierge routing. Each country has city pages and integration with the global map.

Country pages are dynamic — they do not exist as static files. They are generated in real time by the worker from D1 data: breweries, cities, awards, and editorial content. This means adding a new country to the database automatically creates all of its pages, with no manual publishing work. It is scalable infrastructure disguised as content.

Each city with a critical mass of breweries gets a curated editorial page — not auto-generated, but written with local identity. The base template is caxias.html (serif layout with sidebar, hero, pull-quote, and card grid).

Page structure: hero with a local photo → "why visit" editorial → pull-quote → brewery grid with rating/insta/site/agent → events → suggested itinerary. The news section is fed by utt-beerfeed in real time.

All international city pages live under the country subdirectory: /de/berlim.html, /be/bruges.html, /it/roma.html, etc. Like country pages, city pages are dynamically generated — the worker builds the HTML from D1 on each request, with no pre-compiled files. A new city with enough breweries in the database already has its page available.

Award-winning breweries (CBC, WBC, or WBA) automatically receive a dynamic landing page generated from D1 data — no manual intervention required. Access is via subdomain: slug.tripbier.com.

Content displayed: name, city/state, Google rating and reviews, opening hours by day of the week, beers in production (name, style, ABV, IBU), awards with medal and year, related blog posts, embedded map, Instagram/website/WhatsApp buttons, and a chat with an AI agent specialized in that brewery.

Access rule: If the brewery has an award → renders the full landing page. If no award but has Instagram or website → redirects (302) to the social profile. If neither → 404.

Cache: each landing page is stored in Cloudflare's edge cache for 1 hour (stale-while-revalidate=86400) — zero CPU on repeat visits.

tripbier indexes medals from the leading craft beer competitions and displays them on brewery landing pages and the awards page. Medals are used as a ranking criterion in the Curator agent.

The partner dashboard is the management interface for brewery owners. Accessed via the brewery slug (no login — token-based auth via URL, to be implemented). Direct URL: tripbier.com/admin-parceiro?slug={slug}.

agm.tripbier.com is a dedicated subdomain for the tripbier × AGM partnership — an editorial pitch page featuring the 19 member breweries on a map, the history of the Gaúcho craft movement, and a CTA for membership.

Historical content based on verified academic research: Cruz, R.C. (2016). Consumo e Formação de Mercado: um estudo sobre as microcervejarias de Porto Alegre. Dissertação UNISINOS.

Timeline: Dado Bier (1995, first Brazilian microbrewery) → WE Consultoria (1997) → Acerva Gaúcha (2003) → AGM founded by Jorge Gitzler → reduced ICMS in RS → Polo Anchieta (2010) → 50+ member breweries today.

Breweries without a complete profile display a CTA "Is this your brewery?" on the landing page and in the chat widget. When clicked, the owner fills out a simple form (name, email, role, WhatsApp) that creates a lead in D1 (reivindicacoes) and triggers an internal notification.

This is the entry funnel for the B2B model: Starter (R$89/mo) → Professional (R$149/mo) → Premium (R$297/mo), with incremental features in the partner dashboard and map visibility.

tripbier uses 1st-party analytics — no Google Analytics, no third-party cookies. The tracker (/a/tracker.js) is loaded by every page and sends events to /collect in utt-analytics.

Data collected: pages visited, dwell time, session recurrence, conversion funnel (home → map → itinerary → passport), country/city (CF headers), device type. No PII — the identifier is a SHA1 hash of IP+UA.

Daily cron: utt-analytics aggregates raw events and writes daily summaries to D1 (id: 170900e5) — unique visitors, pageviews, top-5 countries, bandwidth. The analytics dashboard reads from these summaries.

Tracked clicks: Instagram, website, WhatsApp — per brewery, per geographic origin, per device.

The cookie banner is injected by the worker on every page via middleware — no page needs to include the script manually. Consent is stored in localStorage for 365 days.

All deployments are done with Wrangler CLI from the directory G:\Site\tripbier\utt-engine\PRD\js\. Configuration lives in wrangler.toml. API credentials (OpenAI, Serper, Google Places) are stored in G:\Site\tripbier\upg-engine\pipeline\.env.

Golden rule: changing a worker or HTML file without first listing what changes and who it affects can cause silent regressions. The correct process: (1) list changes and impact, (2) confirm with Marcos, (3) publish.

Important: Tripbier and ClubTour are separate businesses with separate accounts — never cross workers, data, or credentials between them.