PRISM workflow / continuous optimization
State changes.
Decisions follow.
Re-evaluate the current book when prices, cash flows, or account rules change, using a defined decision window.
A price move changes weights and exposures. Re-evaluate the current portfolio against its mandate.
The review record
Event decision
- Trigger
- Defined state change
- Input
- Versioned snapshot
- Window
- Agreed deadline
- Output
- Proposal + checks
From computation to action
Fresh enough
to be useful.
Integration should make input versions, decision time, and acceptance checks explicit. The deadline is part of the agreed workflow.
The working model
A new event.
The current model.
Continuous optimization is an operating pattern: refreshed inputs, a defined computation window, and a reviewed result.
Choose the trigger
Define which market, account, or operational events require a new evaluation.
Update the input snapshot
Use a coherent set of holdings, prices, cash, and constraints.
Gate the result
Check feasibility and freshness before your system accepts the proposed decision.
Scope & evaluation
This illustration describes the workflow and does not calculate a financial result. Model features, data requirements, deployment, and acceptance criteria are agreed during scoping. The published benchmarks apply to their stated workloads; they do not establish live execution, realized savings, or performance for this specific account or book.
Work with Asymmetry