====== 4.5 FX Information Structures before Serialisation ====== [[fxdemo:03-part:04-fx-demo-logical-profile-principles:start | Go To FX Demo Logical Profile Principles ]] The FX Demo Logical Profile defines FX logical information structures, with later parts selecting serialisation formats, schema languages, programming-language types, database structures, ontology languages, or wire representations. FX logical information structures include [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_transaction_candidate|FX Transaction Candidate]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_transaction_record|FX Transaction Record]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_validation_result|FX Validation Result]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_semantic_assertion|FX Semantic Assertion]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state|FX Contract State]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation|FX Cash-Flow Obligation]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|FX Policy Decision]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_release_package|FX Release Package]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_audit_record|FX Audit Record]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_provenance_record|FX Provenance Record]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_node_status|FX Node Status]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_control_command|FX Control Command]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_command_acknowledgement|FX Command Acknowledgement]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_replay_request|FX Replay Request]], and [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_replay_result|FX Replay Result]]. These logical information structures define FX meaning, structure, constraints, lineage, governance context, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] expectations. Implementation profiles later map them to selected representation mechanisms. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.