s-m-r-t
Open the s-m-r-t source on GitHub Switch to dark color scheme

Reference

Evidence

Each claim the site makes about the framework, with the page that explains it and the released source it was checked against.

Package sources are the AGENTS.md contracts shipped in s-m-r-t 0.57.40; the site row links a commit of this repository.

ClaimSource

One record description becomes both the human screens and the agent tools.

Explained at What is a SAADL?

Core release contract ↗

Every control has a stable name; an agent can stage a value only where sensitivity rules allow, and only a person’s confirmation applies it.

Explained at Agent-assisted forms · Try it: Agent-aware form demo

smrt-ui release contract ↗

Selected operations become agent tools with the same names, inputs, and policy as the human interface.

Explained at Agents · Try it: UI overview

smrt-web release contract ↗

However a request arrives, the same permission checks apply — down to the stored record.

Explained at Security defaults · Try it: Governed interaction demo

Application MCP release contract ↗

A coding agent’s development server reads the project and its installed packages. It sees a development database’s system tables only when one is configured, and never your records.

Explained at Agent-legible applications

Development MCP release contract ↗

Native mobile shares one Kotlin Multiplatform core behind separate Compose and SwiftUI screens.

Explained at Mobile

Mobile source contract (source-only; package publishing deferred) ↗

This site itself runs on the released packages it documents, not a separate internal build.

Explained at Component playground

Documentation site source ↗

The audit wording for each row lives with its id in the site source, src/lib/data/why-smrt-claims.ts. A row is removed when its source no longer supports it.