Markets
Instrument coverage on shared lifecycle stages
Equities through tokenised product write to the same book of record. Confirm, settle, mark, and evidence do not fork into a separate programme per asset class.
How coverage works
Stages stay fixed. Markets extend the book.
Book → confirm → settle → mark → evidence is the same spine whether the instrument is a cash equity, a bond, an FX fill, a listed future, or a tokenised note. Configuration and static data carry the market; they do not invent another platform.
| Market | What lands on the book | What stays shared |
|---|---|---|
| Equities | Orders, fills, allocationsCash equity capture and desk blotter views | Confirm, settlement status, marks, audit |
| Fixed income | Bond tickets and economicsGovernment and corporate product | Same confirm and fail evidence path |
| Rates & credit | Rates and credit bookingsCross-asset positions with cash markets | Finance and risk read one truth |
| FX | FX capture and statusStreet match against the same trade_id | Ops and control on the lifecycle log |
| Listed derivatives | Listed product on shared stagesInventory and marks with the desk book | Evidence without a second archive |
| Tokenised | Post-issuance lifecycleRepo, bonds, equity after the token exists | Same stages as conventional markets |
Cash markets
Equities and fixed income
Cash equity operating day
- Order, fill, and allocation on the event log
- Desk blotter as a projection of the book
- Counterparty confirm and break against the same trade_id
- Settlement status and fails attached to the lifecycle
- Marks and control evidence without a franchise silo
Bonds on the same spine
- Government and corporate product on shared stages
- Economics and settlement status with the trade
- Finance reads booked positions — not a rebuilt extract
- Cross-asset with equities and rates in one truth
- Audit trail travels with every amend and repair
Rates · credit · FX
Markets that usually force another programme
Rates, credit, and FX are where firms most often stand up a second OMS, a second confirm path, and a second control archive. Sylgate keeps them on the lifecycle stages already running for cash product.
Rates product
Bookings and marks on the shared event log. Risk and finance see the same positions Trade worked during the day.
Credit product
Credit sits with cash and rates for confirm, settlement status, and evidence — not a franchise tower of its own.
FX capture
FX fills join the same confirm and settlement status path. Breaks and repairs use four-eyes on the lifecycle log.
Listed derivatives
Listed product without a side book
Listed derivatives write inventory, fills, and marks into the same book of record as cash and OTC-style product. Settlement status and evidence stay attached to the trade_id.
Market-making modules that quote listed names still land fills on this lifecycle — liquidity does not invent a second operating archive.
What stays shared
- Book and allocate on the event log
- Confirm and break against the same record
- Marks to P&L for finance
- Control gates and audit projections
Digital / tokenised
Post-issuance on the institutional lifecycle
Issuance rails create the token. Sylgate is the post-issuance control plane — booking through evidence — so tokenised repo, bonds, and equity do not need a second franchise stack.
Same stages as cash
Tokenised product runs book → confirm → settle → mark → evidence. Digital is a market on the spine, not a parallel company operating model.
Finance, reporting, ops
Trade reporting, treasury-style views, settlement status, and control evidence attach to the same trade_id conventional markets already use.
What still needs the firm
Live venue connectivity, counsel, and hosted production environments remain firm responsibilities. The book and portal are ready to carry the lifecycle depth.
Next