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.
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. Thus, the agent can understand and change one definition instead of rediscovering each 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. It keeps the codebase map current and makes infrastructure replaceable. Security improvements can then flow from shared framework packages into each application.