Operate · Experimental
Adoption contract
Reach the owning service's deployment and operations contract with its access limitations intact.
Orientation time: about 15 minutes
Confirm the private production-image boundary before committing to a company-cluster deployment.
Orientation time: about 20 minutes
The public OCI chart can be inspected and rendered, but it is insufficient for deployment without private images and deployment-specific values.
The production image is not publicly distributed and is not required for the public frontend-review path.
Support status is paused. Required artifacts are not available: devcenter-production-container (unpublished). Effective access is private.
The public chart is insufficient on its own, and the required production image is unpublished and private. This path is paused; review the operator documentation, then wait for an explicit distribution, license, and access contract.
Review operator documentation — this does not grant artifact access01 · Learn
Use the public architecture map to identify the service that owns the boundary you need.
You can name the owning service without assuming the reading order is a deployment stack.
02 · Do
Use the source-owned service documentation for configuration, security, reliability, and operations.
The deployment follows an explicitly published service contract.
Use Connectors documentation when external actions require catalog, credentials, grants, invocation, and events.
External effects have an attributable, bounded operations path.
03 · Verify
Verify maturity, required artifacts, and access before copying any deployment command.
No deployment plan depends on an artifact that the public cannot obtain.