II.
ScopeBoundary JSON
Structured · livescope-boundary:nextjs.scope
scope-boundary:nextjs.scope json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "scope-boundary:nextjs.scope",
"_kind": "ScopeBoundary",
"_file": "sourceref-scope/scope-boundaries/scope-boundaries-frameworks.yaml",
"_cluster": "sourceref-scope",
"attributes": {
"subjectId": "framework:nextjs",
"inScope": "Full-stack React meta-framework — file-system routing, server\ncomponents, server actions, edge runtime, image optimization, and\nVercel-aligned deploy story. Strong for SaaS, e-commerce, and\ncontent-heavy sites needing SSR/ISR.\n",
"outOfScope": "Pure SPAs without an SSR boundary (use Vite + React), heavy\nNode-only backends without a UI, and projects that need to\navoid the Vercel-shaped deployment model.\n",
"outOfScopeReasonIds": [
"out-of-scope-reason:implementation-detail"
]
},
"outgoingEdges": [
{
"from": "scope-boundary:nextjs.scope",
"to": "framework:nextjs",
"kind": "bounds_subject"
},
{
"from": "scope-boundary:nextjs.scope",
"to": "out-of-scope-reason:implementation-detail",
"kind": "has_out_of_scope_reason"
}
],
"incomingEdges": []
}