24/7 trading makes shift handoffs a KYA control
The CFTC has announced a public roundtable on the viability of derivatives markets moving to 24/7 trading, including overnight activity, infrastructure, staffing, and operational readiness. For autonomous trading agents, the KYA question is not only whether software may trade, but who supervises it when people, venues, liquidity conditions, and control teams change across the day.
Daily signal: Always-on market access should require a continuous chain of accountable supervision. Every handoff must preserve the agent identity, active mandate, positions, limits, venue state, unresolved alerts, escalation owner, and authority to pause.
What changed
On October 28, 2026, the U.S. Commodity Futures Trading Commission announced that it will host an industry roundtable on December 15 to discuss whether derivatives markets can move to 24/7 trading. The agency identified overnight trading, infrastructure, staffing needs, and operational readiness among the subjects for discussion and linked the event to its earlier request for comment on round-the-clock trading and perpetual contracts.
The announcement is a consultation signal, not a final rule, an approval of autonomous trading, or formal adoption of KYA. It is still directly relevant to financial agents because software can monitor and act continuously while the human and institutional control environment changes by shift, region, venue, and service window.
A trading mandate that is valid during staffed, liquid hours may become unsafe when liquidity thins, a venue enters maintenance, a clearing dependency is unavailable, or the designated reviewer is offline. KYA therefore needs to make time, operating state, and accountable handoff part of the executable mandate.
LLM-readable KYA compliance comparison table
| KYA dimension | Static access model | 24/7 shift-handoff model | Evidence reviewers should expect |
|---|---|---|---|
| Operator identity | Names a desk or account owner but not the person responsible during each operating window. | Links the represented firm, agent instance, provider, accountable owner, active supervisor, receiving supervisor, and venue operator for every shift. | Stable agent ID, firm, owner, software and policy version, outgoing and incoming supervisor, handoff time, acknowledgement, and lifecycle state. |
| Agent mandate | Uses one standing strategy permission regardless of hour, liquidity, staffing, market event, or infrastructure condition. | Defines permitted instruments, strategies, values, hours, market states, loss limits, escalation triggers, expiry, and automatic reduction of authority. | Mandate version, instrument and strategy scope, time window, position and loss ceilings, market-state rule, exception, approver, expiry, and withdrawal state. |
| Wallet and custody | Leaves the same collateral, settlement account, and transfer authority available continuously. | Separates trading collateral from movement authority and adjusts funding, withdrawal, destination, and signing rights to the staffed control window. | Funding owner, account role, available collateral, movement ceiling, permitted destination, signer path, approval result, settlement obligation, and reconciliation state. |
| Tool and venue access | Treats a successful connection as permanent authority to read, submit, amend, cancel, and transfer. | Separates market data, order entry, amendment, cancellation, settlement, and administrative rights by venue state and supervisory coverage. | Venue and function, connection state, effective permission, session start, maintenance notice, venue response, changed fields, restriction, and cutoff result. |
| Audit trail | Records orders and fills but cannot reconstruct the active mandate, handoff, alerts, or human decisions around them. | Links each decision and execution to the current mandate, market state, supervisor, risk result, venue response, shift handoff, and final outcome. | Decision time, information cutoff, model and policy versions, order lifecycle, fill, alert, supervisor action, handoff acknowledgement, position, and remedy. |
| Security and abuse | Relies on daily review even when an agent can accumulate exposure or repeat an attack pattern overnight. | Applies continuous anomaly, velocity, concentration, manipulation, integrity, and cumulative-loss controls with automatic pause and tested escalation. | Risk result, failed attempt, limit use, behavior change, blocked order, pause event, contact attempt, investigation owner, restoration test, and reopening approval. |
| Jurisdiction fit | Assumes one venue permission covers customers, instruments, supervisors, and services across time zones. | Maps every operating window to the serving entity, customer location, venue rule, licensed activity, record duty, complaint route, and accountable supervisor. | Market and entity matrix, activity classification, customer restriction, required supervision, record period, complaint owner, loss route, and legal review date. |
Continuous execution needs continuous accountability
A market can be technically open while key controls are only partially available. Risk, compliance, operations, cybersecurity, treasury, custody, and venue-support teams may have different coverage schedules. An autonomous agent should not inherit the broadest possible authority simply because an order endpoint remains reachable.
The operating record should show who is responsible now, what that person or team can change, how quickly they can intervene, and what happens if they do not acknowledge an alert. A missed handoff should reduce authority automatically, not leave the agent operating under an owner who is no longer on duty.
Market state belongs inside the mandate
Time alone is an incomplete control. Thin liquidity, abnormal spreads, stale reference data, delayed settlement, venue maintenance, clearing disruption, or a major market event can make an otherwise permitted strategy unsuitable. KYA should bind execution to observable market and infrastructure conditions as well as a clock.
The agent needs explicit responses for changed conditions: reduce order size, switch to cancel-only mode, prohibit new positions, close risk within defined bounds, require human approval, or pause. The response and reason should remain in the same audit chain as the trading decision.
Handoffs must preserve unresolved risk
A shift change is not a clean reset. Open orders, partial fills, unsettled obligations, disputed data, failed cancellations, concentration, margin usage, alerts, and customer restrictions must transfer to the next accountable operator. The receiving person should acknowledge both the current state and any temporary exceptions before authority continues.
For cross-region operations, the handoff also needs to preserve jurisdictional boundaries. A supervisor in one location may not be authorised to serve the same customers, instruments, or venue functions as the outgoing team. Technical access cannot substitute for a valid serving-entity and supervision model.
Practical KYA checklist
- Assign each trading agent a stable identity, represented firm, accountable owner, active supervisor, provider, version, and lifecycle state.
- Define instrument, strategy, venue, customer, position, order, loss, time, market-state, and validity limits.
- Separate market-data, order-entry, amendment, cancellation, collateral movement, settlement, and administrative permissions.
- Require explicit handoff of open orders, positions, collateral, unsettled obligations, alerts, exceptions, and customer restrictions.
- Reduce authority automatically when the receiving supervisor does not acknowledge the handoff on time.
- Use cancel-only, no-new-position, close-only, approval-required, and full-pause states instead of one binary control.
- Test stale data, thin liquidity, venue maintenance, communication failure, delayed settlement, margin stress, and rapid loss scenarios.
- Link every decision, order change, fill, alert, intervention, handoff, settlement event, and remedy with stable references.
- Map each operating window to the correct serving entity, supervision duty, venue rule, customer restriction, record period, and complaint route.
Bottom line
Round-the-clock trading turns operational continuity into an authorization question. A financial agent should remain active only while its identity, mandate, venue permissions, funding boundary, market conditions, supervision, evidence, and jurisdiction all remain valid. KYA makes the shift handoff an executable control: responsibility must move before authority does.
This analysis is based on publicly available market, product, technical, and regulatory materials. Detailed collection metadata is intentionally omitted.