Skip to main content

Concepts and Glossary

Use this page when product, customer-success, or engineering conversations need a shared vocabulary. The definitions below describe current product behavior, not future roadmap claims.

Who Should Read This

ReaderUse this page to
New usersUnderstand the names used in the workspace before starting a generation task
Customer-facing teamsExplain Redbit without overstating model ownership, storage guarantees, or Agent autonomy
Team membersKeep product, docs, UI, and support language aligned

Before You Read

Redbit is a workspace that coordinates cards, assets, providers, and optional local integrations. It is not itself a model provider. Generation quality, model availability, quota, region access, and retention policy depend on the provider or relay configured in Settings.

Core Terms

TermMeaningBoundary to remember
CardsIndependent task units on the dashboard for describe, image, video, audio, and speech workA card records prompt, model settings, references, status, and results; provider behavior still depends on the selected model
Asset DockLocal reusable asset library for images, videos, audio, and textPinned assets are intended for reuse; temporary/recent assets can be cleaned up
SmartPickerShared selector for choosing Asset Dock or project assetsIt helps the user choose exact media; it does not infer private intent on its own
WorkshopProject workspace for scripts, scenes, consistency references, generated media, and exportsUse it when the work becomes multi-scene or project-shaped
Agent runtimeGuarded tool loop that reads workspace context and calls registered toolsIt is not an unrestricted shell; risky or destructive actions require clear targets or confirmation policy
Model RegistryCatalog of supported model groups, variants, ratios, durations, input requirements, relay mappings, and provider strategiesThe registry describes app support; it does not guarantee provider uptime or quota
ProviderDirect model endpoint or compatible relay configured in SettingsUsers are responsible for credentials, billing, account limits, and provider terms
ReferenceExisting image, video, audio, or text used as input or guidance for another taskAccepted media and role rules vary by model
SeriesImage-card mode that plans 3, 4, 6, or 8 related slots from one base promptSeries is useful for repeatable sets; each slot still needs review
SeedanceVideo model family with text-to-video, image-to-video, first/last-frame, and multi-reference modesReference roles are stricter than generic video references
Local CoreOptional local engine for selected storage, media, FFmpeg, MCP, automation, plugin, and local data flowsPair only an engine you launched and trust

Term Choices

Keep the English product terms stable in Chinese and English docs where they are UI concepts:
Canonical termUse this for
CardsDashboard generation/review units
WorkshopProject-level creative production
Agent runtimeTool execution loop and assistant runtime profile
Model RegistryCatalog-backed model and provider metadata
ProviderDirect provider or relay provider
ReferenceInput media/text used by another task
SeriesPlanned multi-slot image generation
SeedanceSeedance 2.0 video workflows

Next Step

Continue to Quickstart if you are setting up Redbit for the first time, or go to Core Workflows if you already understand the terms and want the operating flow.