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.
1.9 KiB
1.9 KiB
OQ-48: Network and Volume Operation Surface
- Origin: crates/docker/docker-operations.md §"Operation Surface (v1 scope)" (out-of-scope list).
- Status: deferred(scope)
- Door type: Two-way
- Priority: low
- Impacts: None — dev containers use the default bridge network; hosted services declare networks/volumes in docker compose. Would impact a fleet coordinator or dev-container orchestrator if one is built.
- Blocked on: a concrete use case for network or volume management
over the call protocol. The two container use cases (disposable dev
containers, hosted services) don't currently require
network/volume CRUD over the call protocol — dev containers use
the default bridge network; hosted services are configured via
docker composewith networks/volumes declared in the compose file. - Resolution: Not yet decidable. bollard has the API surface
(
network.rs:create_network,remove_network,inspect_network,list_networks,connect_network,disconnect_network;volume.rs:list_volumes,create_volume,inspect_volume,remove_volume,prune_volumes) — the mapping is mechanical, the same shape as the container lifecycle ops (Query/Mutation, singlecall.responded). The deferral is scope, not feasibility: v1 is containers + images; networks and volumes are added when a use case forces them (e.g., a coordinator that needs to create isolated networks for dev containers, or a fleet layer that manages volumes across hosts). Adding them is additive (new operations in the registry) and does not break the existing surface. - Cross-references:
ADR-058 (the shared
alknet/callregistration model new ops would follow), crates/docker/docker-operations.md