7.0.0-dev.117

Event Model - Reset Instruction and Create_Reset Refactoring

Background

Currently, the model relies on an inconsistent downstream design where the ResetInstruction serves as a bare trigger, with the actual observation retrieval and fixing rate calculations deferred to the final state modification function (Create_Reset). This deviates from more robust workflow patterns established in other parts of the lifecycle model (such as the Transfer logic), where specific values (Quantity, Asset, Settlement Date) are fully computed and evaluated at the Instruction generation level before a WorkflowStep is proposed or accepted. This PR shifts the reset observation and calculation processes upstream. Specific reset values and audit points are now evaluated inside CalculateReset, producing a fully populated ResetInstruction. The downstream execution function (Create_Reset) has been simplified to focus strictly on updating the TradeState history with the values defined in the instruction.

What is being released?

Functional Refactoring: Function - Create_Reset: Has been simplified to focus strictly on updating the TradeState history with the values defined in the instruction Function - CalculateReset: Refactored to act as the primary orchestration entry point for evaluating data resolution Type - ResetInstruction: Updated to carry the explicit outcomes of the upstream calculation. It now handles the state transmission container (Reset (1..1)) with native observations, final calculated rates, and averaging methodology Type - CalculateResetInstruction: Hardened to enforce clean cross-referencing to the target payout, explicit resetDate, and optional fallback timeline audits (rateRecordDate)

Review Directions

Changes can be reviewed in PR: #4752

Note

This comment was generated via Rosetta.