iiRecord
Agentic AI Atlas · Technical Communication
specialization:communicationa5c.ai
II.
Specialization reference

specialization:communication

Reading · 2 min

Technical Communication reference

Processes for communication work: channel management (Slack/Discord), content

Specializationwiki/library/communication.mdOutgoing · 1Incoming · 8

Communication specialization

Processes for communication work: channel management (Slack/Discord), content production and validation, and governed multi-audience announcements. The specialization layers a flagship orchestrated pipeline over four Style-B persona point files.

Flagship

multi-audience-announcement-pipeline.js — end-to-end governed announcement flow: source-material intake -> single canonical fact sheet -> ctx.parallel per-audience variants (internal, customers, press, partners) -> adversarial claim-trace/tone/cross-audience-drift gate -> per-audience routed approvals (frozen audience->expert map) -> policy-gated sends -> delivery confirmation; kip recall at intake and assert at close (kind communication).

Policy-gated actions:

actionIdAudiences coveredExpert
internal-broadcastinternalexec-sponsor
external-comms-sendcustomers, partners (single gate covering both variants)comms-lead
press-release-publishpresscomms-lead

Point files

classify each (respond / moderate / escalate / notify), draft per-mention responses in parallel, send via @slack/web-api ad-hoc code.

classify, draft and execute per-mention actions in parallel via discord.js.

flagship's per-audience drafting stage.

perspectives, ambiguity, metaphors, consistency); drives the flagship's tone-audience critic.

  • slack-manager.js — Slack-manager persona: scan channels/unanswered mentions,
  • discord-manager.js — Discord counterpart: scan server/unanswered mentions,
  • content-writer.js — brief -> plan -> draft -> self-edit persona; drives the
  • content-validator.js — 5-axis devil's-advocate review (clarity, audience

Note: the flagship composes these point files BY NAME as draft/send-stage executor personas in task prompts — there are no ESM imports of point files.

Shared combinators

The flagship depends on ../common-utilities/routed-gate-combinators.js (routedBreakpoint, adversarialGate, kipRecall, kipAssert, gateFixerTask).

Governance model

Fail-closed policy gates: breakpointId equals the actionId, send executors run ONLY inside approved === true guards, and every outcome — including skipped gates on a failed accuracy gate and non-interactive auto-approvals — is recorded in outputs.gatedActions. One audience's rejection records the decision and never blocks the other audiences.