glm-5.2
5941280bca
Address the root cause of rework-causing hedging: the architect was
put in a logical bind where it couldn't express justified uncertainty
('the pieces exist but the shape isn't clear yet'). The only options
were 'decide now' (premature) or 'deferred(scope)' (false — the
information isn't missing, it's un-synthesized). The agent picked
deferred(scope) with a circular blocking condition (OQ-64 blocked on
OQ-55, OQ-55 needs OQ-64) because there was no honest way to say 'I
can see the pieces but I can't see the shape.'
Changes to the architect role spec:
- Add deferred(unclear) state: the pieces exist but the composition
isn't clear; resolution requires investigation (work through
examples, POC), not waiting. Has an investigation target and an
impacts field.
- Add 'Impacts' field to the OQ format: what does this block
downstream? Be specific ('blocks the first hub deployment because
the hub dials workers' not 'blocks the hub crate'). The triage
signal that makes deferral urgency visible — the field that would
have made the AlknetClient circular hedge visible.
- Add circular-reasoning guard to self-review: 'check that your
blocking condition isn't a prerequisite of the thing you're
deferring.'
- Trim anti-patterns #9-#11 (hedging synonyms catalog, ~40 lines):
detection belongs in the reviewer, not the architect's self-review.
The architect is too close to its own reasoning to see its own
circular hedges.
- Trim door-types section (30→10 lines): keep the one-paragraph
summary, cut the elaboration.
Changes to the architecture-reviewer role spec:
- Add Decision Quality (F) category: false-deferral check
distinguishing three cases — (1) hedging on a resolved decision, (2)
false deferral / circular hedge (the blocking condition is a
prerequisite of the thing being deferred), (3) legitimate deferral.
- Add Impacts Field Coverage (G) category: check that unresolved OQs
have specific impacts fields.
- Note: the Decision Quality category is often the highest-value
check on poorly-defined projects — the architect cannot self-review
it (circular reasoning is invisible from inside the circle).
Retrofit existing OQs:
- Add Impacts field to all 16 unresolved OQs (10 deferred, 6 open).
- Update OQ-63 (TlsError shape) to reflect ADR-087's client-side
addition — the error type now covers both server and client
variants.
- Move OQ-65 (WebSocket carrying channels) to alknet-http theme
(done in prior commit; this commit adds its impacts field).
- Verified: no circular reasoning found in existing deferrals. The
AlknetClient hedge (OQ-64) was the circular one; it's already
resolved by ADR-087.
2.6 KiB
OQ-41: Stream Operators Library
-
Origin: ADR-049, operation-registry.md §"OperationEnv"
-
Status: deferred(scope)
-
Door type: Two-way (additive utility library; no protocol or API-surface change)
-
Priority: low
-
Impacts: None — handlers produce streams today without it. Would reduce boilerplate in stream-transforming handlers when added.
-
Blocked on: A handler that needs stream operators and finds the existing combinators (
Box::pin(stream::iter(...)),async_stream::stream!,futures::stream) insufficient. The operators library is a convenience, not a prerequisite for any handler. -
Resolution: ADR-049 establishes that stream composition (filter, map, combine, window, dedupe) is a handler-level concern, not a protocol composition concern.
OperationEnv::invoke()is request/response-only; stream manipulation happens at the handler level with stream operators on theBoxStream<ResponseEnvelope>the handler itself produces. The@alkdev/pubsuboperators.tsis the prior art: 13 operators (filter,map,take,batch,dedupe,window,chain,join,reduce,groupBy,flat,pipe,toArray) that operate onAsyncIterable<T>, forked from graphql-yoga's subscription implementation.The Rust analogue — a stream-operators utility crate or module providing the same set of operators on
BoxStream<T>/impl Stream<Item = T>— is a feature extension. Handlers can produce streams today without it (Box::pin(stream::iter(...)),async_stream::stream!,futures::streamcombinators all work); the operators library is a convenience that reduces boilerplate for handlers that transform streams (filter, batch, dedupe, window). No ADR is needed for the library itself — it's internal utility code that doesn't cross crate boundaries as a contract. An ADR would be warranted only if the operators become part of a public API surface (e.g., a handler-registration DSL that references operator names).This OQ exists so the operators library is tracked and findable, not left as inline hedging in the spec docs. It is not a deferral of a decision — the architectural decision (stream composition is handler-level, not protocol-level) is made in ADR-049. This tracks the implementation of the utility library, which is scheduling work, not architecture work.
-
Cross-references: ADR-049, operation-registry.md §"OperationEnv",
/workspace/@alkdev/pubsub/src/operators.ts(TS prior art)