Maya · Operator
The dashboard still shows green. Did the new target load the policy?
This website explains the full platform direction. A page describing a control does not certify that it is released, connected or enforcing in your environment.
Explore the platformA rollout target stops reporting even though its last dashboard status was green.

The near-term product focus is Solo: a project profile for a supported coding client such as Codex or Claude Code, with independently authorized accounts and an observed client state. Scoped GitHub and Notion connections are early integration candidates, each requiring its own permissions and target binding. These are launch focus and candidate paths, not a claim that a specific release is live today.
The larger platform model adds governance for consequential business operations, shared administration and reviewed learning. ACP adapters, broad enterprise connectors, native hosted agents and cross-tenant learning are planned qualification areas rather than established launch coverage. Ask which exact path exists in the release being evaluated, and verify it in the target environment.
For Observe or Warn, inspect the source, coverage and delay of the signal. For Require Approval, check the material inputs and current authority bound to the decision. For Enforce, demonstrate a denied request at the real pre-effect path. For unknown outcomes, show how the original operation is reconciled before retry.
Commercial, infrastructure and support scope belong in the relevant agreement. This site does not assert a named connector matrix, release date or live certification.