Dynamic Valuation Control (VCA) Engine · P&P

This Policy & Procedure document is generated live from the governed definition of the application. Its authority derives from the platform record — the versioned DAG, the governance sign-offs and the append-only audit log — not from separate manual authoring.

Document ID

PP-VCA-IPV-V1

Application

Dynamic Valuation Control (VCA) Engine · vca-ipv

Version

v1

Status

Tech standards review

Category

Middle office

Owner

Sophie Laurent — Desk Head (Cross-Asset Solutions desk)

Classification

Internal

Effective date

—

Review cycle

Annual

Last submitted

25 May 2026

Generated

25 Oct 2026 · 22:34 UTC

Purpose

Compares trader marks to Bloomberg consensus and routes large variances to product control for an IPV adjustment.

It sits in the Middle office domain of the Markets OS App Studio and is delivered as a visually-built Directed Acyclic Graph of typed nodes, executed in a deterministic topological order under enforced governance.

In scope

• The end-to-end automated workflow defined by the current app version and its nodes.
• The controls embedded in that workflow (human approvals, risk monitors, validations).
• The systems and datasets the workflow reads through the safe MCP broker.
• The governance gates every version must clear before it can run in production.

Out of scope

• This is a decision-support / automation workflow — it is not investment advice, and it does not itself constitute an order to trade.
• In this proof-of-concept the external connectors (Murex, TLM, Bloomberg, Progmat, SAP, Oracle ERP) are simulated behind the broker; no live booking or settlement occurs.
• Bespoke desk mandates, limits and suitability checks remain governed by their own policies.

The parties below carry the app through its lifecycle. HITL approver roles are read directly from the app's HUMAN_IN_LOOP node configuration, so this table reflects the controls actually wired into the workflow.

RACI matrix

RACI — Responsible does the work · Accountable owns the outcome · Consulted gives input · Informed is kept in the loop.

The procedure below is the exact sequence the execution engine runs, listed in the topological order the platform schedules (Kahn's algorithm — every step appears after the steps it depends on). Each step names the action, the system or dataset it touches, its inputs and outputs, and any control that fires at that point.

Controls prefixed C- are wired into this app's DAG; controls prefixed P- are platform controls that apply to every governed app. Evidence for each is recorded in the named table.

The operational metrics below are computed live from the execution ledger. The workspace for this app presents the same figures as live KPI tiles and charts.

Open the live workspace KPIs →

Every external system this workflow interfaces is reached through the MCP broker — the only safe path to a connector. The broker allow-lists the operation, denies any write on a read-only connector, and audits the call. No node touches a live system directly.

Regulatory validations

This version references no explicit VALIDATION ruleset. Regulatory obligations remain governed by the desk's standing controls and the platform governance gates.

Governance status

Current version status

Tech standards review

Release control

Gated (DRAFT → PROD) with cryptographic sign-offs

Audit trail

Append-only mos_audit_log

Model risk

Any pricing, risk or NLP node embeds a model. In this proof-of-concept those computations are deterministic simulations; in production they fall under the bank's model-risk management framework (independent validation, periodic review and performance monitoring) before use.

Every version this app has carried, newest first. A new version is always a fresh DRAFT until it clears governance.

Node types used in this app

Connectors

Platform terms