Concept and mechanics · v2 · 14 September 2026
The KOR app
An inside-only social layer for KOR Taipei. Scan to check in, see the room, send a drink, earn status.
02 · The idea
Three things, in one room, for one night
The room is already full on a Saturday. The app does not have to find people. It has to make it easy to be seen, make interest credible, and reward the people who keep coming back.
Inside only
Only guests who scanned tonight's rotating code and are on KOR's Wi-Fi can see the room. Outside, the link shows a live count and nothing else. Exclusivity is the hook.
The room
A swipe deck of guests who chose to be visible tonight. Likes stay silent until mutual. A drink offer is the one move that carries real information, and the recipient always decides.
Status
Gold, Platinum and VIP are earned by checking in and completing a profile. Benefits are real: skip the line, reserved seats, free entry on ticketed nights, a birthday table.
One rule everywhere: every gate sits after a reward. Check in and you get a drink. Add a photo and you see the room. Verify a handle and you can send offers. Nobody is asked to do work before they have received something.
03 · What is decided
Locked before design
04 · A night at KOR
The app follows the rhythm of the room
Gold band: welcome-drink window. Orange band: last-call window. Times follow KOR's canonical schedule once confirmed.
05 · Check-in funnel
From a screen on the wall to a checked-in guest in under 30 seconds
Screens at 1F reception, the host stand, the bar and the restroom corridor show the same rotating code. Scan, claim, sign in, one photo. The drink appears before anything else is asked.
掃描加入今晚
Welcome drink until 22:30
You're at KOR tonight.
Claim your welcome drink and see who's here.

By continuing you confirm you are 18 or over
Sign in to claim.
One tap. Nothing is posted anywhere.
Locals use LINE. Visitors use Apple, Google or a number.
Your card for tonight.

06 · Reward before gate
Progressive commitment, one small ask at a time
Illustrative funnel for a peak night
Table view
| Ask | Reward that comes first | Principle |
|---|---|---|
| Scan and sign in | Welcome drink voucher on screen | Foot in the door |
| Add one photo | The room becomes visible | Curiosity, reciprocity |
| Complete height, intent, socials | Profile meter starts at 40%, points toward Gold | Endowed progress |
| Verify Instagram or TikTok | Sending offers unlocks, verified tick on the card | Costly signal of being real |
| Check in before 22:30 | The drink, plus early-bird points | Loss aversion, fills the room early |
Show this at the bar.
07 · Inside only
Presence is a server-side decision built from three factors
No phone can prove it is inside a room. The server combines a code that only exists on KOR's screens, traffic that only comes from KOR's Wi-Fi, and a heartbeat that stops when the guest leaves.
Rotating code
An HMAC over the current 45-second slot, single use per guest. Proves the guest saw a KOR screen within the last minute.
Cannot tell who is by the door from who is at a table. Solved by table QR or host assignment for delivery.
Wi-Fi fixed IP
Every request is checked against KOR's fixed public IP. Guests join the guest Wi-Fi by scanning a Wi-Fi QR on table cards; the password rotates weekly.
Guests on 5G or a VPN run on the code alone with a shorter session and a re-scan prompt.
Heartbeat and TTL
The page pings every few minutes while open. Unseen for 3 to 5 minutes marks away; 10 to 15 minutes marks left and removes the guest from the roster.
Return, scan again, and the same visit resumes.
Visit states
Offers, likes and table requests are only accepted from guests in the checked-in state. The roster shows checked-in guests only, so it reflects the room within a few minutes.
08 · The room
A deck of people who chose to be seen, ordered by a score nobody sees
Three gestures
| Pass | Card goes away for tonight. Nobody is told. |
| Like | Silent. Revealed only when the other side likes back. An unreturned like is never surfaced. |
| Send a drink | The costly signal. The recipient sees your card and the drink, and decides. Detail on the next slides. |
Who sees whom
| Only people I liked default | You appear in someone's deck only after you liked them. Removes the feeling of being browsed. Recommended default for everyone, and the one women keep. |
| Everyone tonight | You appear in every deck. The choice for guests who want maximum reach. |
| Hidden | You can browse and like; nobody sees you until you change it. Likes from hidden guests still count when mutual. |
The private score
Orders each guest's deck and is never displayed. Inputs: profile completeness, verified handles, tier, intent compatibility, past accepted offers, and right-swipe ratio. A diversity rule guarantees that new and lower-scored guests keep appearing, so the deck never collapses onto five people.
09 · The costly signal
A like is cheap talk. A drink is a signal the recipient can trust.
The sender pays the bar, not the app. The recipient decides before anything is made. Staff deliver by hand and say who sent it. Both sides get a cheers thread.



Why this converts
- Sending costs nothing until accepted, so trying is easy.
- Accepting is low risk: the drink comes from staff, the sender's location is revealed only on the recipient's terms.
- A decline is invisible to everyone else and shown to the sender without detail. No public rejection, so senders keep sending.
Rules
- Offers only from checked-in guests with a verified handle or a door-verified stamp.
- Recipient must be checked in and visible to the sender.
- Expire at 15 minutes; no ticket is ever created for an expired offer.
- Last call for offers at 01:30.


10 · Congestion control
Caps spread the offers, and that is what keeps the room alive
Two-sided markets fail through congestion, not through lack of interest. Without limits, a few guests are flooded and everyone else is ignored. The caps below are the product's market design.
Offers pending per recipient, night one
Table view
Accepted offers per night over six nights
Table view
The caps
- 5 offers per sender per night. Platinum and VIP get more.
- 1 pending offer per sender per recipient.
- 3 pending offers per recipient at any time. Capped recipients drop out of decks until an offer resolves.
- Each guest is shown to a bounded number of viewers per ten-minute window.
What the numbers say
On night one the caps deliver about the same number of drinks while cutting offers sent in half, so the acceptance rate roughly doubles and nobody is flooded. From night two the difference compounds: recipients who were not flooded stay visible, senders who got a yes keep sending, and the visible pool grows. Assumptions are in the table views and are deliberately simple; the pilot replaces them with measured rates.
11 · Table rounds
The table as a social unit
Groups and business travellers do not swipe. They send a round. One table greets another, the receiving table accepts together, and the ticket is bigger than any single drink.
Send a round to Table 12.


4 guests · they accept or decline as a table

Why tables matter at KOR
- Bottle-service booths and sofa groups are the core of the room on weekends.
- Group consent lowers individual pressure: a table can accept a round without any one person feeling singled out.
- Splitting the cost lowers each sender's threshold and raises the ticket.
- Networking intent maps naturally to tables: a table of visitors greets a table of locals.
Mechanics
- Any checked-in member of a table can propose a round; the table sees it before it is sent if split is on.
- The receiving table sees the sending table's card: names of the visible members, intents, tiers.
- Accept requires one tap from any member; decline is silent.
- On accept, one ticket for the whole round goes to the bar console, and staff settle per the split.
12 · After a match
Twenty metres apart, so the thread exists to get people to the bar, not to keep them typing


It's mutual.
You and Daniel liked each other.
DanielThread rules
- Opens only after a mutual like or an accepted drink.
- Prompts come first; free text is short, no attachments, no in-app camera.
- Either side can end it. Block and report are one tap away.
- The other person's Instagram or TikTok appears only if they tap reveal.
Connections persist
The roster wipes at close, but a connection both sides keep stays on the profile as “met at KOR”. Next visit, the app shows who among your connections is checked in. This is the reason to come back on a Wednesday.
13 · Tier program
Status is earned by showing up and by finishing your card
Points come from check-ins and from profile completion. Nothing about who liked you touches tiers. The engine is the same for everyone; promotions on top are where KOR decides who gets what.
Tiers, rolling 90 days
| Gold | Platinum | VIP | |
|---|---|---|---|
| Reach at | 60 points | 150 points | 320 points, or management invite |
| Typical path | 3 check-ins plus a completed card | 6 check-ins, verified handle, one event | 12 check-ins, two referrals, events |
| Venue benefits | Skip the line · welcome drink every visit | Reserved seat before 23:00 · free entry on ticketed nights | Guaranteed table on peak nights · birthday table · private event invites |
| In-app privileges | See who liked you | Incognito · priority in the deck · 8 offers a night | Everything · 12 offers · bring two friends who get Gold for the night |
Points
| Action | Points | Limit |
|---|---|---|
| Check in | 10 | once per night |
| Check in before 22:30 | +5 | once per night |
| Photo added | 10 | once |
| Height, intent, languages, drink of choice | 5 each | once each |
| Instagram or TikTok verified | 10 each | once each |
| Referred friend checks in | 15 | 5 per month |
| Ticketed event attended | 20 | per event |
| Accepted cheers, either side | 2 | 10 per night |
| Upheld report against you | −50 | and a pause |
Points expire 90 days after they are earned, so tiers decay without punishment. A full card on the first night puts a guest at 50 points: one more visit reaches Gold.
14 · Progression
Every visit moves the meter, and the meter is always on the profile

Points to each tier and where a typical guest sits
Table view
Badge on the card
The badge is the member's choice, on by default. Because it is earned by loyalty, showing it flatters a regular instead of rating them. A visible points leaderboard among members is fine for the same reason: the axis is showing up.
15 · Ladies' program and promotions
The tier engine is neutral. Promotions are where KOR sets the offer.
A ladies' night is a promotion rule. So is a welcome drink for first-timers, or free entry for Platinum members on Fridays. Management edits rules; the app applies them at check-in.
| Rule | Who | When | Benefit | Status |
|---|---|---|---|---|
| Welcome drink | First check-in ever | Any night, before 22:30 | One welcome drink | Live |
| Welcome back | Gold and above | Any night | Welcome drink every visit | Live |
| Ladies' Friday | Women · Platinum and above | Fridays | Free entry, reserved seat before 23:00 | Live |
| Jazz Wednesday | Everyone | Wednesdays | Social mode on for all check-ins, ticket includes a drink | Live |
| Bring a friend | Referrer and friend | Any night | Friend gets welcome drink, referrer +15 | Live |
| VIP birthday | VIP | Birthday week | Reserved table, bottle on the house | Draft |
Rules are ordered; the first matching rule per benefit type applies. Every applied benefit is logged against the visit so the bar can see why a voucher exists.
16 · Controls
The controls are what make people opt in
A guest who knows she can go quiet in one tap, that nobody sees her table, and that a manager will come if she asks, is a guest who turns visibility on.
Guest controls
- Visibility mode, changeable any time, defaults to only people I liked.
- Quiet mode pauses offers and likes without leaving the room.
- Block removes both from each other's decks for good. Report goes to the manager's console with the thread attached.
- Discreet staff request: come to my table, help me leave, I feel unsafe. The manager gets the table number; nobody else sees anything.
Staff controls
- Pause a guest's visibility for the night in one tap, for example when someone has had too much.
- Stop further offers to a specific guest.
- Freeze or ban an account, with the door list updated.
- Staff never appear as social contacts. Staff screens show badges and table numbers, never a browsable gallery.
What is never shown to other guests
Table, zone, time of arrival, tier points, who liked whom, and any decline. Every one of these is a reason someone would stay hidden.
17 · Privileges for senders
Status for the people who send, earned the same way
Payment stays offline, so spend is not tracked. Senders earn tiers from check-ins, a complete card, and deliveries the bar confirms. Privileges buy reach and information, never a way around someone's controls.

Tonight.



Privileges by tier
| Gold | See who liked you · 5 offers a night |
| Platinum | 8 offers · one boost a night · priority in the deck |
| VIP | 12 offers · two boosts · guaranteed table · bring two friends |
What privileges never do
- Reveal a hidden guest or bypass only-people-I-liked.
- Lift the recipient cap of three pending offers.
- Show a decline, a table, or a location.
- Rank recipients or show anyone's points.
18 · Staff console
One screen at the bar, one at the host stand, one in the manager's hand
The console is the same web app under a staff login, installed on iPads. It shows tickets, requests, redemptions and the guest list. It never shows a browsable gallery.
Drink offers · accepted
Daniel
Mia · deliver to T7
Jun
Sofia · deliver to bar leftRequests and redemptions
KOR-7F3Q · Mia · first visitGuests tonight
Mia · T7Platinum
Daniel · T14Platinum19 · Growth loop
Inside-only is the exclusivity hook. The share link is how the outside finds out.
people are at KOR right now
Mia invited you. Check in at the door and your welcome drink is waiting.The room is visible only inside.
Why this works at a lounge
- The live count is a fact about right now, which is the only thing that moves someone off a sofa at 21:40.
- The reward is symmetric and immediate, so people send links while they are still deciding where to go.
- Referrals cap at five a month so points cannot be farmed.
- VIPs can bring two friends who get Gold for the night, which turns regulars into hosts.
20 · Psychology map
Every mechanic, the principle behind it, and where it lives
| Principle | Mechanic | Where |
|---|---|---|
| Foot in the door | Welcome drink for a scan and a sign-in; the bigger asks come later | Check-in |
| Endowed progress | Profile meter starts at 40% after sign-in; first-night card puts a guest ten points from Gold | Profile |
| Loss aversion | Welcome drink expires at 22:30; offers expire in 15 minutes; points expire after 90 days | Voucher, offers, tiers |
| Costly signalling | A drink carries information a like cannot; the recipient reads it as intent | Offers |
| Plausible deniability | Likes reveal only when mutual; declines show no reason | Deck, offers |
| Scarcity | Five offers a night; three pending per recipient; one boost | Caps, privileges |
| Reciprocity | An accepted drink opens a thread with a cheers already in it | Threads |
| Social proof | Live counters: checked in, drinks sent, drinks accepted; never names | Everywhere |
| Commitment and consistency | Rolling 90-day tiers reward regular visits and decay gently | Tiers |
| Status | Badges earned by loyalty, shown by choice; benefits that staff can see and act on | Card, door, host stand |
| Group dynamics | Table rounds: group consent lowers pressure, splitting lowers thresholds, tickets grow | Rounds |
| Exclusivity | The room exists only inside; outside sees a number | Share link |
| Control | Visibility modes, quiet mode, block, a manager one tap away | Settings |
21 · Game theory
A signalling game inside a congested matching market
The signalling game
The separating equilibrium holds as long as the drink is costly to the sender and free to the recipient, and as long as declines cost the sender nothing socially. That is why declines are private and why sending is free until accepted.
The congested market
Attention is the scarce resource. Left alone, offers follow a power law: a few recipients get dozens, most get none, and both sides churn. Caps are a rationing rule that forces senders down the list and gives every recipient a manageable inbox. The result on night one is a higher acceptance rate; the result over weeks is a larger visible pool. Slide 10 shows both.
Diversity in deck ordering is the same idea on the viewing side: bounded exposure per guest per window keeps the market thick instead of winner-take-all.
Mutual reveal removes the rejection cost
If unreturned likes were visible, the expected cost of liking would include embarrassment, and liking would fall. Hiding them makes the like free again, which raises the number of mutual pairs, which is the supply of matches the drink mechanic converts.
Tiers as a repeated game
A single night is a one-shot game with weak incentives to behave. Rolling 90-day tiers turn it into a repeated game: status is worth protecting, an upheld report costs fifty points and a pause, and the door list remembers. Cooperation becomes the rational strategy for anyone who wants to come back.
22 · Data model
Sixteen entities, seven of them gone by morning
Dashed boxes are erased at close. Solid boxes persist: they are the profile, the status, the connections and the safety record.
Presence is derived from Visit state plus heartbeat, never stored as a separate table. Deck order is computed per request and never persisted.
23 · Pilot gates
Five numbers decide whether the social layer widens beyond event nights
Also measured from night one
- Verified-handle share among visible guests
- Recipients with more than three pending offers (should be zero)
- Senders with zero acceptances per night
- Reports, blocks, quiet-mode uses and manager requests per night
- Referral links sent and friends arrived
- Time from scan to voucher on a real phone in the room
Gates
- Pilot → soft launch: staff run a night without the developer; voucher redemption above 60%.
- Event nights → every night: visible share above 30% on two consecutive event nights, acceptance rate above 40%, zero flooded recipients.
- Shelve social: visible share below 15% on four event nights with no lift in early check-ins.
24 · License it to other venues
Built for KOR, designed to be licensed: a recurring revenue line for the bar
Every mechanic is venue-agnostic: rotating codes, presence, the deck, offers, the tier engine, promotion rules, the staff console. KOR is the flagship and the reference case; other clubs and lounges pay monthly to run it.
Multi-venue from day one
The data model is tenanted by venue. Each venue has its own code secret, Wi-Fi IP, menu, promotion rules and staff. Guest accounts span venues; connections and tiers can be shared or isolated per group.
Pricing model (illustrative)
| Setup | NT$150k–300k: network check, screens, table cards, staff training |
| Monthly licence | NT$30k–60k per venue, tiered by capacity |
| Add-ons | Brand activations, group dashboard, POS integration |
Sequence
- KOR runs three months first and produces the measured case study.
- Sister venues in the same group next: shared guest accounts, separate rooms.
- Other Taipei lounges and clubs, then Asian cities.
- Ten venues on a monthly licence is a stable income line independent of bar sales.
Numbers are illustrative to show the shape of the model; real pricing follows KOR's measured results and costs.
25 · Investment
One fixed price to build it, one flat fee to run it
FlowOS builds, installs and runs the KOR app. The team flies to Taipei to survey the venue before design, and returns on site for the installation.
Included in development
- Design spec and implementation plan, derived from this deck
- Guest web app, staff console, presence service, tier and promotion engine
- On-site survey in Taipei: network, screen positions, table layout
- Installation: rotating-code screens, table cards, Wi-Fi configuration
- Staff training and on-site support on pilot night
Included in the monthly fee
- Hosting, servers and realtime services
- Monitoring and maintenance
- Updates and support
Venue hardware (access points, screens, iPads) is purchased separately at cost.
26 · Next step
Ready to build.
FlowOS will develop the KOR app: from this deck to the design spec, the implementation plan and the pilot night.
People and venue photos: Unsplash licensed imagery. Icons: Phosphor Icons (MIT). Type: Inter, Fraunces, Noto Sans TC, Noto Serif TC.