Review untangle (three layers: local door / wire protocol / fabric):
- vanilla ssh -D binds its SOCKS5 proxy client-side (the local door —
alksocks' local-door shape) and opens plain direct-tcpip per
connection: the server needs nothing SOCKS-shaped (tunnel row +
route-1 bridge cover the leg; POC-3 correction 2 already said this)
- the family-native SOCKS5-in-channel server row served no consumer
of ours: family apps compose alksocks' local door locally over the
alkssh client's direct-tcpip DialFn — alkssh doesn't depend on
alksocks on this path
- amendments: ADR-003 §1a (feature removed), ADR-006 point 3 (SOCKS-
detect retired; session dispatch is parse-only; request-less
session channels decline), OQ-02 resolution updated with the
simplification, mapping-table.md rows annotated (research doc keeps
POC-3 stage B as the re-add feasibility record)
Phase 1 (architecture) — in progress. Phase 0 is closed: all three
POCs passed (121 checks; docs/research/poc-{1,2,3}-*.md) and the
research docs record their corrections. This directory is being
populated: ADR-001 (the alk/ssh ALPN pin) is drafted for review, the
OQ tracker is seeded from the POC findings, and the spec documents
below are being written. No implementation until specs reach
reviewed (per docs/sdd_process.md).
Tracked in open-questions.md — OQ-01 … OQ-13,
seeded from the phase 0 POC findings and research docs. Five resolved
(ADR-002/006 review + evidence), four deferred with named blockers.
Document Lifecycle
Status
Meaning
Transitions
draft
Under active development; may change significantly
→ reviewed when its open questions are resolved
reviewed
Final; implementation may begin; changes require review
→ stable when implementation is complete and verified
stable
Locked; changes require review and may warrant an ADR