microsoft / microsoft/qlib

Add real-time market state verification for live execution path

Open
#2,185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
48.7k
Forks
7.7k
PR merge metrics
No merged PRs in 30d

Description

Hi,

I saw qlib's trade_calendar handles scheduling for backtesting, but for live agent execution it doesn't cover unplanned halts, circuit breakers, or real-time session state. That's the gap that bites when agents go from backtest to production.

I've been building Headless Oracle — a signed market oracle for AI agents. It returns Ed25519-signed receipts confirming an exchange is OPEN, CLOSED, HALTED, or UNKNOWN. 60-second TTL. 28 exchanges. The rule: UNKNOWN must be treated as CLOSED.

import requests

r = requests.get('https://headlessoracle.com/v5/demo?mic=XNYS')
receipt = r.json()

if receipt['status'] != 'OPEN':
raise Exception(f"Market not open: {receipt['status']}")

Free to try (no key needed). pypi.org/project/headless-oracle

If there's interest in adding a pre-trade verification step to qlib's live execution path, happy to contribute.

— Mike (headlessoracle.com)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating qlib's trade_calendar and the live execution path to determine where a pre-trade market-state check could belong. Review how live orders are currently scheduled and executed; done would require an agreed verification design that handles OPEN, CLOSED, HALTED, and UNKNOWN states safely.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.