Program - template¶
Authoring template
Copy this file to programs/<owner>.md, fill in every section, and add the
page to mkdocs.yml nav and to the table in
programs/index.md. Delete this note.
A program describes only what varies per market owner. Do not restate platform mechanics (session lifecycle, scoring layers, reward mechanism) - link to them instead.
Snapshot, not the authority
State that the API is authoritative and this page is a dated snapshot.
Effective:
Forecast targets & data sources¶
One subsection per resource, with the heading set to the resource's API name so the markets directory and programs/index.md can deep-link to it. A program is not publishable without this section: a forecaster cannot model a target they cannot read a definition of.
<resource_api_name>¶
One plain sentence naming the physical quantity.
| Quantity | … |
| Unit | … |
| Resolution | … |
| Local time | … |
| Boundary | What is included and excluded (asset, zone, portfolio) |
Ground truth. Publisher, linked dataset, the exact field and any filter applied. State whether a near-real-time feed exists alongside the settled one.
Owner benchmark. If the owner submits its own forecast to the challenges, say so - forecasters are ranked against it.
Revisions & settlement¶
When measurements can still change (re-import window) and when they are frozen.
Challenge schedule¶
Within the platform's hourly sessions, this owner publishes:
| Category | Target window | Published at (gate closure, CET) |
|---|---|---|
| … | … |
State any horizons that are not published.
Eligibility & missed-day rules¶
- At most N missed days per month for monthly-league eligibility.
- Missed-day penalty: peer 75th-percentile substitution (or program-specific).
Prize pool & distribution¶
State the monthly pool per resource and how it splits into (track × horizon) envelopes. If the per-envelope distribution matches another program, link to it rather than duplicating the tables. Otherwise provide the per-rank breakdown.