Anyone can copy the interface. The scoring record has to be earned in public.

Every forecast is written with its resolution criterion frozen before the result is seen, and scored with a Brier score once the criterion resolves. The machinery is live and the register opened with ten frozen forecasts on 14 August 2026; the scored record accumulates only as criteria resolve, and the register page shows its current state.

Why it is hard to copy: a competitor shipping tomorrow also starts at zero resolved forecasts. History is the one input that cannot be bought, hired, funded or accelerated. Whoever starts scoring first stays that far ahead for as long as both keep scoring.

Every result carries the model name and version, the frozen inputs, the random seed and a SHA-256 receipt over the canonical bytes of the whole thing. Anyone can re-run it and get the identical number, or paste the receipt into the verifier and watch their own browser recompute the hash.

Why it is hard to copy: the format is trivially copyable and that is the point. Once results circulate as artefacts that anyone can re-run, the format becomes the thing people cite, and citation is distribution. A competitor adopting it is adopting our standard; a competitor refusing it is publishing numbers nobody can check.

Each resolved outcome on the public register sharpens the calibration LEXUN publishes for that domain, and each outcome a person resolves in their own workspace sharpens the calibration they see — on their own device, where it stays. What does not happen, and cannot with this architecture, is a private decision improving the model for anybody else: saved decisions and outcomes are encrypted locally and never transmitted as records (the optional Copilot receives only what a person types or a filtered result summary), so there is no corpus of customer outcomes here and no flywheel that turns usage into a better global prior. Saying otherwise would be the one claim on this page that the privacy notice forbids. What compounds is the public record and each user’s own history — and if consented, anonymised outcome aggregation is ever built, it will be announced as a change to what leaves your device, not shipped as a side effect. The Accuracy Centre refuses to display an accuracy figure for any domain with fewer than ten resolved outcomes, which today means every domain.

Why it is hard to copy: the improvement loop runs on resolved outcomes, and resolved outcomes only exist after real decisions have played out in real time. Capital shortens almost every other path in software. It does not shorten this one.

The simulation runs in the visitor's browser. Decision data is held in that browser's own storage and is never transmitted; the optional Copilot is the one exception, and it receives only what a person deliberately types or a filtered result summary. Running one needs no Key; keeping one needs a LEXUN Key, which is a locally derived passcode rather than an account — there is no server session, no user directory and no server-side copy of any decision to subpoena, leak or sell.

Why it is hard to copy: this is structural, not a policy line in a privacy notice. Anyone running inference server-side cannot retrofit "there is no server copy" without rebuilding the product, and any competitor whose business model depends on holding the data cannot make the claim at all.

Assumption registers, decision templates and audit trails deepen inside a team over years. All of it exports as a .lexun package, and the package is documented rather than obfuscated, so leaving costs one click.

Why it is hard to copy: the fact that the exit is free is exactly why a team is willing to put years of real reasoning in. A rival can copy the export format in an afternoon and still not have the years.

Every result carries the version of the model that produced it. Audit events are hash-chained, so an entry cannot be edited, back-dated, reordered or removed without the chain reporting it. The engine ships with 711 automated checks, all currently passing, including tests that deliberately tamper with a sealed record and assert that the tamper is caught.

Why it is hard to copy: any buyer with a compliance function requires this before they can use a number in a decision they have to defend. It is a discipline that has to be demonstrated over releases rather than claimed in a sales deck, and the demonstration takes exactly as long as it takes.

Five dated, frozen, publicly scored predictions per month, with misses left up permanently. The first six entries were frozen on 14 August 2026 and the earliest met reality within days — the counters above read straight from the ledger, misses included, and grow only as criteria resolve.

Why it matters here: this is the mechanism that converts elapsed time into the track record described at the top. Until the first entry publishes, the compounding items on this page are a design, not an asset.