Glossary

Short definitions for terms and concepts that show up across Stario docs and code.

Term	Meaning
`App`	The concrete HTTP application type (`Router` + `__call__`, `on_error`, `url_for`, `create_task`). See Runtime.
Bootstrap	Callable loaded as `module:callable` (the CLI resolves an attribute on the module—`main:bootstrap` is the usual name); wires routes, assets, shared services. See Application lifecycle.
Context (`c`)	Per-request: `app`, `req`, `span`, `route`, `state`. See Request and context and Reading and writing Datastar signals · No validation layer in the framework.
Datastar	Browser runtime + `stario.datastar` SDK (attributes, actions, SSE). The go-to architecture.
Handler	`async def handler(c: Context, w: Writer)` — scheduled after request headers are parsed; the body may still be streaming (`await c.req.body()` / `stream()`). See Handlers, context, and the writer.
HTML	Document trees built with `stario.html` (tags, attributes, children). HTML reference.
Middleware	`(inner: Handler) -> Handler`; composed at registration time. See Routing — Middleware.
Relay	In-process pub/sub; not NATS/Redis compatible by design. Toolbox — Relay.
Route trie	Matcher: optional host segments, path segments, HTTP method. Routing · Router design.
`Server`	Asyncio listener around an `App`; signals, bind addresses, graceful shutdown. See Runtime — Server.
Signals	JSON-shaped client/server state; see Datastar.
Span / event / attribute	Telemetry primitives; see Telemetry design.
Tracer	Creates spans; TTY, JSON, SQLite, or custom. Telemetry design · Telemetry reference.
`url_for`	Reverse routing from registered `name=` keys. Runtime — Reverse URLs.
Writer (`w`)	Outbound HTTP: status, headers, body, streams. Responses — Writer.