====== 8.3 IDL-Derived Artifacts ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:08-generated-artifacts:start | Return to Generated Artifacts ]]

[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]]-derived [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] include [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] data structures, type-support code, and language-specific bindings generated from IDL source files. These Artifacts allow Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] to publish, subscribe, serialise, deserialise, and validate [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] carried by DDS topics.

The team should treat IDL source files as the governed source definitions. Generated language bindings should trace back to those IDL files. Developers should not modify IDL-derived generated files directly unless the team has explicitly approved a temporary exception.

The generation workflow should identify:

  - The IDL source file.
  - The DDS generator or IDL compiler.
  - The generator version.
  - The target language.
  - The output directory.
  - The command or script used to generate the Artifact.
  - The expected regeneration behaviour.

The team should regenerate IDL-derived Artifacts whenever an IDL source definition changes. The team should also verify that generated outputs remain compatible with the relevant topic definitions, Node implementations, and tests.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>