Integration Architecture: System Connectivity & API Contract Design

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Integration architecture defines how systems communicate, share data, and maintain consistency across the enterprise landscape. The skill produces integration landscape maps, contract registries, and sequence diagrams that enable reliable, maintainable system connectivity [EXPLICIT]

When to use

• Use for the integration architecture capability. [EXPLICIT]
• NOT for adjacent domains — route to the matching skill. [INFERENCE]

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Assumes system inventory is available or can be constructed from documentation · Does not implement integrations — produces architecture and design artifacts · API contract detai. [EXPLICIT]
• Casos borde: 1. Sistemas legacy con protocolos obsoletos (SOAP, FTP, ficheros planos) — El skill disena adaptadores/wrappers que encapsulan protocolos legacy detras de interfaces modernas (. [EXPLICIT]
• Supuestos: · Assumes system inventory is available or can be constructed from documentation · Does not implement integrations — produces architecture and design artifacts · API contract detai. [SUPUESTO]
• Trade-off: 1. Patron por conexion vs. patron unico — Se selecciona patron por conexion porque un enfoque unico (ej: todo async) genera sobre-ingenieria en integraciones simples y sub-inge. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.