# ADR 0003 — Hono Transport

**Status:** Accepted

## Context

AWP needs a lightweight TypeScript HTTP layer that can run at public/edge boundaries and on Node without dictating domain/module architecture.

## Decision

Use Hono for gateway and control-plane HTTP transport. Runtime-neutral contracts are shared; Hono request/context types terminate at transport handlers.

## Consequences

Transport remains portable and small. Domain/application code is not coupled to Hono, Cloudflare or edge APIs. Public compatibility is later protected by OpenAPI/oasdiff when stable consumer boundaries exist.

## Rejected Alternatives

- treating Hono as an application module/container framework;
- framework-specific domain types;
- building a custom HTTP framework.

## Increment Realization

I0 transport conventions; I1 first lifecycle contracts; public/stable API productization only when declared, especially I9.