alknet/tasks/architecture/oq-09-wasm-server-use-case.md at c6eef730e4d0f81fbf0d09472ccbb0cd2ddd40e3

alkdev/alknet

0 Fork 0

Files

T

glm-5.2 df5d04af1d tasks(arch): adopt taskgraph for architecture work — blocker tasks for deferred OQs, level mapping, status fixes

Establishes the tasks/architecture/ blocker-task half of the Safe Exit
protocol. Each deferred OQ now has an external-trigger tracker task
representing its unblocking condition, and the OQ's Blocked on field names
the tracker task ID — closing the gap where the deferral field existed but
the task-graph half was unenforced.

Changes:
- Add 6 external-trigger tracker tasks for the deferred OQs (OQ-09, 10, 32,
  41, 44, 46) under tasks/architecture/, tagged [external-trigger, deferred-oq]
- Add structured Blocked on field to OQ-09 and OQ-10 (previously used legacy
  'deferred' status with the reason in the Resolution prose); index now
  surfaces all 6 deferred OQs with concrete conditions, no placeholders
- Document the architecture-task level mapping (level: implementation for
  ADRs/specs, decomposition for spec-to-ADR breakdown, planning for backlog
  seeding, research/review direct fits) and the deferred-OQ blocker-task
  pattern in docs/sdd_process.md
- Mark architecture/safe-exit-blocker-task-mechanism and
  architecture/oq-09-10-blocking-conditions completed (implemented by this pass)
- Fix 4 pre-existing ADR-050 implementation tasks: status: done → completed
  (taskgraph enum is 'completed', not 'done') — taskgraph validate now passes
  for all 100 tasks

2026-07-06 16:34:01 +00:00

2.3 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-09 (WASM Target Boundaries). This is not actionable work — it tracks whether a concrete server-side WASM use case has emerged, or whether the project confirms that WASM compatibility remains a client-side design constraint only (a browser can implement BiStream over WebTransport streams; the server-side dispatch door is a known, accepted closure per ADR-007/009).

Trigger condition

Either:

A concrete server-side WASM use case arrives (a deployment that wants to run an alknet server peer compiled to WASM, which would require a Connection trait and a runtime-abstracted accept loop — currently not planned), or
A deliberate confirmation that WASM stays a client-side design constraint, at which point OQ-09 transitions from deferred to resolved with the accepted-closure framing already in its Resolution text.

The second path is the more likely one — the OQ exists mainly so the server-side WASM door closure is documented rather than implicit.

What unblocking looks like

When a decision is made (either direction):

Mark this task status: completed.
Move OQ-09 from deferred to either resolved (client-side-only confirmed) or open (server-side use case arrives, requiring a Connection trait + WASM runtime abstraction ADR).

Why this is a task, not just an OQ field

OQ-09 predates the formalized deferred(scope) + blocking-condition pattern and lacked a structured Blocked on: field (it used the legacy deferred status with the deferral reason in the Resolution prose). This task formalizes the blocking condition and gives the OQ a machine-readable presence in the task graph.

Verification

This task is "completed" when either a server-side WASM use case arrives (move OQ-09 to open) or the client-side-only constraint is confirmed (move OQ-09 to resolved).

2.3 KiB Raw Blame History