> ## Documentation Index
> Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt
> Use this file to discover all available pages before exploring further.

# Feature Availability Model

> Understand how plan, rollout, organization policy, model capability, and administrator configuration determine whether a Starfire AI feature is usable.

# 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

```text theme={null}
Implemented in this deployment?
        ↓
Feature flag / rollout cohort?
        ↓
Plan entitlement?
        ↓
Organization policy?
        ↓
User or resource override?
        ↓
Required model/tool/provider healthy?
        ↓
Effective availability
```

## 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

1. Confirm the feature is marked Available or Alpha/staged in the relevant docs.
2. Confirm the active personal or organization context.
3. Check plan entitlements.
4. Check organization policy and role.
5. Check user/resource override.
6. Check whether the required model, tool, or provider is healthy.
7. 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.

<Card title="Platform status & terminology" icon="circle-info" href="/getting-started/platform-status">
  See the documentation-wide status language and Alpha conventions.
</Card>