alksocks/tasks/architecture/oq-sk2-06-wasm-adapter-story.md at 53739b20cbde2d0d6672124e028f8f4402346cfb

0 Fork 0

Files

T

glm-5.3-flash 9587670138 docs: Phase 1 architecture — specs, ADRs 001-012, open-questions tracker

- docs/architecture/: README index, overview, wire, producer,
  consumer, vendor, bast specs + open-questions.md (the OQ-SK-01..09
  ledger promoted; new questions as OQ-SK2-06..)
- ADRs 001-012: ALPN/op/params, protocol base, the handle swap,
  the dial-callback shape, auth split by the door, access control
  (open gate + BIND command gate), BIND in base, provider defaults,
  feature gates, channel capacity, the inline vendor, target policy
- deferred OQs (SK2-06, SK2-07) with tracker tasks in
  tasks/architecture/ per the sdd_process deferred-OQ protocol
- review pass applied: frame-length joint bound (65766 corner),
  accept_no_auth vs skip_auth corrected against fast-socks5 source,
  composed-feature wasm posture, cross-reference fixes

Verified: cross-references (all ADR/OQ refs resolve), doc sizes
under split threshold, Phase 0 fidelity spot-checks

2026-09-20 18:41:56 +00:00

1.4 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

architecture/oq-sk2-06-wasm-adapter-story

Track — OQ-SK2-06 unblock condition (sandboxed-wasm-consumer adapter)

pending

single

trivial

component

research

Description

External-trigger tracker for OQ-SK2-06 (docs/architecture/ open-questions.md): the sandboxed-wasm-consumer adapter story. This task is NOT actionable work — it tracks whether the external unblocking condition has arrived. Tagged [external-trigger, deferred-oq] per docs/sdd_process.md §Deferred OQs.

Unblocking condition: a concrete sandboxed-adapter use case exists — a TS/Python (or other) adapter embedding the alksocks consumer session in a wasm runtime.

Work

When the condition arrives:

Mark this task completed (the condition arrived).
Transition OQ-SK2-06 from deferred(scope) to open (or directly to resolved if no architecture decision remains).
Decide: how much wasm surface to exercise in the default crate (bindings ergonomics, which session types to expose, whether any surface is missing).

Verification

N/A (tracking task — trivial risk, no code).

Out of scope

Any wasm-binding implementation; any protocol change (the wasm-clean default-crate invariant, ADR-009, holds regardless).

Notes

Agent fills this during implementation.

Summary

Agent fills this on completion.

1.4 KiB Raw Blame History