Expand the minimal OperationEnv trait from the operation-context task with concrete dispatch implementations per ADR-024: - LocalOperationEnv (Layer 0): wraps Arc<OperationRegistry>. invoke_with_policy runs the scoped_env reachability check (ADR-015/022), looks up the registration, then constructs a child OperationContext with internal: true, identity = parent.handler_identity.as_identity() (the ADR-015 authority switch), fresh metadata (HashMap::new() — ADR-014 security constraint, no parent metadata propagation), inherited deadline (parent.deadline, not a fresh 30s), inherited env (parent.env.clone() — Arc::clone per ADR-024), and the child's own composition_authority + scoped_env from its registration. contains() uses the default impl (returns true — curated registry contains everything it can dispatch). - CompositeOperationEnv (per-call, ADR-024): composes session (Layer 1), connection (Layer 2), and base (Layer 0) trait objects. invoke_with_policy runs the same reachability check, then probes overlays in order via contains() (the overlay-dispatch contract from review #003 C9), dispatching to the first overlay that contains the op. contains() aggregates all layers. The trait-object design is load-bearing: making OperationEnv concrete would close the session-overlay and connection-overlay patterns. Same integration- point pattern as IdentityProvider (ADR-004). Tests cover: allowed/disallowed reachability, internal-flag propagation, authority switch (child identity = parent handler_identity), fresh metadata, inherited deadline, composite session-overlay dispatch, composite fall-through to base, composite connection-overlay dispatch when session lacks op, and composite contains aggregation.
Alknet
Status: Pre-alpha — This project is undergoing a major architectural pivot to an ALPN-as-service model. The previous implementation has been archived and a greenfield rebuild is in progress.
A self-hostable networking toolkit built on QUIC+TLS with ALPN-based protocol dispatch. Each protocol handler (SSH, SFTP, Git, HTTP, DNS, messaging, call protocol) registers an ALPN string on a shared endpoint. The ALPN negotiation during the TLS/QUIC handshake routes connections to the correct handler before any application bytes are read.
Core Insight
A service IS an ALPN. One endpoint, one port, many protocols — dispatched by the TLS handshake, not by application-level peeking or separate listeners.
Crates
| Crate | Status | Description |
|---|---|---|
alknet-vault |
stable | Local key vault: BIP39/SLIP-0010/AES-GCM key derivation and encryption |
alknet-core |
planned | ProtocolHandler trait, ALPN router, auth/identity, config |
alknet-ssh |
planned | SSH handler (russh), SOCKS5, port forwarding |
alknet-call |
planned | JSON-RPC call protocol (EventEnvelope framing) |
alknet-fs |
planned | Content-addressed file storage (iroh-blobs backend) |
alknet-sftp |
planned | SFTP handler (russh-sftp protocol core) |
alknet-git |
planned | Git smart protocol handler (gix) |
alknet-http |
planned | HTTP handler (axum, REST API, MCP) |
alknet-dns |
planned | DNS handler (hickory-proto, pkarr) |
alknet-msg |
planned | E2E encrypted messaging, mixnet support |
alknet |
planned | CLI binary (assembles and registers handlers) |
Documentation
- ALPN-as-service architecture — pivot proposal
- Cleanup plan — greenfield transition plan
- SDD process — spec-driven development process
- Research references — iroh, russh, russh-sftp deep dives
Reference implementation (previous architecture) is preserved at /workspace/@alkdev/alknet-main/.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.