Market infrastructure
Operational infrastructure for governed event markets
Map available venue contracts to event definitions, record semantic relationships, monitor rules and lifecycle signals, and preserve resulting records with versioned provenance.
How the layers fit together
REFERENCE AUTHORITY
Governed reference definition
PREDICT HERE
Canonical event
VENUES
Available and entitled venue contracts
Price comparison should follow semantic verification
STEP 4
Semantic conformance
VERIFIEDPARTIALNOT_EQUIVALENTUNREVIEWEDSTEP 5
Rules and lifecycle monitoring
STEP 6
Versioned provenance
STEP 7
Workstation / API
These labels describe a reviewed relationship between contracts; the event-level rollup can remain more cautious when a relevant contract is unreviewed.
Architectural model — integration not enabled. An external authority can govern an event definition. Predict Here has not enabled an external reference-authority ingestion workflow in production.
Price comparison should follow semantic verification
Finding similar wording or automatically matching text does not establish that two contracts have the same economic meaning. A relationship review records one of the states below. Price comparison must not silently imply equivalence.
Price comparison should follow semantic verification, not precede it.
VERIFIED
The reviewed relationship is verified under the current relationship review. This is not a legal opinion or proof that terms will never change.
PARTIAL
The underlying relationship is marked REVIEW_REQUIRED; the public display maps that review status to PARTIAL. Differences still require review; this is not a final partial-equivalence verdict.
NOT_EQUIVALENT
The reviewed relationship is not semantically equivalent.
UNREVIEWED
No reviewed relationship is recorded. Similarity or an automated suggestion does not promote it to verified.
Conformance can change over time
Contract terms, resolution wording, source rules and lifecycle state can change. Existing code detects source-rule hash changes and includes lifecycle and source-health signal types. These signals do not provide automatic legal interpretation or guarantee that every change invalidates a mapping.
RULES_CHANGED · SEMANTIC_DIVERGENCE · MARKET_LIFECYCLE · SOURCE_DEGRADED
SEMANTIC_DIVERGENCE relates to cross-venue equivalence. With one active entitled venue today, cross-venue comparison is not currently available.
Preserve the context behind a record
The current response envelope and mapping records provide the following fields where the endpoint or source makes them available. Availability varies by response; this is not a promise that every field appears on every record.
- Source
- Venue/source identifier attached to an observation.
- Source timestamp
- Source as-of time when supplied; freshness and quality state are kept distinct.
- Event and contract IDs
- Canonical event ID and source contract/market ID where returned.
- Mapping relationship and version
- Relationship type, review status and mapping version where applicable.
- API methodologyVersion
- Version stamped on supported API envelopes; it varies by endpoint and processing path.
- Execution algorithm version
- Separate version identifier for the price-at-size execution calculation where used.
- Event taxonomy version
- Separate version identifier for event classification where supplied.
- Semantic state
- Relationship state is recorded separately from event-level rollup.
- Quality and freshness
- Quality flags and freshness status are returned where defined.
- Entitlement context
- Source entitlement mode is checked server-side and included in supported envelopes.
- Rules/reference version
- A source-rule hash can signal change; no external methodology archive is claimed.
Entitlement-aware by design
Technical connectivity does not create redistribution rights. Product access and third-party source rights are separate checks; delivery is enforced server-side against the organization’s actual source entitlement. Current source and cross-venue availability are shown from the shared capability registry below.
Rights are source-specific. Do not infer that Predict Here holds unrestricted redistribution rights; customer-owned source arrangements require the customer’s own licence.
Who this is for
- Index and benchmark providers
- Reference-data providers
- Exchanges and market infrastructure
- Institutional research and risk systems
Discuss an Infrastructure Partnership
Share the area you are exploring and how to reach you. This opens a prefilled email to our partnerships team; this form does not submit or store your message.