P3-REQ-17-8-002

The FX Transaction and Contract Lifecycle Model SHALL distinguish candidate transaction information, validated transaction information, semantically interpreted transaction information, contract state, computed cash-flow obligations, policy release state, and audit/provenance records.

Part 3, Section 17.8: FX Lifecycle Requirements.

The lifecycle model must distinguish the major categories of information that arise during logical FX processing because each represents a different stage of processing, governance responsibility, and architectural meaning. Separating candidate transactions, validated transactions, semantic interpretations, contract state, computed obligations, policy release state, and audit or provenance information preserves architectural clarity while supporting traceability, governance, interoperability, and evidence generation.

Maintaining these distinctions independently of implementation technologies allows multiple Implementation Profiles to realize equivalent lifecycle behaviour without changing the logical architecture.

This requirement applies to the FX Transaction and Contract Lifecycle Model defined by the FX Demo Logical Profile.

It applies specifically to:

  • lifecycle information classification;
  • logical information modeling;
  • architectural governance;
  • lifecycle reviews; and
  • derived Implementation Profiles.

Verification SHALL confirm that the lifecycle model distinguishes each required category of lifecycle information.

Verification activities should include review checks confirming that:

  • candidate transaction information is distinguished;
  • validated transaction information is distinguished;
  • semantic interpretation information is distinguished;
  • contract state is distinguished;
  • computed cash-flow obligations are distinguished;
  • policy release state is distinguished; and
  • audit and provenance records are distinguished.

This requirement establishes the logical lifecycle information model used throughout the FX Demo Logical Profile.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-03/p3-req-17-8-002.txt
  • Last modified: 2026/07/21 15:56
  • by owen