An Orveth application is an instance of the Orveth class. You register routes and middleware, then start an HTTP listener. Phase 1 adds path parameters, wildcards, richer context, and clearer HTTP error semantics.
Application
The application owns the route table and middleware stack. TLS, validation, CORS, and security ship as optional packages.
RequestContext
Handlers receive ctx with routing data (params, query, method, path, url), request/response access, and response helpers. Validated data appears on ctx.valid when using validation middleware.
HTTP errors
Unmatched routes return 404. Unsupported methods on a matched path return 405 with an Allow header listing permitted methods.