Explanation

Why Stario is shaped the way it is: mental models, architecture patterns, and boundaries—not step-by-step tasks.

For hands-on paths, see Tutorials and How-tos. For API contracts, see Reference.

Essays

• The Stario way — the overarching idea: teach the internals, not a private interpretation.

• Handlers and the writer — why the handler is async def handler(c, w), why Context and Writer are separate, and how one signature covers three kinds of work.

• Go-to architecture — one subscribe stream, short commands, and ui = f(state).

• Telemetry design — close the development loop: observe real traffic, then choose where those traces land.

Start here by goal