II.
Workflow JSON
Structured · liveworkflow:schema-migration
Schema Migration json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "workflow:schema-migration",
"_kind": "Workflow",
"_file": "domain/workflows/workflows-technical-depth.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Schema Migration",
"description": "Safe, audited workflow for evolving database schemas in production without downtime\nor data loss. The data engineer authors a migration script and a corresponding rollback\nscript, both reviewed by a backend engineer for correctness and performance impact on\nlarge tables. Migrations are tested against a production-sized data snapshot in a\nstaging environment with execution-time profiling. The migration is applied to production\nin a maintenance window or via a zero-downtime strategy (expand-contract pattern),\nand automated integrity checks verify row counts and index health after completion.\n",
"workflowKind": "development",
"triggerType": "on-demand",
"typicalCadence": "per-feature",
"complexity": "complex"
},
"outgoingEdges": [
{
"from": "workflow:schema-migration",
"to": "role:data-engineer",
"kind": "involves_role"
},
{
"from": "workflow:schema-migration",
"to": "role:backend-engineer",
"kind": "involves_role"
},
{
"from": "workflow:schema-migration",
"to": "role:sre",
"kind": "involves_role"
},
{
"from": "workflow:schema-migration",
"to": "role:tech-lead",
"kind": "involves_role"
},
{
"from": "workflow:schema-migration",
"to": "domain:data-engineering",
"kind": "applies_to_domain"
},
{
"from": "workflow:schema-migration",
"to": "role:database-administrator",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "role:db-migrator",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "role:tech-lead",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "skill-area:database-migrations-zero-downtime",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "skill-area:postgres-tuning",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "domain:databases",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "domain:platform-engineering",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "responsibility:approve-deploys",
"kind": "triggers_responsibility",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "responsibility:review-architecture-changes",
"kind": "triggers_responsibility",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "org-unit:database-team",
"kind": "performed_by_org_unit",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "org-unit:engineering",
"kind": "performed_by_org_unit",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "role:database-administrator",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "role:db-migrator",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "role:tech-lead",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "skill-area:database-migrations-zero-downtime",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "skill-area:postgres-tuning",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "domain:databases",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "domain:platform-engineering",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "responsibility:approve-deploys",
"kind": "triggers_responsibility",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "responsibility:review-architecture-changes",
"kind": "triggers_responsibility",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "org-unit:database-team",
"kind": "performed_by_org_unit",
"attributes": {}
},
{
"from": "workflow:schema-migration",
"to": "org-unit:engineering",
"kind": "performed_by_org_unit",
"attributes": {}
}
],
"incomingEdges": [
{
"from": "stack-profile:crm-customer-platform",
"to": "workflow:schema-migration",
"kind": "follows_workflow"
},
{
"from": "stack-profile:multi-tenant-saas-backend",
"to": "workflow:schema-migration",
"kind": "follows_workflow"
},
{
"from": "stack-profile:event-sourcing-cqrs",
"to": "workflow:schema-migration",
"kind": "follows_workflow"
},
{
"from": "tool:saleor",
"to": "workflow:schema-migration",
"kind": "supports_work",
"attributes": {
"confidence": "low",
"evidence": "Commerce schema changes require coordinated migration and API compatibility review."
}
},
{
"from": "tool:neon",
"to": "workflow:schema-migration",
"kind": "supports_work",
"attributes": {
"confidence": "high",
"evidence": "Database branching and migration history are direct schema-migration projection points."
}
},
{
"from": "tool:supabase",
"to": "workflow:schema-migration",
"kind": "supports_work",
"attributes": {
"confidence": "medium",
"evidence": "Supabase projects require coordinated schema and API migration review."
}
},
{
"from": "tool-server:mcp-neon-candidate",
"to": "workflow:schema-migration",
"kind": "supports_work",
"attributes": {
"confidence": "high",
"evidence": "Database branch and migration data are direct migration-review inputs."
}
},
{
"from": "lib-process:data-engineering-analytics--ab-testing-pipeline",
"to": "workflow:schema-migration",
"kind": "lib_implements_workflow",
"attributes": {
"weight": 1
}
}
]
}