GLINTARY

HOW GLINTARY WORKS

How a market gets onto Today’s Board.

Every published position must pass five checks.

Five checks

  1. 01

    Evidence

    Are the key facts confirmed?

  2. 02

    Odds

    Do the available odds support the research case?

  3. 03

    Availability

    Are the source, region and observation time documented?

  4. 04

    Uncertainty

    Does the case still hold under less favourable assumptions?

  5. 05

    Red team

    What is the strongest reason we may be wrong?

Record rules

  • Singles only.
  • 1.00 unit per position.
  • Some days have no positions.
  • Losses stay on the record.
  • Updates are appended, never rewritten.

What we measure

Net units, ROI, closing-line value and performance by sport and market.

Every number comes from the public Ledger. A small record proves very little.

Technical methodology · v1.0

Pipeline

  1. Ingest the day's real events for the covered sports.
  2. Exclude simulated, virtual and unverifiable events.
  3. Collect pre-match markets and outcomes from the recorded source.
  4. Screen for initial candidates.
  5. Deep-research the candidates that remain.
  6. Confirm key facts against official and primary sources.
  7. Document the recorded odds, source, region and observation time.
  8. Define the minimum odds at which the position still qualifies.
  9. Stress the case under less favourable assumptions.
  10. Run the red-team review.
  11. Decide: position, pass or watchlist.
  12. Lock the position record before the event.
  13. Publish to Today's Board and the Ledger.
  14. Monitor odds, availability and material news while active.
  15. Append updates and status changes; never rewrite.
  16. Record the result and the closing odds after the event.
  17. Compute unit P&L and same-line closing-line value.
  18. Publish daily and weekly audits once official positions settle.

Source hierarchy

TIER 1 · OFFICIAL, then TIER 2 · TRUSTED LOCAL, then TIER 3 · SECONDARY, then TIER 4 · DISCOVERY. Higher tiers override lower tiers. A single unconfirmed report never carries a position on its own.

Odds layers

Recorded odds are the odds observed from the named source when the position was published, with region and observation time. Minimum odds are the lowest odds at which the position still meets the published research threshold. A market reference, where recorded, is a neutral comparison line and not a recommendation.

Coverage definitions

Reviewed counts appear publicly only when a coverage run for that board day is on record. Without a logged run, no reviewed, passed or candidate numbers are shown.

Status definitions

OPEN
The available odds are still at or above the minimum odds.
CLOSED · ODDS
The available odds have fallen below the minimum odds. The research stays on record, but the position no longer meets its threshold.
MARKET UNAVAILABLE
The market is no longer listed at the recorded source. The research stays on record.
REVIEW
New material information is being evaluated against the original case.
NO NEW ENTRY
New information has materially weakened the original case. The position no longer stands as current research.
REVEALED
A previously hidden position is now public.
POSTPONED
The event was postponed. The result follows the published market rules.
SUSPENDED
The market is suspended at the recorded source.
UNMONITORED
Odds, availability and news were not monitored for this record after publication.
SETTLEMENT REVIEW
The event has finished. The result and closing odds are being checked.
SETTLED
The result and closing-odds comparison are published.
VOID
The position was voided under the market rules. Unit P&L is zero.

Record classes

OFFICIAL records pass the full pipeline with documented odds evidence and a cryptographic commitment; only they form the public record, which starts with the public beta. Research from the build phase before launch is development history and is not part of the public record. DEMO records are illustrative and never appear in the public beta.

Version history

Methodology v1.0, 3 September 2026. Later versions are published here and referenced on every record they apply to.

How a locked record is protected against later changes is described under Verification.