A map-first restaurant product for places featured in Tzuyang videos.
Live app (external status; not verified by this candidate) · Latest release (external status; not verified by this candidate) · 한국어 · MIT
Tzudong Map turns mukbang video evidence into a usable restaurant map: users discover places on mobile, operators verify data in an admin console, and the storyboard workspace creates visual cuts for content production.
| Product surface | What it does |
|---|---|
| Map discovery | Search, filters, clustered food markers, current-location flows, and restaurant detail bottom sheets. |
| Community loops | Reviews, stamp passport, ranking, likes, and profile surfaces for repeat engagement. |
| Admin operations | Guarded moderation, source readback, approve/delete/restore flows, and audit-friendly mutations. |
| Storyboard workspace | Chat-driven storyboard planning, 10-cut generation, cut metadata, image refresh, and provider readiness UX. |
| Evidence pipeline | Crawling, Rule/LLM-as-a-Judge evaluation, fail-closed validation, and Supabase-ready payloads. |
- Toolchain. The web runtime is Node 24.x. Bun remains supported for day-to-day install and unit flows, while npm 11.6.2,
package.json, andpackage-lock.jsonare the release package authority;bun.lockmust be reconciled with that authority. - Compiler evidence. The native TypeScript CLI is the exact
@typescript/nativealias at7.0.2; TypeScript6.0.2is the stable API/compatibility bridge. Usenpm run typecheck:parityandnpm run typecheck:benchmark; never suggest a global compiler. - Performance evidence. Canonical performance material lives in
apps/web/performance/*, uses its scorer/validator, and maps artifacts to an out-of-band SHA. Reports state absolute, relative, and noise budgets and retain frozen-tree evidence; zero admitted slices is valid. No current G003 measured improvement is established without retained raw and scored artifacts. - Style and naming evidence.
apps/web/stylegallery-adoption.v1.jsonrecords Tzudong-owned clean-room adoption. The unlicensed StyleGallery commit775430bbaf4ee208a642220f440f6926d79c90a3is question-only and no code, CSS, prose, names, tests, or assets are copied; this does not imply affiliation.backend/naming-renames.v1.jsonis bounded high-confidence taxonomy/rename evidence, not authorization for all-path churn. - Accessibility, visual, and load evidence. WCAG 2.2 AA is a target, not certification. Focus stays visible and is scrolled into the owning region; mobile controls respect safe areas; reduced motion is honored. Keep only sanitized visual evidence. Load tests require authorization, non-production scope, bounded volume, explicit stop conditions, rollback, and readback receipts.
- Worktree, release, and Vercel evidence. The dirty original worktree is immutable; edits belong in an isolated recovery candidate with no reset, stash, or clean. Fresh-head serialized content-patch PRs move
develop -> data -> mainunder external approval and branch protection. Before any hosting action, verify the exact Git-integratedtzudongVercel project; do not use a stalewebproject or mutate DNS. Release and rollback require approval, branch-protection, rollback, and readback receipts. No merge, deployment, or live URL state is verified by this candidate.
Map discovery and restaurant detail
Admin storyboard workspace
| Home map Browse markers → expand restaurant detail ![]() |
Review feed Scroll reviews → open restaurant detail ![]() |
| Stamp passport Browse stamped places → read detail ![]() |
Ranking profile Open top profile → switch tabs ![]() |
G010/G013/G014 source safeguards implement fail-closed privacy boundaries:
- Account creation is bound to an explicit acknowledgement of the exact published Korean policy version and content hash.
- Registration for users under 14 is unavailable until a verified guardian workflow is deployed and read back; the flow does not request a birth date, guardian contact, or resident registration number.
- Marketing consent is purpose- and channel-specific, with a separate grant for advertising between 21:00 and 08:00.
- Shared sanitization keeps credentials, personal data, precise location, raw OCR, arbitrary bodies, and provider diagnostics out of logs and minimized audit evidence.
- Device location is disclosed just in time, held in memory only, and stopped when the user cancels or leaves the flow.
- Account deletion, retention, and privacy incidents use Preview → Confirm → Apply → Readback → Audit with fixed codes, legal-hold/authorization checks, and human-owned external notices.
These source safeguards are not legal compliance or production proof. Release remains blocked pending external evidence of exact policy publication; Korean legal/privacy-owner review; location-business filing or documented non-applicability; guardian/provider approval before any under-14 support; incident submission and receipt; operator-approved retention classes; an approved HTTPS marketing provider with production secrets and internal capability controls; and hosted migration/RLS/grant/RPC/type/catalog, backup/PITR, key-management, and operator-access readback. The external links above are status references only and are not verified by this candidate.






