# DNA OS

> Public developer portal and integration contract for DNA OS. Read the quick start before writing an integration. Registry presence means documented; it does not mean the runtime API is currently deployed.

## Start here

- [AI and developer quick start](https://dnaos-developer-portal.pages.dev/ai-start-here.md): canonical reading order, connection boundaries, and live status.
- [Human-readable developer portal](https://dnaos-developer-portal.pages.dev/): capabilities, API contracts, security rules, and integration flows.
- [Machine-readable portal contract](https://dnaos-developer-portal.pages.dev/api/v1/developer-portal): endpoint schemas, examples, references, and system journey.
- [Health status](https://dnaos-developer-portal.pages.dev/health): status of the documentation site only; it does not indicate runtime API health.

## System discovery routes (declared by Registry)

- `GET https://dnaos.dev/api/v1/spec` — AI tool schemas.
- `GET https://dnaos.dev/api/v1/capabilities` — capability registry and composition plan.
- `GET https://dnaos.dev/api/v1/modules` — module ownership and exports.
- `GET https://dnaos.dev/api/v1/constitution` — system rules and constraints.
- `POST https://dnaos.dev/api/v1/query` — central command gateway; requires a DNA OS API token.

These runtime routes returned HTTP 404 when checked on 2026-11-13. Treat them as documented contracts, not available production services, until a later live check confirms otherwise.

## Source of truth

- `registry/developer-portal-spec.ts` — endpoint contracts and reference documentation.
- `registry/integration-portal-spec.ts` — end-to-end integration stories and pipelines.
- `registry/command-registry.json`, `registry/permissions.json`, `registry/capability-registry.json` — commands, access rules, and capability definitions.

Use the machine-readable portal contract first. Follow only the `registryRefs` needed for the feature; do not scan the repository broadly or infer production status from source code alone.