---
id: architecture/oq-tn-14-tracker
name: "[external-trigger, deferred-oq] OQ-TN-14 unix/stdio placement tracker"
status: pending
depends_on: []
scope: single
risk: trivial
impact: isolated
level: research
tags: [architecture, deferred-oq, external-trigger, unix, stdio]
---

## 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):

1. A consumer needs unix-socket tunneling through alktunnels (a hub exposing
   a docker container's unix socket, or a local daemon bridge).
2. 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.