Shared Brioso vocabulary

Shared Brioso vocabulary

Internal reference for naming product concepts and platform components. Use these terms in plans, tickets, reviews, and team documentation. This page describes concepts; the linked sources own schemas, states, prices, and configuration.

View the product to platform map or edit it in Excalidraw.

Product lines, shared assets, and generation path

Product lines

Preferred term Meaning Source
Creator Studio The creator experience for making a custom track from a brief and iterating on the result. The PRD calls this line creator custom generation. PRD, creator flow
Royalty-free Catalog The browsable library of previously generated tracks. A buyer selects an existing track; browsing does not submit a generation job. PRD, catalog model
Audio Brand Kit The agency product: an approved Audio Strategy leads to several generated assets and a white-label kit. The kit is a parent deliverable, not one track. PRD, kit state
Brioso Pro The subscription product that grants creator and catalog access through entitlements. It is not a product line that generates audio itself. PRD, entitlement resolver

Domain and commercial assets

Preferred term Meaning Source
Brief The customer’s input describing the desired audio or brand. Creator jobs and kits store different brief forms. PRD, data model
Audio Strategy The editable agency plan inferred from a brand and approved before kit generation. It specifies the kit but is not generated audio. PRD, strategy code
Kit The agency parent record and assembled set of brand audio assets. Its lifecycle is separate from each child job’s lifecycle. kit state, data model
Job A queued unit of generation work with its own lifecycle and selected runner. A kit can create multiple jobs. job contract, jobs guide
Generation One execution of a job that produces audio. Recreating a creator result starts another generation within that job’s history. creator flow, job model
Track One audio result or catalog item. Say generated job track for an entry in jobs.tracks and catalog track for a catalogTracks row. data model, job schema
Preview The protected listening version of a track. It is distinct from a clean downloadable master. PRD, storage model
Master The clean, full quality source audio used for eligible downloads and deliverables. FLAC is the platform’s lossless master format. PRD, storage model
Deliverable The customer-facing package or file provided after the relevant access check, such as a track download or kit ZIP and guidelines. PRD, kit assembly
Checkout The Stripe session that starts a paid transaction. Creating a session does not itself prove payment or grant access. catalog checkout, kit checkout
Purchase A recorded acquisition of a specific item. A catalog purchase row can represent a paid sale or a Pro access claim with a synthetic session ID and no charge. catalog access, billing webhook
Entitlement The resolved access a user currently has from subscriptions and grants. It can permit an action without a purchase of that individual track. resolver, billing model
License The legal rights and conditions attached to a delivered item. Use the relevant creator, catalog, kit, or free license document for the actual terms. creator, catalog, kit, free
Share link A token URL associated with a job for viewing its shared space or kit. It is not scoped to one track and does not prove a purchase or license. share link schema, sharing store

Catalog discovery

Preferred term Meaning Source
Browse axis A dimension used to browse the catalog, such as genre, mood, instrument, or use case. An axis is a route and classification dimension, not an audio asset. taxonomy, catalog routes
Taxonomy leaf A selectable category within an axis, such as a genre or mood. A leaf can exist before it has published tracks. taxonomy, use cases, PRD
Slug The stable URL token for a category or catalog track, derived separately from its human label. slug rules
Display name The name shown to a person browsing a taxonomy leaf. It need not be the best token for model conditioning. taxonomy nodes
Prompt term The optional model conditioning term for a taxonomy leaf when its display name produces a poor result. taxonomy promptTerm
Catalog track A published or unpublished library item in catalogTracks, with catalog classification and storage keys. It is not a creator or kit job track. data model, schema

Platform and operations

Preferred term Meaning Source
App A deployable or runnable entrypoint under apps/, such as the web app or home worker. architecture
Vertical A product-line slice under packages/verticals/ that owns line-specific workflow code. It is not a separate deployed app. repo layout, vertical packages
Shared package A reusable capability under packages/, such as jobs, storage, billing, or dispatch, used across product lines. repo layout
Contract A shared typed boundary between components, especially the job states and web to runtime payload. A contract defines shapes, not a product line. job states, contract package
Queue The durable job and lease machinery that records pending and in-flight work. The queue does not choose a GPU by itself. jobs guide, job model
Dispatch The web-side action that selects a candidate runtime and pushes a job to it. It uses the gateway’s ordered fallback chain. jobs guide, dispatch code
Reaper The periodic recovery and completion check for stale or unfinished runtime calls. It can poll runtime status and apply fallback. architecture, dispatch package
Gateway The resolved configuration and routing boundary that declares runtime IDs, kinds, and fallback order. gateway contract, config loader
Runtime One configured execution destination, identified by a runtime ID. Its ID can be stored in a job’s runner field. gateway contract, jobs guide
Runtime kind The runtime’s implementation family, such as home, local, or modal. Kind selects the push and status protocol; it is not the runtime ID. gateway contract
Runner The job field jobs.runner: the selected runtime ID used when dispatch starts. Use runtime for the configured destination and worker for the process doing work. jobs guide, data model
Worker The process or service that accepts a pushed job, runs generation, and reports or exposes its result. architecture, worker guide
Model handler The worker-side implementation that invokes an audio model for a job. It is downstream of routing and independent of the product line. architecture, inference core
Storage surface The database or object store holding records or artifacts. Job and catalog objects use separate R2 buckets. data model

Do not conflate

Terms Distinction
Catalog track and generated job track A catalog track is a library row; a generated job track is a result inside a job. They have separate storage, discovery, and sale paths.
jobs.runner, runtime, and provider runner is a runtime ID on the job. A runtime is a gateway destination with a kind. Provider or hardware names do not replace that ID.
Runtime kind and runtime ID modal describes a protocol family; an ID identifies one configured destination.
Checkout, purchase, entitlement, and license Checkout starts payment; purchase records an acquisition, which can be a Pro catalog claim; entitlement resolves access; license defines legal rights.
Preview, master, and deliverable A preview is for listening, a master is source audio, and a deliverable is what the customer receives.
Kit and job A kit owns the agency result and can fan out into multiple generation jobs. Their state machines are separate.

The current state sets live in the job-state contract and kit-state source. Current prices and product status live in the PRD; database and bucket details live in the data model; runtime configuration lives in the gateway contract.