iiRecord
Agentic AI Atlas · scope-boundary:technical-writing.scope
scope-boundary:technical-writing.scopea5c.ai
II.
ScopeBoundary JSON

scope-boundary:technical-writing.scope

Structured · live

scope-boundary:technical-writing.scope json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · sourceref-scope/scope-boundaries/technical-writing.yamlCluster · sourceref-scope
Record JSON
{
  "id": "scope-boundary:technical-writing.scope",
  "_kind": "ScopeBoundary",
  "_file": "sourceref-scope/scope-boundaries/technical-writing.yaml",
  "_cluster": "sourceref-scope",
  "attributes": {
    "subjectId": "skill:technical-writing",
    "inScope": "Producing clear technical documentation for engineering audiences —\nREADMEs, runbooks, API references, architecture overviews, and\nonboarding guides. Targets markdown output suitable for repo\ndocumentation or static-site generators.\n",
    "outOfScope": "Marketing or sales copy, end-user product documentation requiring UX\nresearch, video / multimedia content, translation/localization,\nand legal-compliance documents (privacy policies, ToS).\n",
    "outOfScopeReasonIds": [
      "out-of-scope-reason:future-phase",
      "out-of-scope-reason:implementation-detail"
    ]
  },
  "outgoingEdges": [
    {
      "from": "scope-boundary:technical-writing.scope",
      "to": "skill:technical-writing",
      "kind": "bounds_subject"
    }
  ],
  "incomingEdges": []
}