← Reference

Framework concept

Software as Agentic Domain Logic

A SAADL application exposes the same domain operations to people and software agents instead of maintaining a separate, reduced bot interface.

Manifest
RESTMCPWebMCPCLIBrowser
Each interface reads the same declared model capabilities.

One definition, several ways to operate it

The domain model is the source of truth. REST routes, CLI commands, MCP and WebMCP tools, and human interfaces are projections of that same model rather than independent implementations that drift apart.

Useful to operators and builders

An operating agent receives the same permitted capabilities as a person. A coding agent receives a manifest of the objects, fields, relationships, and generated tools, so it can understand and change one definition instead of rediscovering every interface.

What does not count

A chatbot beside an application is not automatically SAADL. Neither is an agent-only tool or a generated UI. The defining property is parity: human and agent operations resolve through the same domain logic and security boundaries.

Why s-m-r-t uses this shape

One model reduces duplicated code and review, keeps the codebase map current, makes infrastructure replaceable, and lets hardening flow from shared framework packages into each application.