Application foundations
How the common parts fit together.
These guides explain the connected parts that are already in a smrt app. They run in order, from your product model through ownership, identity, access, pages and external interfaces.- 01 smrt-core · smrt-config →
Model your application
An object is one record, such as an Item or Invoice. Its collection is the place you work with many of those records.
- 02 smrt-tenancy · smrt-users →
Decide where data belongs
A tenant can be one customer account, a branch inside a larger organization, or a member of a network. You decide which shape matches the business.
- 03 smrt-users · smrt-profiles →
Add people and accounts
A user answers “who signed in?” A profile answers “who or what is this in the product?” They are related, but they are not the same record.
- 04 smrt-users · smrt-tenancy →
Grant access
A membership connects a user, a tenant, and a role. Permissions are named actions such as items.read or articles.publish.
- 05 smrt-svelte · smrt-web →
Build pages and live data
SvelteKit can send useful HTML with the first response. Hydration gives those same rows to the browser store, so it does not immediately fetch them again.
- 06 smrt-core · smrt-app-mcp →
Connect APIs, tools, and agents
You choose what people, agents, browsers, and operators can do. smrt generates the repetitive route, tool, schema, and command wiring.