docs(limits): integrate Segmentation platform limits in-context (§12) - #438
Open
mallikarjun-dhulange wants to merge 4 commits into
Open
docs(limits): integrate Segmentation platform limits in-context (§12)#438mallikarjun-dhulange wants to merge 4 commits into
mallikarjun-dhulange wants to merge 4 commits into
Conversation
Fill gaps: total active segments 1,000, max users/file segment 5M, File Segment API ops 10/hr-100/day, file URL 300MB, computed traits 10. Reconciled §4-vs-§12 conflict toward §12 values. Held nesting depth at 3 (docs consistent; Confluence 6 likely stale). API-surface limits deferred to API POD. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Drop "may require evaluation" qualifiers; a plain contact instruction is sufficient. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
mallikarjun-dhulange
marked this pull request as ready for review
July 23, 2026 12:44
PM confirmed §12 is source of truth: max nesting is 6 levels, not 3. Updates the cap in manage-segments.mdx and new-ui custom-segments.mdx, and reworks segment-nesting.mdx — the level-counting logic is unchanged; only the ceiling (3->6) and the worked example's conclusion (level 4 is now within the limit and processed, not rejected) are corrected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Replace the loosely-spaced, inconsistently line-broken worked example (mixed hard-break/blank-line steps, a bold-italic-then-italic final line, and a sentence split across a blank line) with a numbered list using inline code for the boolean expressions. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Platform limits — Segmentation POD
Integrates the Segmentation platform limits (Confluence §12, cross-checked against §4 "File Imports") into the docs, in context. No snippets, no hub. Confluence is the source of truth for this work.
Gaps filled in-context
Verified already-documented (no change needed)
File segment users/day 2M · direct upload 64 MB · custom segments usable in a definition 10 · auto-archival 60 days · post-archival expiry 30 days · archived listing cap 1,000 · value suggestion 254 (array) / 1000 (non-array) · user exports 20M data points.
Deferred to the API POD (API-surface limits)
File Segment API max file size (150 MB) · Filter Segment API rate (50/min·200/hr·1000/day) · custom segment API expiry (max 365-day extension). These belong on
api/pages, not the user-guide.🤖 Generated with Claude Code