glm-5.2
1baa619ce9
The monolithic open-questions.md (1310 lines, 47 OQs) was large enough to be unmanageable, with high size variance (OQ-42 at 220 lines next to OQ-06 at 8). Decomposed into one file per OQ under docs/architecture/questions/ (NNN-slug.md, mirroring the ADR convention), with open-questions.md retained as the index: theme-grouped tables plus a cross-theme Deferred/Blocked section that surfaces the 6 deferred OQs with their Blocked-on conditions inline (the safe-exit visibility surface). Per-OQ content moved verbatim; all 62 inbound links stay valid (none used anchors). README's curated OQ summary dropped (now redundant with the index tables). Also seeds tasks/architecture/ with this task plus two follow-ups found during the decompose: OQ-09/10 missing structured Blocked-on fields, and the tasks/architecture/ blocker-task half of the Safe Exit protocol being unenforced.
73 lines
3.2 KiB
Markdown
73 lines
3.2 KiB
Markdown
---
|
|
id: architecture/safe-exit-blocker-task-mechanism
|
|
name: Establish the tasks/architecture/ blocker-task half of the Safe Exit protocol
|
|
status: pending
|
|
depends_on: []
|
|
scope: moderate
|
|
risk: low
|
|
impact: project
|
|
level: architecture
|
|
---
|
|
|
|
## Description
|
|
|
|
During the open-questions.md decompose (July 2026), I found that the role
|
|
spec's Safe Exit protocol says "create a blocker task in `tasks/architecture/`
|
|
that names the dependency" when deferring a decision — but that directory has
|
|
never existed. The four `deferred(scope)` OQs in the current file (OQ-32,
|
|
OQ-41, OQ-44, OQ-46) carry a `Blocked on:` field but no corresponding blocker
|
|
task files anywhere in the repo.
|
|
|
|
So the deferral *field* exists (the visibility half), but the *task* half of the
|
|
safe-exit mechanism is unenforced/unused. This task is about establishing the
|
|
convention so future deferrals create the corresponding blocker task, and
|
|
backfilling the existing deferred OQs.
|
|
|
|
## Context
|
|
|
|
The project's broader pattern (per the July 2026 discussion): questions often
|
|
lead to decisions which lead to tasks — a graph not unlike how implementation
|
|
tasks are modeled as a DAG. The `tasks/architecture/` directory is where the
|
|
"this decision is blocked on X" blocker tasks live, so that:
|
|
|
|
1. A deferred OQ has a visible `Blocked on:` condition in the index (the
|
|
open-questions.md "Deferred / Blocked" section — already in place after the
|
|
decompose).
|
|
2. A deferred OQ has a corresponding blocker task that names the dependency and
|
|
can itself be depended on by downstream work that needs the decision
|
|
resolved.
|
|
|
|
The two halves serve different audiences: the index section is for the
|
|
architect ("what's currently parked and why"), the blocker task is for the
|
|
implementation agent / planner ("what unblocks this, and what's waiting on
|
|
it").
|
|
|
|
## Work
|
|
|
|
1. Confirm the task file format (YAML frontmatter: `id`, `name`, `status`,
|
|
`depends_on`, `scope`, `risk`, `impact`, `level`) is the right shape for
|
|
architecture blocker tasks, or adjust if the architecture workflow needs
|
|
different fields (e.g., a `blocks:` field pointing back at the OQ).
|
|
2. Backfill blocker tasks for the four existing `deferred(scope)` OQs:
|
|
- OQ-32 (Multi-Hop Federation) — blocked on a concrete multi-hop use case
|
|
- OQ-41 (Stream Operators Library) — blocked on a handler needing operators
|
|
beyond existing combinators
|
|
- OQ-44 (Terminal Modes) — blocked on a concrete mode-control use case
|
|
- OQ-46 (Runner API Surface) — blocked on a concrete runner-policy use case
|
|
3. Document the convention (one line in `docs/sdd_process.md` or the architect
|
|
role spec) so future deferrals create the blocker task as part of the Safe
|
|
Exit step.
|
|
|
|
## Out of scope
|
|
|
|
- The DB-backed backend (no manual links, vector/text search) — that's a future
|
|
evolution that this file-based pattern informs, not something to build now.
|
|
- Re-resolving any of the deferred OQs — this is about the tracking mechanism,
|
|
not the decisions themselves.
|
|
|
|
## Verification
|
|
|
|
- `tasks/architecture/` contains one blocker task per `deferred(scope)` OQ
|
|
- Each blocker task's `depends_on` names the concrete unblocking condition (or
|
|
a task that represents it)
|
|
- `docs/sdd_process.md` (or equivalent) references the convention |