Developer Team Guide implemented
This path is for engineers shipping product code, shared services, or platform-consumer capability on top of GPUaaS. It should answer where to start, what to trust, and which model governs a change before you touch code.
Start Here
What Developers Need From The Portal Now
| Need | Portal route |
|---|---|
| Contract-first API and event entry | Developer APIs |
| Runtime and implementation boundary map | Developer Implementation Map |
| Delivery model and design-before-code lifecycle | Contract-First SDLC |
| ARB/JAD and design packet entry | Architecture Review Pack |
| App/platform-consumer integration model | Build on AI Cloud |
| Evidence, Fairway, and definition-of-done discipline | Engineering System, Governance & Agents |
Use This Route By Task Type
| If you are doing... | Start here |
|---|---|
| New or changed API behavior | Developer APIs |
| Backend or worker implementation change | Developer Implementation Map |
| New product or app-platform integration | Build on AI Cloud |
| Design review or architecture handoff | Architecture Review Pack |
| Release, evidence, or workflow closeout | Governance & Agents |
Developer Navigation Model
What Makes This Route Usable
The portal is not just a reading pack anymore. A developer should be able to reach:
- contract authority;
- route and domain ownership;
- runtime/C4 structure;
- lifecycle state rules;
- sequence entry points;
- ER/schema ownership;
- definition-of-done and evidence expectations.
If one of those is missing, that is a docs portal gap, not just a reading problem.
What This Proves To A Developer
This portal is now strong enough for a new engineer to answer the following without reading the whole repo first:
- where contracts live;
- where product code versus shared-platform code belongs;
- what runtime surfaces exist;
- which pages explain launch, access, billing, evidence, and release posture;
- which docs are explanation and which files are the source of truth.
Authority Rule
The portal is the navigation layer. Source contracts, canonical architecture docs, schema, and Fairway evidence remain authoritative when a summary and a source differ.
Canonical sources