Cross-fiber notification uses Channel

Platform spec ADR

Cross-fiber notification uses Channel

Back to Fibers and spawn ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• No directly attached article pages for this node.

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 8 SpecSection(s) · 1 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Fibers and spawn

  Parent feature hub

Context

event multicast is defined for ownership within one fiber; UI/IO delivery across fibers needs a defined transport.

Decision

Delivering notifications to another fiber must use Channel<T> (or coordination primitives), not language event delivery across fiber boundaries.

Consequences

Events stays single-fiber; console and host specs reference channels for cross-fiber IO.

Verification anchors

Fibers and spawn; Events.