Most Akan features can be understood as a conversation between the interface and the business service. The interface shows useful content and captures intent. The business service receives a safe request, decides the rule, changes data, and may trigger background or realtime follow-up work.
User sees or acts: SSR helps the first view appear early. Client components handle typing, clicking, filtering, chat, maps, camera, and local state.
Generated helpers call the service surface: fetch calls signal endpoints, st manages client state, Model namespaces keep model usage typed, and usePage handles i18n.
Signal routes intent: Signal is the callable surface for endpoint, slice, and internal work. It applies boundaries before sending valid work to services.
Service decides business behavior: Services coordinate rules, stored data, external APIs, dependency injection, background work, and realtime publication.
Document and runtime complete the loop: Documents define schema, query, sort, methods, and statics. Runtime and infra decide where the work is reached and executed.
