Glossary

Introduction

Shared vocabulary for the platform: the roles (who's who), the platform and architecture terms, and the iGaming domain terms.

Roles

| Term | Who it is | | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Operator / consumer | The developer or company that installs @openora/core and runs their own iGaming. The end user of the package, not a gambler. Brings their own extensions.config.ts and vendor adapters. | | Player | The person who registers on an operator's site, deposits funds, and plays. The operator's customer. | | Admin / backoffice user | Operator staff who manage players, approve withdrawals, configure games, and edit content. A role on the auth user, not a separate person type. | | Maintainer / core contributor | Someone working on the framework itself - distinct from an operator who only consumes it. |

Platform and architecture

| Term | Meaning | Maps to | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- | | Headless | The platform ships backend only - modules, contracts, API, and an SDK consumption surface. The operator supplies the entire frontend. | @openora/core/react | | Module | A business domain packaged as an independently loadable unit. Never imports another module's internals. | packages/core/src/<domain>/<module>/ | | Domain | A grouping of related modules sharing one subpath. Nine of them ship. | @openora/core/<domain> | | Plugin / overlay | A drop-in unit that adds or overrides behavior via definePlugin({ id, register }). The only way new functionality enters the system. | extensions/* | | Adapter / port | The vendor-agnostic interface a module depends on, plus its per-vendor implementations. The swap seam: a module declares the interface and a DI token; an operator binds a concrete impl. | @openora/core/contracts + <module>/adapters/<vendor>/ | | Contract | The composed oRPC router. Drives request validation, the typed client, and the emitted OpenAPI spec. | @openora/core/contracts | | Command port | A synchronous, transactional interface one module exposes so another can mutate it atomically inside the caller's own tx. | WALLET_COMMANDS | | Sealed token | A SealedToken<T> whose backing service an operator may never override - RG enforcement, KYC writes, AML/SAR, ledger writes, RNG. Structurally incompatible with Token<T>, and rejected at bind time by the plugin host. | @openora/core/compliance | | Outbox | A table an event envelope is written to inside the emitting transaction, so a durable broker can publish it after commit, at least once. | event_outbox | | Platform config | Operator-editable, Zod-validated YAML or JSON consumed at boot. Controls feature flags, brands, and responsible-gaming defaults per geo. | loadPlatformConfig() | | Scaffold | A deterministic code-mod that stamps a module, plugin, route or adapter skeleton. | pnpm gen | | MCP dev server | A stdio tool server agents connect to for read-only inspection and scaffolding. | apps/mcp-server-dev | | RGS | Remote Gaming Server: the engine that runs rounds, applies RTP, and settles bets. Third-party, or your own. | gaming module + GAME_ADAPTER |

Identity and compliance

| Term | Meaning | Maps to | | -------------------- | -------------------------------------------------------------------------------------------------------------------------- | ----------------------------- | | KYC | Know Your Customer. Verifying a player's identity - ID, selfie, proof of address - usually via a third party, before withdrawals above a threshold. | identity / KYC_ADAPTER | | AML | Anti-Money Laundering. Controls and monitoring to detect laundering through play: limits, source-of-funds, suspicious-activity flags. | compliance | | 2FA | Two-factor authentication (TOTP) on a player or admin account. | identity | | Geo-blocking | Refusing service from restricted jurisdictions based on IP or region. | compliance / GEO_IP_ADAPTER | | Jurisdiction | The regulatory regime an operator runs under. Dictates allowed countries, game rules, RG requirements, and reporting. | operator concern |

Wallet and payments

| Term | Meaning | Maps to | | ----------------------- | --------------------------------------------------------------------------------------------- | ------------------------------ | | Wallet | A player's balance plus the append-only log of money movements. | wallet module | | Balance | Spendable funds, shown in real time. May differ from pending. | wallet | | Deposit / withdrawal | Money in, money out, in fiat or crypto. | wallet | | PSP | Payment Service Provider - a fiat payment vendor integrated behind an adapter. | wallet / PAYMENT_ADAPTER | | Idempotency key | A key carried on a money-path write, unique per wallet, so a retried webhook applies once. | wallet_transaction | | Chargeback | A reversed card payment a player disputes with their bank. A fraud and risk concern. | operator concern |

Games and fairness

| Term | Meaning | Maps to | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- | | Game provider | A studio or vendor supplying games, integrated behind an adapter. | gaming / GAME_ADAPTER | | Aggregator | A single integration that fans out to many game providers' catalogues. | AGGREGATOR_ADAPTER | | Game round | One play cycle: bet, result, settle. | gaming | | Lobby | The browsable surface of games: categories, featured slots, search. | lobby | | RTP | Return To Player - the long-run percentage of stakes a game pays back. The complement is the house edge. | game config | | Provably fair | A scheme letting players verify a result wasn't tampered with: a server seed is committed before the round, combined with a client seed and a nonce, then revealed. | gaming (foundation) |

Responsible gaming

| Term | Meaning | Maps to | | --------------------------------- | -------------------------------------------------------- | ------------ | | Responsible gaming (RG) | Player-protection features required by most regulators. | compliance | | Deposit / loss / wager limits | Player-set or mandated caps over a period. | compliance | | Cool-off | A short, self-imposed break from play. | compliance | | Self-exclusion | A player blocking themselves from play for a set period. | compliance |

Content, social and business

| Term | Meaning | Maps to | | ----------------------------- | ----------------------------------------------------------------------------------------------------------- | ----------------------------- | | CMS | Operator-managed static pages and banners: terms, FAQ, promos. | cms module | | Notifications | In-app and email events: deposit confirmed, withdrawal status. | notifications | | Chat | Global and in-room messaging with user blocks, pushed over SSE. | chat module | | VIP tiers | Loyalty levels granting perks based on activity. A consumer extension, not core. | your overlay | | Affiliate | A partner who refers players for a revenue share. Not core. | operator concern | | GGR / NGR | Gross and Net Gaming Revenue - stakes minus wins; NGR also nets bonuses and fees. The core operator KPI. | analytics |