II.
Methodology JSON
Structured · livemethodology:trunk-based-development
Trunk-Based Development json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "methodology:trunk-based-development",
"_kind": "Methodology",
"_file": "domain/methodologies/methodologies-expanded.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Trunk-Based Development",
"description": "A source-control branching model where developers collaborate on code in a\nsingle branch (trunk/main), using short-lived feature branches (< 1 day) or\ncommitting directly to trunk. Relies on feature flags, branch-by-abstraction,\nand comprehensive CI to keep trunk always releasable. Enables continuous\nintegration and reduces merge conflicts dramatically.\n",
"methodologyKind": "engineering-practice",
"origin": "Paul Hammant",
"yearIntroduced": "2013"
},
"outgoingEdges": [
{
"from": "methodology:trunk-based-development",
"to": "domain:software-engineering",
"kind": "applies_to"
},
{
"from": "methodology:trunk-based-development",
"to": "domain:devops",
"kind": "applies_to"
},
{
"from": "methodology:trunk-based-development",
"to": "platform:kradle",
"kind": "applies_to",
"attributes": {
"notes": "Kradle branch protection and fast-forward merge support trunk-based development"
}
}
],
"incomingEdges": []
}