GLOBAL TRADER RANKINGS / RECORD COMPARISON
Trading Record Period and Compatibility Bridge
Compare metadata and transform an observed return pace without creating a trader score.
Entered labels are not verified source records. The screen checks matching metadata only; annualisation assumes repetition of an observed pace. Exact decimal arithmetic is not financial assurance.
Result
No calculation yet.
Calculation contract
Total return must be greater than minus one hundred percent and at most one hundred thousand percent. Duration must be positive and at most twelve hundred months. Drawdown must be nonnegative and below total loss. The annualised result is bounded to prevent impractical extrapolation. Exact decimal strings are retained in the JSON export; displayed values are rounded to two decimals.
Metadata checks are deliberately narrow
Object, currency, cost definition, valuation basis, first and last observation dates must match. Unknown labels are unresolved even when both records say unknown. A reversed date interval is invalid. The entered month duration is separate from exact dates; the tool does not infer it or certify the source's calendar convention. Different month durations also prevent metadata compatibility.
What no output can establish
A passed compatibility screen does not establish true labels, complete performance series, absence of flows, risk equivalence or comparative skill. A period transformation does not fill a missing year. The tool does not convert currencies, estimate expenses or combine overlapping competition accounts. No real account records are included.
Inspect the authored references
The complete practice packet gives four invented records, all their fields and a membership register with a missing outcome. Use it to inspect incompatible inputs rather than to infer a real-person rank. The source dossier preserves provenance questions as a separate workflow. Entries stay in the current page until a requested export and clear on reload.
Use and invalidate a result
The starting inputs are invented examples. Calculate first, then inspect each output and the metadata gap list. Change a currency or cost label to observe the compatibility boundary. Any changed input invalidates the result and disables export until recalculation. Reset restores the initial example inputs and clears the result. Reload also starts a fresh page; there is no account history, saved portfolio or source verification service behind this form.
Exact strings and display precision
The dependency uses forty-digit decimal precision with half-even rounding. Displayed percentages use two decimal places, while the JSON retains exact decimal output strings under that declared precision. This prevents a rounded display from becoming the reproduction reference. The independently prepared Python fixtures check the numerical implementation; they are invented software cases, not strategy observations. Near-total-loss inputs are bounded, and invalid calendar dates, reversed intervals and impractical annualisation are rejected.