glm-5.2
d0e3711b46
Built /workspace/alknet-tty-poc against portable_pty 0.9 to validate the local-PTY path (Step 2 of the build order) before Phase 1 specs. The POC surfaced two constraints that were not knowable from reading the portable_pty docs alone and that the architect must carry into the tty-backend.md and tty-local.md specs: - REQ-TTY-01: portable_pty is a blocking std::io API; the TtyBackend trait must accommodate blocking backends that bridge to async via std threads + tokio mpsc. exit_code resolves to a Future the adapter awaits (resolves the load-bearing half of OQ-TTY-01). - REQ-TTY-02: signal forwarding must target the process group (kill(-pgid, sig)), which depends on the child being a session leader (portable_pty's controlling_tty=true default). The POC also validated the control channel (stream_type 3), JSON control messages (DP-3), and exit-code-on-control-chunk (DP-5). OQ-TTY-01 is marked resolved with the control-as-Clone-trait-object sub-question left open with a POC-informed recommendation. The POC itself lives in the dev workspace, not the repo; this doc is the durable record.
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.