Reference
Every package, every error class, every spec — linked to the canonical source artifact.
The reference section is the source of truth. Inbound and outbound concept pages aim for narrative; reference pages aim for completeness.
Packages
Every @postel/* package — what it does, what it depends on, and whether it ships today.
Core API
Postel() / definePostelConfig(), PostelConfig, the lifecycle API, observability, pagination, and the shared utility types.
Inbound API
InboundSource config, verify(), every Verifier factory, JWKS, deduplication, and signFixture.
Outbound API
OutboundConfig, the full OutboundApi, and every supporting type — endpoints, keys, tenants, replay, messages.
Strategies
The retry, rate-limit, worker, signing, and KMS strategy factories.
@postel/http
The framework-agnostic gate every adapter is built on — outcomes, options, the error→status policy.
@postel/effect
The Effect-TS layer — PostelLive, PostelTag, and the typed error channel.
Errors
Every PostelError subclass — its code, when it's thrown, and how to recover.
Specs & standards
Wire format (AsyncAPI 3.0), DB schema (SQL DDL), capability specs, ADRs, conformance levels — on the Project tab.
If a narrative page elsewhere contradicts a reference page, the reference page wins.