Repository navigation
docs(company-monitoring): remove provider approval claims - #6494
Merged
koala73 merged 1 commit intoAug 12, 2026
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
koala73
deleted the
codex/remove-company-monitoring-provider-approval-docs
branch
August 12, 2026 10:06
This branch was successfully deployed
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
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.
Summary
Company Monitoring documentation no longer says that Exa needs a separate paid-runtime approval or that X needs written commercial-use approval. It now describes the actual code-level rollout flags and keeps the technical provider controls visible without presenting vendor approval artifacts as documentation requirements.
This is an editorial change only. The frozen cm_eval_v1 machine contract and runtime behavior are unchanged and remain authoritative for current stop reasons.
Test plan
Post-Deploy Monitoring & Validation
No additional operational monitoring required because this PR changes internal documentation only and does not alter runtime configuration, protocol data, or provider execution.
Related
Related: #6003
Related: #6006