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.2 KiB
OQ-28: from_call Namespace Collision Behavior
-
Origin: client-and-adapters.md, ADR-017 §3
-
Status: resolved (2026-06-27)
-
Door type: Two-way
-
Priority: low
-
Resolution: ADR-017 §3's
FromCallConfignamespace prefix is optional, default no prefix, same-peer collision = error. A node importing from a peer that exposes two ops with the same name should fail loudly rather than silently overwrite. This matches the default-deny, explicit-allow posture (ADR-015). The alternative (last-wins) would silently mask one op behind another, which is the kind of surprise the default-deny posture exists to avoid.Cross-peer collision dissolved by ADR-029. Under the peer-keyed overlay model, same name on different peers is fine — they live in separate peer sub-overlays, no collision, no prefix needed.
FromCallConfig::namespace_prefixis optional local-naming sugar for when the importing node wants to expose a peer's ops under a different name locally — a local-naming concern, not a disambiguation concern. See ADR-029 §5. -
Cross-references: ADR-015, ADR-017,
ADR-028(superseded), ADR-029, client-and-adapters.md