s-m-r-t docs

Application foundations

Understand how the common parts fit together.

These guides explain the connected parts already present in a s-m-r-t app. The narrative moves from your product model through ownership, identity, access, pages, and external interfaces.
  1. 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.

    smrt-core · smrt-config →
  2. 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.

    smrt-tenancy · smrt-users →
  3. 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.

    smrt-users · smrt-profiles →
  4. 04

    Grant access

    A membership connects a user, a tenant, and a role. Permissions are named actions such as items.read or articles.publish.

    smrt-users · smrt-tenancy →
  5. 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.

    smrt-svelte · smrt-web →
  6. 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.

    smrt-core · smrt-app-mcp →