Understand Rivya terms for Studio, public pages, credits, models, tools, uploads, task states, providers, commercial use, and docs.

Use this glossary when a Rivya term appears across docs, model pages, pricing, Studio, or support flows and the product meaning needs to stay consistent.

It exists for two reasons:

to keep the product terms precise across docs, blog, model pages, and pricing pages
to keep English and Chinese content aligned in meaning without forcing either language to read like a literal translation

Why This Page Exists

This glossary helps when a term keeps appearing, but you are not sure whether it is:

a UI label
a path boundary
a billing concept
a workflow concept
a policy term

If the product seems confusing, the problem is often not the feature itself. It is the vocabulary around the feature.

Product Area Terms

Public pages: browseable paths such as /chat, /image, /video, /audio, /ai-models, /tools, /blog, and /docs
Public start pages: public paths such as /chat, /image, /video, /audio, /ai-models/[slug], and /tools/[slug] that combine explanation, examples, and a fast starting point on one page
Studio: the signed-in work area where saved, billable, continuing work lives
Dashboard: the logged-in orientation page that shows balance, recent work, and quick reopen paths
History: the saved record of generations and chats that lets you return to previous work
Notifications Center: durable operational events such as billing updates, credit warnings, and generation outcomes
Settings: account-management pages such as profile, billing, credits, and security

Billing Terms

Credits: the spendable unit Rivya uses across chat, image, video, audio, and tool-based chat work
Signup credits: the starter credits new accounts receive, currently with a shorter expiry window
Subscription credits: recurring monthly credits attached to a paid plan
Credit packs: one-time purchased credits used for overflow, burst work, or non-subscription use
Wallet: the shared balance layer that holds the account's usable credits
FIFO: "first in, first out" spending logic, where older unexpired credit balances are consumed first
Credits hint: a model-page comparison cue, not a binding final invoice by itself

Execution Terms

Model page: the structured public detail page for one live model, including strengths, use cases, parameters, and a first-run path
Tool: a narrower way into chat when the task already has a clear shape, not a separate mini product
Direct generation: whether a model can actually be run in Rivya instead of only being listed in the catalog
References: image, video, or audio files that guide a run when a model accepts them
Uploads: files sent into a signed-in workflow for reference, source transformation, cleanup, or analysis
Task lifecycle: the sequence from validation and credit handling through provider submission, success, failure, history, and notifications
Task states: the tracked status values such as WAITING, GENERATING, SUCCESS, and FAILED
Callback / polling: the ways Rivya learns the result of an async run after the provider has started work

Trust And Policy Terms

Provider: a third-party service Rivya relies on for billing, sign-in, generation, storage, email, or infrastructure
Upstream provider: the model or infrastructure provider used behind a workflow after Rivya paths the request
Commercial use: using outputs in client work, campaigns, product assets, or other business contexts
Output ownership: the current Rivya policy position that outputs generated through your account are yours as between you and Rivya, to the extent permitted by law
Sensitive data: personal, confidential, regulated, or high-risk information that deserves extra care before submission
Public vs authenticated boundary: the line between browseable public paths and signed-in saved execution

Bilingual Notes

Studio stays in English in the docs because it is a product label, path name, and UI concept
Create now appears mainly in historical or retirement-note context, not as a current public page family
model names, provider names, and brand names stay in their original form
Chinese docs should translate the concept, not mechanically translate the sentence shape
English docs should stay precise for search and product clarity, not try to imitate Chinese phrasing

That is the real goal of bilingual alignment here: same meaning, natural reading in each language.

Glossary Review Checklist

Before adding or changing product vocabulary, check:

Confirm whether the term is a UI label, route family, billing concept, workflow concept, or policy concept.
Keep English and Chinese aligned by meaning, not sentence shape.
Use Studio, model names, provider names, and route names consistently.
Avoid inventing a new label when an existing docs term already explains the same thing.
Recheck pricing, upload, provider, or commercial-use terms before using them in public pages.

The goal is to keep Rivya understandable across docs, blog, model pages, and product pages.

When To Recheck Vocabulary

Recheck vocabulary when a new page introduces a route, model capability, billing behavior, upload type, provider boundary, or commercial-use statement.

In those cases, update this glossary before the term spreads into multiple pages.

Rivya Glossary