Feature status taxonomy
How AACSearch labels feature availability across docs, marketing and the dashboard. Every feature flagged on a docs page resolves to one of these six states.
Every feature mentioned in AACSearch documentation and marketing copy resolves
to one of the six states below. The label is the contract — if a feature is
not explicitly labelled Available, treat it as not generally available.
The six states
| State | Means | Example markers |
|---|---|---|
| Available | Shipped, supported, billed on the live plans. Safe to build production workloads against. | "Available on all plans", no badge required |
| Beta | Feature-complete and on production for some customers, but interface, pricing or limits may still change. | Beta badge on the docs page |
| Enterprise | Shipped but gated to Enterprise plans or contract terms. Pricing/scope is decided per-customer. | Enterprise badge; row in /overview/plans-and-limits table |
| Internal preview | Running in production for AACSearch's own use or design-partner customers. Not yet billable. No external SLA. | Internal preview badge; usually no docs page yet |
| Roadmap | Committed for a named release (v0.x, v1.0 etc.) but not yet implemented. Do not market as available. | Roadmap (vX.Y) badge linking to Status & Roadmap |
| Not available | Out of scope. Either dropped, or covered by a different product/partner. | Mentioned only in Status & Roadmap "Out of scope" |
When to apply a badge
Apply a status badge whenever a docs page or marketing block describes a
feature that is not Available everywhere. The default is "no badge =
generally available on all live plans". Specifically:
- A feature gated by plan tier → badge stating the gate (e.g.
Enterprise). - A feature behind a contract/SLA → badge stating the gate plus a link to sales.
- A roadmap feature mentioned as motivation/context → badge stating the target release with a link to Status & Roadmap.
- An ambient claim about performance, uptime or scale that is not measurable on a current plan → either remove it, or replace it with a target plus a link to Claim status.
Anti-patterns
These have caused trust issues in past audits — avoid them:
- Aspirational SLA copy. "99.99% uptime" without a published measurement window, exclusion list and credit policy. If a contract does not back the number, do not print the number.
- "Coming soon" without a release. Use the
Roadmap (vX.Y)badge with a named target so readers can subscribe to the right milestone. - Reusing a competitor's terminology to describe AACSearch features that behave differently. Prefer the term defined in the Glossary (once published) over Algolia/Elasticsearch vocabulary.
- Marketing-only features. A feature page must point to either a docs
page, an oRPC procedure, a Prisma model, or an env flag. If none exist, the
feature is
RoadmaporNot available.
Source of truth
For each named feature, the source-of-truth order is:
- Code — the procedure / model / package referenced from Status & Roadmap.
wiki/tasks/*.md— engineering plan with current status (linked from Claim status per claim).- Plan tables — Plans and limits controls the gate, not the marketing page.
When marketing copy and one of the above disagree, the code wins. Open an issue against marketing rather than updating the docs to match the brochure.
Connectors changelog
Webhook connector platform release notes — PrestaShop, Bitrix, Shopify and future modules. Subscribe here if your storefront syncs to AACSearch via a connector module.
Claim status
Fact-check of the performance, security and enterprise claims that appear in AACSearch docs and marketing. Tracks each public claim against the current implementation.