Skip to content

Glossary

Showliner uses precise words for things that overlap with everyday language. These definitions are generated from the project’s canonical glossary, so they can never drift from the product.

Entity

A first-class directory subject, a Performer, Venue, or Collaborator. The thing a workspace manages, fans support, and verification applies to.

Say it to users as: In Guides, use the concrete type, “your venue”, “the performer”, “a collaborator”, or “workspace” for the operator-side generic. Reserve “Entity” for the developer/API track.

Workspace

The account a person operates as, a Performer, Venue, or Collaborator they own and manage. One person can own and switch between several. A workspace is the operator-side lens on an Entity (the same brand seen from the public/directory side); it also holds the Unclaimed entities it has added for others.

Say it to users as: “workspace” is correct in Guides too, it matches the UI.

Stub

An Entity with no owner workspace yet, a placeholder a workspace created for an act/venue/collaborator that isn’t on Showliner (parentEntityId set, no managedEntityId). Becomes a full workspace when claimed.

Say it to users as: “Unclaimed”, on both the operator’s and the public’s view (chip tooltip: “Not on Showliner yet”); pairs with “Claim this profile”.

Claim

Taking ownership of an Entity, a Stub becoming a workspace someone owns (EntityClaim, claimService, /api/claims). About a brand, always ends in a workspace, always needs a real signed-in user. Only the workspace that keeps the Stub can start one: a claim carries the act onto every bill it is on, so another workspace on the bill that wants the act invited asks the keeper to send it. The claim link is the credential (whoever completes it holds the link that went to the act), not a match on the account’s email.

Say it to users as: “Claim this profile”, pairing with the Unclaimed chip.

Convert

A guest session becoming a registered account, the fan’s coins, badges and items stop being temporary (convertGuestSession, /api/auth/convert, adopt-guest-session for the OAuth arm). About a person’s login, and it creates no workspace: a fan owns nothing.

Say it to users as: “Save your account”, on the audience buttons and on the admin page they land on, which must agree.

Sign in

How a person authenticates. One spelling everywhere, sentence case (“Sign in”, not “Log In” or “Sign In”), because the app had both and mixed them inside single flows: the admin header said Login/Logout while the menu one component away said Sign in.

Say it to users as: “Sign in”, “Sign out”, “Sign up”, “Sign in failed”.

Collaborator

The third entity type alongside Performer and Venue (photographers, engineers, etc.). Stored in code as ServiceProvider.

Network

The collection of entities a workspace works with, built through connections, follows, and added (Unclaimed) entities. This is the page formerly labeled “Collaborators”.

Say it to users as: prefer naming the action over the bucket (“add an existing performer”); use “Network” when a collective noun is unavoidable.

Remove from Network

Taking an Unclaimed entity out of a workspace’s Network, the way back from a name typed onto a bill, a walk-up added at an Open mic, or a typo. Offered on Unclaimed entities only: a claimed Entity runs its own workspace, and the way out of that relationship is ending the connection.

Say it to users as: “Remove from Network”, on the entity card’s overflow menu. Say what survives (“shows they have already played still list them”), never “deleted” or “erased”.

Shared bill

Two workspaces that were both on the bill of a show that happened: a completed Event each of them agreed to be on, where neither was a Pencilled act. It is the evidence behind the Network page’s suggestion to make a connection: acts meet at shows, and the last bill is how most acts find the next one. Only a claimed Entity can be suggested, because an Unclaimed one has no workspace to connect to.

Say it to users as: “You’ve shared a bill”, with the show(s) named.

Not now

Setting a Shared bill suggestion aside. It belongs to the workspace, not to one teammate, and the other side is never told. It is answered by evidence, not by time: the suggestion stays gone until the two play another show together, and then it returns naming that show.

Invite suggestion

A workspace asking the workspace that maintains an Unclaimed act it shared a bill with to invite that act to Claim its profile, supplying the contact it has. Only the maintaining workspace ever sends the claim invite; the suggestion is never an invite itself, and there is no path around it. One per Unclaimed act, gathering every suggester; the maintaining workspace hears once, and an unanswered suggestion lapses after 30 days, after which it may be suggested again. Each suggester is told when the invite goes out, and nothing else: never another suggester’s contact, never a refusal. The invite names the acts that suggested it, and a suggester is told so before it suggests. The contacts a suggestion carries are discarded when it closes, whichever way it closes, except the one the claim invite was actually sent to.

Say it to users as: “Suggest an invite” (the suggester), “Mudhoney suggests inviting The Beths to claim their profile” (the maintaining workspace), “Invited by the Crocodile” (once sent).

Played together

The public form of a Shared bill: two Entities that shared a completed bill. A show is a public event, so its bill is public and nobody opts in (ADR-0045). Undisclosed acts never count, nor does an act that did not agree to be on the show. Between two other Entities it says that they played together and how many times, never which show, when or where. Either side may hide one link: everyone else stops seeing it, silently, until the side that hid it restores it. An Unclaimed act cannot hide links until it is claimed. On the public Scene, an Entity with public discovery off has no links at all, and is never counted or routed through.

Say it to users as: “Played with” (the viewer’s own), “Played together” (one degree apart), “Hide link”.

Scene

The web of Entities linked by Played together, seen from one workspace and explored like a graph: its own Shared bills closest in, and everyone they played with beyond, out to a chosen depth in Degrees. Venues are part of it, but Degrees never step through one. It reaches past the Network on purpose, to acts and venues the workspace has never worked with.

Degrees

How far apart two Entities are in the Scene, counted in Played together links between acts: one degree means they played together, “2 degrees from Mudhoney” means through one act they both played with. A venue is never a step: two acts that played one room on different nights are not 2 degrees apart. The familiar “six degrees” idea, said in the trade’s own terms.

Event

The scheduled plan for a happening, date, lineup, venue. Exists before and after; may never go live. Starting an Event instantiates its Room. An Event takes place at one Venue, or none (a house show), on one Stage: several venues at once is a Festival of several Events, and a presenting label is a Collaborator, not a second venue.

Say it to users as: “Event” in Guides and step-by-step instructions. The Showliner app says “show” in its everyday copy (“New show”, “Shows”), where it names the thing a person is booking rather than defining it.

Visibility

Whether an Event is public (the default: announced, so its bill is public and it draws Played together links) or private (a wedding, a corporate party, a private hire: never listed on a profile, never drawn on the Scene, never reachable through a Standing link door). Only the Organizer sets it, and every workspace on the bill can see it. Before the Event completes it can be switched either way; afterwards it can only become private. Private hides the Event from people who weren’t involved and changes nothing for anyone who was (ADR-0046).

Say it to users as: a Public / Private toggle on the Event.

Festival

An umbrella over several ordinary Events that are promoted as one: a multi-stage day, a crawl across a neighbourhood’s venues, a weekend. Each Stage on each day is its own Event, with its own Lineup, Room and Running order; the Festival holds only what is shared across them. A Festival is never itself an Event, so it has no Lineup, no Room and no Run state of its own. It is one dated instance (“Dark Bloom, October 31, 2026”), never the recurring brand behind it: the brand is the organizing workspace, and a festival returning next year is a new Festival. Its Organizer organizes every Event in it. A venue hosting a stage is on that stage’s bill as the Venue, not an Organizer, unless it is made one for that Event; a stage curated by someone else (a label presenting its own stage) has that curator as an Organizer of that Event alone. Neither sees another stage before it is revealed, and only the Festival’s Organizer may Reveal its acts, because the reveal is the festival’s announcement plan and one stage going early breaks it. Its standing rules hold on every stage. Asking or telling every act can be set on the Festival, and then covers every act on every Event in it, stages added later included; a stage adds its own rules on top (the drum kit one stage provides) but cannot switch a festival rule off. Its standard terms are a starting point, never a price. Each act is still its own Booking with its own Offer: the Festival’s standard terms (an amount and the conditions every act agrees to) fill in each Offer, the amount can differ per act, and each Offer carries its own copy, so changing the standard later changes nothing already sent. A show already on the calendar can join one. It can be added to a Festival or turned into a new one while it is still to be played, if it is not part of a series, and it can be taken back off before it starts. Acts already public stay public, because a Reveal can’t be taken back; acts told afterwards wait for the reveal. Its status is read off its Events, never kept. It is Confirmed when every stage is, live while any stage’s Room is, and over when every stage has completed or been cancelled. Cancelling one stage is an ordinary Event cancellation. Cancelling the Festival cancels every stage that has not yet happened, tells each act once (not once per stage), and leaves a stage that already finished completed, because those acts played. Fans meet it stage by stage. Each stage has its own Room and Join code, and there is no festival-wide Room or chat: each stage is its own crowd, as it is at the real event. The Festival has a public page (the revealed lineup by stage, the schedule once published, what is on now) unless it is private.

Say it to users as: “Festival” (“New Festival” in the create menu); once created it is called by its own name. Its Organizer works it as one thing, from its schedule, and a stage’s Event is reached through it and named after it (“Dark Bloom · Logan House”); everyone else on a stage sees an ordinary show of their own, marked “Part of Dark Bloom”.

Quick start

The on-ramp for running something now, an Open mic someone decides to hold this evening, a last-minute gig an act wants a QR for. Each situation creates an Event and starts it in one gesture, ending on the join QR. There are exactly two, and they fork on one real difference: who fills the Lineup. An Open mic fills itself from walk-ups, which needs a public signup address and a queue to work; a Live show is filled by the operator, which needs none of that. Nothing else earns a fork, in particular headcount does not. A solo act and a three-act bill were briefly separate starts, and they are the same start: the number of acts is not known at go time, and a Lineup is editable while the Room is open, so it never has to be. It is not a wizard. An early design put both behind a generic button, on a chooser screen, asking the operator something they already knew when they opened the app. Named directly, neither asks anything at all: tap, and the show is live. Anywhere this grows, the question to keep asking is whether a screen collects an answer or merely confirms one the operator arrived with. It always produces an ordinary Event. There is no lighter object and no second kind of night: the situation chosen at the start is a preset, not a type. It sets fields and is then forgotten, and every surface afterwards decides what to show from what is actually true, an Open mic shows walk-ups because open mic is on, never because a tile was tapped. This is the resolution the Economy and tiered-Event entries already reached: capability, not kind. The tell that it is right: a planned open mic gets the same treatment without going near Quick start. The one thing recorded is provenance, for learning whether the on-ramp works, and nothing user-facing may read it. Its test for asking a question is “can this be fixed at 9:15pm, with the Room already live?” Everything can, the name, the venue, the Stage, the whole Lineup, so nothing is asked. The one thing that fails the test is whether the workspace can actually be paid: a Connect account needs documents and minutes, so that is raised before the show rather than discovered after it. It is not a question, though; it is a statement of readiness, and it never blocks a start. Each carries a plain line beneath it, and that line does the teaching, someone can reach a working QR without ever learning what a Room is. “Quick start” stays the team-canonical name for the set, and is fine as a Guides heading.

Say it to users as: the situations name themselves, “Quick start” is never a label on anything. They are “Open mic” (Anyone can sign up on the night) and “Live show” (You add who’s playing, before or during), “Live show” rather than bare “Show”, which is reserved for marketing voice and must not stand where an Event or a Room is precisely meant. They appear together under a Start now heading in the create menu, above the divider that separates them from the things that merely make an object (a planned Event, a standalone Room, a store item), and again on the dashboard, which is where someone in a hurry actually lands. The grouping is not decoration: starting one puts a live Room in front of an audience, while everything below the divider costs a back button, and a flat list would make those neighbours.

Room

The live digital space where fans join, chat, earn Housepower/Cheer, and trigger effects on the venue’s displays. Usually created by starting an Event, but a Room can also stand alone, created directly, with no Event, and with no venue or bill behind it (see Economy). An Event has at most one live Room at a time.

Say it to users as: “Room”.

Join code

How a fan gets into a Room, a short code and the QR that encodes it, both pointing at the same audience URL. Per-room and minted with the Room; it dies when the Room closes. It is shown in two places for two different reasons. On the venue display it is the wall telling a room how to get in. In the Operator console it is for an operator who has no screen, a phone behind a bar at an Open mic, and can be taken full screen to hold up or leave on a table. Both render one code from one URL: a fan scanning a phone and a fan scanning the wall are joining the same Room by the same address. The code is offered as text beside the QR deliberately, because the two fail in different rooms: a camera needs light and a steady hand, while a code read aloud carries across a loud bar and over a PA.

Say it to users as: “Join code”; “Room code” for the letters alone.

An Entity’s durable public address, printed once and never reissued, the QR on a merch table, the sticker by the door, the link in a bio. Scanning it joins whatever Room that entity is on the bill of right now, regardless of which workspace started that Room; when nothing is live it falls through to the entity’s public profile, which carries a card saying so and what is next. Its whole value is that it stands: it outlives every Room, so a weekly open mic and a touring act print one sign instead of a new one every show. It is a door, not a place, deliberately a different address from the profile it falls back to, because the two are reached with different intent. Someone who tapped a link in a bio came to look, and auto-joining them would hijack that; someone who scanned the code on the table came to get in. One address cannot honour both. At a Festival the door asks which stage only when it must. A venue or an act is on one stage’s bill, so its link joins that stage’s Room as usual; the festival’s Organizer is behind every stage at once, so its link opens the festival’s page showing what is on now, and the fan picks a stage. On the bill of, never owned by: a performer’s sign sits on their merch table inside someone else’s venue, so keying on ownership would kill it on exactly the nights the act is booked. The fan’s question is “is this act playing right now?”, which ownership does not answer. This is safe without a new rule because a live Room’s lineup already carries disclosed, accepted participants only, so a Pencilled act can never be exposed by it. The address is a handle the workspace chooses, /@thecrocodile for the profile, /@thecrocodile/join for the door, and /@thecrocodile/tip for the tip jar: a third intent, so a third address. Someone who scanned a “Tip” sign came to tip, so it opens the tip sheet straight away rather than dropping them into a room to look for a button. /@thecrocodile/merch is a fourth, for a sign on the merch table: it sends the fan straight to the entity’s Merch link, and falls through to the profile, unexplained, when there is none. Handles are case-insensitive (a sign set in caps must still resolve), and a workspace may rename: the old handle redirects here for good rather than being freed. That is not a courtesy, a released handle must never be re-claimable, or a sticker printed last year quietly starts pointing at a stranger’s room, with nothing anywhere appearing broken.

Say it to users as: “your Showliner link”, “your QR”; “handle” for the name itself.

An Entity’s link to the store where it already sells merch (Bandcamp, Shopify, Big Cartel), rendered to fans as a Merch button: on the act card in a Room, on the venue’s line in a Room, under Phone lock, and on the public profile. Off-platform by design (issue #43, phase 1): the store is the merchant of record and owns tax, shipping and refunds, so Showliner moves no money and no Stripe setting changes. It is its own field rather than a social link, because a social icon reads as “follow” and this one reads as “buy”. Set by the entity itself, or for an Unclaimed one by the workspace that maintains it, on the same terms as its name and social links. Hidden entirely when unset, never explained (ADR-0024). Taps are counted per Room into the show’s archive, which is the number that decides whether a native checkout is ever worth building.

Say it to users as: “Merch”, “merch store link”.

Show

Marketing-voice word for a live Event/Room happening. Fine in headlines and prose (“Run your show”); never a precise term in how-to steps, say Event or Room there.

Advancing

The phase of an Event between booking and show night, confirming the lineup, merging stage plots over the house backline, settling logistics and load-in. In-app this is just editing the Event; “advancing” is the live-industry word for it. The marketing lifecycle frame is Book the show → Advance the show → Run the show. It is a two-way exchange, not a briefing: the Venue tells the act load-in, doors, backline and wifi, while the act owes the Venue its input list, party size, merch and arrival. Each advance item therefore knows who owes the answer (owedBy), and an item owed-but-unanswered is outstanding, completeness is derived from that, never tracked as its own status. Advancing has no separate document object; the advance is the Event. An advance item has exactly one owner, the organizer, or one named act. Asking three acts on a bill for an input list makes three items, not one shared question with three answers: acts answer differently (a file, a note, “same as last time”), and an item that only one party may write is what keeps “answer only what you owe” a single comparison. Acts are unaffected either way, each sees only what it owes. The multiplication is the organizer’s problem alone, and it is a presentation problem: group by act, because the question before doors is “what am I still waiting on from Mudhoney?”, never “who owes me input lists?” Asking every act for something is a standing rule about the bill, not an action taken on it: it holds for whoever is on the bill, so an act added a fortnight later is asked too, without anyone remembering to. A one-shot expansion is the failure mode to avoid, it leaves a late addition owing nothing and appearing in no waiting-on list, which reads identically to an act that has already answered. The organizer can also tell one act something, not just the whole bill: an item the organizer owes may be addressed to one act, and then only that act and the Organizer read it. A call time is the first of these (when this act must be there, distinct from an event-wide load-in); a per-act soundcheck is the same shape. Telling every act is the mirror of asking every act: a standing rule that gives each act on the bill its own addressed item, whose value can follow from the act’s Set time (“60 minutes before your set”) and moves when the set time does, until the Organizer sets one by hand, after which that act’s value stays where it was put.

Say it to users as: “Advance the show” in marketing and Guides headings, always beside the concrete tasks (confirm the lineup, merge the plots, settle load-in) so the term teaches itself on first read. “Outstanding” for an unanswered item the other side owes.

Showliner app

The native phone app for running a Workspace between shows, the advancing surface: the calendar, the events, the lineup, the invites and claims. Workspace-agnostic: a Venue, Performer, or Collaborator workspace uses the same app, because entity type is a property of the workspace, not a mode of the app (the same resolution EventView reached, capability, not layout). iPhone first, Android to follow. Called plainly “Showliner”, with no qualifier: the operator is the paying customer and fans never install anything (the fan experience is the web, entered by QR), so the unqualified brand belongs to the operator app, and it survives the app later growing a fan side.

Say it to users as: “the Showliner app”.

Organizer

The workspace running an event (it holds the event’s admin role). Owns the event’s settings, lineup, and guest access.

Say it to users as: “Organizer”.

Event authority

A workspace’s authority on an event has three levels (data: SessionMember.role = admin / participant / viewer). Only Organizer is a named role in the UI; the other levels are surfaced as actions, e.g. “Make organizer”, “Remove organizer access”, “Set to view-only”, never as a role noun.

Lineup

The ordered bill of performers on an event, and the single ordered truth for the night. The Venue and Collaborators appear on the event but are not “on the lineup”. The Running order is the operator driving through this list, not a second list beside it, so there is exactly one answer to “who is next”. An act on the Lineup is still to come, on, or already played, and which one is a recorded fact rather than a position: an act that has gone on carries the record of it, so the Lineup can be reordered mid-show without rewriting what already happened. An Open mic is the case that makes this visible, because its Lineup is built live by walk-ups rather than booked in advance.

Say it to users as: “lineup”.

Set time

When an act on the Lineup is planned to start and finish. Before the show the times decide the order: on a bill where every act has one, the Lineup’s order is the order of start times, so the two can never disagree; a bill without times keeps the order the Organizer set. On the night the Running order decides, and a set time is never rewritten to match what happened: it stays the record of the plan beside the time the act actually went on. Nothing happens when the clock reaches a set time: the act on stage changes only when the operator goes live, and the venue display follows the Running order, never the clock. Two acts overlapping on one Stage is a warning, not a refusal. An act always sees its own set time; everyone else sees set times once the schedule is published. On an ordinary Event that is the moment its acts are revealed. A Festival publishes its schedule separately and later, because festivals announce who long before when. Unlike a Reveal, publishing can be undone, since a time is meant to be corrected; once published, every change tells the acts it moves.

Say it to users as: “Set time”, “Set times”; “Publish the schedule”.

Open mic

An Event whose Lineup is built during the show by walk-ups rather than booked in advance. Signing up is public and account-less: someone at the bar scans a code, types a name, and is on the bill, so an Open mic is the case where Booking never happens at all, and the whole commercial axis stays untouched. A signup becomes an ordinary lineup row, not a parallel list beside one. Pre-booked acts and walk-ups share the same Lineup, which is what lets a night open with a booked feature and fill out with whoever turns up. It is a property of the Event, never of the Room, which is why an Open mic cannot be run from a standalone Room, and why anything that starts one has to start an Event.

Say it to users as: “open mic”.

Walk-up

A person who signs up to an Open mic on the night. Usually has no Showliner account and often no Entity, signing up creates an Unclaimed performer for them, which they may later claim.

Say it to users as: “walk-up”; addressed directly as “you’re up next”.

Slot

A numbered place on an Open mic’s Lineup. The host says how many there are; slot 7 is the seventh act to go on. Booked acts hold slots too, numbered with everyone else, so a feature booked for slot 10 is the tenth act whoever fills slots 1-9. A slot is a position, never a time: an open mic runs late, and a slot defined by the clock would be wrong after the first overrun. No time is shown beside a slot, not even an estimate: changeovers and a loose start make any “about 9:10” wrong (dropped 2026-10-14). An empty slot is a gap in the Lineup, not a row on it. A Pencilled act never holds a slot: showing its slot as taken would tell strangers a secret booking exists, so it waits outside the numbering until it is disclosed.

Say it to users as: “slot” (“Slot 7”, “3 slots left”).

Sign-up screen

The host’s own device (an iPad by the door, a phone passed around, a laptop’s browser) turned into the place walk-ups sign up: the open mic’s code for anyone who would rather use their own phone, the slots with who holds them, and a way to sign up right there. The digital form of the paper sheet on the bar. A sign-up made on it never needs approval, because whoever used it was physically in the room, which is the one thing a scanned code cannot promise; approval, when the host wants it, applies to sign-ups from people’s own phones only. It works at any time before the show, so a host can put regulars in their usual slots during the week, while sign-ups from phones open only when the host says (an hour before the start unless changed), and the screen shows its code from that moment. It clears itself after each sign-up so the next person never sees the last one’s details.

Say it to users as: “Sign-up screen”.

Event participant

The record linking an entity to an event; surfaces as the Organizer, the performer lineup, the Venue, or a Collaborator.

Say it to users as: no generic noun, name the concrete role, or say “everyone on the event”.

Fan

An audience member in a Room, a registered user or a no-account guest. Earns and spends Housepower/Cheer.

Say it to users as: “fan”, or “audience” collectively.

Guest

A person with no Showliner account, either a no-account fan in a Room or an event invitee who hasn’t signed up. Becomes a registered user / workspace by claiming. A Guest is not limited to looking: every counterparty action in the booking loop is completable without an account, accepting an Offer, answering an outstanding advance item, acknowledging a Settlement, with authentication stepping up to an emailed one-time code for the consequential ones. See ADR-0015. The premise underneath it: most acts will never sign up, and a feature that assumes otherwise does not get used, it gets worked around by text message, which is the situation Showliner exists to replace. So an account may unlock a better way to do something, never the only way. A Stage plot answering an outstanding input list is the pattern: acts with a workspace point at their plot, everyone else uploads a photo or a PDF, and the venue’s item is answered either way. A question only an account-holder can answer is an unanswerable question for most of the bill.

Say it to users as: “guest”.

Crew

The marketing-voice word for the people who work a show (sound, photo, video, lights), the humans behind Collaborator entities. Acceptable in marketing copy only; the entity type itself is always Collaborator.

House currency

A Venue’s entity currency, earned by fans for time spent in that venue’s rooms, specific to that venue. Default platform name: Housepower; Pro workspaces can rename it.

Fan currency

A Performer’s entity currency, earned by fans at that performer’s shows, portable across every venue they play. Default platform name: Cheer.

Verification mark

The entity-level marker that an admin has confirmed an Entity is who it claims to be (verificationStatus === 'verified'). It belongs to the Entity, gates public discoverability, and renders on directory/profile surfaces. It is not a Badge and is never worn by a User in chat.

Badge

A platform-owned image a User equips to display next to their name in chat, everywhere on Showliner. Badges belong to the platform catalog and are granted to Users; they are never uploaded by workspaces.

Identity badge

A Badge the platform grants automatically from user-level state (e.g. Staff, Founder). Cannot be bought, configured, or revoked by a workspace.

Supporter badge

A Badge granted automatically from a User’s active follows of qualifying Entities (those whose workspace plan entitles it). Recomputed as follows start and end; never purchased; the workspace has no control over the grant.

Qualifying entity

An Entity whose workspace plan entitles its followers to supporter-badge credit.

Grant

How a User comes to own a Badge, always automatic, never a purchase.

Unlock

How a fan comes to own an Entity’s emote set, a one-time purchase in that Entity’s currency.

Equip

A User’s choice of which owned Badges display next to their name, capped at three, one per Badge family. Equipping is global, not per-room.

Badge family

A ladder of related Badges (e.g. the Supporter tiers) of which only the highest earned rung ever displays.

Text

An SMS message Showliner sends to a phone number the recipient provided for that purpose, an event invite, an open-mic “you’re up next” alert, a login code.

Say it to users as: always “text” / “text message”, “we’ll text you”, “Text invite”. Venue operators and performers say “text”; “SMS” reads like a telecom spec.

Booking

The commercial relationship with one act on one date. A three-act bill is three Bookings, not one, they are negotiated separately, agreed separately, and settled separately. This is how the trade uses the word (“we’ve got Mudhoney booked”, “I have three bookings that night”), and it is the unit everything commercial hangs off: an Offer is made on a Booking, a Deal freezes one, a Settlement reckons one.

Say it to users as: “Booking”; Booking status for where one stands.

Booking status

Where a single act’s Booking stands: pencilled → offered → confirmed → settled, or released. Stages are sequential, so an act has exactly one, the furthest it has reached, and surfaces show that one status rather than parallel badges for invite, terms and settlement.

Say it to users as: the stage word, carrying its money only when money was recorded, “Offered · $400”, “Confirmed · $400”, or a bare “Confirmed” when there is no Deal. A Booking with no money on it is complete, not half-filled: never render a placeholder, a dash, or “no terms” where an amount would go. Before an act is told at all, it reads “Not notified” (see Disclosure).

Run state

An Event carries two independent lifecycles. Run state (Event.status) is whether the show is happening: scheduled → active → completed | cancelled. The commercial axis is Booking status, which lives per act and rolls up to the Event (Event.pipelineStatus, a code-only name, never shown): inquiry → pencilled → offered → confirmed → settled, or released. A confirmed booking is still scheduled on the run axis; the two never encode each other.

Assumed complete

A past show that Showliner moved to completed itself because nobody ended or cancelled it: a day after its end (or its start, with no end), when at least one act on it was disclosed and the date was not released. Covers a show that never had a Room and one whose Room closed without anyone pressing End. It is provenance, not a fifth Run state: the show is completed like any other, recorded as completedVia: 'sweep' beside a person’s 'person'. Unlike a show a person ended, it can be corrected to cancelled for 7 days, and its post-show prompt waits 24 hours for that correction. ADR-0044.

Say it to users as: “Marked complete”, with “Marked complete automatically after the show date” and, during the 7 days, “Didn’t happen? Mark as cancelled”.

Pencilled

A date a Venue is keeping warm for an act before either side has agreed, the informal, single-act, small-room version of keeping a slot. Carries no priority and no expiry protocol.

Say it to users as: “Pencilled”, and the verb “pencil in”.

Hold

The formal, prioritized claim on a slot: a stated priority (1st / 2nd / 3rd), an expiry, and a challenge protocol that forces the higher hold to commit or drop. A larger-venue practice. The word is reserved and must not be used for a Pencil, shipping “hold” as a synonym for pencilled would leave us writing “hold levels on a hold” when the real feature lands. Until it exists, say Pencilled.

Confirmed

Every act the organizer has disclosed has agreed to play. Money is not part of it, a Deal is optional enrichment, so a venue that settles in cash, runs a free showcase, or simply doesn’t keep its books here never touches a money field to book a band. It does not claim the bill is closed, a Confirmed Event may still carry undisclosed Pencilled acts while the organizer shops a remaining slot, and those acts neither block the confirmation nor become visible because of it. The word describes the parties, never the completeness of the lineup.

Say it to users as: “Confirmed”, and always beside what is still open, “Confirmed · 1 slot still being shopped”. The word alone overstates on a bill that is still being worked.

Released

A Pencilled or offered date that never firmed up, the venue booked someone else, the act went quiet, the deal died before agreement. It is invisible: nobody was notified, nothing was announced, no tickets exist. The only terminal-failure state on the pipeline axis.

Say it to users as: “Released”, verb “release the date”.

Blackout

A date a workspace has declared itself unavailable: a venue closed for renovation, an act on tour elsewhere, a stage promised to a private hire. It suppresses pencilling and raises a conflict without being an Event, there is no bill, no pipeline status and no money, and it never counts toward the booking meter. Scope narrows rather than adds: the whole workspace, one venue, or one stage.

Say it to users as: “Blackout” (noun), verb “block the date”, the UI reads “Block out a date”.

Avails

Publishing availability so other workspaces can see it, the booking industry’s term for an act or venue advertising when it can be booked. This is a deliberate publish, and the opposite of Disclosure: disclosure withholds what nobody chose to reveal, avails broadcast what someone did. A shared Blackout sends only the fact that a date is unavailable, never the reason, which stays with its owner.

Say it to users as: “Share this blackout” / “Shared with other workspaces”. The word avails is industry jargon and stays out of the UI.

Disclosure

Whether an entity on an Event knows it is on the Event. An undisclosed participant is on the record for the Organizer only, no notification, no access, invisible to the entity itself, which is what makes it possible to pencil an act, or to line up a backup, without announcing it. Disclosing is a deliberate, one-way act. It is the first step of a ladder of who knows about an act: not notified (the Organizer only), notified (the act too, seeing its own Booking and no one else), revealed (everyone else; see Reveal). An act is always on exactly one rung, so it can never be revealed before it is notified.

Say it to users as: Organizer-side only, “Not notified yet” as the state, “Notify the act” as the action. There is no act-facing word, because an undisclosed participant cannot see anything.

Reveal

The step that makes a notified act known beyond itself: to the rest of the bill, to a Festival’s other acts, and to the public. Before it, an act knows it is booked and sees nothing about anyone else, which is how a festival keeps its lineup under embargo until announce day, releases it in waves, and keeps a surprise guest secret. On an ordinary Event an act is revealed the moment it is notified, so nothing waits; a Festival holds its acts at notified until the Organizer reveals them, and may reveal some and not others. An act going on stage is revealed, and so is everyone who played once the show is over, since the night happened in public. On a private Event a reveal reaches the bill and stops there: Visibility still keeps it off every public surface. A reveal is one-way, like Disclosure: what the public has seen cannot be unseen, so the Organizer is shown exactly who becomes visible, and to whom, before confirming.

Say it to users as: “Reveal” / “Revealed”, and “Not revealed yet” on the Organizer’s side; the act is told its lineup is not public yet.

Stage

A distinct physical performance space at a Venue, the main room, the back bar, the patio. A Venue has one or more; an Event occupies one. Stages are what the booking calendar lanes against, and what a Blackout and a double-booking check apply to.

Say it to users as: “Stage”; a single-stage venue never has to think about it (its one Stage stays implicit).

Offer

A proposal of commercial terms for an Event, sent by one party to the other and awaiting accept / counter / decline. Append-only and versioned: a counter is a new Offer, never an edit of the old one. Either side may offer, a Venue offering an act and an act quoting a Venue are the same object in opposite directions.

Say it to users as: “Offer”; the verbs are “send an offer”, “counter”, “accept”, “decline”.

Deal

The agreed commercial terms of record on an Event, what the parties actually shook on. Usually created by accepting an Offer, and frozen at that moment: a Deal is never edited. Changing agreed terms means sending a new Offer and getting it accepted, which supersedes the previous Deal. At most one Deal is in force at a time. Everything financial computes against the Deal: Settlement, payment tracking, reporting.

Say it to users as: “Deal”; “the agreed terms”.

Recorded deal

A Deal the organizer wrote down after agreeing terms elsewhere, a phone call, a text, a handshake at the bar. It settles like any Deal, because a venue paying cash still needs a reckoning, but it is attested by one side only: the act never assented here. Every surface showing one must say so.

Say it to users as: “Recorded” (never “Agreed” or “Confirmed” for this one), and on the act’s side “Recorded by The Crocodile, not confirmed by you”.

Entity contact

A named, role-tagged person to reach at an Entity, “Dave, booking” / “Sara, production”, held on the Entity and maintained by the workspace that owns it. A claimed Entity keeps its own contacts current, so counterparties always read live truth; an Unclaimed Entity’s contacts are maintained by the parent workspace and become self-maintained when claimed.

Say it to users as: “Contacts”, “who to reach”.

Roster

The people an act works with, held on the Entity and maintained by the workspace that owns it, exactly like Entity contacts. It answers who plays with this act, never who is on the bill. Deliberately a pool, not a membership. “The current members” was the first definition and it was wrong: it serves a band and abandons everyone else. A five-piece’s pool is its membership, set once and never revisited. A solo artist who assembles friends per show has a pool of eight and draws a different four each time, and under the membership reading his Roster is either permanently empty or a list he overwrites every show, destroying last month’s record to write this month’s. One object, two lifetimes, and neither act has to understand the other’s usage. A Roster member may be marked as playing by default, which is what lets the two lifetimes share a screen: the band marks all five and never touches it again, while the solo artist defaults his usual rhythm section and swaps the horns. The default is a property of the member, never a saved set, a saved set would be a second list, needing reconciliation with the first. What the defaults seed is the show’s Personnel. The Economy reads the Lineup, never the Roster. This is free by construction rather than enforced: a Roster member is not an event participant, so no code path that mints currency can see one. Cheer therefore follows the slot, not the person, Liam playing his own set and playing bass in The Whatevers on the same night is on the Lineup once and on a Roster once, and only the Lineup pays. Performer entities only. A Venue’s people are Team members and Entity contacts; a Collaborator sending a different camera operator each show is answered by advancing, not by a Roster. A Roster exists to seed a show’s Personnel, and only an act plays a slot.

Say it to users as: “Members” on the act’s own page, where standing on the act makes it unambiguous; “roster” when a collective noun is unavoidable. The members marked playsByDefault are “Regulars”, rendered as a zone you move people into and out of rather than a per-row property, because every other chip in the product is a status you read. A zone is labelled whenever it has anyone in it, the first cut hid both headings unless both zones existed, which meant a band that had just typed in its members (they default to Regulars) saw an unlabelled list where every row carried a bare minus, and no hover tooltip to explain it on the phone where it is read. Never “group”: that word is already the entity-level distinction here (an individual’s own act versus the band they are in), so “add Greg to the group” would be ambiguous between putting him in the band and making him a regular.

Roster member

One person on an act’s Roster, a name and what they do (“Greg, bass”). Not an Entity: no Cheer, absent from the directory, never on a Lineup. Adding one costs nothing, which is the point, a dep drummer for one night is a row, not a profile. A Roster member may point at a Performer Entity, and that optional pointer is how an individual is linked to a group: Liam’s solo act is a real Entity with real Cheer, and the row on The Whatevers references it. It is a reference, not a join, the row’s own name is display truth, so a linked act renaming itself never silently rewrites somebody else’s bill. An unlinked row is a claimable slot, and deliberately the best claim vector in the product: “you’re listed on bass in The Whatevers, claim your own profile” invites a musician to claim their own act. Today’s accidental version invites them to claim a stub somebody else minted for them. Claiming a roster row creates no connection. An EntityConnection is a consented handshake between workspaces, and minting one as a side effect of a claim would hand two people a business relationship neither agreed to, the same class of mistake as the bug that started this. The claim’s closing screen offers one to both sides instead, which is the only moment both are demonstrably paying attention. The two stay independent deliberately: a session player is on six Rosters without doing business with any of those workspaces, and an act is connected to venues it shares no Roster with. A Roster member can now say who they are. userId, a plain User, never a workspace, is stamped by the person themselves from the act’s per-show share link, which is what makes ADR-0035’s readership rule checkable at last: access is a live check against the Roster, and until a member could carry an identity there was nobody to check. It is deliberately a second axis beside linkedPerformerId, never a reuse of it: who this person is and what act they front are different questions, and answering the first through the second would mean handing somebody an act, and a Cheer, in order to hand them a chord sheet. The act may clear an identity (a mis-tap needs an escape hatch) and may never assign one, or it could read a member’s material as them. See ADR-0035’s amendment and ADR-0037 phase 3.

Attachment

What an act shares within itself for one show, its set list, charts, chord sheets. Held on the Booking, readable by that show’s Personnel, and attached rather than authored: Showliner stores the file the act already has and does not try to be a songbook. It is not a set list editor and should not become one. Bands have better tools for writing one, and a chart library is years of work, the switching cost is the whole game. What Showliner uniquely holds is context: this material, on this date, with the people who played it, as part of the record of the night. The same shape a Stage plot already uses to answer an Input list, point at yours if you have one, upload a photo if you don’t. Its link is an on-ramp to identity, never an alternative to it. A per-show magic link reaches people with no account (a chord sheet is the lowest-consequence thing in the product, and ADR-0015 scales authentication to consequence), and the page will carry a quiet “this is you” that mints a plain User, never a workspace. The link is never a dead end and the account is never a gate. Built: the share link (one URL for the band’s group chat, /set/:token, dying with the show). Not built: the per-member link and the “this is you” conversion, which wait on RosterMember.userId. Nothing here is access-controlled, and no surface may say otherwise. An uploaded file is unlisted, stored by us, linked from nowhere, take-downable, but it lives in a public bucket, so its URL is the key; a linked one is external, opening wherever the act keeps it, where the access is theirs and a reader may hit a “request access” wall we can do nothing about. Two kinds, two sentences: one sentence over both is true of one and a lie about the other. The share link is bearer authority, revocable only by rotation. The word is unambiguous only in context, exactly like “Members”. An event will want it too, a venue attaching a contract, a poster or an invoice to a booking, and that one is shared with the act, where this one is private to the act’s Personnel. One noun over two readerships is the shape that leaks. Standing on an act’s own show surface, “Attachments” means the act’s own; anywhere else it takes a qualifier, and neither sense may inherit the other’s readership by sharing a word. See ADR-0037.

Say it to users as: “Attachments” on the act’s surface; name the thing itself where you can, “set list”, “charts”.

Personnel

Who is playing one show, the subset of an act’s Roster that is on the bill that night, held on the Booking (one act, one date). Seeded from the Roster members marked as playing by default, adjusted per show; a name not yet in the pool joins the Roster by being added here, so nobody is ever typed twice. The distinction is the industry’s and Showliner adopts it rather than inventing one: jazz credits list Personnel per session precisely because the leader is constant while the players change per date. The test both words have to pass is the one “lineup” fails, “Greg is on Liam’s Roster” and “Greg is on tonight’s Personnel” each read correctly and neither can be mistaken for the other. Personnel is the readership. Whatever an act shares within itself for a show, its set list, charts, chord sheets, is scoped to that show’s Personnel: never to the act’s whole Roster, and never to the Event. A dep drummer gets tonight’s material and not the back catalogue, and is not carrying it into somebody else’s band next month. The Event is the surface an act shares with the venue and the rest of the bill; the Personnel is the surface it shares with itself. This paragraph is about the material, not the names, who is playing is readable by the Organizer (below), while what they are playing is not, and the two rules are easy to collapse into one another by accident. Personnel feeds advancing; it never bypasses it. Party size, and a door list, where a venue asks for one, is answered from the Personnel with a tap rather than typed, which is the shape ADR-0028 already gives a Submitted plot answering an Input list: an object in the act’s own domain answers an item the venue asked. What is stored is still an ordinary answer the act gave, so the venue reads a number that holds still rather than one that changes under it when a friend is added at 4pm. Personnel changing afterwards mints no new state, completeness stays derived, but the advance surface shows the current Personnel beside the item, so an act can see it has outgrown what it told the venue. That is presentation, not a status field. The Organizer reads it; co-participants do not. Three viewer classes look at a bill and they are not one group. The act manages its own Personnel. The Organizer reads it, a venue has an operational need (door, hospitality, load-in), and reading the live list is better than a headcount typed once in March, which is what makes this one source rather than two. Co-participants see nothing, not even the count: ADR-0014 already names the co-participant as the dangerous reader on a bill, and an opener inferring a headliner’s scale or budget from its headcount is that leak wearing different clothes. So the gate is a viewer check, and deliberately not the ownership check the Stage plot beside it uses, a plot has a view-only state for the venue, and Personnel’s readership is drawn differently. Counterparty visibility is not publication. A venue is a working counterparty, which is the same reasoning that makes an Entity contact readable by the people it exists to be reached by. Fans and the directory remain no, see Roster. A Personnel surface shows people, never material. Personnel is also the readership for the act’s set list and charts, so the surface an Organizer can open must not be the way into them. One dialog with a hidden zone is how that leak ships; the material belongs behind a surface only the act reaches. The row is the record; the access is not. Once the act has gone on, its Personnel is history: the row freezes exactly as a played act on the Lineup does, and carries the name it was set with, so a later tidy-up of the Roster can never blank out who played. Whether someone can still open that show’s material is a live question, answered by whether they are on the act’s Roster today, which makes removing someone from the pool the one gesture that ends access, and is why there is no per-show revocation. See ADR-0035.

Say it to users as: “who’s playing” on the show itself; “personnel” where a noun is unavoidable.

Economy

The set of currency entities a Room awards into, its Venue (paying Housepower) plus the performers on its bill (each paying their own Cheer). A Room’s Economy is derived, never configured: attach a venue or add a performer and the Room has one; do neither and the Room has no Economy. A Room without an Economy is a supported, first-class state, not a broken or half-made Room. The currency surfaces (wallet, store, gift) are simply absent, and everything else a Room does, chat, the display, panels, QR join, the lighter, moderation, runs unchanged. This is what makes a Room usable for a networking night, a pop-up open mic, or any gathering a Collaborator workspace throws on a projector with no venue and no booked act.

Say it to users as: don’t name it. A Room with an Economy shows its currencies; one without doesn’t mention them. Never tell a fan a room “has no economy”.

Panel

A single piece of audience-facing content composed for the venue display, a titled card with body text, a background image, and a theme. Owned by a workspace and reusable across shows; a Panel is authored ahead of time, not typed at show night. The word is reserved for signage: an operator-facing console zone is a Pane.

Loop

An ordered, timed rotation of Panels that plays on the venue display, the venue’s signage reel (house rules, drink specials, upcoming shows, sponsors). Owned by a workspace, assigned to a Room one at a time, and each Panel carries its own dwell time. A Loop plays between sets, pre-show and changeover, and yields when an act takes the stage. Like a Visualizer it has a placement, but only two steps: sharing the screen with the room info, or full screen. There is no third step, between sets there is no act card to sit behind.

Say it to users as: “signage loop”, or just “loop” once the context is the display.

Visualizer

A looping, silent video that plays on the venue display while an act performs, the moving backdrop behind a set, the digital equivalent of an oil-wheel projector or a VJ feed. Chosen by the operator, not bought or triggered by a fan. Always muted: the band is the audio. How much of the screen it takes is a single choice with three steps, video with act info (the act’s name, photo, and socials sit over it; the QR join code, lineup, and chat all survive), video only (same footprint, act card hidden), or full screen (everything else covered).

Say it to users as: “visualizer”; the placement steps name what is on the screen, not where the video sits, “Video + act info” / “Video only” / “Full screen”, each with a line saying what it costs you (full screen covers the QR code fans join by). “Full screen” means the same thing for a Visualizer and a Loop and is deliberately worded identically on both, so an operator learns one vocabulary for the display rather than two.

Showing

The operator’s override for what fills the main region of the venue display. By default (Auto) that region follows the running order with no operator input at all, the bill before the show, signage between sets, visuals while an act is on, and a goodnight message after the last act. An operator can instead pin it to one source: nothing, the lineup, the signage Loop, or the Visualizer. A pin holds through a live set and survives Go Live; it ends only when the operator sets it back to Auto.

Say it to users as: “Showing”, and the choice itself, “Auto” / “Nothing” / “Lineup order” / “Signage loop” / “Visualizer”. Each carries a line saying what it does. Sits with Blackout and Display chat, the other two venue-display controls (ADR-0007).

Announcement

A short message with an optional link, delivered to fans’ phones in a Room, a banner on the Room surface, above the venue and lineup. Read at arm’s length, and tappable. It is the answer to “the audience needs this link” that does not put a second QR on the display. A screen already carries one code, the join QR, and a second one beside it is unreadable by design: nothing tells a fan which is which. So the division of labour is the display gets you into the Room; the Announcement is what you find when you arrive (a signage Panel reading “scan to join, details inside” is the whole bridge). It is deliberately passive: it does not interrupt, take over, or notify. A fan finds it because they looked. An Announcement is an act of posting, not a library object, the contrast with a Panel, which is composed ahead of time and reused across shows. It is authored ahead of time on the Event (or at Room creation), or posted live from the Operator console, and it is Live from that moment until someone takes it down or the Room closes. Room close ends every Announcement live in it, so posting one can never let it follow its Event into a future show. There is no staged state and no scheduled expiry: authored means live, and mid-show timing is achieved by posting mid-show. Exactly one is Live at a time (a banner is a singular affordance; posting a second replaces the first), and only the Room’s owning workspace may post, a band whose fundraiser it is asks the house to post it. See ADR-0027.

Say it to users as: “Announcement”; the verbs are “post an announcement” and “take it down”.

Poll

A question the operator asks a Room, with two to four fixed answers, which fans answer from their phones for free. A Poll is Open (fans vote, and may change their vote) until the operator closes voting; it is then Closed (the tally is final and stays visible, so the room sees how it came out) until someone takes it down or the Room closes. At most one Poll is in a Room at a time: asking another replaces it, whatever state it was in. Fixed once asked. Neither the question nor the answers can be edited, and a Closed Poll cannot be reopened: either would let the tally report answers to something nobody was asked. A typo, or closing too soon, is fixed by asking again, which starts from no votes. No clock. Voting closes when the operator closes it, never on a timer: a Poll in a room is timed by the room (“Encore?” closes when the band walks back on), the same reasoning that gives an Announcement no expiry. A Poll belongs to the Room, not to an act, so Go Live and a changeover leave it alone. The tally is live, the way a stream’s poll is: on the venue display the Poll is pinned above the chat from the moment it is asked and its bars move as the room votes, and a fan’s phone shows the live bars once they have answered (before that, just the choices, so they pick rather than follow). The operator may make it a blind vote (user-facing: “hide results until voting closes”), which keeps the count off the wall and every phone until voting closes. Closing voting always reveals the final tally everywhere, since seeing how it came out is the point. The operator always sees the running tally, blind vote or not. The Poll lives only in the display’s chat sidebar: with chat off the wall, or a full-screen Visualizer or Loop over it, the operator has chosen a clean wall and the Poll is not put over the stage instead. Answering is not posting. A Muted fan, and any fan under Chat lock or Phone lock, may still vote; the lock screen presents the Poll, since “Encore?” is asked while an act is on. One answer per fan, which a fan may change while voting is Open. The question and its answers go through the Content filter like anything else the host publishes. Chat points at a Poll; it never carries one. On fans’ phones, asking a Poll and closing its voting each drop one line into the chat that says so and opens the Poll when tapped. The line never carries the tally (a snapshot of a moving count, and one a blind vote must not show). The display leaves these lines out, since it pins the Poll itself above its chat. A Poll is not a chat message: chat is a short live buffer, and a ballot that scrolls away while voting is still open is a ballot nobody finds. A fan may fold it, never lose it. The card folds to one line so it stops taking the screen; the line still says whether they have voted, or that voting closed, and opens the Poll again. There is deliberately no dismiss: a Poll a fan cannot get back to is one they cannot change their vote on or see the result of.

Say it to users as: “poll”; the verbs are “ask”, “close voting” and “take it down”, the last deliberately the same as for an Announcement, so an operator learns one gesture for removing something from fans’ phones.

Phone lock

A room state that locks the fans’ phones to a “show in progress” takeover: no nav, no compose, no store, no chat, only the free lighter hype gesture and a follow-the-act tap. Its purpose is attention: phones down, eyes up, and any phone use channeled into low-distraction hype + social follow (“if you’re staying on your phone, at least follow the bands and earn for it”). It is a show-state, auto-driven by the Running order: Go Live (an act takes the stage) turns it on, changeover / pre-show turns it off, so it tracks “an act is performing”. A manual override exists for the exceptions, and it lives on the show surface (centered in the Title bar as the show’s focal control), not among the chat controls, it acts on the whole phone, not the chat (see Chat lock). A first-class room concept, independent of any external show-control integration, not a DAW feature. It controls the fan-phone surface; it does not touch the venue display (see Display chat). Named to parallel Chat lock by axis (chat input vs whole phone). The three live-room “clamp” controls sit on three different axes, keep them distinct: Phone lock (the whole fan phone), Chat lock (the fan chat input), Display chat (the venue display). The two that clamp fans are enforced on the server, not just presented by the fan shell; Display chat is presentation only, because it clamps a screen rather than a person.

Say it to users as: the control shows the live state, “Phones locked” (on) / “Phones open” (off); “Phone lock” names it in the tooltip. Fan-facing copy on the takeover screen stays warm (it’s a celebratory “eyes up” moment, not a punishment).

Display chat

The chat sidebar shown on the venue display (the big screen), distinct from the chat on fans’ phones. Its visibility is an operator control (displayChatHidden room flag, toggleDisplayChat): show it for engagement/social-proof, or hide it for a clean screen (a dramatic moment, sponsor content, the act’s visuals), fans keep chatting on their phones either way. Orthogonal to Phone lock (which is the fan-phone takeover). Lives in the Output preview footer next to Blackout (the venue-display controls, grouped on the surface they act on, ADR-0009 moved it there from the Chat pane). Operator-facing label: “Display chat” / “Chat on screen”.

Chat lock

A moderation/pacing clamp that freezes fan chat posting while the show runs open: fans can still read the chat and use the rest of their phone (store, lighter, follow), but can’t post, the host (operator) is exempt and can still post. The lighter-touch counterpart to Phone lock: reach for it when the chat itself is the problem (a spam/abuse pile-on, or quieting the room for a sensitive moment), not when you want the whole phone locked down. Belongs with the moderation cluster (Muted / Removed / Banned / clear), not the presentation toggles.

Host message

A chat message the operator sends from an operator surface (the Operator console), posted under the room’s owning workspace identity, the venue, or for a performer-run room the performer, not the individual staffer’s name. A stable, show-long identity the audience already recognizes (we attribute it to “The Blue Note”, never to whichever act is currently on stage). Identified on every surface (fan phone, venue display, console monitor) by a host badge next to the name (Twitch broadcaster-badge style); the row is otherwise a normal chat row. Driven by a server-stamped authorRole on the message ('host' today; reserved for 'mod', room moderators, later), so the marker is role-derived and not client-spoofable. The host posts through the normal send path, so the content filter still applies.

Content filter

The mechanism that rejects unacceptable text before it is published, chat messages, usernames, and tip messages alike. Two layers, always evaluated together: the Baseline filter (platform-wide, non-disableable) plus the sending room’s owning workspace’s House rules. Applies to everyone who posts, including the host (a Host message goes through the normal send path, so the filter still applies to it).

Say it to users as: “content filter”; to fans at the moment of rejection, just describe what happened (“that’s not allowed here”) rather than naming the machinery.

Baseline filter

The platform-wide layer of the Content filter, the standards that hold in every room on Showliner regardless of who owns it. A workspace cannot switch it off wholesale, replace it, or edit its terms; it can only carve exceptions with an Allowed phrase. Curated by Showliner, not by workspaces.

House rules

A workspace’s own layer of the Content filter, layered on top of the Baseline filter, the terms this house won’t have in its rooms. The configurable half: a venue blocks a banned regular’s name, a competitor’s slogan, a chant it doesn’t want on the screen. Scoped to the workspace, so it holds across every room that workspace runs, and is never visible to fans or to other workspaces.

Say it to users as: “House rules”.

Blocked term

One entry in a Content filter, a word or phrase that causes a message containing it to become a Blocked message. Lives either in the Baseline filter or in a workspace’s House rules.

Allowed phrase

A narrow exception in a workspace’s House rules that exempts that phrase only, never the message containing it. Exists for the case the domain actually produces: an act whose name trips the Baseline filter (live music is full of them), which fans must be able to type while the act is on the bill. A message is still evaluated in full around the exempted phrase.

Blocked message

A message the Content filter rejected. It is never published, not held, not queued, not releasable. Three things follow instead: the sender is told, immediately and specifically enough to fix it; the attempt is recorded against the sending device; and it appears masked in the operator’s chat feed, where the operator can Reveal it. So the message is dead, but the attempt is visible, the operator moderates the person, never the message.

Say it to users as: to the fan, “blocked”; to the operator, “blocked message”.

Reveal

The operator action that un-masks a Blocked message in the chat feed to read what was actually sent. Deliberately a separate gesture from seeing that a block happened, the operator can see that someone is testing the room without having the content pushed at them unbidden. The three fan-moderation states form one ladder, weakest to strongest, Muted (can’t post, still here) → Removed (out for the night) → Banned (not welcome in the house). They differ in what they cost the fan, how long they last, and how much deliberation they deserve; keep them distinct. See ADR-0025.

Muted

A fan state where one device can’t post for a short window but stays in the Room and keeps watching. The per-device counterpart to Chat lock (which freezes every fan at once), and the lightest rung of the ladder, the right automatic consequence for repeated Blocked messages, because it costs a fan a few minutes and never removes a paying customer from a show they came to see.

Say it to users as: “muted”, “muted for 10 minutes”.

Removed

A fan state where a device is put out of one Room and cannot rejoin it. It lasts exactly as long as the Room does, when the show ends and the room closes, the removal ends with it. This is housekeeping, not door policy: the judgement of whoever is running the board, made in seconds, deserving no ceremony and no record.

Say it to users as: “remove for tonight”, “removed”.

Banned

A fan state where a device or account is not welcome in any Room owned by a Workspace. Durable by definition: it outlives every Room it was issued in, which is what separates it from Removed. This is the house’s door policy, the same authority that sets House rules, exercised against a person instead of a word, so it is a deliberate act of the Workspace, not a reflex of whoever holds the board at 11:40pm.

Say it to users as: “ban from our rooms”, “banned”.

Show control

The roadmapped capability for external hardware/software (DAW, OSC, DMX lighting) to drive room events, phone lock, overlays, track-triggered effects. Its forward home is the apps/desktop operator surface (a deferred ShowControlBridge seam). Supersedes the removed “DAW integration”.

Operator console

The surface a venue operator uses to drive a live room during a show. Single-room-centric: it shows the one live room at a glance, lets the operator drive it (the Running order), and puts it on displays. The operator drives the show by hand here; Show control (external DAW/OSC/DMX automation) is the deferred, separate path. Structurally it is a persistent shell (room/show context + global tools, always present) wrapping a dockable Layout of Panes, not a centered web-style card column. Cross-platform: the same console renders natively on desktop (Electron, apps/desktop) and embedded in the admin web app (apps/admin, a full-bleed immersive surface). The two differ only at two seams, the PlatformBridge (window/display capabilities) and the top-chrome (Title bar on desktop vs the web app’s immersive header). It replaced the older per-app web room tooling (AdminRoom, now retired, every room entry point lands on the console). Its design centre is the booth: a desktop, a screen to drive, and often a second person on sound and lights. But not every show has a booth. A one-person Open mic at a back bar is run from a phone with no screen attached at all, and the console is the surface that runs it, there is no separate pocket console. So the console degrades by what the room actually has, on any width: a Pane with nothing to drive is absent rather than empty, exactly as the fan side drops the Store and Wallet from a Room with no Economy. That is one rule serving two ends, it is what makes a phone usable, and it is also what stops a booth operator on a wide screen staring at panes for equipment that isn’t there.

Pane

A single dockable zone inside the Operator console, the Running order, the live/displays output, chat/moderation, audience monitoring, etc. Panes can be shown/hidden, resized, and popped out. Distinct from a signage Panel (which is audience-facing display content); a Pane is operator-facing console furniture. Two different disappearances, and they must not be confused. A Pane the operator hid is part of their Layout, a preference, device-local, and re-showable from the panes menu. A Pane that has nothing to drive is not hidden at all: it is absent, offered nowhere, and returns by itself when the room grows the thing it drives. The Walk-ups Pane is the first of these: it exists only for an Open mic, and only for an operator with authority on the event behind it. The Output preview is the second: it previews a venue display, so with no screen attached to the room it is absent, and the Displays Pane is demoted to the one action that gets you a screen rather than hidden, hiding it would be a chicken-and-egg, since it is how the first display is opened. The Requests Pane is the third: it exists only for an operator who answers for an act on the bill (the act’s own workspace, not the room or event role), and only when the show takes Song requests or that operator could switch them on, so a venue engineer never sees it. Only the first is a Layout concern; conflating them puts panes for absent equipment in the operator’s menu and makes the menu a list of things that do nothing.

Pop out

Detaching a Pane from the docked Layout into its own window the operator can drag to a second monitor, a third window family alongside the console and the audience display windows. Universal across platforms (not gated by a capability): it’s divergence-by-implementation, fully absorbed by the PlatformBridge as popOutPane(paneId, roomCode). On desktop (Electron) it spawns a native frameless BrowserWindow (main-process-managed, can remember position); on the web it window.opens a same-origin popup window (a separate draggable window, not a background tab), auto-authenticated by the shared showliner_session cookie, so its socket rejoins the room with no re-login. Either way the window loads the console in single-Pane mode; the Pane stays the same self-contained unit (own data subscriptions, own socket), so it renders identically docked or popped out.

Layout

The operator’s saved customization of the Operator console, near-term: which Panes are shown/hidden, their sizes, and which are popped out (not free-form repositioning, which is deferred). The console ships with an opinionated default Layout; every Pane is hideable (ADR-0009 dropped the earlier non-hideable Running order, the Transport now carries always-relevant control). State is device-local (localStorage), one Layout per device, not per-workspace (the arrangement reflects how the operator works, not the room; entity-type differences belong in the default Layout). Future: in-grid repositioning/docking, and task-/role-specific named Layouts (e.g. moderation-heavy vs. show-driving). See ADR-0009.

PlatformBridge

The injected seam that tells the cross-platform Operator console what its host can do locally, window management for putting a room on a screen. The console talks only to this interface, never to window.showliner or a navigator.userAgent sniff directly; one swap point keeps it platform-agnostic. Electron supplies the real one (enumerate physical monitors, open/close native fullscreen display windows; today’s window.showliner); the web app supplies a thinner one. The only capability the browser genuinely lacks is send-to-physical-monitor, opening a room’s display in a browser tab is universal, so it lives here for both. The console’s “put a room on a screen” actions, by where they live: send to monitor (local, Electron-only, via PlatformBridge) · open in browser (local, both, via PlatformBridge) · cast to a display device (server-mediated, both, future, not the bridge).

Title bar

The desktop Operator console’s top-chrome, the macOS title strip (inset traffic lights, draggable). One of the two swappable top-chromes (the web app supplies its own immersive header instead). Beyond chrome, it carries the ambient live status, LIVE state + timecode, the active Performer (who’s on now), show/room identity, headcount, the Phone lock override (the auto-driven show-state that locks fans’ phones while an act performs), plus the global tools (workspace switcher, settings). Glanceable-always furniture you read, not an instrument you act on. No in-app branding (the OS owns the app name).

Running order

The live lineup the operator advances from the Operator console, pre-show → each act → changeover → show-end, marking who is currently on (the active Performer) so the room and displays follow. “Go Live” promotes the next act; it also flips the room into Phone lock. It is the manual counterpart to the deferred Show control automation, and is purely a client of existing room socket events (no new backend). In the console it is a Pane showing the full timeline (per-act “Go Live” is the dominant action), now a normal hideable/poppable Pane (ADR-0009 superseded the earlier “privileged always-present” rule): act-less or single-act rooms can hide it, and the Transport carries the always-relevant control.

Say it to users as: “Running order”, “Go Live”, “Up next”.

Transport

The compact show-driver Pane split out from the Running order list (ADR-0009), three bare buttons that step the show through the timeline (◀ previous · ▶| next · ▶▶| go to end), with no state text (the list shows what’s live / up next). Both panes read the same pure timeline model, so they can’t disagree. This reverses the earlier “no separate transport bar” rule: the old “Live bar” was cut as a duplicate that always sat alongside the same list; the Transport instead is the always-relevant minimal driver while the list becomes optional (hideable), complementary, not duplicative. Like every Pane it is hideable + poppable (e.g. onto a touch monitor). Ambient read-only status still lives in the Title bar; the Transport is the thing you act on.

Say it to users as: “Transport”, “Previous”, “Next”, “Go to end”.

Request list

The songs an act will take requests for, offered to the crowd in a Room. Belongs to the act’s Performer Entity, not to a show, so it carries from gig to gig. A row is a title, optionally the original artist (for covers) and a minimum. The act’s settings sit beside it: whether it is taking requests, whether custom requests are allowed, and a default minimum. Setup is pasting a list, one song per line; an empty list with custom requests on is a working setup. It is not a repertoire in ADR-0037’s sense and never touches the act’s set-list Attachment. An Attachment is the act talking to itself, readable by that show’s Personnel only; a Request list is the act talking to the crowd. One object over those two readerships is the leak the Attachment entry warns about. See ADR-0038.

Say it to users as: “request list”, “songs you take requests for”.

Song request

A Fan’s ask that one act play one song during one Room, optionally with a short dedication, optionally with Backing. Addressed to an act, never to “the active performer”: on a three-act bill a fan can request from the headliner during the opener. Lifecycle pending → accepted → played, with declined, and lapsed when the Room closes on a request the act never played, whether still pending or accepted and waiting. An accepted request waits in the act’s Up next, which the act may reorder; playing one is a single tap that marks it played and makes it Now playing. An act that will not play an accepted request after all drops it, which ends it exactly as a pass does: nothing charged, Cheer returned, the backers told on their own phones; it never goes back to pending, and the Room closing drops whatever is left. Money orders requests only while they are pending: once the act has said yes, the order is the act’s. Money moves when the act plays the song, never earlier: accepting is a promise, and a fan pays only for a song they heard. It is released on decline or lapse. A fan may withdraw their own Backing while the request is pending (the hold released, the Cheer returned; the request ends only if nobody else backs it, and other backers are not told), never once the act has accepted, since accepting is the act’s promise and it runs both ways. There is no edit: a different song is a withdrawal and a new request, and more is backing again. Switched on by the Event and answered only by the act (ADR-0038). The Organizer turns requests on for an Event (never a standalone Room, like Open mic), including during the show; the act’s own workspace separately chooses to take them, and only that workspace may accept or decline. So an Unclaimed act is never offered: nobody could answer. Allowed during Phone lock for the act on stage.

Say it to users as: “request”, “request a song”.

Custom request

A Song request whose title the fan typed rather than picked from the Request list. Offered only when the act allows it. The title goes through the Content filter under the room owner’s House rules, as a dedication does.

Say it to users as: “request something else”.

Up next

An act’s accepted Song requests that it has not played yet, in the order it intends to play them. Starts in the order they were accepted, and only the act reorders it: fans’ money ranks requests before the act says yes, never after. Fans never see it: a backer’s card shows the request’s state (waiting, the act said yes, playing now, played), never its place.

Backing

What a fan puts behind a Song request: the act’s Cheer, or real money. A request can have many backers, and adding to someone else’s request is how a crowd moves a song up the incoming requests, which are ordered by dollars, then Cheer, then time; the act still answers whichever it likes, and once accepted a song’s place in Up next is the act’s alone. A fan may still back a request the act has accepted: it is charged with the rest when the song is played, cannot be withdrawn, and never moves the song. Money backing is authorized when made (the request stays invisible until the card hold is confirmed), captured when the act plays the song, and released when the act passes or the Room closes before it is played; Cheer backing is debited when made and credited back on decline or lapse. Fees are Tip fees: the act keeps 100%, with optional Lights-on and Cover fees.

Say it to users as: “back this”, “add to it”.

Now playing

The song the act on stage is playing, set by the act, usually by playing a Song request from its Up next. The next song played replaces it, and changeover clears it. A room detail beside the active Performer; shown under the act’s name on the display’s act card and on the Phone lock screen.

Meet people

The fan-to-fan discovery feature: registered, 18+ fans who are physically at the same show browse each other’s Meet profiles and Like or Pass. Social first, with dating as one opt-in Looking for option, never the premise. It belongs to the platform, not the Room: the Room only proves the fans are there together. On by default for every Event-backed Room; the Organizer can turn it off for a show, and never sees inside it. Nobody working a show takes part in that show’s Meet people, the acts on the bill and their Personnel, the owning Workspace’s Team, anyone with Room authority, in either direction; at someone else’s show they are just fans. It never touches the Economy (no Cheer or Housepower is spent or earned in it), and the venue display carries only the Presence code, never a count, a name, or a celebration of who is using it.

Say it to users as: “Meet people here”.

Meet profile

A fan’s platform-wide card for Meet people, photos, first name, Looking for, set up once and carried to every show. Belongs to a User, never to a Room or a Workspace.

Say it to users as: “profile”, “your profile”.

Looking for

What a fan says they are open to at a show: making friends, finding a ride, a show buddy, or dating. A fan picks any number, and sees only fans whose choices overlap theirs. Dating is strictly mutual: only fans who both picked it ever see each other as dating-open, and nobody else learns that either picked it.

Say it to users as: “Looking for”.

Like

A fan’s yes or no on another fan’s Meet profile, by swipe or button. A Like is invisible to its recipient until it is returned.

Say it to users as: “Like”, “Pass”; swipe right / swipe left.

Match

Two fans who Liked each other. The only state in which either can contact the other. A Match outlives the show: the browsing is show-scoped, the Match is not. Its only channel is a 1:1 text chat inside Showliner that opens on the Match, and it runs the Baseline filter alone, a private conversation is not a venue’s publishing surface, so no House rules apply.

Say it to users as: “It’s a match”, “matches”.

Unmatch

Ending a Match. The chat closes for both, and nobody is told beyond the chat disappearing.

Say it to users as: “Unmatch”.

Block

An Unmatch that also keeps two fans out of each other’s browsing at every future show. Instant, permanent, and owed to nobody’s review.

Say it to users as: “Block”.

Report

A Block that also sends the other fan to Showliner’s own moderation queue, the platform acting about someone, not a venue.

Say it to users as: “Report”.

Presence code

The short-lived code on the venue display that a fan scans to prove they can see the screen right now, the proof of being at the show that Meet people unlocks on, alongside a minimum time in the Room. The Join code gets you into the Room; the Presence code proves you are standing in it, because a Join code can be posted online and typed from anywhere.

Say it to users as: never named, “scan the screen to meet people here”.

Multi-workspace ownership

One person (a User) owning and running several Workspaces of their own. Long supported (a User owns many Workspaces; the unified view across them is the cross-workspace hub), and gated by plan: a Free user owns one Workspace, a Pro user owns several. It is account-level, each Workspace keeps its own plan and bill; there is no separate billing object.

Organization

A billing container that would sponsor one or more Workspaces under a single subscription, paying for their plan without owning them. Its reason to exist is consolidated billing across workspaces owned by different people (booking agents, management companies) while preserving each owner’s sovereignty. Not an Entity, not a Workspace.

Say it to users as: “Organization” (once built).

What an Organization would do to a Workspace: pay for its plan without owning it. The Workspace’s owner keeps full ownership and can end the sponsorship at any time. Sponsorship runs Organization → Workspace and is about billing, never ownership or control of the Workspace’s content.

Say it to users as: “sponsor”, “sponsored workspace” (once built).

Tip

A one-time, real-money payment from a Fan (a registered user, a guest, or anonymous) to a Performer, Venue, or Collaborator. Real dollars, entirely separate from the in-room virtual currency (Housepower/Cheer). It pays out directly into the recipient’s Stripe Connect account; the platform takes nothing from the tip itself.

Say it to users as: “tip”.

Lights-on

A small, voluntary amount a tipper may add on top of a Tip to support the platform. It is the platform’s only revenue from tipping, the tip itself is taken at 0%. Goes to the platform, not the recipient.

Say it to users as: “keep the lights on”, “chip in for Showliner”.

Cover fees

A tipper’s choice to absorb the card-processing fee so the recipient nets the full intended Tip. When off, the fee comes out of the tip instead.

Say it to users as: “cover the fees”.

Payout

A cash-out from a recipient’s Connect-account balance to their bank or debit card (standard or instant). The Connect balance is the source of truth for what’s available; a local record (TipPayout) is kept for history.

Say it to users as: “cash out”, “payout”.

Connect account

A recipient Workspace’s Stripe Connect account, it holds Tip balance and receives Payouts. A Workspace must create and onboard one (identity/KYC) before it can receive Tips; receiving Tips is gated on this onboarding, not on plan.

Say it to users as: “payouts setup”, “connect your bank”.

Settlement

The reckoning of a played show against its Deal, what was agreed, what actually happened, what is owed. It computes against the frozen Deal (never against live event fields), and both parties acknowledge the same sheet rather than one side printing a PDF for the other to sign. Showliner records a Settlement; it does not move the money. How payment happened (cash, bank transfer, check, app) is a recorded fact on the Settlement. Pay-through-Showliner is a deliberately staged future option, kept behind a seam, see ADR-0016.

Say it to users as: “Settlement”, verb “settle the show”.

Fan support

Umbrella term for audience → performer money. Today it is one-time Tips; recurring fan subscriptions and supporter tiers are roadmapped. It is B2C and runs on Stripe Connect, distinct from workspace plans (B2B subscriptions).

Stage plot

A scaled diagram of where everything goes on stage, instruments, mics, monitors, gear, on a grid sized to the stage. Belongs to a Workspace and is reusable across events (cloned per event via EventStagePlot). The visual core of a Tech rider.

Say it to users as: “stage plot”.

Submitted plot

What an act hands the venue for one event, a revision, frozen at the moment it was submitted, not a window onto the plot the act is still working on. The act keeps editing freely; the venue keeps reading the last thing it was actually given, and sees only that newer unsubmitted changes exist. Submitting again supersedes; revisions are kept, never pruned, so “what did we advance against?” always has an answer, the same reason a Deal freezes its terms rather than joining back to the Offer. This is what makes Revision requested meaningful: the venue objects to a specific version, not to a moving target. See ADR-0028.

Say it to users as: “submitted” / “send to the venue”; “the venue asked for changes”.

Tech rider

A performer’s technical-requirements document for a show. Showliner generates it (a PDF) from a Stage plot. Today it is the stage-plot-plus-input-list core: the stage-plot diagram, the input list, the backline, and stage dimensions + notes. A fuller tech rider (hospitality, power, monitor mixes, and the like) is roadmapped, not yet modeled.

Say it to users as: “tech rider”.

Stage outline

The shape of the stage’s edge on a Stage plot. By default the stage is the full width × depth rectangle; an outline lets a non-rectangular stage (an L-shape, a thrust, an angled wall) be drawn inside that rectangle. It constrains where gear can validly sit; it does not change the stage’s dimensions or the grid (those stay the outer bounding box). Absent outline = plain rectangle.

Say it to users as: “stage shape” (the verb is “edit the stage shape”); “stage outline” in code/stageOutline.

Input list

The audio channels a stage needs, inputs and outputs, each with a channel number, label, connector (XLR / TRS / USB / MIDI / …), and phantom-power flag. A core section of the Tech rider. An act may answer the venue’s outstanding “input list” advance item with its Stage plot rather than a file, the channels are already on the plot, so asking for a PDF of what Showliner can print is asking twice. Two rules make that safe. It counts as answered only when the plot actually carries input channels: a plot with the gear placed and no channels typed is the likely case, and treating “a plot exists” as an answer tells the venue they have an input list they have never seen, worse than a blank, which at least prompts a phone call. And the venue reads only what the act submitted, never the plot as it stands: a plot the act is still moving things around on is not an answer, and one that changes after the venue has read it is how a desk gets patched wrong on the night.

Say it to users as: “input list”.

Backline

Shared stage gear a Venue provides for performers, amps, drum kit, monitors, so an act builds on top of it rather than hauling everything. Marked per item (isBackline); appears as its own section of the Tech rider.

Say it to users as: “backline”.