Group activities into workflows
AAP-2 Order: #2 Ontology Assembly Has Dependencies
Updated 3 months, 4 weeks ago
Guidance
Cluster activities into coherent sequences that share a defined output. Assign each workflow a name, 3-letter abbreviation, and description.
Grouping heuristics:
- Pipeline stage: what triggers the next group? (data prep → model → evaluation is a natural boundary)
- Shared artifact: activities that produce and consume the same intermediate artifact belong together
- Role boundary: if a different skill or team takes over, that is often a workflow boundary
- Size check: prefer 3–7 activities per workflow — fewer suggests over-splitting; more suggests under-splitting
Details
- Order:
- #2
- Phase:
- Predecessor:
- AAP-1 Map goals to hierarchy
- Created:
- May 20, 2026
- Last Updated:
- May 21, 2026
Workflow
Assemble Playbook
Map the Extraction Worksheet onto the Mimir schema and wire everything together into a complete, executable playbook — phases, workflows, …
View WorkflowAssigned Agent
No agent assigned
Required Skills
- Ontology Mapping Knowledge Engineering
Rules
-
Granularity rule
granularity-rule -
Naming convention
naming-convention
Input Artifacts 1
-
Extraction Worksheet
Document
Required
Produced by: Review worksheet
Output Artifacts
No output artifacts