Flowable BPMN Category Governance Restructuring L3
Domain: business_finance — Enterprise Analytics & Planning

Summary: Redesign Z Global's Maternal & Baby category governance workflow in Flowable BPMN 6.5.0 for a compound organizational disruption, then produce the required BPMN, compliance, scenario-result, and design-decision artifacts.

Task prompt:
You are working on a Linux VM with Docker, Docker Compose, Python, and curl available.

## Your Task
Redesign Z Global's Maternal & Baby category governance workflow in Flowable BPMN 6.5.0 so it handles a compound organizational disruption:
1. the M&B category owner vacancy immediately before a promotion cycle
2. temporary Beauty peer-owner unavailability
3. a regulator-triggered emergency delisting and brand-risk reassessment
4. a hard 48-hour senior-lead decision SLA

## Visible Inputs
- task prompt: `base/input/task_prompt.md`
- starter project directory: `base/input/starter_project`
- original BPMN: `base/input/starter_project/original_process.bpmn20.xml`
- disruption scenario: `base/input/starter_project/disruption_scenario_L3.md`
- business rules: `base/input/starter_project/business_rules_L3.md`
- org hierarchy: `base/input/starter_project/org_hierarchy.json`
- scenario suite: `base/input/starter_project/test_scenarios_L3.json`
- stakeholder artifacts: `base/input/starter_project/stakeholder_artifacts`
- Flowable stack file: `base/input/starter_project/docker-compose.yml`
- original diagram: `base/input/starter_project/original_process_diagram.png`

## What You Must Do
1. Read the staged task materials.
2. Modify the BPMN while preserving original anchored elements and IDs.
3. Use process definition key `zMBCategoryGovernance_modified_L3`.
4. Start or reuse the local Flowable stack from the staged Docker Compose file.
5. Deploy the modified BPMN and validate it against the provided scenario definitions.
6. Write the final output bundle to `base/output`.

## Required Output Files
- `base/output/modified_process.bpmn20.xml`
- `base/output/structural_changes.json`
- `base/output/business_rules_compliance.json`
- `base/output/test_results.json`
- `base/output/design_decisions.md`

Do not modify files under `input/`. Do not write final outputs outside `output/`.

The agent must:
Read the staged task prompt, starter BPMN, business rules, org hierarchy, scenarios, and stakeholder artifacts.
Modify the BPMN to handle the L3 compound governance disruption while preserving anchored original elements and IDs.
Use process definition key `zMBCategoryGovernance_modified_L3` and keep new manual work as `userTask` nodes.
Start or reuse the Flowable stack and validate the design against the visible scenario definitions.
Write the BPMN plus structural, compliance, scenario-result, and design-decision artifacts under `output/`.

Software: Flowable 6.5.0
Docker
Docker Compose
Python
curl

Input files:
name: task_prompt.md
format: Markdown
description: Agent-visible task contract
name: starter_project/original_process.bpmn20.xml
format: BPMN XML
description: Original Flowable process definition to modify
name: starter_project/disruption_scenario_L3.md
format: Markdown
description: Compound organizational disruption narrative
name: starter_project/business_rules_L3.md
format: Markdown
description: Authoritative L3 business rules
name: starter_project/org_hierarchy.json
format: JSON
description: Role hierarchy and authority constraints
name: starter_project/test_scenarios_L3.json
format: JSON
description: Scenario definitions for validation
name: starter_project/stakeholder_artifacts/
format: Markdown directory
description: Context-bound stakeholder constraints
name: starter_project/docker-compose.yml
format: YAML
description: Flowable runtime stack definition
name: starter_project/original_process_diagram.png
format: PNG
description: Visual diagram of the original workflow