Agent Roles
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Agent responsibilities must be explicit: an agent may act as a governed domain participant without owning every business decision.
Domain-Driven Design starts from bounded contexts, shared vocabulary and business decision ownership. In logiCells, these are projected into concepts, relations, Actions, Events, Processes and semantic specifications. A business domain boundary should not be inferred from an HTTP endpoint, a database table or a microservice topology.
Engineering rules
- Identify the bounded context responsible for each rule and identity.
- Map aggregates and invariants before choosing persistence and transport.
- Publish explicit contracts between contexts and version their semantics.
- Test business decisions and authorization independently of interface details.
Chapter outline (original LaTeX headings)
- An Agent Is a Caller, Not an Alternate Domain Model
- Give Agents an Execution Envelope
- Separate Observation, Proposal, and Commitment
- Semantic Memory Improves Explainability
- Generated Knowledge Is Candidate Knowledge
LaTeX provenance
Primary chapter: Domain-Driven Design with logiCells/agents-as-domain-participants.tex.