PLATFORM SCOPE AND AVAILABILITY

Platform scope and availability

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 platform

Show stale evidence honestly

A rollout target stops reporting even though its last dashboard status was green.

Microsoft TeamsRollout status
Team conversation
Maya · Operator

The dashboard still shows green. Did the new target load the policy?

DriftGate

The last green report is no longer current.

Observation is staleScope review
Last report
Earlier target status
Loaded revision
Unknown now
Next
Inspect target and outage rule
Maya · Operator

Can we mark this rollout complete?

DriftGate

No current loaded-state observation supports that. The last healthy report is historical; inspect target connectivity and the executor's outage rule.

Maya · Operator

Keep the rollout pending until fresh evidence arrives.

Ready

Start with a personal environment, then qualify each expansion.

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.

Use precise status language.

Described capability
A published product model or design intent. It does not establish an active implementation.
Qualified integration
A specific client or business-system path tested against a named release and supported operation.
Observed control
A runtime readback showing an actual decision, effect or record in the target environment.
Planned scope
A direction for later qualification. It is not a committed delivery date or a substitute for a scoped agreement.

Qualify the boundary before relying on it.

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.

EXPLORE DRIFTGATE

Find your starting point.

Search DriftGate

Quick jumps