How it works#
You can build a lot with the guides alone. These pages explain the few contracts that are worth understanding before you push the runtime further — what one request owns, when context changes, and which channel carries which message to your UI.
Architecture and ownership
What each object owns, and where your application’s responsibility starts.
Request lifecycle
The exact order of hooks, phases, and cleanup inside one request.
Context and memory
Which messages the model sees, and how compaction changes them.
Events and channels
UI events, internal notifications, and external input are different things.
If you only read one page before writing a stateful extension, read The request lifecycle; if you are wiring a UI, read Three kinds of events.