II.
Methodology JSON
Structured · livemethodology:state-machine-orchestration
State Machine Orchestration json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "methodology:state-machine-orchestration",
"_kind": "Methodology",
"_file": "domain/methodologies/methodologies.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "State Machine Orchestration",
"description": "Explicit state management with formal state machine semantics for workflow\norchestration. Defines explicit states (INIT, PLANNING, EXECUTING, VALIDATING,\nCOMPLETE, FAILED), conditional transitions with guards, entry/exit actions for\neach state, state history tracking, and transition validation. Provides\ndeterministic, predictable workflows with clear state transitions and validation\nat each step for complex multi-phase processes.\n",
"methodologyKind": "orchestration",
"origin": "Babysitter community"
},
"outgoingEdges": [
{
"from": "methodology:state-machine-orchestration",
"to": "domain:software-engineering",
"kind": "applies_to"
}
],
"incomingEdges": [
{
"from": "lib-process:shared--state-machine-orchestration",
"to": "methodology:state-machine-orchestration",
"kind": "follows_methodology",
"attributes": {
"weight": 1
}
}
]
}