II.
Workflow JSON
Structured · liveworkflow:M-and-A-tech-integration
M&A Technology Integration json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "workflow:M-and-A-tech-integration",
"_kind": "Workflow",
"_file": "workflows/workflows/workflows-expanded-3.yaml",
"_cluster": "workflows",
"attributes": {
"displayName": "M&A Technology Integration",
"workflowKind": "strategic",
"triggerType": "event-driven",
"typicalCadence": "per-acquisition",
"complexity": "cross-team",
"description": "Integrating technology stacks after mergers and acquisitions —\ntechnology due diligence, architecture assessment, system consolidation\nplanning, data migration, team integration, and toolchain unification.\nCovers technical debt assessment and platform rationalization.\n"
},
"outgoingEdges": [
{
"from": "workflow:M-and-A-tech-integration",
"to": "role:engineering-manager",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:M-and-A-tech-integration",
"to": "role:technical-program-manager",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:M-and-A-tech-integration",
"to": "role:solutions-architect",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:M-and-A-tech-integration",
"to": "domain:software-engineering",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:M-and-A-tech-integration",
"to": "domain:operations",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:M-and-A-tech-integration",
"to": "responsibility:architecture-decision",
"kind": "triggers_responsibility",
"attributes": {}
},
{
"from": "workflow:M-and-A-tech-integration",
"to": "responsibility:stakeholder-communication",
"kind": "triggers_responsibility",
"attributes": {}
}
],
"incomingEdges": []
}