Reference6 minNoindex · follow
Use current product terminology
Translate current user-facing labels consistently and keep internal implementation language out of customer procedures.
- Audience
- Customers, evaluators, writers, reviewers, and support operators
- Prerequisite
- A product label or capability phrase that needs a consistent definition.
- Outcome
- The same task uses the same term across public pages, Docs, and the signed-in product.
Last reviewed 2026-08-02 · Product Information · v2026.08
Core terms
FlywheelBrander is a Supervised B2B content operating system.
| Term | Use it to mean |
|---|---|
| Business context | Reviewed audience, offer, goals, and workspace guidance |
| Content queue | The current set of content items and their states |
| Review | Human inspection and editing of a selected item |
| Approve | Explicit human confirmation for the selected item |
| Schedule | Save an approved item into a deliberate delivery slot |
| Publish | Confirm a supported delivery action or bounded receipt |
| Insights | Available bounded evidence and next reviewed action |
Channel terms
Use the execution class instead of a broad connected-channel claim.
| Class | Meaning |
|---|---|
| Native connection | A current provider-native connection path |
| App-managed workflow | FlywheelBrander-managed execution without an ordinary native connection claim |
| Owned distribution | A FlywheelBrander-owned newsletter or website lane |
| Preparation-only | A reviewed package that must be delivered outside FlywheelBrander |
Avoid internal release language
Internal implementation stages are not customer tasks or current capability promises.
- Use Home, Work, Context, Channels, Insights, and Settings for navigation concepts.
- Use human-approved, AI-assisted workflow for the supervision model.
- Use approved scheduled delivery for due background execution.
- Do not use internal release-stage names in customer procedures.
- Use Guided Pilot as the proper program name.
Related documentation
FlywheelBrander documentationTask-based guidance for using FlywheelBrander as a Supervised B2B content operating system.Review current capability limitsSeparate current supervised product behavior from future, native-provider, plan, or cross-request claims.Control approval and scheduled automationUnderstand exactly where human review ends and approved scheduled background delivery begins.