SG institutional OTC workspace

Run an SG institutional OTC workspace where classification, custody readiness, RFQ commit, settlement affirmation, booking, and reconciled evidence close stay on one operating record.

Overview

Institutional OTC workspace for Singapore. StableNexus orchestrates classification, custody scope, approval flow, commit handoff, settlement confirmation, booking visibility, and evidence close while counterparties, custodians, and settlement rails stay explicit.

StableNexus coordinates orchestration, workflow, approvals, normalization, callback recovery, and evidence packaging. Dealing, custody, settlement, and official posting remain partner-owned.

Operating map

Actor-lane operating map showing who acts at each stage of the workspace.

Route coverage

Compressed route chips used by cards and the public case surface — derived from the 6 canonical chapters below, not a replacement for them.

  • Classification and custody scope
  • Quote approval and trade commit
  • Settlement affirmation and booking
  • Exception-led close and evidence

Canonical chapters

  1. Counterparty scope and SG classification
  2. Custody readiness
  3. Quote formation and execution approval
  4. Execution commit and settlement instruction
  5. Settlement affirmation and booking
  6. Reconciliation sign-off and evidence close

Lifecycle stages

What becomes true at each chapter and which docs-derived surfaces that chapter feeds.

ChapterWhat becomes trueDerived surfaces
Counterparty scope and SG classificationSG classification lane fixed, counterparty scope approved.counterparty_readiness_state
Custody readinessCustody scope confirmed, balance posture bound.custody_readiness_state
Quote formation and execution approvalBilateral quotes collected, selected quote approved.quote_state
Execution commit and settlement instructionTrade committed, settlement instruction published.execution_commit_state, settlement_affirmation_state
Settlement affirmation and bookingSettlement affirmed, booking posted.settlement_affirmation_state, booking_state
Reconciliation sign-off and evidence closeReconciliation signed off, evidence closed and exported.reconciliation_signoff_state, evidence_close_state

Control overlays

OverlayOverlay IDContract source
Callback / status update posturestatus_update_posturePartner Control Plane
Signed acknowledgmentsigned_acknowledgment_posturePartner Control Plane
Poll or inquiry fallbackfallback_posturePartner Control Plane
Idempotent replay / recoveryreplay_recovery_posturePartner Control Plane
Operator approval / sign-off gatesoperator_gate_posturePartner Control Plane

Lifecycle state map

Canonical lifecycle states with mainline progression and exception lanes.

Evidence and exports

Primary artifact keys per chapter and who acknowledges them on the run record.

ChapterPrimary artifactsWho acknowledges
Counterparty scope and SG classificationclassification_snapshot, counterparty_scope_recordCounterparty / OTC desk
Custody readinesscustody_scope_receipt, custody_balance_confirmationCustodian
Quote formation and execution approvalrfq_quote_record, quote_selection_recordInstitution team
Execution commit and settlement instructiontrade_commit_record, settlement_instruction_packCounterparty / OTC desk, Settlement / booking partner
Settlement affirmation and bookingsettlement_affirmation_receipt, allocation_posting_record, booking_reference_packCustodian, Settlement / booking partner
Reconciliation sign-off and evidence closereconciliation_match_report, exception_resolution_log, reconciliation_signoff_record, workspace_packet, closeout_evidence, archive_manifestInstitution team

Evidence derivation

Artifact keys derive docs-surface state; runtime truth stays run-centered.

Setup reference

FieldExplanationRelated terms
Trade notionalSets the notional carried through affirmation, booking, settlement, and reconciliation. Determines the values shown across the workflow records.
Execution pathSupports more than one execution path. Controls how the trade is sourced before settlement.
Traded productFixed for this case. Scoped to one traded product or pair.
Trade directionFixed for this case. Determines how settlement and booking are read.
Custody modelFixed for this case. Scoped to one custody model. Determines how custody confirmation is handled.
Settlement patternFixed for this case. Scoped to one settlement pattern. Determines how affirmation and settlement are recorded.
Counterparty classFixed for this case. Scoped to one counterparty class. Determines which counterparty context appears in the workflow.
Operating windowOperational timing for classification, custody confirmation, quote validity, settlement affirmation, and close. Drives cutoff, quote-expiry, and reconciliation sign-off timing across the workspace.Operating window

Support terms

OTC
Over-the-counter trading executed directly with a dealer or broker.
DvP
Delivery versus payment: the asset and cash legs settle together.
Execution adapter
A connected external venue, broker, or settlement function used in the workflow.
Operating window
The timing rule that determines when movement can proceed.

Boundary

This docs page owns the canonical readable structure. The public case page and projector consume the shared schema. Runtime owns emitted truth. /ops remains separate.