Tenant scoping (multi-tenant isolation)
The backend enforces multi-tenant isolation with a framework-level guard, not
API interceptor (cross-module endpoint extension)
The API Interceptor mechanism lets a module attach behavior to an
Database migrations (naming, registry & ordering)
Migrations are module-local files with UTC timestamp names, registered once in a
Command Bus (uniform write auditing & undo)
Sensitive writes are audited by a framework-level command path, not by
Custom fields for core entities
Operators can add fields to core entities at deployment time — as data, never a
Overlay pattern (per-deployment customization)
The platform is a multi-deployment product — one codebase, many client
The customisation ladder
The ordered list of seams for changing what the platform does — what each costs, what it loses, and who may use it.
Declared extension columns
How an installed module package adds its own columns to an extensible core table — declaration, generated DDL, ledger, accessor, admin reads, uninstall and drop.
Permissions — admin and organization codes, and which one you are looking at
How admin permission codes and organization permission codes are declared, granted, enforced and switched off.
PIM connector shared layer
The module that holds the behaviour every inbound PIM connector needs, without