Relationships, made explicit.

Organizational alignment and accountable scope connect to supported runtime controls and retained evidence. Operational extensions remain in development. Conceptual relationship; organizational approval is not executable enforcement.

Prepare an immutable proposal, obtain independently assigned reviews, assess the exact version, and activate only through existing gates. Current workflow; activation and runtime enforcement are separate checks.

Organization, project, workload and exact policy references constrain interpretation; inventory alone never grants permission. Registry is implemented; project execution authority is default-off and limited to payload-sanitize-v1.

Self AI, Team AI and Managed AI describe operating contexts, not maturity steps, risk ratings or subscription tiers. Profile configuration and contextual reporting are In Development.

Compliance and regulatory governance uses scoped policies and evidence. Operational governance describes planned network, discovery and cost capabilities. U.S.-first supported policy scope; no legal compliance certification.

A versioned policy is evaluated and explicitly assigned; the server resolves the exact applicable binding and rechecks it before release. Current version binding; autonomous source-to-policy promotion is not implemented.

Ingress runs before permitted dispatch; output is checked and final authority is refreshed before atomic evidence publication and return. Simplified sequence; ingress denial makes no provider call, while egress denial may follow execution.

Only traffic routed through supported, configured Gateway paths receives those boundary controls. Other traffic is outside that enforcement path. Supported inline/API placement; not organization-wide network interception.

The current Gateway supports configured request paths. Broader enterprise egress integrations require explicit development and customer qualification. Enterprise network harness is In Development; no universal traffic coverage claim.

Planned discovery brings qualified signals into attribution and investigation; missing source coverage must remain visible. In Development; this is a planned workflow, not a measured enterprise inventory.

Provider usage metadata at a supported boundary is distinct from planned enterprise allocation, billing and financial controls. Enterprise Tokenomics is In Development; financial admission is unavailable.

A request identity links the exact policy, recorded boundary outcome and artifact fingerprint to retained reports. Intermediate events do not establish release. Evidence integrity within retained scope; transaction commit is not downstream delivery.

Official source records support a bounded published inventory. Review and applicability are separate from collection and publication. Research inventory; a source record or enacted instrument is not an implementation obligation.

The governance boundary resolves authority and policy independently of model output, while each provider adapter has its own qualification requirements. Adapter architecture is not universal provider or tool availability.

Cloud API, Gateway and private deployment options are scoped delivery patterns with common governance boundaries and distinct customer requirements. Commercial architecture options; availability and readiness depend on the agreed deployment.

Workload measurements, coverage and failure-mode evidence determine a justified operating envelope. Illustrations do not establish capacity. Requires customer qualification; 100 / 3,000 / 30,000 profiles are illustrative, not benchmarks.

Reports share a retained, authorized relation while distinguishing totals, excerpts, unknown outcomes and event-time attribution. Historical evidence uses recorded context, not current assignments; report scope and limits remain visible.

Execution authority, content policy and final publication are separate gates; a hold never becomes permission through a UI override. Current supported boundaries; public teaching simulations do not resume real effects.

Governance Workbench is a public demonstration context; Developer Evaluation is a separate private, bounded API experience. Neither free path grants production entitlement or is a prerequisite for the other.

Untrusted clients and content cannot grant authority. Server authorization, qualified adapters and scoped evidence each have separate responsibilities. Architecture boundaries; no certification or complete customer-environment qualification claim.