TBG Network LLC / Production directory / Read-only status
Your directory.
One authoritative corpus: 351 Designworks shops now hosted in TBG Cloudflare D1 and serving thebarbergame.com.
Authoritative data.
Verified checkpoint · November 11, 2026
Directory Admin: live publishing and permanent team address.
Owner-verified: 351 shops searchable in the separate Cloudflare-hosted Directory Admin; an edit to Chop it Up – Bellevue was saved as a draft, reviewed, explicitly approved, and displayed on the live customer profile. The customer site now renders approved descriptions under “About the shop.”
Team bookmark: directory.thebarbergame.com. This production custom domain is connected to barbergame-directory-admin-poc. Cloudflare Access uses the existing BarberGame Team Members Allow policy for all traffic; the owner verified Access email sign-in followed by the existing Admin password.
Next / proposed feature roadmap
Stabilize. Review. Approve. Publish.
With the 351-shop directory now live, the next release is an owner-controlled directory operating system. Stabilize the production site first, then add a protected admin panel, a review queue and an explicit approval gate before any new shop or change reaches the public directory.
| Order | Feature | Acceptance / outcome | State |
|---|---|---|---|
| 01 · Now | Stabilization & recovery | Keep the original SQLite/export and Git/Worker rollback; confirm built-in D1 Time Travel is available; perform one non-production recovery rehearsal. Avoid extra backup infrastructure until needed. | In progress |
| 02 · Next | Protected directory admin panel | Owner can search all 351 shops, view provenance/status, edit draft changes, inspect duplicates and missing data. Authentication and authorized roles; no public editing of D1. | Proposed |
| 03 · Next | Review → approve → publish | Submissions and edits enter a private queue. Review proposed changes versus the published record, resolve duplicates, preview the result, then the owner explicitly approves and publishes. Capture audit history and offer rollback. | Proposed |
| 04 · After | Photo-first crowdsourcing | Customers, barbers or shop owners can submit one storefront photo with no required typing; signage and optional consent-based location help create a draft for the same review queue. Never auto-publish photos or shops. | Proposed |
| 05 · After | Bronze quality & expansion | Queue missing coordinates, incomplete hours and duplicate candidates; add Washington chain/city records through source-linked reviewable imports. | Proposed |
| 06 · After | Latent Silver & Gold enrichment fields | Support valuable optional data before it is collected for every shop: Silver candidates include descriptions, verified hours, service menus, booking/social links and photos; Gold candidates include barber profiles, specialties, accessibility, amenities and portfolios. Keep unfilled fields hidden, retain source/provenance, and publish only useful verified information after owner approval. Tiers remain flexible, not mandatory checklists. | Proposed |
| 07 · Future | Optional Walking Compass | Consider close-range directional guidance from phone orientation and bearing to the shop to answer “Which way should I walk?” Preserve the circular map and existing blue-dot behavior; request sensor permission separately, retain walking directions for routing, and validate mobile browser support. No implementation now. | On hold |
Approval design: submitted → pending review → changes reviewed → approved by owner → published. Rejected or needs-information items stay private. Draft storage must be separate from the published record until approval; the approval button is not an automatic deployment of unrelated website code.
Stabilization / basic recovery
If something breaks.
We already have layered protection. No new scheduler is needed if Cloudflare D1 Time Travel is enabled for our production database—it automatically records recovery history. The original private SQLite and SQL export remain the older recovery baseline; Git and Cloudflare Worker versions protect the website code.
| Protection | Where / use | Verification |
|---|---|---|
| Original source & SQL export | Designworks barbergame-original.sqlite3 and ~/barbergame-private/. A preserved 351-shop baseline, not a live mirror of future edits. | Preserved during migration |
| Cloudflare D1 Time Travel | Cloudflare automatically retains recent recovery history on production D1: typically 7 days (Workers Free) or 30 days (Workers Paid). No setup required if D1 version is production. | Read-only version and bookmark check pending |
| Git + Worker deployment history | Git checkpoints 5d8cd52, 7c25777; Worker version ea48fe7c-302d-41cc-84d2-6e737991df17. Restore code separately from database content. | Release checkpoint saved |
Safe verification: On Designworks with TBG Wrangler authenticated, run npx wrangler d1 info barbergame-directory and npx wrangler d1 time-travel info barbergame-directory. Check version: production and confirm a bookmark is returned. Both commands are read-only.
Recovery rule: A D1 Time Travel restore overwrites the database in place and can discard newer changes; never run it on production as a routine test. Rehearse any destructive restore only on the separate disposable test database with its own bookmark. Before a real emergency restore, record the current bookmark, record the target timestamp, pause directory edits and obtain explicit owner approval.
Cloudflare documentation: Time Travel and backups · Wrangler D1 commands. This is a recovery guide, not an automated restoration service.
Production connection.
| Component | Current state | Next |
|---|---|---|
| Original Designworks shops barbergame-original.sqlite3 · recovery copy | Preserved | 351 original rows and private SQL export retained |
TBG Cloudflare directory storagebarbergame-directory / shops | 351 imported and verified | Worker binding: DIRECTORY_DB; 7 confirmed / 344 entered |
| Customer shop search and profiles | Production live | Cloudflare Worker barbergame-customer; stable designworks-{id} shop URLs |
| Shop submissions | Separate D1 barbergame-shop-intake | 7 previously recorded; new end-to-end submission check remains outstanding |
| Release and legacy API | Owner-deployed Nov 11 | Retain old public API until other consumers are audited; no automatic publishing |
Migration history · November 10–11, 2026
How we got here.
The goal was to establish one owner-controlled BarberGame shop directory. We started with an authoritative Designworks SQLite file, moved its complete contents into TBG Networks LLC’s Cloudflare account, and changed the existing customer Worker to read that database. This page records the decisions and locations so the setup can be recovered later.
- Selected the authoritative corpus.351 Designworks-owned shop records, not the larger unrelated directory returned by the old API. No merges and no pre-migration cleanup.
- Imported and verified all 351 rows.Private SQL export on Designworks →
barbergame-directoryD1. Verification: 7 confirmed, 344 entered; 88 distinct raw city values. Nine missing/invalid coordinates retained for later enrichment. - Rewired the customer website.The existing
barbergame-customerCloudflare Worker now reads viaDIRECTORY_DB. Search, city browsing, location radius, maps, shop detail pages and sitemap use D1. Stable profile IDs:designworks-{id}. - Preserved the separate intake workflow.The form checks duplicates against the directory but still writes to
SHOP_INTAKE_DB; seven earlier submissions remain distinct from published shops. No automatic publication. - Built, tested and deployed manually.Shop search/map/profile tests passed locally; sitemap had 351 unique shop IDs. Production /shops, /city/seattle, /sitemap.xml and /add-barbershop returned HTTP 200. Owner visually verified live Seattle and Bothell profiles.
Recovery reference
Where everything lives.
| Item | Location / identifier | Why it matters |
|---|---|---|
| Original database | Designworks: ~/designworks/projects/barber-directory/data/barbergame-original.sqlite3 | Preserved source / recovery copy |
| Private SQL exports | ~/barbergame-private/d1-directory-shops.sqld1-directory-import.sql | Original and D1-ready snapshots; private, not website assets |
| TBG Cloudflare account | 707cdd30dab4f1606629739fce05a265 | Owner-controlled Cloudflare account |
| Production directory D1 | barbergame-directory8427bee6-6d91-4bc3-aac9-3b2a8f644aec | shops table · Worker binding DIRECTORY_DB |
| Separate intake D1 | barbergame-shop-intakeWorker binding SHOP_INTAKE_DB | Submitted shops are review records, not automatically in the directory |
| Customer website source | Designworks: ~/designworks/projects/barbergame-map-home-v01 | Existing project; unfinished Map Home edits preserved separately |
| Clean release worktree | ~/designworks/projects/barbergame-d1-releaserelease/cloudflare-d1-directory | Release snapshot that was deployed |
| Integration code | cloudflare.config.tssrc/lib/directory/public-json.ts (D1 reader)src/app/sitemap.ts and src/app/api/shop-intake/route.ts | Bindings, public search/data mapping, sitemap and intake duplicate check |
| Production Worker | barbergame-customerVersion ea48fe7c-302d-41cc-84d2-6e737991df17 | Serves thebarbergame.com and www |
| Git checkpoints | 5d8cd52 · 7c25777 | Binding addition and D1 reader/sitemap/intake integration |
Owner decisions
What we decided.
| Decision | Reason / operating rule |
|---|---|
| One directory corpus | The 351 Designworks rows are the only approved authoritative directory; no silent merge with the old API’s larger dataset. |
| Preserve the complete snapshot | Keep existing IDs, provenance and statuses. Defer potential duplicates, coordinate gaps and city-name cleanup rather than delaying deployment. |
| Keep publication separate from intake | Existing submissions stay in a different D1 database and do not become public shops automatically. |
| Use the existing Worker | Read directory data directly through DIRECTORY_DB instead of introducing another customer API service. |
| Owner-controlled deployment | Build with vinext, deploy manually to Cloudflare, and retain Git/Cloudflare release history for rollback. |
| Do not retire legacy services prematurely | Audit any other consumers of the former directory API before removing it. A working customer site does not prove all other integrations have moved. |
Migration record and remaining actions.
The beta cutover is complete. This checklist records the accomplished migration and the small number of remaining cleanup tasks.
Related destinations.
These remain separate from the canonical published data until you approve an import.