Platform Status & Terminology

Understand Starfire AI Alpha status, feature availability, rollout language, and documentation conventions.

Platform status & terminology

Starfire AI is under active Alpha development. Features can move from internal implementation to staged rollout to broad availability without waiting for a major version boundary.

This page explains how the documentation describes that reality.

Feature-status language

Available

The feature exists in the current product line and is intended for normal use by eligible accounts.

Available does not mean every user receives it. Plan limits, organization policy, feature flags, model capabilities, or administrator controls can still restrict access.

Alpha / staged

The feature is implemented or actively shipping, but one or more of these can still change:

• UI location
• configuration model
• limits
• permissions
• request/response shape
• rollout population
• operational behavior

Treat Alpha interfaces as real product surfaces, but do not build a critical external dependency on an undocumented behavior.

Planned

The feature is part of the documented product direction but is not presented as generally available.

The docs never use a planned feature to imply that your current account can access it today.

Account eligibility

A feature can be affected by several layers at the same time:

Platform availability
        ↓
Feature flag / rollout
        ↓
Plan entitlement
        ↓
Organization policy
        ↓
User override / role
        ↓
Model or provider capability
        ↓
Runtime health

If a feature exists in the docs but is missing in the app, that does not automatically indicate a bug.

Product terminology

Starfire AI refers to the overall product platform.

Starfire Chat refers to the interactive human-facing conversation experience.

Control Center is the privileged administrative and operational interface for running Starfire AI.

Developer Platform is the programmatic surface for API keys, applications, APIs, webhooks, logs, usage, and integrations.

FORGE is the software-building system for project generation, repair, validation, repository intelligence, and artifact packaging.

Project OS is the persistent project-context model that ties together chats, files, knowledge, artifacts, and project state.

Knowledge refers to persistent reference material and retrieval systems such as uploaded files, indexed content, repositories, embeddings, and RAG.

Credits are Starfire’s internal unit for measuring eligible platform compute and feature usage. Exact plan allowances and pricing are controlled by the current billing configuration.

Public contract vs internal implementation

These docs intentionally distinguish supported product behavior from internal implementation details.

Public documentation can describe:

• supported workflows
• public developer contracts
• administrative controls
• status and error semantics
• security expectations
• observable platform behavior

It does not publish:

• private source code
• production secrets
• internal database credentials
• provider credentials
• private infrastructure topology
• proprietary routing algorithms
• security-sensitive internal procedures

Version labels

Starfire uses Alpha version numbers to group major product work. A release page describes the scope of that product line; it is not a guarantee that every component rolled out simultaneously to every account.

Alpha 1.6.3 — NEXUS

Review the current major platform expansion and its subsystem changes.