alktunnels/tasks/architecture/oq-tn-14-tracker.md at 69498b79cc183f9ca01201426c193a47ad3a9439

Files

T

glm-5.3-flash 69498b79cc tasks: Phase 2 decomposition — 12-task dependency graph for v1

tasks/architecture/:
- oq-promotion-sync (planning): back-pointers from the phase-0 ledger
  + AGENTS.md to the promoted OQ tracker (the convergence checklist's
  final half)
- oq-tn-14-tracker: the Safe-Exit external-trigger tracker task for
  OQ-TN-14 (unix/stdio placement; [external-trigger, deferred-oq],
  risk trivial, level research per the two-halves rule)

tasks/tunnels/ (the implementation graph, 8 generations):
- crate-init: module skeleton per overview.md's module map
- params: TunnelParams + open-op spec (ADR-001 wire-stable surface)
- wire-codec: frame_datagram/DatagramReader + the 8 POC-pinned test
  families (ADR-003)
- producer-open-op: establisher (dial, plan flow R-01) + pump handler
  (pump_bidi inline R-02) + registration; POC-ported integration tests
- consumer-session: TunnelSession (open/adopt, data planes, teardown
  matrix — ADR-005); generalizes the reverse POC's ReverseTunnel
- producer-listen: the listen establisher + AcceptQueue contract
  (ADR-004 shape 2)
- local-socket-halves: the local feature (TCP/UDP/unix halves
  functions; truncation fail-loud per OQ-TN-13; unix ships per
  OQ-TN-14's lean-yes, stdio deferred)
- review-core-crates: review-injection point before the downstream
  tasks build on the high-risk producer/consumer shapes
- end-to-end-suite: 6 suites / >=20 tests consolidating both POC
  suites against the public API (the spec's executable form)
- review-impl: the phase-gate review (wire/API/conventions/docs sync;
  findings doc per the alkhttp/alkcall house pattern)

Graph verified with taskgraph: 12 tasks valid, no cycles, 8
generations; critical path = oq-promotion-sync -> crate-init ->
params -> wire-codec -> producer-open-op -> consumer-session ->
review-core-crates -> review-impl; risk concentrated in the two
session tasks (both POC-validated); parallel groups available at
generations 1 and 6

2026-09-07 19:07:20 +00:00

1.8 KiB

Raw Blame History

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

name

status

depends_on

scope

risk

impact

level

Description

External-trigger tracker for OQ-TN-14 (docs/architecture/open-questions.md — unix-socket and stdio substrate placement, currently open leaning unix-yes-v1). This task is NOT actionable implementation work; it tracks whether the unblocking condition has arrived. If the condition arrives, this task flips the OQ (and the implementation task tunnels/local-unix-halves below) from its deferred/open posture to actionable.

Unblocking conditions (any one):

A consumer needs unix-socket tunneling through alktunnels (a hub exposing a docker container's unix socket, or a local daemon bridge).
The tunnels/crate-init task lands and the local feature module needs its v1 surface finalized (the decision point baked into that task).

If neither arrives by the end of the v1 implementation phase, the OQ stays open and local ships TCP+UDP only (the lean posture ADR-004 endorses).

Work

Re-read OQ-TN-14 + docs/architecture/overview.md §Feature Gates when triaging; confirm whether the unix helper ships with local v1.

Verification

Tracked (this file existing and being reviewed at triage time IS the tracking mechanism — no code or doc change is expected until the condition arrives)

Out of scope

Implementing the unix/stdio helpers (see tunnels/local-unix-halves)

References

docs/architecture/open-questions.md OQ-TN-14
docs/sdd_process.md §Deferred OQs and the blocker-task half

Notes

Agent fills during implementation.

Summary

Agent fills this on completion.

1.8 KiB Raw Blame History