Public documentation

Understand the control model before the API.

These public docs explain the operating model without exposing private production endpoints, credentials, internal runbooks, or customer data.

1. Identify resources

Give assets, services, applications, tenants, owners, environments, and dependencies stable identities with provenance.

2. Model desired and observed state

Keep desired, observed, reconciled, and verified state distinct so drift and controller decisions remain explainable.

3. Collect evidence

Use metrics, logs, traces, profiles, configuration observations, release data, SLO signals, and business context without treating correlation as proof.

4. Investigate and recommend

AI and deterministic logic build hypotheses, confidence, blast radius, and recommendations while preserving an INCONCLUSIVE outcome.

5. Authorize

Identity, tenant scope, policy decisions, approvals, capability truth, risk, and feature state determine whether a typed action may progress.

6. Execute durably

Governed jobs evolve toward checkpoints, idempotency, retries, timeouts, compensation, safe-stop, and bounded credentials.

7. Verify and recover

Post-action verification is part of the action. Failure triggers safe-stop, rollback, containment, or recovery where contracts support it.

8. Remember and learn

Record outcomes, incidents, evidence, lessons, calibration, and model evaluation without letting historical similarity silently become canonical truth.

Clients & integrations

ChatGPT is optional, not the runtime.

The native direction includes Web, API, CLI, automation, agents, and provider connectors. External AI and agent protocols sit behind the same identity, policy, evidence, and verification model.

Native

Web, API, CLI, automation

Core operations must remain usable without one external AI provider.

Connectors

Hosting, cloud, Git, containers, Ads, and more

Provider adapters translate typed capabilities while preserving tenant and credential boundaries.

Interop

MCP/A2A are optional adapters

External agent protocols can integrate without becoming GATOCP authority.

API boundary

Private by default today; stable public interfaces later.

The current operational API remains intentionally local/private. A stable public API, SDK/CLI, connector SDK, and compatibility policy belong to later GA stages after tenancy, security, upgrade, and support contracts are proven.