Methodology
Data collection
How a production EPIC stack would collect venue data, and what this demonstration actually contains.
Updated 2026-09-25
A production collection layer would use official REST and WebSocket feeds, venue specification pages, rulebooks, index-provider notes, corporate-action notices, calendars and status pages. Each response would be stored raw, hashed, timestamped and then normalised.
This demonstration does none of that. There are no venue credentials, no scrapers and no live prints. Every figure is generated from a fixed snapshot so the product can be reviewed without pretending to be the market.
Rules that still apply
- Do not present a missing field as zero.
- Do not silently overwrite a prior specification.
- Do not scrape pages where the terms forbid it.
- Send ambiguous corporate-action and eligibility items to a person, not straight to the public page.