# Items requiring owner approval

Date: 2 November 2026

These items are not silently resolved in the preview implementation:

1. Drink taxonomy: the brief flags "DJ Nights" vs "DJ Nights & Party Bars" for an owner decision. The current public page already shows "DJ Nights & Party Bars". Confirm whether to retain that label and any slug/query behaviour.
2. Typography conflict: the main brief and brand kit specify Inter/Inter Display; Section 34.15 also mentions Plus Jakarta Sans. The preview keeps Inter/Inter Display because the approved brand tokens and guidelines name them.
3. Homepage headline conflict: the final proposed copy says "The city, seen differently." Section 34.15 also proposes "BENGALURU LOOKS BETTER IN MOTION." The preview keeps the final proposed copy.
4. Alcohol data policy: Open Data withholds alcohol-category data while the public Drink page displays expanded source counts. Confirm whether to keep this split.
5. Ice-cream source records need an approved home: Dessert Parlours or a future subcategory.
6. Parks, attractions, museums, galleries, generic resorts, community spaces, clubs, event spaces, theatres, sports centres, turfs and broad shopping records need evidence-led or owner-approved mappings before full inclusion.
7. Canonical place schema and migration plan require owner approval before any production database migration.
8. Editorial import/merge/translation/audio approval workflow requires backend design, security review and owner approval.
9. Club eKYC, booking, payment and cashback remain non-live and require separate legal, payments and operations approval.
10. Studio commercial economics, subscriptions, payouts and brand approval workflows remain simulated/proposed.
11. Place submissions remain paused until the owner explicitly reopens intake.
12. Claim verification/business tooling remains manual and requires backend implementation before any verified/claimed badge is shown.
13. Buddy native-language AI and non-English voice support remain experimental until verified.