Add the parts your application needs.

An agent receives bounded descriptions of the model, interface, and callable actions. The runtime bridge can also provide an active-environment view. The agent does not have to infer these details from files or rendered pixels.

An agent can find a field, explain it, highlight it, check it, or propose a value. The user still confirms changes, and secret or read-only fields remain protected.

Learning is opt-in. Before a run, an agent recalls confident memories. After the run, success strengthens them and failure weakens them. Human feedback can become a proposed persona update, but approval is a separate permissioned action.

smrt-mobile is Kotlin Multiplatform shared logic. smrt-android supplies Compose UI and Android adapters; smrt-ios supplies SwiftUI and Apple adapters. Your product keeps native UI while the hard stateful behavior stays consistent.

Server rendering gives the first page. Hydration teaches the browser store what it already has. Change signals and a durable outbox handle what happens next—online or off.

In a browser with WebMCP support, your page can advertise useful application actions to an AI agent. Those actions still run as the signed-in page user through the generated REST API, so existing authentication, tenant, permission, and field policies remain in charge.

Define how rows group and which measures to calculate. s-m-r-t compiles the aggregate, stores the result in an ordinary report table, and tracks refresh runs, watermarks, locks, and schedules.

The shell owns application chrome so each domain package can focus on its working surface. A manifest can build tenant navigation on the server; live jobs and changes can feed activity without coupling the shell to a transport.

Use a normal list when you want real objects and their methods. Use select when you only need a few columns. The type system tells you which shape comes back.

The form your code ships is a starting point, not a final answer. An organization can change field visibility or set a default for all users. An individual can make the same changes for one account. These changes do not require code edits.

You can keep an existing form and use policy to set the initial field visibility. You can also give an object reference to one component. The component then builds the form.

Administrators set the arrangement everyone starts from. Everyone else can adjust their own view unless a field is locked. A personal preference belongs to the person who set it: the server takes the identity from the request, never from the request body.