User Input
$ARGUMENTS
Outline
- Read
docs/skills/catalog.md#add-bridge-or-adapter. - Read
docs/seams.mdand glossary entries for the relevant terms. - Identify both sides'
.Corecontracts, ownership boundaries, dependency direction, and allowed crossing point. - Keep the bridge/adapter outside the domains it connects unless an existing local pattern says otherwise.
- Plan failure semantics, tests, docs, and extension-point catalog updates.
- If this touches Workflows.Design/Runtime execution, read the runtime pre-spec handoff and avoid turning open architecture questions into code.
If the boundary is ambiguous, use elsa-critical-constitution-review or elsa-work-unit-planner before implementation. After the user approves the bridge/adapter plan, complete required tests, extension-point catalog updates, generated-map refreshes, and small docs follow-through as part of the approved work.