Platform architecture
A foundation made to last.
Inkuru is organized around independent modules and a small shared platform core. New capabilities can be installed without rewriting existing features.
URL composition, SSR metadata and page composition only.
Independent module UI, hooks, validation and query keys.
The only client-side boundary allowed to call Blink DB.
Shared types, audit, activity, versioning, flags and pagination.
Profiles, memberships, skills, languages and interests are separated into focused records. Foreign-key-shaped columns and compound indexes support selective reads.
Audit logs, immutable activity history, entity versions and soft-delete fields are first-class platform concerns.
The module registry and migration ledger create a clean installation contract for future features.
Repositories own pagination, filters, limits, indexes and mapping, keeping rendering code predictable and cacheable.