II.
Specialization JSON
Structured · livespecialization:communication
Technical Communication json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "specialization:communication",
"_kind": "Specialization",
"_file": "domain/specializations/specializations-additional.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Technical Communication",
"parentDomainId": "domain:software-engineering",
"description": "Effective communication in technical contexts — writing clear technical\nproposals, status updates, incident reports, architectural decision\nrecords, and stakeholder presentations. Covers structured argumentation,\naudience-aware framing, visual communication (diagrams, charts), and\ncommunication practices that scale across remote and distributed\nengineering teams. Sourced from library/specializations/communication/.\n"
},
"outgoingEdges": [
{
"from": "specialization:communication",
"to": "domain:software-engineering",
"kind": "specializes"
}
],
"incomingEdges": [
{
"from": "domain:diplomacy",
"to": "specialization:communication",
"kind": "contains"
},
{
"from": "skill-area:technical-documentation",
"to": "specialization:communication",
"kind": "applies_to",
"attributes": {
"confidence": "secondary"
}
},
{
"from": "lib-process:communication--content-validator",
"to": "specialization:communication",
"kind": "lib_belongs_to_specialization",
"attributes": {
"weight": 1
}
},
{
"from": "lib-process:communication--content-writer",
"to": "specialization:communication",
"kind": "lib_belongs_to_specialization",
"attributes": {
"weight": 1
}
},
{
"from": "lib-process:communication--discord-manager",
"to": "specialization:communication",
"kind": "lib_belongs_to_specialization",
"attributes": {
"weight": 1
}
},
{
"from": "lib-process:communication--slack-manager",
"to": "specialization:communication",
"kind": "lib_belongs_to_specialization",
"attributes": {
"weight": 1
}
}
]
}