integration_constraint_derivation

Enumerate every API, webhook, file, message, and external-service interaction point, then apply the integration constraint catalog to assign ICD identifiers. Expand retry and idempotency matrices where repeated execution is possible and group unresolved items by integration surface.

It is a Markdown table where each row is a requirement confirmation gate derived from integration structure and assigned an ICD- identifier. Each item links back to the integration surface it came from so nothing is assumed implicitly.

By default the result is written to work/constraint_derivation/ with a date-prefixed filename like YYYY-MM-DD_integration_constraint_derivation_<topic>.md. You can override this by explicitly supplying a different output path.

Stop if retry or duplicate-delivery behavior is being left implicit, or if failure handling is being assumed from generic platform norms rather than design evidence. Provider defaults must not be treated as satisfying business requirements.

It requires external integration structure such as API specs, webhook definitions, file exchange contracts, integration flow diagrams, and messaging designs. Inputs describing only nominal success cases are insufficient for derivation.