gormes-interface-designer

Design Go interfaces for Hermes by identifying callers, contracts, and existing patterns, then evaluating at least two interface shapes for compatibility. The approach maps trade-offs across tests and migration costs to produce a recommended boundary design.

Reducing coupling when swapping provider implementations in Go requires proposing multiple interface shapes to compare trade-offs. You evaluate each shape against Hermes compatibility, testability, and migration impact across relevant modules before selecting a design.

Yes, comparing multiple interface shapes for a Go gateway is the core process. You draft at least two distinct interface designs and map their compatibility with Hermes, Honcho, tests, and migration costs to determine which boundary works best.

Plan migration costs for new Go interface boundaries by mapping compatibility across relevant modules. The process evaluates at least two distinct interface shapes against existing tests and migration impact, producing a builder-ready row with a recommended design and implementation plan.

Yes, Hermes and Honcho compatibility is evaluated directly during interface design. Each proposed interface shape is mapped against both systems alongside testability and migration costs to ensure the boundary design supports providers, gateways, sessions, memory, and plugins.

Before drafting interface boundaries for a Go subsystem, identify existing callers, contracts, and current patterns. This context informs the evaluation of distinct interface shapes and ensures the proposed design aligns with Hermes and Honcho compatibility requirements.