alknet/tasks/architecture/oq-46-runner-policy-use-case.md at df5d04af1d3166f6b5070db728fdd5e5dcdf5f8b

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.0 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-46 (Runner API Surface). This is not actionable work — it tracks whether a concrete runner-policy use case has emerged that forces the API surface (job management, log persistence, task graph integration). The runner mechanism (pipe mode) is already in alknet-tty (ADR-054); the runner policy is a downstream crate's job.

Trigger condition

A concrete deployment that needs runner policy — job management, log persistence, task graph integration — on top of the pipe-mode mechanism (TtyParams.terminal = None → std::process::Command with piped stdio → framed byte stream + exit code) that alknet-tty already provides.

What unblocking looks like

When a runner-policy use case arrives:

Mark this task status: completed.
Move OQ-46 from deferred(scope) to open.
Decide whether a runner-policy crate (e.g., an alknet-runner crate that builds on the pipe mode + the wire format to provide job management) is needed, and what its API surface would be. The mechanism is preserved regardless of the policy decision.

Why this is a task, not just an OQ field

The OQ's Blocked on: field in open-questions.md is the human-readable visibility surface. This task is the machine-readable half: it lives in the task graph so taskgraph tools can reason about it, and so downstream work that depends on runner policy can declare depends_on: [architecture/oq-46-runner-policy-use-case].

Verification

This task is "completed" when a concrete runner-policy use case is documented and OQ-46 has been moved to open.

2.0 KiB Raw Blame History