alknet/docs/architecture/crates/channels/README.md

status, last_updated

status	last_updated
draft	2026-07-18

alknet-channels

A multiplexing proxy: a ProtocolHandler on alknet/channels that decomposes a single bidirectional transport stream into N logical channels, each carrying a different ALPN. Channel 0 is pre-negotiated as alknet/call (ADR-072); every other channel is opened dynamically via call operations on channel 0 and routed through the same HandlerRegistry as top-level connections. The channels layer is a re-framing proxy — it converts between "one transport stream carrying N channels" (the wire) and "N independent BiStream handles" (what handlers see) — and it does no protocol work itself. The channels layer has no stream_type concept (ADR-093); the handler owns its sub-stream multiplexing on the BiStream it receives.

Documents

Document	Status	Description
overview.md	draft	Crate purpose, the multiplexing collapse, dependencies, ALPN, transport agnosticism, WASM, relationship to existing crates
channels-wire.md	draft	The 8-byte chunk format ([channel_id:u32 be][length:u32 be][payload]), the add/strip composition, sentinels, framing disambiguation, wire-level invariants (REQ-CH-01..05)
channels-connection.md	draft	ChannelBidiStreamSource (implements BidiStreamSource — ADR-070/074, as amended by ADR-093), accept_bi yields one BiStream per channel, recursive composition
channels-adapter.md	draft	ChannelsAdapter (ProtocolHandler on alknet/channels), ChannelManager, demux/mux contracts (REQ-CH-01..04), the two-pump pattern (ADR-078)
channel-operations.md	draft	channel/open, channel/close, channel/control, channel/resources/subscribe — call-protocol operations on channel 0, ACL flow, direction semantics, the hub relay contract (ADR-079)
channel-client.md	draft	ChannelClient — the client side of a channels connection; transport-agnostic from_connection primary; connect_quic removed per ADR-089 §5 (dial extracted to AlknetClient); bidirectionality preserved

Applicable ADRs

ADR	Title	Relevance
071	channels Wire Format — 8-Byte Chunk Header	The chunk format; channels layer has no stream_type concept (amended by ADR-093); substrate-agnostic; one-way door
093	channels Pure Channel Multiplexing	The umbrella decision: 8-byte header, no stream_type, into_sub_streams removed, BiStream-only, TTY always 5-byte
072	Channel 0 Is Pre-Negotiated alknet/call	Channel 0 = call protocol; no special control plane
073	Channel Lifecycle Operations on the Call Protocol	channel/open/close/control/resources/subscribe; direction semantics; subscribe not poll
074	ChannelConnection — BidiStreamSource over Chunk Reassembly	Per-channel BidiStreamSource impl; accept_bi yields BiStream (amended by ADR-093 — into_sub_streams removed)
075	ChannelsAdapter and ChannelManager	Substrate-agnostic demux loop; REQ-CH-01..04 contracts
076	Backpressure, Channel Limits, and ID Reuse	Bounded-buffer (1 MiB default), 256-channel cap, monotonic IDs with wrap
077	TTY Inside Channels — Sub-Streams, Not Wire Format	TTY's two modes (direct vs channels); reversed by ADR-093 — TTY always uses its 5-byte format, carried transparently
078	Two-Pump Shutdown-on-Completion Pattern	The two-pump deadlock contract; handler-level, not channels-layer
079	Hub Relay — Translate, Not Transparently Forward	The hub translates channel 0, byte-forwards data channels with ID rewrite
080	ChannelClient — the Client Side of a Channels Connection	ChannelClient, transport-agnostic from_connection primary; connect_quic removed per ADR-089 §5; AlknetClient dial-seam extracted (ADR-089, resolves OQ-55)
081	channels Sub-Crate Decomposition	channels-core (pure multiplexer) / channels-call (call coupling + ChannelClient); hub and worker are consumers, not sub-crates
070	BidiStreamSource Trait	The Connection extension point ChannelBidiStreamSource implements
092	BiStream as the Handler Leaf	accept_bi returns BiStream; the transport-leaf decision ADR-093 builds on
065	Connection::from_stream	The transport-agnostic Connection the channels layer rides on
052	alknet-tty Wire Format	The 5-byte format carried transparently in the channels payload (control bidirectional via STREAM_CTRL_IN/OUT — Phase 7 amendment)
049	StreamingHandler for Subscriptions	The machinery channel/resources/subscribe uses
032	Forwarded-For Identity	The auth chain for hub-relayed channel opens
003	Crate Decomposition	alknet-channels depends on alknet-core only; no handler-depends-on-handler

Relevant Open Questions

OQ	Title	Status	Relevance
OQ-55	AlknetClient / Client Establishment Extraction	resolved (ADR-089)	ChannelClient's API is decided (ADR-080): transport-agnostic from_connection primary; connect_quic removed (ADR-089 §5). AlknetClient core extraction is now resolved — the native dial seam is alknet-client (ADR-089)
OQ-56	Full channel-level flow-control windowing	deferred(scope)	Bounded-buffer is decided (ADR-076); full windowing is an extension blocked on "a real deployment observes HOL blocking on a saturated channel where bounded buffer is insufficient"
OQ-57	Two-pump helper extraction to alknet-core	deferred(scope)	The shutdown-on-completion contract is decided (ADR-078); the helper extraction is blocked on a second two-pump handler existing (shape convergence)
OQ-68	Add/strip API shape (built-in vs utility)	open	Whether the 8-byte header add/strip is built into the channels read/write path or exposed as a standalone utility. The contract is decided (ADR-093); the function surface is not

Key Design Principles

1. Streams are streams. A TTY session, an SSH channel, a forwarded TCP connection, a QUIC bidi stream — they're all BiStream (a concrete AsyncRead + AsyncWrite newtype, per ADR-092). The differences are only in how they're opened (negotiation via channel/open on channel 0) and what multiplexing layer carries them (the 8-byte chunk format). Once normalized, every channel is an ALPN routed through the same HandlerRegistry. See overview.md and ADR-071 (as amended by ADR-093).

2. Channel 0 is alknet/call pre-negotiated, not a special control plane. The call protocol runs on channel 0 exactly as on a top-level alknet/call connection. Channel lifecycle operations (channel/open, channel/close, channel/control, channel/resources/subscribe) are call operations on channel 0's OperationRegistry, gated by the existing AccessControl::check. No new auth machinery, no new framing. See ADR-072, ADR-073.

3. The channels layer is a re-framing proxy, not a protocol engine. It converts between "one transport stream carrying N channels" (the wire) and "N independent BiStream handles" (what handlers see). It does no ALPN-specific parsing, no auth, no transport coupling, and carries no stream_type concept (ADR-093). This makes it WASM-compatible and transport-agnostic by construction. See channels-adapter.md and ADR-075.

4. The handler owns its sub-stream multiplexing. The channels layer yields one BiStream per channel; the handler sub-multiplexes it however it wants (TTY's 5-byte format, call's length-prefixed JSON, tunnel's raw bytes, SSH's channel protocol). The channels layer carries the bytes transparently. See channels-connection.md and ADR-093.

5. channel/resources/subscribe is a Subscription, not a polled Query. The call protocol has StreamingHandler / invoke_streaming (ADR-049, implemented and tested). The first consumer (the hub aggregating worker resources) needs live updates. Polling would be built and immediately reworked. See ADR-073.

6. Bidirectional open. Either side can open a channel to the other, just like the call protocol's operation overlay. The direction field on channel/open pins who is the ALPN-server vs ALPN-client. See ADR-073 §Direction semantics.

7. Wire-level invariants are contracts, not implementation details. The POC surfaced five invariants (REQ-CH-01..04, plus REQ-CH-06 for close ordering) that hang channels silently if underspecified: shutdown emits a zero-length sentinel; transport close drops all senders; the mux supports dynamic registration; unknown channel_id is lenient-dropped; bounded-buffer backpressure doesn't deadlock; data chunks flush before channel/close. See channels-wire.md and channels-adapter.md.

8. The hub translates, not transparently forwards. The hub terminates channel 0 on both legs, runs AccessControl::check, and re-issues channel/open on the spoke leg with forwarded_for (ADR-032). Data channels are byte-forwarded with channel_id rewrite (a 4-byte rewrite within the 8-byte header). This preserves the auth model. See ADR-079.

References

• docs/research/alknet-channels/phase-0-findings.md — Phase 0 research (vision, hub motivation, wire format, negotiation, internals, DPs, OQs)
• docs/research/alknet-channels/poc-summary.md — the de-risk POC (28 tests, three validated targets, REQ-CH-01..06 wire-level invariants surfaced; REQ-CH-07 is a cosmetic clippy item, not a wire invariant)
• docs/research/alknet-channels/poc-plan.md — the POC plan
• docs/research/stream-unification/findings.md — the research that surfaced the pure-channel-multiplexing resolution (ADR-093)
• /workspace/alknet-channels-poc/ — the POC codebase
• docs/research/alknet-tty/phase-0-findings.md — the TTY crate's chunk format (the seed of the channels generalization)
• docs/research/alknet-ssh/phase-0-findings.md — SSH's channel multiplexer (the prior art for N-channel multiplexing)
• docs/architecture/crates/hub/README.md — the hub crate (the primary consumer; the relay implementation's home)