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.
33 lines
1.7 KiB
Markdown
33 lines
1.7 KiB
Markdown
# OQ-49: Image Build (buildkit) Scope
|
|
|
|
- **Origin**:
|
|
[crates/docker/docker-operations.md](crates/docker/docker-operations.md)
|
|
§"Out of scope for v1"; [ADR-059](decisions/059-bollard-021-dependency-and-features.md)
|
|
§3 (no `buildkit` feature).
|
|
- **Status**: deferred(scope)
|
|
- **Door type**: Two-way
|
|
- **Priority**: low
|
|
- **Impacts**: None — current use cases pull pre-built images. Would
|
|
impact any use case that builds images via alknet rather than
|
|
operator-side `docker compose build`.
|
|
- **Blocked on**: a concrete use case for building images over the
|
|
call protocol. The two container use cases (disposable dev
|
|
containers, hosted services) pull pre-built images (`docker/image/pull`)
|
|
rather than building them. The reverse-proxy and other hosted
|
|
services build via `docker compose build` (operator-side), not via
|
|
alknet.
|
|
- **Resolution**: Not yet decidable. bollard's `build_image` (image.rs:655)
|
|
and the `buildkit` feature (which pulls tonic +
|
|
bollard-buildkit-proto) are available but deferred. Build is a large
|
|
feature (build context upload, layer caching, multi-stage, buildkit
|
|
progress streaming) and is not needed for the current scope. When a
|
|
use case forces it, the operation is a `Subscription` (progress
|
|
events → `call.responded`, build complete → `call.completed`) and
|
|
the `buildkit` feature is enabled in `Cargo.toml` (two-way-door
|
|
feature addition, per ADR-059). The v1 surface has `image/pull` +
|
|
`image/list` + `image/inspect`; `image/build` is added when needed.
|
|
- **Cross-references**:
|
|
[ADR-059](decisions/059-bollard-021-dependency-and-features.md)
|
|
(feature set decision — `buildkit` not enabled),
|
|
[crates/docker/overview.md](crates/docker/overview.md) §"bollard
|
|
version and features" |