Verified meals
Wallet-paid dining receipts separate people who actually ate from drive-by review noise.
Zweispace vertical AI token family
OMT
A Tokyo-born restaurant intelligence layer for verified dining, omotenashi ranking, URA owner voting, and new-opening market decisions.
Core thesis
The guide should come from the city that eats here.
OMT turns wallet-paid restaurant visits, hospitality signals, restaurant-owner votes, and AI market models into a restaurant ranking and launch support system. It is built for diners, chefs, owners, landlords, and new concepts that need proof before they commit to a permanent location.
Omotenashi ranking
A rating system for proof, craft, and hospitality.
The public score can look simple, but the underlying system should show what was earned and how it was verified.
Hospitality score
OMT records omotenashi signals such as service, consistency, memory, care, and repeat trust.
Owner respect
URA lets restaurant owners support their own house or respected peers, with conflict labels.
Anti-gaming
Self-votes, friend clusters, suspicious receipts, and related-party voting should be visible.
OMT plus URA
Customer proof creates owner voting power.
The working chain target is public Zweichain. OMT and URA contracts are now scaffolded for deployment, but public addresses stay pending until verification.
PayA diner pays with a wallet and creates a verified restaurant receipt.
Receive OMTThe diner receives OMT as a proof-of-dining and hospitality participation record.
Earn URAThe restaurant earns URA capacity from verified customer and payment flow.
VoteOwners allocate URA to their own restaurant or peers, with conflict labels and ranking weights.
OMT as thank-you proof
Customer history can unlock review weight, loyalty, events, concierge access, and verified recommendation status.
URA as ranking voice
Owners who keep serving verified customers gain a measurable voice in restaurant awards and rankings.
Readable trust
Rankings should show meal proof, OMT activity, URA support, expert lanes, and conflict-adjusted scores.
Zweichain ready
Contracts, deployment scripts, and wallet-watch templates are staged for chain ID 7853.
New-opening AI
Before the lease, test the recipe and the street.
OMT should help owners model the business, estimate demand, and test a cuisine category in real space.
Restaurant economics
Seats, turns, ticket size, food cost, labor, rent, utilities, service windows, and break-even runway.
Station-area demand
Potential customer base by walking radius, time of day, weekday pattern, and cuisine category.
Competitor map
Category density, price bands, gaps in the market, expected share, and launch positioning.
Pop-up validation
Lunch, dinner, weekend, retail, station-street, or kitchen-share experiments before permanent buildout.
Real estate lane
From concept to location, contract, design, and opening.
OMT should connect ranking and market intelligence to the practical work of opening a shop: finding a site, negotiating the lease, designing the kitchen, and building the room.
- 1Find the right block, station, building, and service window.
- 2Compare rent pressure against projected sales and cuisine-market share.
- 3Use shared lunch, dinner, weekend, or event time before a full lease.
- 4Route owners into real estate, contract, architecture, and construction support.
MVP path
Start with a flat page, then build the local app.
The first app should simulate the loop before live chain work: restaurants, receipts, OMT proof, URA voting, ranking math, and new-opening modeling.
Guardrails
Ambitious, but clean enough to publish later.
Current wording avoids private team details, live-token claims, and unsourced market-size numbers.
No private team claims
Named team members, partners, and private access stay off the public page until approved.
No investment promise
OMT and URA are described as product mechanics, not investment assets or live sale instruments.
No silent vote capture
Self-votes, friend votes, related-party patterns, and unusual receipt clusters should be visible.