How the kernel runs
Sumeru is one Go process: PostgreSQL, XML metadata, and a SWC workspace inside a server-rendered shell. Addons register models. They do not fork core/.
Boot and install
- Config points at PostgreSQL and
addons_path. - The module loader reads each
manifest.jsonand orders modules bydepends. - Schema sync adds columns for installed models. It does not drop columns.
- XML data loads security, views, and actions. View inherits (
inherit_id) apply in a second pass.
Kernel modules and their depends are listed on Kernel addons. platform, currency, uom, geo, i18n, im, and audit auto-install with base.
Open and save a record
- The shell loads
/static/swc/swc.js. GET /web/swc/workspacereturns the merged view arch and rows.- Reads and writes go through model ACL, field ACL, and record rules, then SQL.
POST /api/rpcis the same path for the client and for API keys. There is no public REST API.
Diagram and package map: Architecture layers.
Subsystems
- ORM — CRUD, domains, compute
- SDK — the addon import surface
- Event bus and cron — in-process events,
sys.cron, PostgreSQL NOTIFY for the SWC socket - Web and render and SWC
- Auth: password, OIDC providers, TOTP, trusted device. See
sumeru/docs/sso.mdin the kernel repo. - Ops:
sumeru/docs/ops-runbook.md,sumeru/docs/ha-ops.md,sumeru/docs/ddl-policy.md
Change the kernel
From sumeru/, make runs lint, SWC, and Go tests. Go tests live under sumeru/test/. SWC tests live under sumeru/core/swc/tests/. Addon code should call sumeru/core/sdk rather than importing core/orm directly.
What is partial or absent: Limitations. Mail has outbound and in-app messages, not inbound IMAP. Portal is a shell and share links. Studio, a website CMS, and an offline client are not in the kernel.