Feature availability model
A feature can exist in Starfire without being usable by every account. Availability is calculated from several layers, and the docs use that model consistently.Availability layers
Availability states
Available
The capability is implemented and intended for normal use by eligible accounts.Alpha / staged
The capability is implemented or actively shipping but can still change in interface, configuration, limits, or rollout population.Planned
The capability is part of the documented product direction but is not represented as generally usable today.Why another user can have a feature you do not
Possible differences include:- different plan
- different organization policy
- feature-rollout cohort
- per-user override
- different model/provider eligibility
- administrator test access
- region/deployment differences
- temporary provider or subsystem health
Diagnose a missing feature
- Confirm the feature is marked Available or Alpha/staged in the relevant docs.
- Confirm the active personal or organization context.
- Check plan entitlements.
- Check organization policy and role.
- Check user/resource override.
- Check whether the required model, tool, or provider is healthy.
- If multiple eligible users lose the feature simultaneously, check system health.
Documentation rule
A page that explains a planned or staged architecture should say so explicitly. Starfire documentation should not use future design work as evidence that the capability is enabled for a current account.Platform status & terminology
See the documentation-wide status language and Alpha conventions.