Simon separates the agent, interface, and business logic. Both surfaces call the same MCP tools, which apply validations on a local data store.
Simon gives the agent autonomy without opaque data access. Domain tools carry the validations.
Creating a counterparty in a view or asking the agent to create it produces the same action with the same business validations.
Sequence diagram with UI/agent calling the same MCP action, then db.changed event.
Dispatchers turn dozens of similar actions into a hierarchical choice: domain, action, validated parameters.
Domain/action matrix with integrated help and validation schemas.
Accounting data, files, views, and traces stay on the machine. The embedded tax knowledge base helps the agent cite sources.
Visual of versioned tax sources and local company data, with AI provider boundary.
The marketing site must be transparent about beta scope and responsibilities.
Simon helps produce and control accounts; it does not sign them.
Simon prepares data and documents; the user files outside Simon.
The beta product targets a local database and workstation.
The user configurés the model and accepts that provider's terms.
Public pricing is intentionally hidden during beta. The getting-started docs explain scope and prerequisites.