{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/give-technical-terms-one-local-definition",
  "id": "MHC-D-RESEARCH-0618",
  "version": "0.1.0",
  "title": "Give technical terms one local definition",
  "summary": "Shared words can hide unshared models.",
  "kind": "principle",
  "body": "When a term is necessary and potentially ambiguous, define it once where first used or point to the authoritative glossary. Prefer the team's actual domain term over a simpler but inaccurate substitute. Do not expand every familiar acronym mechanically.",
  "limits": [
    "Local definitions should not silently redefine regulated or system-standard terminology; use authoritative definitions where they exist."
  ],
  "topics": [
    "union-actionable-async-writing"
  ],
  "intents": [],
  "source_ids": [
    "RS-B843492FBF1442AD"
  ],
  "evidence": [
    {
      "claim": "CDC guidance recommends active voice and familiar audience language, with technical terms explained where needed.",
      "source_id": "RS-B843492FBF1442AD",
      "role": "supports",
      "note": "Technical precision should not be removed when it is necessary for the task.",
      "locator": "Core items 6 and 7"
    }
  ],
  "use_when": [
    "A specialist message uses a term that different teams interpret differently."
  ],
  "avoid_when": [
    "Local definitions should not silently redefine regulated or system-standard terminology; use authoritative definitions where they exist."
  ],
  "example": "'Activated = change request completed and BP data written to active area; it does not mean DRF replication finished.'",
  "check": "The term has one operational meaning for this message.",
  "sources": [
    {
      "id": "RS-B843492FBF1442AD",
      "title": "Description and Examples of Index Items",
      "url": "https://www.cdc.gov/ccindex/tool/description-examples-parta.html"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-0618",
      "to": "MHC-D-RESEARCH-0610",
      "type": "useful_with",
      "url": "/knowledge/write-known-unknown-and-assumed-as-different-states"
    }
  ],
  "collections": [
    {
      "id": "RC-ECF674DEF65C9DAB",
      "title": "Write asynchronous messages that can be acted on without a meeting",
      "url": "/collections/write-asynchronous-messages-that-can-be-acted-on-without-a-meeting"
    }
  ]
}