This is an old revision of the document!
Prepare your Process for Agentic AI
- define collection - define exposure to MCP (permissions)
How it works
The Agent governance MCP toolset consists of 3 tools:
- Stages projects list: lists all available collections
- Stages usecases list (projectID): lists all use-cases for a given projectID
- Stages usecases get (use-case ID): get the Use Case package in MarkDown for a given use-case-ID
Use-case modelling
A Use Case is a subtype of the Phases and Milestones element type. It is intended to serve as a top-level element in the process element tree. As a container element, it comprises Phases and Milestones and defines the scope of a use-case package.
From a methodological perspective, the scope of a Use Case should be aligned with the responsibilities and tasks of a single agent. This ensures that the agent receives the appropriate amount of process governance for the task at hand.
When generating a use-case package, the following modeling patterns are taken into account:
- Sections: The sections, each represented by a Phase → Milestones tuple, are included in the order defined by the Use Case.
- Milestone gates: For each Milestone, the applicable gates are included. These comprise the required Work Products and Quality Levels, including their criteria presented as a checklist.
- Activities and flow: For each section, the Activities of the associated Workflows are included in the order defined by their sequence associations. This also includes Decisions and their alternative branches.
- Roles and work products: For each Activity, the Responsible Role and other RASIC Roles are included, together with the input and output Work Products and the applicable agent policy regarding roles that may only be performed by humans.
- Supporting process elements: All Practices, Tools, and Checklists associated with the Use Case, its subordinate Phases and Milestones, and the associated Quality Levels, Activities, and Work Products are included. Templates, Trainings, and other Guidance elements are excluded from the generated package.
- Association comments: Comments attached to associations are included as notes on the respective process element.