research-document ROADMAP-COMMUNICATION-ENGINEERING-BODIES-2026

Communication Engineering adjacent-body analysis program

Purpose

Determine whether the proposed “Communication Engineering” label identifies a distinct and useful engineering profile, or merely renames established bodies of knowledge. This roadmap is a mutable execution view, not a registry record and not evidence by itself.

Completion gate for every body of work

A stream may be marked complete only when it records:

  • foundational constructs and theories;
  • recent peer-reviewed or standards-based developments;
  • at least one empirical or field result where available;
  • competing interpretations and counterevidence;
  • methods and outcome measures reusable by this repository;
  • what the body already explains;
  • what it does not explain;
  • overlap with the proposed profile;
  • at least one assumption or belief challenged;
  • a discriminating prediction or experiment;
  • confidence, limitations, and exact source provenance;
  • ten nontrivial future research questions when the stream is treated as a completed topic.

Shared claims to challenge

  • Communication failure is mainly an information-content problem. Rejected: coordination, trust, ownership, and authority can dominate.
  • More complete documentation necessarily improves outcomes. Rejected: relevance and managed selectivity matter.
  • Communication quality can be evaluated independently of recipient, purpose, authority, timing, and organizational context. Rejected by expertise reversal, interruption moderators, and organizational mediation.
  • Tacit knowledge can usually be converted into an artifact. Rejected: transactive memory and knowledge integration remain social.
  • Reduced clarification means better communication. Rejected: questions can be productive coordination; silence can be disengagement.
  • A technically correct message causes correct action. Rejected: rhetorical framing, authority, closed-loop confirmation, and context mediate action.
  • A reusable template works across expertise levels and risk classes. Rejected by expertise reversal; adaptation must itself be tested.
  • AI summarization reduces total communication cost. Rejected as a general claim: factuality, verification, omission, and calibration costs apply.
  • Integration of existing methods constitutes a new discipline. Rejected: incremental predictive or practical value must be demonstrated.
  • The word “engineering” is justified without predictive or verification capability. Rejected: systems and decision science already provide the relevant burden of proof.

Execution checklist

# Body of work Core analysis Completion evidence Status
1 Technical communication Task-oriented documentation, audience analysis, minimalism, structured authoring, information quality, maintenance JR-TECHCOMM-2026-A631; EV-TECHCOMM-* [x] bounded map complete
2 CSCW and coordination theory Common ground, articulation work, awareness, boundary objects, distributed work, coordination breakdown JR-CSCW-2026-B027; EV-CSCW-* [x] bounded map complete
3 Requirements engineering Elicitation, ambiguity, traceability, rationale, specification quality, validation, evolution JR-REQ-2026-51E8; EV-REQ-* [x] bounded map complete
4 Software maintenance and program comprehension Information foraging, mental models, task resumption, change rationale, onboarding, maintenance outcomes JR-MAINT-2026-18D2; EV-MAINT-* [x] bounded map complete
5 Human factors and safety-critical handoffs Shift handoffs, checklists, read-back, cross-checking, resilience, adverse-event prevention JR-SAFETY-2026-2B41; EV-SAFETY-* [x] bounded map complete
6 Knowledge management and organizational learning Tacit/explicit knowledge, transactive memory, expertise location, organizational memory, communities of practice JR-KM-2026-4AE3; EV-KM-* [x] bounded map complete
7 Cognitive psychology Working/prospective memory, interruption recovery, cognitive load, calibration, expertise reversal JR-COG-2026-6D08; EV-COG-* [x] bounded map complete
8 Information architecture and retrieval Findability, information scent, metadata, provenance, search, stale information JR-IA-2026-80F6; EV-IA-* [x] bounded map complete
9 Rhetoric and discourse studies Rhetorical situation, genre as social action, argumentation, discourse coherence, commitments JR-RHETORIC-2026-7A3E; EV-RHETORIC-* [x] bounded map complete
10 Systems engineering and decision science Interfaces, lifecycle traceability, assurance cases, uncertainty, value of information, verification JR-SYSTEMS-2026-956A; EV-SYSTEMS-* [x] bounded map complete
11 Accessibility and inclusive communication Cognitive accessibility, assistive technology, plain language, multilingual and neurodiverse contexts JR-A11Y-2026-CA09; EV-A11Y-* [x] bounded standards map complete; empirical participation debt
12 AI-mediated communication Summarization, provenance, hallucination, automation bias, common ground, context compression, decay JR-AI-COMM-2026-E51B; EV-AI-COMM-* [x] bounded map complete

Synthesis gate

After all streams:

  • Build a claim-by-field coverage matrix. See RP-BOUNDARY-2026-5A7C.
  • Identify any exclusive object, mechanism, method, or prediction. None found.
  • Compare an integrated profile against the strongest adjacent method.
  • Quantify added value and added process cost.
  • Test whether the label improves retrieval and decisions or creates terminological confusion.
  • Accept, narrow, rename, or reject the proposed profile through a Decision Record. DF-BOUNDARY-2026-3F72 rejects the discipline claim and leaves only an experimental profile.

The three unchecked items are empirical follow-ups, not incomplete literature streams. They require a preregistered experiment or terminology study and must not be checked from synthesis alone.

Stop and continuation rules

Stop a stream when its completion gate is met or when access limitations are recorded and the remaining evidence cannot change the current decision. Never mark a literature search exhaustive unless a reproducible systematic protocol was actually run. Every incomplete stream must state the next source class, query, or experiment needed.