'%20d='M64%205c-3%2018-15%2026-13%2043-9-5-13-13-13-22C20%2043%2015%2062%2022%2082c7%2022%2023%2037%2042%2041%2022-4%2039-21%2043-43%203-17-3-32-18-45%202%2011%200%2018-6%2025C84%2036%2075%2019%2064%205Z'%20/%3e%3cpath%20fill='url(%23heat)'%20d='M64%2045c-2%2015-14%2022-13%2038-5-4-8-9-9-15-7%2010-8%2020-4%2030%205%2012%2014%2020%2026%2023%2013-3%2023-12%2027-25%203-11%200-20-8-29%200%207-2%2012-6%2016%201-16-5-27-13-38Z'%20/%3e%3cg%20fill='none'%20stroke='%230d100d'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='8'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3cpath%20stroke-width='7'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3c/svg%3e){kind=small}
s-m-r-t documentation · 0.38.26
Build an application from the model outward.
s-m-r-t starts with TypeScript objects and connects the common application pieces around them: storage, tenants, users, permissions, web pages, APIs, agent tools, and operator commands.
How an application comes together
These guides move from describing the product to deciding ownership, identity, access, and interfaces. Read across them or enter at the part you need.
- 01 →
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 →
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 →
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 →
Grant access
A membership connects a user, a tenant, and a role. Permissions are named actions such as items.read or articles.publish.
- 05 →
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 →
Connect APIs, tools, and agents
You choose what people, agents, browsers, and operators can do. s-m-r-t generates the repetitive route, tool, schema, and command wiring.
Newer parts of the framework
Use these when the basic application path reaches the problem they solve.
Agent-assisted forms
Let chat, voice, tutorials, or tests find and explain controls, then stage changes behind explicit confirmation.
Read more →Learning agents
Agents can recall useful experience, track outcomes, and propose instruction changes behind a human approval step.
Read more →Mobile foundation
Shared offline, authentication, networking, and evidence-capture behavior for native Android and iOS apps.
Read more →Hydration and live data
Start with server-rendered rows, seed the browser collection, then keep it current without a duplicate first fetch.
Read more →WebMCP
A page can offer selected application tools to a browser agent through the signed-in user session.
Read more →Reports
Define durable aggregate models with full and incremental refresh, schedules, watermarks, and tenant scope.
Read more →Standard UI foundation
Build with one accessible component contract for forms, collections, tables, feedback, overlays, layouts, and themes.
Read more →