Build on GPUaaS implemented
This is the App SDK product surface. It is for internal, partner, and future external developers who need to package, register, test, and promote GPUaaS apps without learning the whole platform implementation first.
Shipped Proof
The App SDK path is not only a contract story. GPUaaS already has two working reference controllers on the platform path:
- Slurm reference controller
- RKE2 self-managed controller
Those controllers are the strongest proof that app composition, runtime reconciliation, and platform-shared authority are already real in the codebase. See Platform Proof Points for the hard evidence view and App SDK Proof for the developer-focused explanation.
Persona Route
| Persona | First-read path | Decision points | Next-action pages |
|---|---|---|---|
| App developer | App Developer Onboarding, App SDK Overview, Add a New App | Am I learning the platform/app boundary, creating a manifest, packaging a runtime artifact, setting up service-account identity, or preparing launch/connect/decommission proof? | Manifest Model, Artifact And Runtime Lifecycle, Artifact Trust and Promotion, Developer APIs |
| Architecture reviewer | System Overview, Domain Ownership, Developer API Contracts | Does the app path respect platform boundaries, API ownership, runtime lifecycle, and artifact trust contracts? | API Domain Authoring, State Machines, External Developer Review |
| Shared-platform product builder | Shared Platform Consumer Track, Product Onboarding, Shared Platform Builders | Am I onboarding a second product or just packaging an app/runtime? Which shared services must I consume and register first? | Platform Contracts for Builders, Shared Services, Platform Status, Governance Model |
Developer Path
- Learn the app boundary: what the app owns and what GPUaaS owns.
- Start from the app developer starter pack and quickstart.
- Use Add a New App to map manifest, artifact, service-account, catalog, entitlement, and runtime expectations.
- Define the manifest and launchable OCI workload profile.
- Test credential, storage, runtime, observability, and billing expectations.
- Publish and promote the app through the artifact trust path.
SDK Reference Path
| Step | Portal page | Validation surface |
|---|---|---|
| Manifest | Manifest Model | App SDK manifest contract families and validators |
| Publish | Artifact Trust and Promotion | artifact registration, digest, trust, and promotion evidence |
| Promote | Artifact Trust and Promotion | channel transition, actor, correlation, and trust state |
| Launch | App Developer Quickstart | public app instance APIs, idempotency, and entitlement checks |
| Connect | SDK Evidence Path | active route/connect action evidence |
| Decommission | SDK Evidence Path | app decommission API and cleanup evidence |
| Examples | Example App Workflow | reference app workflow and live smoke follow-up |
Start Reading
- App Developer Onboarding
- Shared Platform Consumer Track
- App SDK Overview
- App SDK Proof
- Add a New App
- Platform Contracts for Builders
- SDK Evidence Path
- App Developer Quickstart
- Manifest Model
- Artifact Trust and Promotion
- Artifact And Runtime Lifecycle
- Example App Workflow
First Portal Expansion
The next pages after this cut should cover local test workflow and deeper runtime-specific example apps. Each example must be runnable or clearly marked conceptual.