Skip to content

Document organization and project spending caps - #520

Draft
dcruzeneil2 wants to merge 5 commits into
mainfrom
hypeship/spending-caps-guide
Draft

Document organization and project spending caps#520
dcruzeneil2 wants to merge 5 commits into
mainfrom
hypeship/spending-caps-guide

Conversation

@dcruzeneil2

Copy link
Copy Markdown
Contributor

summary

  • add a dedicated spending caps guide under info
  • compare organization and project cap accounting, scope, and use cases
  • document the 80% warning, 100% pause, monthly reset, layered behavior, and enforcement caveats
  • use native cards, comparison tables, and step flows instead of a dashboard screenshot that can drift
  • link the guide from pricing, projects, and the docs navigation

testing

  • mint validate
  • mint broken-links
  • rendered /info/spending-caps locally in chromium
  • git diff --check main...HEAD

@mintlify

mintlify Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 27, 2026, 3:31 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

cursor[bot]
cursor Bot approved these changes Aug 27, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk assessment: Very Low (re-evaluated after push)

Previous approval remains in effect. This run does not re-approve.

Verified from the current diff only (4 files, +151 / −0 vs main; 1-line change since the prior approval on ab83382).

What changed (full PR)

  • New Mintlify page info/spending-caps.mdx (product docs for organization vs project spending caps)
  • One nav entry in docs.json (info/spending-caps)
  • Two cross-links from existing docs (info/pricing.mdx, info/projects.mdx)

What changed since last approval

  • In info/spending-caps.mdx, the limited-preview note now uses a mailto:support@kernel.sh link instead of /info/support. Still documentation-only.

Why this remains Very Low

  • Documentation-only on a docs site; no application logic, APIs, auth, billing enforcement, CI, or infrastructure
  • docs.json change is a sidebar path addition, not runtime/infra config
  • No CODEOWNERS file and branch ruleset has require_code_owner_review: false
  • Risk did not increase, so the existing approval is not dismissed

No production codepaths or shared systems are modified.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk assessment: Very Low (re-evaluated after push)

Previous approval remains in effect. This run does not re-approve.

Verified from the current diff only (4 files, +156 / −0 vs main).

What changed (full PR)

  • New Mintlify page info/spending-caps.mdx (product docs for organization vs project spending caps)
  • One nav entry in docs.json (info/spending-caps)
  • Two cross-links from existing docs (info/pricing.mdx, info/projects.mdx)

What changed since last approval (ab83382eb4fc50)

  • Availability note in info/spending-caps.mdx now splits organization vs project preview access and uses a mailto:support@kernel.sh request link. Still documentation-only.

Why this remains Very Low

  • Documentation-only on a docs site; no application logic, APIs, auth, billing enforcement, CI, or infrastructure
  • docs.json change is a sidebar path addition, not runtime/infra config
  • No CODEOWNERS file in the repo
  • Risk did not increase, so the existing approval is not dismissed

No production codepaths or shared systems are modified.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk assessment: Very Low (re-evaluated after push)

Previous approval remains in effect. This run does not re-approve.

Verified from the current diff only (4 files, +177 / −0 vs main).

What changed (full PR)

  • New Mintlify page info/spending-caps.mdx (product docs for organization vs project spending caps)
  • One nav entry in docs.json (info/spending-caps)
  • Two cross-links from existing docs (info/pricing.mdx, info/projects.mdx)

What changed since last assessment (eb4fc50b639f53)

  • Organization and project cards in info/spending-caps.mdx now use inline SVGs instead of named icon strings. Cosmetic docs markup only.

Why this remains Very Low

  • Documentation-only on a docs site; no application logic, APIs, auth, billing enforcement, CI, or infrastructure
  • docs.json change is a sidebar path addition, not runtime/infra config
  • No CODEOWNERS file in the repo
  • Risk did not increase, so the existing approval is not dismissed

No production codepaths or shared systems are modified.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant