II.
ScopeBoundary JSON
Structured · livescope-boundary:system-design.scope
scope-boundary:system-design.scope json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "scope-boundary:system-design.scope",
"_kind": "ScopeBoundary",
"_file": "sourceref-scope/scope-boundaries/system-design.yaml",
"_cluster": "sourceref-scope",
"attributes": {
"subjectId": "skill:system-design",
"inScope": "Designing or evaluating system architecture — component decomposition,\ndata flows, API boundaries, failure modes, and tradeoff documentation.\nProduces an ADR or design doc. Covers backend services, data pipelines,\nand inter-service contracts.\n",
"outOfScope": "Detailed code-level design (delegated to code-review), UX / frontend\ndesign, low-level network/hardware design, capacity planning beyond\nrough order-of-magnitude, and vendor procurement decisions.\n",
"outOfScopeReasonIds": [
"out-of-scope-reason:implementation-detail",
"out-of-scope-reason:future-phase"
]
},
"outgoingEdges": [
{
"from": "scope-boundary:system-design.scope",
"to": "skill:system-design",
"kind": "bounds_subject"
},
{
"from": "scope-boundary:system-design.scope",
"to": "out-of-scope-reason:implementation-detail",
"kind": "has_out_of_scope_reason"
},
{
"from": "scope-boundary:system-design.scope",
"to": "out-of-scope-reason:future-phase",
"kind": "has_out_of_scope_reason"
}
],
"incomingEdges": []
}