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.3 KiB
1.3 KiB
OQ-15: Call Protocol Client and Adapter Contract
- Origin: call-protocol.md, operation-registry.md, ADR-013
- Status: resolved
- Door type: One-way
- Priority: high
- Resolution:
CallClientopens QUIC connections and shares the dispatch loop withCallAdapter— both sides can send and receivecall.requestedonce connected. Connection direction (who opened the connection) is independent of call direction (who calls whom).from_calladapter discovers remote operations viaservices/list+services/schemaand registers them with forwarding handlers — same pattern asfrom_openapiandfrom_mcp.to_openapiandto_mcpproject local operations to external protocols. Adapter contract trait (OperationAdapter) produces(OperationSpec, Handler)pairs. Cross-node call tree: abort cascade (ADR-016) propagates across node boundaries throughfrom_callhandlers. Credentials for connections come from capabilities (ADR-014). Adapter-registered operations areInternalby default (ADR-015). See ADR-017. - Cross-references: ADR-005, ADR-013, ADR-014, ADR-015, ADR-016, ADR-017, call-protocol.md, operation-registry.md