# Developer reference

The executable Zod schemas in `@al-amr/contracts` are the source of truth.
Human references explain those contracts without copying field definitions that
can drift.

## Reference paths

- [SDK reference](/reference/sdk) describes the public package boundaries.
- [Manifest reference](/reference/manifests) describes Environment, App,
  Plugin, deployment, and lock artifacts.
- [API reference](/reference/api) describes public Catalog, Management,
  Runtime, and publication APIs.
- [CLI reference](/docs/reference/cli) describes exact commands, structured
  output, exit codes, credentials, and immutable test handoffs.
- [Stable error catalog](/docs/errors/catalog) and
  [troubleshooting](/docs/errors/troubleshooting) map machine codes to safe
  recovery.
- [AI-native development](/docs/ai-native) links the authoring bootstrap,
  Context Packs, digest-bound Journeys, and human gates.

Generated JSON Schema, OpenAPI, and TypeScript declarations share the same
contract source. Use exact-version artifacts when repeatability matters.