Declared League Results Table

How to use Declared League Results Table

Declare teams, points for a win/draw/loss and any signed point adjustments. Enter each result once, choose the descending ranking keys and inspect shared competition ranks with source-order display ties.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Declare teams, points for a win/draw/loss and any signed point adjustments. Enter each result once, choose the descending ranking keys and inspect shared competition ranks with source-order display ties.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 2–50 distinct teams and 0–200 uniquely named results. Each result uses two known, different teams and whole scores from 0 to 1,000,000. Match IDs may represent repeated fixtures; identical scores are not automatically deduplicated.
• Win/draw/loss points are nonnegative exact decimal strings up to 1,000,000; signed adjustments are within ±1,000,000,000. Choose 1–4 unique descending keys from points, goal-difference, goals-for and wins. All quantities allow six decimal places.
• An entered-policy table, not an official federation table or live feed. No head-to-head mini-league, fair-play, shootout/knockout winner, missing fixture inference, sanctions verification or prediction. Equal full keys remain tied even when displayed in source order.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.