Developer Review Path designed
Use this path for partner, external, and internal app developers who need to understand how to build against AI Cloud without depending on hidden internals.
Reader Questions
- How do I build an app for AI Cloud?
- Which API and event contracts are stable?
- How do auth, service accounts, idempotency, and errors work?
- How do manifests, artifacts, and promotion work?
- What is the boundary between my app logic and AI Cloud platform services?
Developer Review Route
| If the developer needs to know... | Open this first | Then go here |
|---|---|---|
| how to get started on the platform | Build on AI Cloud | Developer Onboarding |
| what the integration contract actually is | Developer APIs | Contract Artifacts |
| what an app package must declare | Manifest | App SDK Overview |
| how runtime promotion and lifecycle work | Promotion | Artifact Runtime Lifecycle |
| where AI Cloud platform responsibility stops | Shared Platform Consumer Track | Architecture Review Path |
Start With
Publication Notes
Developer pages may become partner/public earlier than operator or internal security pages, but they still need stable API/SDK references, auth guidance, and artifact promotion language before publication.
Publication Rule
This route should stay integration-first. It should explain how to build on the platform without leaking operator runbooks, internal release packets, or environment-specific control-room material.