হবে নাকি Coffee?
A platform where creators sell, publish and get supported. Creators can bring other people onto their team to help run their account.
Language
People
Creator
A person who has an account to earn from their audience: they receive gifts, publish paid posts and memberships, and sell in a shop. An account becomes a Creator's when its person chooses to earn, at signup or any time later, and never turns back. Avoid: নির্মাতা, influencer (in product copy), seller (as the name for a Creator; a Creator is always the seller in a sale, the platform never is)
Supporter
A person who pays a Creator: for a coffee gift, a paid post, a membership or a shop order. They may live in Bangladesh or abroad. A Creator can be a Supporter of other Creators. Avoid: fan (fine in storytelling, not as the term), patron, donor, customer, সমর্থক
Coffee gift
Money a Supporter sends a Creator for nothing in return except any Reward the gift earns, counted in coffees and sent with a name and an optional message. Anyone can send one without an account. A Coffee gift stays a gift when it earns a Reward: it is never a purchase. Avoid: tip, donation, support (as the name of the payment)
Support or earn
The one question a new account is asked, whether its person is here to support Creators or to earn as one. Earn makes the account a Creator's; support is kept only so the question isn't asked again, and the person can still choose to earn later. Avoid: account type, role (a Team role or a Manager's role), intent
Reward
Something a Creator gives back to a Supporter whose single Coffee gift meets the Reward's minimum, in taka. It can be an item from one of the Creator's services, granted to that Supporter alone and earned once, or a link or note that anyone holding it can open. A Reward with no minimum goes to everyone who sends a gift. Gifts never add up towards a minimum, and a refund doesn't take a Reward back. A personal Reward that isn't handed over at once must be claimed within 30 days of the gift, and can't be claimed once the whole gift has been refunded. Avoid: thank-you gift, perk, gift (for the thing given back), bonus
Claim
A Supporter taking a Reward their Coffee gift earned, through that gift's claim link, within 30 days of the gift. Anyone holding the link can claim; each Reward is claimed once. Avoid: redeem (for a Reward)
Undelivered Reward
A Reward a paid Coffee gift earned that the platform failed to hand over. It stays owed until it is given or its 30-day Claim window ends. Avoid: failed reward, lost reward
Reward hint
The line telling a would-be Supporter what their Coffee gift would earn, in the Creator's own words. It shows only while a Reward can still be earned: on the Public page, on a post page and in the Page widget, never in a Share kit output that can't change once it is made, like a Share image or a printed QR code. Avoid: teaser, nudge, perk banner
Coffee
The unit a Coffee gift is counted in: ৳20, the same on every Creator's page. A gift is worth as many whole coffees as the amount the Supporter paid covers; the coffees are never chosen separately, and taka left over stays part of the gift. The smallest Coffee gift is one coffee, and there is no largest number of coffees. Avoid: cup
Accepting Coffee gifts
Whether a Creator can receive a Coffee gift right now: they have gifting turned on for their Public page, and a Manager hasn't turned off their gift service. While a Creator isn't accepting Coffee gifts, nothing invites a Supporter to send one: not the gift form on their Public page, the Support button Element or the Gift prompt. Avoid: gifting enabled, gift service on (alone)
Member
A Supporter on a Creator's membership plan. A Creator has one monthly plan: there is no yearly or lifetime plan, and no price lock, because each payment buys one month at the plan's price that day. Each period is paid up front and nothing is charged automatically, so a membership ends when its paid period ends unless the Member renews. A Member can't cancel or pause; they simply don't renew. A Reward can also give a Supporter free months, which are added after any months already paid for and never count as a sale. Avoid: subscriber (in product terms), সদস্য
Renewal
A Member paying again while their membership is still running, which extends it. This holds even if they had cancelled: a cancelled membership runs until its period ends, so paying before then reactivates and extends it. Joining again after the membership has ended isn't a Renewal: that person is a new Member again. Avoid: resubscription, re-join (for a Renewal)
Paid post
A newsletter post a Supporter reads in full only after buying it, or after getting it as a gift or a Reward. Being a Member doesn't open it. A Creator who wants their Members to read a post free also makes it members-only: then Members read it free, and everyone else can buy it. Avoid: premium post, pay-per-post (in product copy)
Members-only post
A newsletter post that only the Creator's Members can read in full. If it's also a Paid post, people who aren't Members can buy it instead.
Manager
A member of the platform's own staff who works in the admin, with a role that decides what they can do there. The admin's Team Hub and Team Statistics belong to Managers; they have nothing to do with a creator's Team. Avoid: admin (as a person), staff member, bare "team" for the platform's staff
Teams
Owner
The person whose account it is, a Creator or not. The Owner holds every permission on their own account. Avoid: account holder, main user
Team
The set of people an Owner lets work on their account. Each creator has exactly one Team, and it can be paused as a whole. Avoid: workspace, organization
Team Member
A signed-in user who holds a Team Membership in some Owner's Team. A Team Member doesn't need a creator profile of their own. Avoid: delegate, collaborator, staff, bare "member" (which means a supporter on a membership plan)
Team Membership
The link between one Team Member and one Team. It carries that Team Member's role, grants and status. A single Team Membership can be paused on its own. Avoid: delegation, seat, bare "membership" (which means a supporter's membership plan)
Paused
The state of a Team, or of one Team Membership, whose delegated access is switched off for now but kept, Role and Grants included, so it can be turned back on unchanged. Unlike removing a Team Member, pausing loses nothing. Avoid: suspended, disabled, frozen
Actor
Whoever is making a request on an account: the Owner or a Team Member. Avoid: caller, user (when the account's Owner is meant)
Permission
One thing an Actor may do on an account, such as viewing orders or fulfilling them. Some permissions need another one first: fulfilling orders needs viewing them. Avoid: scope, capability, right
Role
A fixed, platform-defined bundle of permissions assigned to a Team Membership, e.g. Admin or Operations. Owners can't create their own Roles. Roles are ranked: Admin outranks the others, and nobody can edit a Team Membership or assign a Role at or above their own rank. A Team Membership may have no Role and rely on Grants alone. A Role never includes a Sensitive permission. Avoid: preset, group
Grant
An explicit allow or deny of one permission on one Team Membership, on top of its Role. A deny always wins, and a deny the Owner placed can be lifted only by the Owner. Avoid: override, exception
Sensitive permission
A permission that only the Owner can grant, and that needs a recent second-factor check each time a Team Member uses it, e.g. issuing a refund. The Owner uses it without that check. Avoid: dangerous permission, elevated permission
Step-up
The second-factor check a Team Member passes right before using a Sensitive permission, when their session hasn't had one recently. Once it succeeds, the action they started is retried once, and only while they're still on the same Team. Avoid: re-auth, 2FA prompt
Owner-only action
Something no Team Member can ever be granted, such as payouts, identity verification (KYC), pausing the Team or closing the account. It isn't a permission at all. Avoid: admin action
Personal area
Part of the app that always belongs to the signed-in Actor, whichever account they're working on, such as their purchases, inbox, notifications and settings. It's never shared with a Team and never needs a permission. Avoid: actor-own (in prose), private area
Public page
The page supporters see for a creator: name, bio, photos, social links, username and Rewards. It belongs to the account, not to the Personal area, so a Team Member with the right permission can view or edit it. Avoid: profile (that's the Actor's own personal details), Creator page
Held username
The username a Creator had just before their latest rename, or when they closed their account. For 90 days nobody else can take it. After a rename the Creator can take it back and a visit to the old link redirects to the new one; after a closure the old link gets a 404. A second rename releases the earlier one, and after 90 days the name is free again and the hold is deleted. It is not a Payout hold, a COD hold, a Payment hold or an Investigation hold, which are all stops on money or content. Avoid: reserved username (that is a name the platform keeps for itself), reservation, redirect hold
Closed account
An account its owner has closed. Their personal details are removed; only the records the law or other users' ledgers need stay, under no name. Avoid: deleted account, tombstone, Deleted User (that's only the label other users see)
Share kit
The tools a Creator uses to send people to their Public page from somewhere else: their own website, a stream, a printed QR code, a social post. Every tool ends on the Public page; none takes a payment off it. Avoid: buttons & graphics, promo kit, embed kit
Share kit link
A link from a Share kit tool to a Creator's Public page, or to one of their posts or products. It may name the tool it came from and suggest either a number of coffees or an amount of at least one coffee, but never carries a message on the Supporter's behalf. Avoid: referral link, tracking link, affiliate link, short link (for our own links; another site's short link, like vm.tiktok.com, is fine)
Permanent link
The address under every Share kit link that never changes, even when the Creator renames or a post or product is retitled, so printed QR codes and pasted buttons keep leading to the right place. People still see and type the Creator's username; the Permanent link is what the code or button holds. Avoid: short link, QR link, Held username (which lasts only 90 days)
Source tool
The Share kit tool a payment came through, if any: the one named by the Share kit link the Supporter followed before paying. Only the payment that visit led to has one; a membership Renewal never does. Avoid: attribution, referrer, campaign, UTM, source (alone)
Website button
A button from the Share kit that a Creator puts on their own website, blog or README, leading to their Public page. It is not the Support button Element, which lives inside a post. Avoid: support button, donate button, tip button, coffee button, badge
Page widget
A small floating button from the Share kit that a Creator adds to their own website, in a style and corner they choose. It invites a visitor to send a Coffee gift, with a Reward hint when the Creator offers a Reward, or to reach the Creator's membership plan, shop and posts, and opens the Public page to finish; it never takes the payment itself. Avoid: support widget, payment widget, donate widget
Creator pixel
A Meta pixel or Google Analytics 4 property of a Creator's own that receives a fixed set of visit and payment events from their Public page. It never runs the Creator's code and never receives a Supporter's personal details. Avoid: tracking code, custom script, analytics snippet, Source tool (that is our own record of which Share kit tool a payment came through)
Stream alert
A message that appears on a Creator's live stream when they receive a Coffee gift, a new Member or a Renewal, or, if the Creator turns it on, a paid post sale. It shows the Supporter's name and, for a Coffee gift, its number of coffees and message; it never shows an amount in taka, and a shop order never sets one off. Avoid: donation alert, tip alert, overlay (that is where it shows, not the alert)
Overlay link
The private address a Creator adds to their streaming software so their Stream alerts appear on the stream. Anyone holding it sees the alerts as they happen, so it is kept like a password, and resetting it replaces it at once, leaving the old one silent. Avoid: alert URL, widget link, browser source (that is the streaming software's name for where it goes), Share kit link (which leads to the Public page)
Share image
A ready-made picture from the Share kit that a Creator downloads or shares to their social media, inviting people to their Public page or to one of their posts, products or membership. It never shows a number. Avoid: social card, promo image, poster, Link preview (which other sites show by themselves)
Link preview
The picture and title other sites and apps show when someone pastes a link to a Creator's Public page. It updates itself when the Creator's photo, name or username changes; the Creator doesn't make or choose it. Avoid: OG image (for a Public page; the marketing site's own pages have generated OG images too), thumbnail, share card, Share image (which the Creator downloads)
Brand kit
The platform's own logos, cast drawings and Stickers that a Creator may use when pointing people to their Public page, with the rules for using them. It is the same for every Creator and is for Creators, not the press. Avoid: creator kit, press kit, media kit
Sticker
A small animated drawing from the Brand kit, such as a steaming cup or a waving cast member, that a Creator drops into posts, stories or videos. It is the same for every Creator and never carries a Creator's name; anything with their name on it is a Share image. Avoid: GIF (the file format), emoji, badge, Share image
Connected app
An outside AI tool, such as Claude or Codex, that a user has allowed to act for them, limited to the Permissions and Personal consents they picked when connecting and never beyond their own access. It can't pay, bill, verify identity, use a Sensitive permission or take an Owner-only action, and the user can revoke it at any time. Avoid: integration, bot, API token (as the name of a Connected app), agent (as the name), delegate (a Team Member is a person)
Throttled
A Connected app is Throttled when the MCP Worker's rate limit refused its calls in the last hour because it used up its budget too fast. Reads and writes have separate budgets. The AI is told to wait and try again, and the Owner sees "Throttled" on the Connected apps screen. Throttling never revokes or ends the connection, and it clears on its own. Avoid: blocked, banned, suspended (those stop the connection; suspended is also a Team stop), revoked (that is the user disconnecting it)
Personal consent
A part of their Personal area, such as their purchases or their inbox, that a user lets a Connected app use. It exists only for Connected apps: it is never a Permission, and no Role or Grant holds one. Avoid: personal permission, scope
Bio
The Creator's introduction on their Public page, describing who they are and what they do. Avoid: profile description (when the Bio is meant), separate About section (when the same Bio is meant)
Creator onboarding
A Creator's guided setup of preferences, Public page, and initial services or content. Finishing setup does not itself approve or publish content. Avoid: page launch (when only onboarding completion is meant)
Onboarding preview
A private illustration or appearance example of the Creator's Public page taking shape during setup. It can build on earlier working changes and show an unapproved Bio without establishing what visitors can currently see. Avoid: live page (when only the preview is meant), published page (when showing working changes)
Onboarding draft
The Creator's private, saved working changes to their initial Public page setup. It is separate from the page visitors see and from a Bio revision submitted for approval. Avoid: published setup (when only working changes are saved)
Setup checklist
The list of first things a new Creator does to get their Public page ready to take support, such as verifying identity and adding a payout method. It is shown on the Activity page to a Creator's Owner, under the Greeting card, until every step is done, and it is the one measure of setup progress however a step gets done. Avoid: onboarding checklist, to-dos, getting started (Creator onboarding is the signup flow before the app)
AI setup
Doing the Setup checklist through a Connected app, such as Claude or Codex, instead of step by step. The AI can only do the steps its tools allow; the Creator still does the rest, such as verifying identity and adding a payout method. Avoid: MCP setup, AI onboarding, auto setup
Greeting card
The card under the greeting on the Activity page. It holds one message chosen by the account's state, such as how to start setup, the latest support or, on an account that isn't a Creator's, the invitation to start earning; a Creator's card also always holds the Public page link. Only the message can be dismissed. Avoid: hero, banner, welcome card
Doel bhai
Doel, the robot from the cast, when he guides a Creator through the app. His lines are written ahead of time; he does not think or answer questions. Avoid: AI bot, assistant, chatbot, Doel AI
Tour
A scripted run of Steps in which Doel bhai shows a Creator how to do one thing in the app, such as finishing setup or adding a shop product. A Creator can skip it at any point. Only one Tour runs at a time. A Tour counts as seen once a person has finished or skipped it; seen belongs to the person, not to the account they are working on, and a seen Tour never starts by itself again but can always be replayed. Avoid: walkthrough, coachmark, tutorial, onboarding tour (when the Tour is not about Creator onboarding)
Walkthrough
The shared step component on a marketing feature page (a number, a drawn screen of the app, one or two spoken sentences, stacked on a phone). It follows one Creator through a real flow, and each page draws its own screens inside it. It is not the Tour, which is Doel bhai's in-app guide. Avoid: Tour (for the marketing component)
Task Tour
A Tour that shows how to get one thing done. Every Step that points at something on the page waits for the Creator to do it. Most Tours are task Tours. A task Tour may start by itself on the first visit to its page, but only while the thing it teaches hasn't been done yet; otherwise the offer chip offers it, unless it is a button-only Tour. Avoid: action tour, interactive tour
Explain Tour
A short Tour, about five Steps at most, that explains a page meant for reading, such as billing. Its Steps may point at things and move on when the Creator taps Next. An explain Tour never starts by itself; it is offered through the offer chip. Avoid: info tour, read-only tour
Offer chip
The small Doel bhai chip that offers one of a page's unseen Tours on a visit where nothing started by itself: a first win not done yet first, then another task Tour, then an explain Tour. Tapping it starts the Tour; dismissing it counts the Tour as skipped. It never offers the Welcome tour or a button-only Tour. Avoid: prompt, nudge, launcher
Button-only Tour
A Tour that starts only from its Doel bhai button or from Help, because few Creators need it, such as paying fees owed. It never starts by itself and the offer chip never offers it. Avoid: hidden tour, manual tour
Welcome tour
The Tour that starts by itself the first time a Creator reaches the app after finishing onboarding. Doel bhai says hello and points at the Setup checklist; the Tour ends when the Creator picks something from it. It only runs where the Setup checklist is shown. Avoid: after-onboarding tour, onboarding tour, intro tour
Tour step
One moment of a Tour: what Doel bhai says in his bubble, how the bubble looks, how he looks, and where on the page he points. The Tour moves to the next Step when the Creator does what he asked; only a Step that asks nothing of them moves on when they tap Next. There is no going back a Step. Avoid: hint, tip, popup
Moderation submission
An exact version of Creator-authored content submitted for the Automatic check and, when needed, Manager review before it becomes public. A decision applies to that version, not to later edits. Avoid: creator report (a complaint about a Creator), approval of the Creator (when only their submitted content is meant)
Approved revision
The one Moderation submission a Manager approved that is currently the public value of a feature (for a Bio, the revision profiles.bio_submission_id points at). Publication writes exactly its text; a Bio that predates moderation has no approved revision and is shown as its legacy plain text. Avoid: published draft, live draft
Video approval
A Manager's recorded decision that one YouTube video, for one Creator's Bio, may be shown. It is keyed by the Creator and the normalized video id, is written together with the publication of the revision the Manager approved, lets later text edits keep the video, and is never shared with another Creator. Revoking it removes the video from the public Bio and can never be undone by resubmitting the same video. Avoid: video verdict, channel approval, whitelisted video
Takedown
A content Manager's recorded removal of one public item (the Bio that is public now, a newsletter post or a shop product), with a reason the Creator reads. It keeps the decision history and never suspends the account or resolves a Creator report. It is distinct from resolving a report (which only records a review) and from account suspension (a separate authority). For a Bio it clears every public Bio value (the approved revision and any legacy plain text) and revokes that Bio's Video approval; a taken-down Bio revision is final: the same text is held for a Manager and its video cannot be approved again. A taken-down newsletter post or shop product comes back only through a new Manager review (or, for a product, a Manager putting it back on sale), never by Fast republish. Avoid: delete the Bio, ban, hide (when a removal is meant), resolving a report (when a removal is meant)
Creator report
A report anyone, signed in or not, files about a Creator for a Manager to review. It can carry one evidence file, sent with the report itself; once attached, the evidence can't be replaced or added to by anyone. Resolving it records a Manager's review and removes nothing by itself. Avoid: complaint, flag, abuse report
Fast republish
A Creator's (or a Connected app's) putting an unpublished newsletter post or shop product back live at once, with no new Manager review, because its moderated text is identical to the text a Manager last approved. It is allowed only when the approved text still matches, the moderation policy version is the one in force when the Manager approved it, and a Manager has not taken the item down. It keeps the same Approved revision, queues no Moderation submission and is audited. Otherwise it is refused with a reason code (taken down, never approved, no Approved revision, edited since approval, policy version changed) and the Creator submits the item for review as usual. A Manager's Takedown is never fast-republishable, and there is no time expiry. A Manager's rejection of the same text, made after the approval it would reuse, counts as a Takedown until a Manager approves that text again; a rejection by the Automatic check does not. While a Manager has paused the whole Shop every product is refused, and once the Manager resumes the Shop a product the Creator unpublished can be republished again by the same rules. Avoid: instant approval, republish without moderation, undo unpublish (when the check is meant)
Investigation hold
A super admin's recorded decision to keep one Moderation submission's text past its 90-day retention, because it is evidence in an active investigation. It has a reason, is released with a reason, and is a separate authority from reviewing content. Without a hold, a superseded or rejected submission's text is removed 90 days after it was superseded or rejected; the Approved revision in use is never removed. Avoid: legal hold, freeze, lock (a lock is the per-target concurrency lock)
Demo profile
A fictional creator presence that shows visitors how a Public page and its services work. It has no Creator account and cannot receive real follows, purchases, gifts or subscriptions. Avoid: demo user, test account
Locked state
Why an Actor can see that a page or action exists but can't use it. It is either service-locked (the Owner hasn't turned on or subscribed to that service, which only the Owner can fix), permission-locked (the Actor lacks the permission and must ask the Owner) or owner-only locked (the page belongs to an Owner-only action, so no Role or Grant can ever open it and there is nothing to ask for). Avoid: plan-locked, paywalled, forbidden
Invitation
An Owner's offer of a Team Membership to someone, with a Role, that is pending until the person accepts or declines it, or the Owner withdraws it. Declining tells the Owner; it isn't the same as letting it expire. Avoid: invite code, join request
Access request
A Team Member's note to the Owner, sent from a permission-locked page, saying they need access to it. There is one per Team Member and page: it stays pending until the Owner changes that member's Role or Grants, or for seven days, and it grants nothing by itself. Avoid: permission request, access ticket
Notifications
Activity
Something that happened on an account that its user should know about, such as a gift received, a new follower or an order shipped. Every Activity appears in the in-app feed, whatever the user's email choices. Avoid: event (in product terms), feed item (for an Activity; a Home feed entry is a feed item)
Activity page
The app page that holds an account's in-app feed of Activities, for a Supporter's account as well as a Creator's. It is where a sign-in lands when it was not started from somewhere it should return to, such as a Creator's page or the Home feed. Avoid: Activities (for the page), dashboard, home (the Home feed is a different page)
Admin alert
Something that happened on a Creator's account that Managers need to know about and the Creator is not told, such as a penalty ending a Raised COD limit. It is not an Activity: it never appears in the Creator's in-app feed and is never emailed. Each kind is shown to the Managers whose role lets them act on it. It stays open until one of them dismisses it, which dismisses it for all of them. Avoid: admin activity, system notification, admin notification
Notification type
A named kind of Activity that can be emailed, such as "new follower" or "order shipped". Each has exactly one Delivery class. The one exception is the chat message email, which has no Activity because chat stays out of the in-app feed. Avoid: notification key, template
Delivery class
How a Notification type reaches the inbox: as an Immediate email, inside the Digest, or as a Lifecycle reminder. It is fixed per Notification type. A user can turn a type off, or ask for their Digest types one email at a time, but can never move an Immediate type into the Digest. Avoid: priority, channel, frequency
Immediate email
An email sent as soon as its Activity happens, used for money, orders, payouts, identity checks and account safety. Emails to people without an account are always Immediate. Avoid: transactional email, instant notification
Digest
One daily email that summarises the user's low-urgency Activities since the last one, such as new followers and coffees received. No Digest is sent on a day with nothing in it. Avoid: summary, roundup, newsletter (that's a creator's paid-post service)
Lifecycle reminder
An email sent on a schedule ahead of, or after, a membership or Add-on expires. It is skipped if the membership or Add-on has already been renewed or cancelled by then. Avoid: expiry notification, renewal nag
Chat message email
An Immediate email telling a chat participant about a message still unread 10 minutes after it was sent. At most one goes out per conversation until the participant reads it (its unread window); the next unread message after that opens a new window. Team Members never get one: in a creator's thread it goes to the Owner. Avoid: message notification, chat digest
Mandatory notification
A Notification type the user can't turn off, because it concerns account safety or access. It has no unsubscribe link. Avoid: required email, system email
Direct email
An email a Manager writes by hand and sends to addresses they type in, in the platform's email layout. Each address gets its own copy. It is not a Notification type and has no Activity, so it has no unsubscribe link. Every send is kept in its history unchanged; sending one again, edited or not, is a new Direct email. Avoid: custom email, broadcast, campaign, newsletter
Messages
Automatic reply
The message a Creator saves for buyers who write to them while they aren't around: outside the reply hours they set for each day of the week, or while they've marked themselves busy for now. It goes once in a chat until the Creator replies themselves. With no reply hours set, every message counts as outside them. Avoid: auto-responder, away message, messaging schedule, out-of-office
Home feed
Home feed
The public stream of what Creators and the platform have published, open to anyone without signing in. Acting on an entry, such as buying, saving, liking or commenting, needs sign-in. It is not the in-app feed, which is one user's own Activities. Avoid: in-app feed (for the Home feed; the in-app feed is a user's Activities), activity feed (for the Home feed), timeline, memberships hub
Feed item
One entry in the Home feed: a Creator's published post or shop product, several shop products one Creator published close together, or a platform announcement or milestone. It shows only while what it points at is still public: deleting the post or product removes it, unpublishing it or a Manager pausing the Shop hides it, and a group loses each product that stops being public and goes once none are left. Avoid: post (for a Feed item; a post is one kind of thing it points at), Activity, feed card
Newsletter posts
Element
A rich visual piece a Creator places in the body of a newsletter post, chosen from a fixed set and saying something Formatting cannot. Elements exist only in newsletter posts, and every Creator can use them. "Element" is the team's word: a Creator is never shown it, only each Element's own name. Avoid: component, block, widget
Formatting
The ordinary shaping of a post's text: headings, quotes, lists, tables, images, links, dividers and the Paywall break. Formatting is never an Element, however it was added. Avoid: basic element, simple element
Excerpt
The short line of plain text a Creator writes to introduce a newsletter post. It shows above the post and wherever the post is listed. Apart from a Free part, it is the only part of a locked post's writing that a reader without access sees, and the only part at all outside the post's own page. It is written, never cut from the body, so it never holds an Element. Avoid: summary, preview text, free part
Paywall break
The mark a Creator places in the body of a members-only or paid newsletter post to say where readers without access stop. A post holds at most one, and none sits below an Element. A post without one has no Free part. It is Formatting, and it shows readers nothing of its own. Avoid: read-more, cut, fold
Free part
The body of a locked newsletter post above its Paywall break, which any reader without access can read on the post's page, signed in or not, followed by the paywall. It is cut from the body, unlike the Excerpt, and the Creator chooses to give it; a post never has one by default. It never holds an Element. Avoid: preview, teaser, sample, excerpt
Element picker
The one place in the post editor where a Creator adds something to the body. It offers every Element, and Formatting as shortcuts beside them. Avoid: insert menu, block menu, slash menu
Element guide
The animated explanation of one Element, showing a Creator what it is for and how to fill it in. Every Element has one; Formatting has none. Avoid: tutorial, tooltip, help article
Element suggestion
A note from the AI review that a passage of a post would read better as a named Element. The Creator accepts or skips each one; nothing changes in the post until they accept. Avoid: recommendation, auto-format, smart block
Shop product Element
The Element that shows one of the Creator's own live shop products in a post and leads the reader to that product's page in the shop. It always shows the product as it is in the shop now, never as it was when the post was published, and it disappears for readers once the product can no longer be found in the shop. It holds no words of the Creator's own. Avoid: product card (as the name of the Element), product embed, shop product (alone, for the Element; that is the thing the shop sells)
Support button Element
The Element that lets a reader send the Creator a Coffee gift without leaving the post. It shows for readers only while the Creator is accepting Coffee gifts, and a post holds at most one. Avoid: donate button, tip button, coffee button, support button (alone, for the Element)
Gift prompt
The fixed invitation to send the Creator a Coffee gift that closes every newsletter post. The Creator doesn't place it and can't turn it off for a post: it shows whenever they are accepting Coffee gifts, and only to readers who can see the whole post. A post holding a Support button Element has no Gift prompt, so a post asks for a gift at most once. It is not an Element. Avoid: support strip, tip jar, donate banner, support button (alone)
Saved version
A copy of a newsletter post's title and body, kept so the Creator can go back to it. One is kept each time the whole body is about to be replaced: before AI polish rewrites the post, and before another Saved version is restored. Ordinary saving while writing keeps none. Avoid: revision, history, backup, AI edit
AI review
The AI's read of a newsletter post before it is sent off, returning todos and Element suggestions for the Creator to act on or skip. It advises the Creator and decides nothing. Avoid: review (unqualified), AI check, AI moderation
Automatic check
The machine check of a Moderation submission's text for profanity and unsafe content: a post's title, excerpt, tags and body (including the text inside Elements) and a Bio's text. It reports evidence only. A fixed server policy turns that evidence into approval, Manager review or rejection, and a check that could not run is a Technical failure, never approval. Images are not part of it; each one passed its own Image check when it was uploaded. Avoid: moderation (unqualified), AI review, filter
Text rule check
The fixed-rule check of text one person sends to another, or that a Connected app writes: credentials, card numbers, identity numbers and script content. It needs no outside provider and has two outcomes, pass or refuse with a reason the sender reads; nothing goes to Manager review. It ignores profanity and ordinary links. Avoid: Automatic check (for the fixed rules alone), filter, profanity check
Image check
The machine check of one uploaded image for unsafe content, made before the image has a public address. The image either passes and becomes public, or it is discarded: there is no Manager review, and a check that could not run discards the image so the Creator can try again. It is not a Moderation submission and decides nothing about the post or page the image is later used in. Avoid: image moderation, upload scan, Automatic check (for an image)
File removal
A content Manager's recorded removal of one public file a Creator uploaded (an image or a product video), with a reason the Creator reads. The file stops being served, the Creator's profile, banner and products stop pointing at it, and the decision is kept. It is distinct from a Takedown (which removes a Bio) and from resolving a Creator report (which only records a review). Avoid: Takedown (for a file), delete the image, purge (a purge is only the cache step)
Technical failure
A Moderation submission whose Automatic check could not produce a usable result (provider outage, timeout, malformed report). Nothing was decided: the submission stays private and the previous approved value stays public. For a Bio, the Creator can ask for the same version to be checked again or to go to Manager review, and once the attempts are used up the same version goes to Manager review by itself; a newsletter post goes to Manager review at once, marked as unchecked. A Technical failure is never approval, only a Manager's decision on the exact text publishes it. Avoid: rejection (nothing was wrong with the content), error (unqualified)
Manager review
A Manager reading a submitted newsletter post and either approving it, which publishes it, or returning it to the Creator as a draft with a reason. Every post passes through it, whoever or whatever wrote its content, except a post the Automatic check clearly rejects, which goes back to the Creator as a draft with a reason until they ask for Manager review. A Bio revision goes to Manager review when the Automatic check is unsure, when the Creator asks after a rejection or a Technical failure, or when a new video needs a person to watch it; the Manager approves it or rejects it with a reason. Every submitted product draft also goes to Manager review, and an uploaded product video has no public address until a Manager approves the draft it belongs to. Avoid: review (unqualified), moderation, approval queue
Reviewed copy
A newsletter post exactly as a Manager last decided on it, whether they approved it or returned it. A post has at most one, replaced at each decision. It exists so a Manager can see what changed when the post comes back to Manager review; the Creator never sees it and cannot go back to it. Avoid: Saved version, snapshot, baseline, previous version
Platform status
Status page
The public page at status.hobenakicoffee.com that tells Creators and Supporters whether each part of the platform they use is working right now. Avoid: incident page, uptime page, health page
Component
One user-facing capability listed on the Status page, named for what a person is trying to do (Sign-in, Payments, Creator pages & shops), never for a vendor or an internal system. Avoid: service, system, dependency
Monitor
A recurring automated check that decides whether one Component is up. A private Monitor alerts the team but is never shown on the Status page. Avoid: probe (that is a one-off check run during a release), health check (as the name of a Monitor), ping
Maintenance mode
The state in which the platform serves its maintenance page during a coordinated release. Avoid: downtime, maintenance window
Held release
A coordinated release that failed after its deploy started, leaving the platform in Maintenance mode until a Recovery succeeds. Nothing is rolled back; the way out is forward. Avoid: stuck release, failed release (one that fails before its deploy reopens the platform by itself), outage
Recovery
A new coordinated release, at a fixed commit, that takes over a Held release and reopens the platform when it succeeds. The Factory starts one by itself once a fix is on main. Avoid: rollback (nothing is undone), retry, rerun
Maintenance notice
The public announcement on the Status page that Maintenance mode is planned or under way. Releases that don't turn on Maintenance mode get no notice. Avoid: scheduled maintenance, downtime notice
Collecting and paying out
Collection agent
The platform's role in a payment. It receives a Supporter's money for the Creator and passes it on, and is never the seller. Avoid: merchant of record, reseller, intermediary
Wallet
The Creator's own money that the platform is holding for them, after the Platform fee and anything else they owe it. Creators see it on the page the app and the marketing site call Earnings (#944). Avoid: earnings we pay, account balance
Fee statement
The document a Creator can download for one payment they received. It shows what the Supporter paid, what the platform charged the Creator, and what the Creator kept, as things stand on the day it is downloaded, Refunds included. It is not a tax invoice. Avoid: invoice, tax invoice, receipt (that's the payer's document), payout statement
Invoice
The tax invoice the platform issues to a Creator for an Add-on or plan they bought from it. The platform is the seller. We never issue an Invoice to a Supporter: they paid the Creator, who is the seller, and get a Receipt (ADR 0016). In Bangla, ইনভয়েস. Avoid: receipt, Fee statement, bill
Receipt
The document the person who paid can download for one completed payment they made, on any service. It is their own record of the payment, not an Invoice, which the platform issues only to a Creator for an Add-on or plan. Avoid: bill, money receipt, Fee statement (that's the Creator's document)
Money back
Refund
Money going back to the person who paid, on any service. Either party to the payment can ask for one, and the platform's staff approve and complete it. It stays open until it's completed or rejected, and an approved Refund can still be rejected. Avoid: reversal, chargeback (that's the payer's bank pulling the money back)
Return
A buyer's request to send a shop item back. If the seller approves the Return, that opens a Refund for the item, so one Return leads to at most one Refund. A rejected Return leads to none. Avoid: refund request (that's a Refund that hasn't been decided yet)
Refusal
A buyer turning away a cash-on-delivery parcel at the door. Nothing was paid, so there is no Refund and no Platform fee. Asking the buyer to pay the delivery charge anyway is the shop's own policy, which the seller collects through their courier when they can. A buyer who refuses too often loses cash on delivery for a while, everywhere on the platform. Avoid: failed delivery, return (that's a Return), cancellation
Pricing
Platform fee
The percentage of a Supporter's payment that the platform charges the Creator for its service, taken out of the money it collected for them. It already includes payment processing, so neither the Creator nor the Supporter pays a gateway charge on top, apart from the Delivery processing charge. It is never taken from a delivery charge. Avoid: commission, cut, service charge
Delivery charge
What a Supporter pays to have a physical shop item delivered: one amount inside Dhaka and one outside. A product follows the shop's shipping settings for each amount until the seller gives that product its own, so changing the shop's settings changes every product still following them; a product with its own amount keeps it. Cash on delivery and processing days follow the shop the same way. A placed order keeps the charge it was placed with. The Platform fee is never taken from it. Avoid: shipping cost, delivery fee
Delivery processing charge
A fixed percentage of the delivery charge on an online payment that the Creator pays, passing on the cost of processing that part of the payment. It is not a Platform fee and doesn't count towards Volume. Cash on delivery has none, and a Fee cover never pays it. Avoid: gateway fee, pass-through, delivery fee, surcharge
Gift wrap fee
The amount, set in the shop's settings, that a Supporter pays for gift wrap on a shop order. It is the Creator's: they set it and do the wrapping, and it is credited to their Wallet in full. It is not a Platform fee, carries none, and never counts toward Volume. It is not one of the things the platform takes from the money it collects for a Creator. In Bangla, গিফট র্যাপ ফি. Avoid: gift-wrap fee, wrapping charge, gift fee
Coupon
A code a Creator makes for their shop that takes a percentage or a fixed amount off a shop order, or off its Delivery charge, when a Supporter enters it at checkout. The Creator can limit it to certain products, dates, a number of uses, or first-time buyers. Avoid: promo code, voucher, discount code, Founder ticket
Over-limit use
A use of a Coupon past its limit, made when a Supporter pays for an order after it expired and the Coupon's uses had run out in the meantime. The payment is kept, so the use stands. It never counts towards the Coupon's uses, and stays an Over-limit use even if the Creator raises the limit later. Avoid: late payment, overuse, extra use
Guest checkout
Buying from a shop without signing in, paying online or by COD with just a name and phone. A guest can't buy digital items or send a gift, and has a cap on unshipped COD orders at one shop. Avoid: anonymous order, quick checkout
Order link
The private link that opens one guest order. Only someone holding it can see the order; a phone number and order number alone open nothing. Avoid: tracking link, lookup URL
Awaiting payment
The state of an online shop order with no booked payment that is under 60 minutes old. The order exists but is not paid, so its page says so and offers Pay again; it is not a confirmed order. Past 60 minutes, or once marked expired, it is closed instead and nothing was charged. Cash on delivery and free Reward orders are never awaiting payment. Avoid: pending order, failed order
Fee cover
An optional amount a Supporter adds to an online payment so the Creator receives the full price. It is that payment's Platform fee, round-up included, and is never itself charged a fee. Avoid: tip, donation, surcharge, payment fee
Rate card
The public table of Platform fees, by Rate family and Volume tier. Avoid: pricing plan, price list
Rate family
A group of services that share the same Platform fees. There are two: Hosted (the Creator sells it and the platform hosts and delivers it for them: coffee gifts, the newsletter, paid posts, memberships and digital products) and Shipped (the Creator delivers it: physical products). Avoid: category, tier, service type (when the family is meant)
Volume
What a Creator's Supporters paid them in a calendar month in Dhaka time, across every service, counted when the money arrives and less any refunds paid out that month. It leaves out delivery charges and Fee covers. Avoid: GMV, sales, revenue, earnings
Volume tier
The step of a Rate family that a Creator pays this month, fixed on the 1st by last month's Volume and never changed afterwards. Avoid: plan, level, bracket
Partner agreement
Platform fees the platform has set for one Creator and that Creator has accepted, on some or all services, for a stated period. Where it applies, it replaces the Rate card, whether its fee is higher or lower. It may carry a monthly cap on Volume, after which the next most specific rate applies for the rest of that month. Avoid: deal, override, custom plan
Floor rate
The lowest Platform fee any Creator can pay unless an admin deliberately overrides it and records why. Avoid: minimum fee
Tax credit-back
Money credited to a company Creator's wallet to match the income tax they withheld from our Platform fee and paid to the government, once an admin accepts their Tax certificate. Like any wallet credit, it pays Fees owed first. Avoid: tax refund, rebate, tax certificate (that's the evidence, not the credit)
Tax certificate
The government's deposit certificate for income tax a company Creator withheld from our Platform fee, which the Creator submits as evidence for a Tax credit-back. An admin accepts or rejects it. Avoid: receipt, challan (that's its number), deposit slip
Launch rate
One flat Platform fee for every Creator on every service, from the platform's launch until a published end date. No Partner agreement may charge more than it while it lasts. Avoid: founder discount, intro offer
Founder rate
The flat Platform fee the Founder cohort keeps for a fixed period after the Launch rate ends. No Partner agreement may charge a Founder more than it while it lasts. Avoid: lifetime rate, founder discount
Founder cohort
The Creators the platform has told in writing that they are Founders. Everyone sent a Founder ticket for joining the Waitlist is one; people who joined before the Founder ticket existed were never told, so they are not. Membership belongs to one account, can't be transferred, and ends if the account is terminated for breaking the Creator Agreement. Reader-facing copy says joiners get the Founder rate and join the Founder community; it never says they "become a Founder" as if it were a title or a role. Avoid: founder 1,000, early adopters, founder discount
Founder ticket
The written notice that makes someone a Founder, sent the moment they join the Waitlist. It carries their Founder number, the Founder rate and the date that rate ends. Avoid: founding member pass, pass, coupon, voucher
Founder number
A Founder's place in the order Founders joined the Waitlist, printed on their Founder ticket. It is theirs alone and never changes. Avoid: ticket ID, serial, rank
Ticket page
The public page a Founder shares to show off their Founder ticket: the Founder number and join date, never who they are. Only someone who has been given the link can find it, and it can be switched off for good on request. A browser that arrived from the ticket email sees an owner view with the Founder rate and a share button; everyone else sees the visitor view with the word "Founder" and a join button. That is a layout hint, not a privacy rule. Avoid: founder profile, share card
Business day
Sunday to Thursday in Dhaka time, except public holidays and bank holidays declared by the Government or Bangladesh Bank. Payout timing is counted in business days. Avoid: working day, weekday
Add-on
A paid monthly extra, such as more storage, that covers a cost the platform carries whether or not the Creator earns. An Add-on never changes a Platform fee. Avoid: plan, platform subscription, upgrade
Self-run
A Creator building and operating their own shop, newsletter, membership or payment page instead of using the platform. Marketing compares the two in the Self-run comparison on each service's feature page. Avoid: DIY, in-house, roll-your-own
Bangla names (product copy)
Agreed in #415. Use these in BN copy; the English labels are the glossary terms. Everyday words (মেম্বার, not সদস্য) are in the writing-copy skill's word list, tooling/content-guard/src/words.json.
| Term | Bangla |
|---|---|
| Hosted (Rate family) | আমরা হোস্ট করি |
| Shipped (Rate family) | আপনি শিপ করেন |
| Delivery processing charge | ডেলিভারি প্রসেসিং চার্জ |
| Volume | ভলিউম |
| Volume tier | ভলিউম ধাপ |
| Launch rate | লঞ্চ রেট |
| Founder rate | ফাউন্ডার রেট |
| Founder ticket | ফাউন্ডার টিকিট |
| Partner agreement | পার্টনার চুক্তি |
| Add-on | অ্যাড-অন |
| Fee statement | ফি স্টেটমেন্ট |
Collecting, holding and paying out
Collection agent
The platform's role in a payment. It receives a Supporter's money for the Creator and passes it on, and is never the seller. It has no Bangla label: Bangla copy describes the act (we take the payment for the Creator) and never says এজেন্ট for the platform's role. Avoid: merchant of record, reseller, intermediary
Creator funds
Money the platform has collected for a Creator and not yet paid out. It belongs to the Creator from the moment the Supporter pays, never to the platform. Avoid: supporter funds, float, escrow, pass-through
Wallet
One person's balance on the platform. A Creator's Wallet is their Creator funds: their own money that the platform is holding for them, after the Platform fee and anything else they owe it. Creators see it on the page the app and the marketing site call Earnings (#944). Avoid: account, ledger, earnings we pay
Payout
Creator funds sent to the Creator's own bank or mobile money account, at the Owner's request. It is not a payment by the platform, and it is free: the Platform fee was already taken when each payment arrived. Avoid: payment, salary, withdrawal (in app and email copy), cash-out, disbursement, settlement
Payout request
A Creator asking for some or all of their Wallet to be sent as a Payout. The terms call it a withdrawal; the app and emails don't. In Bangla, টাকা তোলা, never উইথড্র. Avoid: withdrawal (in app and email copy), cash-out request
One-person approval
One Manager approving a Payout request and recording it as sent in the same step, with the provider transaction ID as the evidence. It stays while the team is small; see ADR 0069. Avoid: single sign-off, self-approval
Identity verification
The platform's staff checking a Creator's Bangladesh NID and selfie by hand. Approval is what allows Payout requests and gives the Creator the verified badge; it says nothing about their character or the quality of what they sell. Avoid: KYC (in copy readers see, except legal pages), NID verification, ID check
Payout hold
The platform delaying or pausing a Creator's Payouts: for suspected fraud, a breach of the terms, an investigation, an open chargeback dispute or a payment gateway restriction. It is one of the four limits the terms put on Creator funds, with Refunds, chargebacks and Fees owed. In Bangla, পেআউট আটকে রাখা. Avoid: fund withholding, fund hold, freeze, withholding (that's tax)
Refund owed
The part of a Refund that the Creator's Wallet couldn't cover because the money had already been paid out. The Creator owes it to the platform, and later credits to the Wallet pay it off first. It is not Fees owed. Avoid: negative balance, refund debt, clawback
Payment hold
A payment the payment gateway took from a Supporter that the platform could not book, so it belongs to no Wallet yet. It stays open, with an alert for Managers, until the payment is booked after all (the gateway sends its notification again) or paid back at the gateway. It is not a Payout hold or a COD hold, which are stops on a Creator, and it is not a ledger row: it moves no Wallet.
Platform revenue
What the platform earned in a period, read from the ledger as separate lines: the Platform fee, the Delivery processing charge, Add-on purchases, and Fees owed paid later (through the gateway or recorded by an admin). The Fees owed lines are cash received against fees already counted, so they are not added to the first lines. The gift wrap fee is not Platform revenue: it is the Creator's.
Creator funds account
A bank account that holds Creator funds apart from the platform's own money. Avoid: settlement account, escrow account, trust account
Gateway deposit
The payment gateway paying money it collected into the platform's bank, as one sum covering many payments less the gateway's own charge. Avoid: settlement (that's cash on delivery, see Settlement window), gateway payout
Cash on delivery
Fees owed
Platform fees on cash-on-delivery sales that the Creator's wallet couldn't cover when the cash was confirmed. Every later credit to the wallet pays them off first, and the Creator can also pay them directly. They count toward COD exposure. Avoid: COD debt, dues, unpaid fees, COD balance
Creator standing
How far we trust a Creator to pay back what they owe us. It is built only from the COD Platform fees they've actually paid and the number of orders those fees came from, less any penalties. It never measures how big or valuable a Creator is. Avoid: trust score, credit score, reputation
Standing level
A step on the platform's ladder that turns Creator standing into a COD limit. KYC raises the starting level and is needed for every level above it. Avoid: tier (that's Volume tier), rank, credit limit
COD limit
The most COD exposure a Creator can carry before cash on delivery stops for them. It is set by their Standing level unless a Raised COD limit or COD hold applies. Avoid: fees owed limit, wallet floor, credit limit
COD exposure
Fees owed plus the Platform fee on every COD item whose cash isn't confirmed yet, counted without subtracting the wallet balance. Avoid: outstanding COD, COD balance, risk
Raised COD limit
A COD limit an admin has set above a verified Creator's ladder limit for a set period. It ends early if the Creator is penalised. Avoid: override, custom limit, manual limit
COD hold
An admin stop on one Creator's cash on delivery, lifted only by hand. Their shop and online checkout stay open. Avoid: suspension, ban, block
Settlement window
The days a Creator has, from shipping a COD item, to confirm its cash. Avoid: grace period, deadline
Overdue settlement
A COD item whose cash is still unconfirmed when its Settlement window ends. It costs the Creator one Standing level. Avoid: aged settlement, late payment
Write-off
Fees owed that an admin cancels without payment. Any Write-off, of any amount, sends the Creator back to the start of the ladder. Avoid: waiver, forgiveness
Public pages
Page language
The language a public page is shown in. The address decides it (an /en/ page, or ?lang=), and failing that, on a Creator's page, the language the Creator chose. Anything the page asks the server for, such as an error message, answers in the same language. The visitor's remembered choice only applies when a page's address names no language. Avoid: calling-page locale, request locale, cookie language
Waitlist
The list of people who asked to be told when the platform opens for them. Joining it is the one thing the landing page asks a visitor to do. Joining before sign-up opens earns news first and a place in the Founder cohort. Once sign-up opens, there is no Waitlist to join. Avoid: wishlist (the code's older name for it), early access, pre-registration, founding member
Public content
Content feedback
A reader’s choice about whether a public content page was Helpful, Partly helpful or Not helpful. It belongs to one page and language, and the reader can change it. Avoid: sentiment, review (Content feedback measures usefulness, not feelings or written reviews)
Experience rating
A person's optional 1–5 stars and optional short comment on how one Rated moment on the platform felt, given right after they finished it. It is about the platform, never about a Creator: the Creator never sees it and it is never public. Only the platform's team reads it. Avoid: review (taken by product reviews, Manager review and AI review), feedback (unqualified; content feedback is the helpful/not-helpful choice on a content page), testimonial, survey
Rated moment
A finished flow that asks for an Experience rating, such as sending a Coffee gift or making a Payout request. Each one is named, so ratings of different moments are never mixed. A rating counts only for a flow that really finished, one per finished flow, and no sign-in is needed. Someone who rated a Rated moment in the last 30 days isn't asked about it again. Avoid: touchpoint, trigger, event
Apps
Desktop app
The web app opened in its own window on a Mac, Windows or Linux computer, for Creators and Supporters alike. It is the same app and the same account as on the web, with a tray icon, desktop notifications and an unread badge added around it. Avoid: native app, Electron app, desktop client, creator app (it serves Supporters too)
Mobile app
The app on an iPhone or Android phone, installed from the App Store or Google Play, for Creators and Supporters alike. It uses the same account as the web. Avoid: phone app, iOS app or Android app (when both are meant)
Coming soon
A service a Creator can't turn on yet, or a Desktop or Mobile app platform (Mac, Windows, Linux, iPhone or Android) that has no download yet. Each one becomes Available on its own, not all at once. It never describes the platform itself before it opens; that is what the Waitlist is for. Avoid: beta, pre-order, waitlist (neither a service nor an app platform has a Waitlist)
Service request
An Owner asking the platform for a service it doesn't offer. It is recorded for review and is not a promise to build it. The Owner sees one of four states: Received, Planned, Built or Not planned. Avoid: feature request, wish, vote
Request reply
What a Manager writes back to the Owner about one Service request. The Owner sees it next to the request's state. A request that leaves Built or Not planned drops its reply unless the Manager writes a new one, so the Owner never reads an old outcome's answer beside a new state. A Manager's internal note is never shown to the Owner. Avoid: admin note (when the reply is meant), comment
Desktop shell
The part of the Desktop app that is not the web app: the window, the tray icon, the notifications, the badge and the updates. It holds no account data and no features of its own, and it opens the hosted web app. Avoid: wrapper, container
System settings
The tab of the Desktop app's settings whose switches belong to this computer, not to the account: launching at login, the dock, running in the tray, desktop notifications and their sound, and the unread badge. It does not exist on the web. Email choices stay in the email preferences. Avoid: desktop settings, preferences, device settings
Desktop notification
A notice the Desktop shell shows for a new Activity, and the click on it opens the Activity page. It follows the System settings, not the email preferences, though it files each Activity under the same category as its email (Earnings, Engagement, Account, Orders). Avoid: push notification, popup, toast
Local development
Full stack
The one complete local Supabase stack (database, auth, storage, API gateway, Studio, Mailpit, edge runtime) on the fixed local ports. Dev servers, browser checks, edge-function integration tests and seeding run against it, and only by the worktree holding the Stack lease. Avoid: the local database (it means a Headless database just as often), shared stack
Headless database
A Postgres-only container that belongs to one worktree and serves its pgTAP and seed tests. It is disposable: it is rebuilt whenever its Schema fingerprint stops matching the branch, and removed with its data after 30 idle minutes. Avoid: test database, shadow database (that is Supabase's own diff database)
Stack lease
The claim one worktree holds on the Full stack, with that worktree's path, its process and a heartbeat. Another worktree may take it over once the holder is gone or silent for 30 minutes; a lease a Factory task holds the owner may take over at once. Avoid: lock (the old dev-stack lock covered the whole machine), reservation
Schema fingerprint
A hash of a branch's migrations and seeds, stored in each local database. Two worktrees with the same fingerprint can share a database as-is; a mismatch means reset and re-seed. Avoid: schema version, migration version (a single migration timestamp misses seed changes)
Hosting
Deployment environment
One complete hosted copy of the platform, with its own data, its own addresses and its own accounts with outside services. There are two, Production and Staging, and neither ever holds the other's data or credentials. Avoid: tier (that's Volume tier), stage, server
Production
The Deployment environment real Creators and Supporters use, at hobenakicoffee.com. Only a Promotion changes it. Avoid: live (as a noun), prod (in docs)
Staging
The Deployment environment where the team tries a change before it reaches Production, at staging.hobenakicoffee.com. A merge to main changes it. It has the same setup as Production but none of its data, the QA team's own data stays there between changes, and only the team's own test accounts can sign up. Avoid: test server, preview, dev (that's local development)
Promotion
Sending a commit that already passed Staging to Production. It happens by itself in the nightly Release window, or at once for a hotfix, and it always ships every commit merged up to the one promoted. Avoid: release (alone, it's ambiguous), push to production, publish
Release window
The nightly time, 04:00 in Dhaka, when the Promotion runs if Staging has something newer than Production and nobody has blocked that night's release. Avoid: maintenance window (Maintenance mode happens inside it only when the Promotion changes the backend), deploy time
Feature flag
A switch, set separately in each Deployment environment, that turns a feature off, on for everyone, or on for a list of accounts. Turning one on in Production is how a feature launches; the code was already deployed. Avoid: toggle, kill switch, experiment
Software factory
Factory
The machinery on the owner's machine that takes issues ready for an agent and turns them into merged pull requests, with a person stepping in only where a check says one is needed. Triage stays with the owner. Avoid: pipeline (that's CI), bot, automation
Agent loop
The part of the Factory that picks the next ready issue, builds it in its own worktree, and carries the pull request through to a merge and a green deploy. Avoid: AI loop, worker, runner
Human-needed check
The step before the Factory merges a pull request that decides whether someone must act on it before it merges (the owner, or the Factory's agent when the work is its own to do), a person after it merges, or no one. Avoid: approval, review (that's code review), human verifier
Merge lane
The line in which the Factory's finished pull requests take turns being the one that is ready for review and merging. Avoid: merge queue (GitHub's feature, which this repo cannot use), release train
Collect run
One scheduled pass of the Factory over the platform's error sources that turns new Leads into issues waiting for triage. Avoid: bug sweep, scan
Lead
Something one or more error sources say might be a bug that has no issue yet. A Lead becomes an issue, or is dismissed. Avoid: finding (that's a review's), alert, incident
Heartbeat
The Factory's regular sign that it is still working. A missed Heartbeat alerts the owner; while Heartbeats arrive, the Factory stays quiet. Avoid: ping, status post
Hand-over
The point where the Factory stops on an issue or pull request and gives it to a person. Avoid: escalation (that's the Factory's last attempt on a stronger model, before a Hand-over)
Follow-up run
A new Factory run on an issue whose merged pull request did only part of it and left it open, building what that pull request listed as not done. The owner starts it; the Factory never picks a merged issue again by itself. Avoid: part 2
Hold
The stop on a Factory pull request that a person must act on before it can merge. It lasts until the owner clears it or merges the pull request themselves. Avoid: block, pause
Start wait
A time when the Factory starts no new task because usage, the machine's load or its memory leaves no room. Tasks already running carry on. Avoid: hold (that's the stop on a pull request), budget wait, pause
Console
The owner's live view of the Factory, and the place they operate it from, on the Factory's machine or their phone. Avoid: dashboard, admin (that's the platform's admin app), control panel
QA issue
The issue the Factory files for a merged change, listing what to check now that the change is live. Avoid: QA ticket
QA pass
One AI tester working through one QA issue and reporting, step by step, what passed, what failed and what it could not test. Avoid: QA run (that's one persona played over one module)
LLM leaderboard
Harness
The coding agent a model runs in, such as Claude Code or the Antigravity CLI. A leaderboard row is one model at one effort in one harness.
Benchmark suite
A fixed list of tasks, each a replay of a real merged pull request, that every leaderboard row is scored on. Once released it is frozen: a changed task means a new suite version with its own board.
Hidden check
A test or script that grades a benchmark run and stays out of the model's copy of the repository until the run ends.
Field note
An unranked, hand-logged impression of a model in a harness after real work: date, link, a rating from 1 to 5 and one line. It never changes a rank.
Judge flag
A marker on a judged convention item whose two judge scores differ by more than 1 point. The project owner decides it, and that score replaces the judges' average. Avoid: dispute