Types reference
Reference · Types
Reference purpose — Use types to make lifecycle assumptions visible without pretending compile-time types validate network input.A readable contract for contexts, handlers, responses, errors, and adapter capabilities.
Key concepts
Compile time
Developer feedback
Runtime
Boundary safety
Result
Caller contract
Reference model
Contract summary
Interpretation
Types reduce accidental mismatch between layers, but boundary validation remains a runtime responsibility.Reference note A type is a promise made by code; validation is the evidence that the outside world kept it.
Implementation notes
Decision lens
Related topics
- globe · Pair types with HTTP — Read the focused guide for this boundary.
- puzzle-piece · Type capabilities — Read the focused guide for this boundary.
- brackets-curly · Apply handlers — Read the focused guide for this boundary.