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.
1.1 KiB
1.1 KiB
OQ-30: PeerRef::Any Routing Policy
- Origin: ADR-029 §2, client-and-adapters.md,
docs/research/alknet-call-peer-routing/findings.md§3.2 - Status: resolved (2026-06-27)
- Door type: Two-way
- Priority: low
- Resolution:
PeerRef::Anyuses insertion-order first-match — deterministic but order-dependent (worker A connects before worker B →Anyroutes to A until A disconnects). This is the simplest routing policy and is correct for the immediate use case (the head picks the first worker that serves the op). A richerRoutingPolicy(round-robin, least-loaded, affinity) is a feature extension — thePeerRefenum is designed to compose with aRoute { selector, policy }struct without breaking theinvoke_peersignature. Adding a routing policy is non-breaking; it's a feature addition when a fan-out use case needs it, not an unmade architectural decision. - Cross-references: ADR-029, client-and-adapters.md