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
Use-case is a subtype of the “Phases and Milestones” element type. It is intended to use as a top-level element in this process element tree. It is a container element which contains phases and milestones and it defines the scope for a use-case package.
From a method perspective the scope of a use-case shall be aligned with the responsibility and tasks of a single agent, so an agent receives the right amount of process goverance at a time.
For generation of an use-case package the following modelling patterns are considered:
- The sections (tupels of Phase → Milestones) in the order as the the Use Case defines it
- For each Milestone, the gates: the required Work Products and Quality Levels, with their criteria as a checklist.
- For each section, the Activities of the associated Workflows in the order given by their sequence associations, including Decisions and their alternative branches.
- For each Activity, the Responsible and other RASIC Roles, input and output work products and the agent policy regarding human only role execution
- All Practices, Tools and Checklists associated with the Use Case, its subordinated Phases and Milestones and the associated Quality Levels, Activities and Work Products. Templates, Trainings and other Guidance elements are not passed on.
- Association-comments, are delivered as notes on the respective element.