Autobonk Contexts

Overview

Turn a replicated domain into a small number of explicit schemas, routes, and context methods. Favor deterministic tables and route handlers over hidden behavior in UI code.

Model the Domain First

• Decide which data is append-only history, which data is a singleton, and which data needs monotonic indexes.
• Keep route names and collection names stable and descriptive.
• Define permissions as domain concepts, then let Autobonk enforce them.
• Keep one Context subclass as the domain authority for a shared context type.

Build in This Order