Map feature availability and badge every gated feature - #1194
Draft
gwenwindflower wants to merge 2 commits into
Draft
Map feature availability and badge every gated feature#1194gwenwindflower wants to merge 2 commits into
gwenwindflower wants to merge 2 commits into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Documentation validation✅ All blocking checks passed. Component system0 finding(s) across the corpus. Findings on lines this pull request touched are annotated inline in Files changed. |
* Map every gated feature to what it needs — Enterprise, the AI add-on, Cloud, or self-hosted — as the availability counterpart to feature maturity levels. * Add an AI add-on badge so the add-on axis is representable, since it is purchasable on any Cloud plan rather than tied to a plan tier. * Add a reusable AI add-on gate snippet for the agents tree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wffdQdvDJWRLQMZr3Vpfs
* Gate the whole agents tree with the AI add-on snippet, so pages reached directly — AI writeback, agent context, data access — no longer read as ungated. * Convert bold-prose availability gates to badges across admin, explore, and semantic layer pages, each linking the availability map. * Separate AI writeback from dbt write-back, which is gated by project role rather than by plan. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017wffdQdvDJWRLQMZr3Vpfs
gwenwindflower
force-pushed
the
docs/feature-availability-map
branch
from
August 27, 2026 23:23
e39f626 to
6241a9e
Compare
gwenwindflower
marked this pull request as draft
August 28, 2026 13:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
support/feature-availability— a map of every gated feature and what it takes to reach it — and makes the badges on individual pages agree with it.The prompt was that write-back looked ungated if you landed on it directly, even though it needs agents. That turned out to be true across most of the agents tree: only the section root carried a gate, so any page reached from search or a deep link read as free.
Changes
support/, the availability counterpart to feature maturity levels. Three tables — AI, administration and governance, data and platform — plus how features get turned on in Cloud versus self-hosted.sparkles). The add-on is purchasable on any Cloud plan, so it is not an Enterprise plan tier and had no representable value before. Added to.mintlify/components.mdalongside the other three.snippets/ai-add-on-availability.mdxtranscluded across 11 agents pages, so the gate has one home and cannot drift.Notes for review
Two plan claims are inherited from the existing pages and worth a second pair of eyes, since nothing in the backend models plans:
agents/thread-retentioncarries Enterprise, but structurally it looks like a feature flag inside the add-on.mint broken-linksis clean apart from two pre-existing/api-reference/scim/list-usersfailures, which come from the OpenAPI spec being unreachable in this environment rather than from this change.🤖 Generated with Claude Code
https://claude.ai/code/session_017wffdQdvDJWRLQMZr3Vpfs