====== Interface Contract ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

An interface contract identifies a version-controlled specification governing the exchange of [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:s:structured_information_artifact|structured information]] across an [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]].

An interface contract defines the structural, semantic, operational, and governance expectations that apply at an attachment point. These expectations support consistent exchange, validation, interpretation, traceability, and conformance evaluation.

An interface contract differs from an implementation interface. An implementation interface realizes an exchange mechanism through a selected technology. An interface contract defines the governed architectural expectations for the exchange independently of the selected implementation technology.

===== Definition =====

//version-controlled specification governing the exchange of structured information across an [[dido:99_annexes:annex-b-terms-and-definitions:a:attachment_point]]//

===== Source =====

Structured Information Processing [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]]

===== Note =====

An interface contract provides a governed basis for evaluating whether information exchange across an attachment point preserves required structure, meaning, authority, and lifecycle control.

===== Example =====

An interface contract specifies the required structure, semantic interpretation, validation rules, version identifier, and governance constraints for structured information exchanged between a [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane]] service and a downstream processing service.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>