Use Reference
Reference pages are for exact names, defaults, limits, compatibility claims, and schema contracts. Use them after you understand the workflow or when validating automation.
Find Answers
Section titled “Find Answers”| Need | Page |
|---|---|
| Direct answers to common questions | FAQ |
| Canonical terms | Glossary |
| Error response codes | Error Codes |
Configure and Run
Section titled “Configure and Run”| Need | Page |
|---|---|
| Runtime and service configuration keys | Configuration Keys |
| Configuration source order | Configuration Order |
| Ports, TTLs, limits | Defaults and Limits |
| Runtime CLI exit behavior | CLI Exit Codes |
Versions and Contracts
Section titled “Versions and Contracts”| Need | Page |
|---|---|
| Supported runtimes and deployment targets | Compatibility |
| Package, image, and release naming | Release Map |
| JSON schemas and fixtures | Wire Contracts |
| Community and Enterprise feature boundary | Compare Editions |
Source-of-Truth Rule
Section titled “Source-of-Truth Rule”When Reference conflicts with API, Operations, or SDK pages, treat code and generated schemas as source of truth and update the docs section coherently.
Next Step
Section titled “Next Step”Start with FAQ for recurring modeling, runtime, troubleshooting, and edition questions.