smrt
Open the smrt source on GitHub Switch to dark color scheme
← All packages
Foundation v0.62.10

@happyvertical/smrt-core

The object model, persistence layer, AI operations, manifests, and generated interfaces at the center of every smrt app.

Source ↗

What it gives you

The object model, persistence layer, AI operations, manifests, and generated interfaces at the center of every smrt app.

  1. 01Typed, column-backed list projections without object hydration
  2. 02Context memory and semantic search for durable learned patterns
  3. 03Change feeds, conditional reads, sync apply, REST, MCP, WebMCP, and CLI generation
  4. 04Recipes: declared user-facing units collected into the manifest, plus a cookbook document and engine
  5. 05A one-call smrt() Vite preset over the packages declared in smrt.config.ts

Recipes and cookbooks

A SmrtRecipe is a named, user-facing unit smaller than a package, such as Sales or Customers. Its static id, label, models, nav, requires, and options are read structurally by the scanner into the manifest and knowledge recipes. The /cookbook entry validates and migrates a cookbook v1 document; /cookbook/engine runs typed cookbook commands with idempotent retries, atomic batches, and receipts.

One Vite plugin call for a SvelteKit app

smrt() from @happyvertical/smrt-core/vite applies the decorator config and composes smrtConsumer and smrtPlugin with the SvelteKit conventions. The consumed packages are the declared list under consumer.packages in smrt.config.ts; a missing or malformed list fails the build. smrtPlugin and smrtConsumer remain public for custom setups. Generated routes resolve collections through the runtime exported from $lib/server/smrt; a hand-written getCollection export is deprecated.

Data shape rules

smrt requires a field only when its own code would be wrong or unsafe without it, and each such field states why. The app decides every other part of a table. An app hardens a smrt class with a subclass that overrides fields. A subclass with the same name replaces the class everywhere in the app. Migrate changes the database to match the code when that loses no data. It stops when it would lose or invent data, such as a field declared required while existing rows are empty.

Migrate is all or nothing

Migrate works out every change first. If any change stops, it applies none and reports what stopped and what it held back. Migrate also stops when a package it saw last time is missing. smrt does not start new code against a database that was not migrated for that build.

Models from data

runtimeModelEntry turns a definition into a manifest entry, and registerRuntimeModel registers it. The model then has storage, REST, MCP, and method surfaces without a class or a rebuild. planRuntimeModelDDL returns additive statements only. The host runs them in its own transaction, because smrt does not create the tables.

App models and cookbook tools

createAppModelEditor from the /app-models entry adds fields and lists to a cookbook with versioned, tracked edits. createCookbookToolService from /cookbook/tools supplies recipe tools, and an app customization set when given modelEditorFor. Removing a field or list, and undo, always need durable owner approval. Removing a list keeps its table and data.

Move a model or close its surface without a subclass

A class that moves between packages declares its old qualified names in previousQualifiedNames, and lookups by the old name keep resolving. smrt db:migrate-qualified-names rewrites stored names on request. ObjectRegistry.registerOverride closes the generated API, MCP, or CLI surface of a package model, or makes its tenancy required, at startup. Only complete closures are supported; reopening throws. The browser entry builds and evaluates without Node-only modules.