Look up the part you need.

Define the work once. People can reach it through pages, HTTP, or the command line, while agents receive callable tools that resolve to the same models, permissions, and field policies.

Private is the default. Secret fields stay out of responses and filters, while read-only and server-managed fields are removed from client writes.

s-m-r-t uses small adapter packages so changing a database, model provider, cache, or file store is primarily a configuration decision instead of an application rewrite.

Context memory remembers useful facts or strategies. Semantic search finds records whose meaning is close to a query, even when the words do not match exactly.

Tests should exercise the real model, collection, permission, tenant, and component contracts at the narrowest useful level.

Configuration tells each package how your application connects to databases, services, models, and runtime options. Secrets should remain references or environment values, not committed strings.

A decorator is a short note attached to a class or field. The scanner records that note in the manifest so migrations and runtimes make the same decision.

Use a normal list when you need real objects and their methods. Use select when a page or report only needs a few plain fields.

REST serves application clients, MCP serves connected agents, WebMCP serves agents in the browser page, and CLI serves people or scripts in a terminal.

These names describe different jobs. Keeping them distinct makes data, identity, and authority easier to discuss.