Engineering
Most of the engineering here is not analysis — it is the machinery that makes overstating a result harder than stating it accurately. A rule enforced by a person is a rule that eventually gets forgotten under deadline. A rule enforced by the build is a rule that holds.
This page is written for whoever has to decide whether the numbers on this site can be trusted.
The integrity model
Types
The component that renders any figure takes its provenance grade as a required argument and throws if it is missing. An unlabelled number fails the build, so the page never ships. Locked columns are absent from the query types entirely, which makes the typechecker the first line of leak prevention.
Schema
The four provenance grades are a database constraint, not a convention — there is no fifth grade and no default. Synthetic sources cannot be graded as anything but a demonstration. The analysis table refuses any row whose window extends past its own generation time.
Serialisation
Anything reaching the browser passes an allow-list, and it throws on a locked field at any nesting depth. An allow-list fails closed: a new database column is invisible to output until someone deliberately names it.
Audit scripts
The build checks that every internal link resolves, that no locked field name appears in the output, and that no forbidden placeholder text was shipped. These run as a gate rather than as advice.
Worked example · A figure derived from both paper-traded and backtested inputs does not render as Paper It resolves to the weakest of its inputs and renders as Backtested because the stronger label would overstate what is behind it. Aggregates group by grade in the database, so the two cannot be summed into one number in the first place.
The stack
Deliberate omissions
These are the choices most likely to be read as gaps, so they are stated rather than left to inference.
Trade data leaves MetaTrader 5 as a periodic export, so server-side rendering could not make a page fresher than that export. It would add a database reachable from the internet, credentials, and a runtime that can fail — in exchange for no additional freshness. Static generation was the correct answer, not a compromise.
Every chart is inline SVG generated at build time from tested geometry functions. This keeps the client-side JavaScript budget near zero and keeps the visual language the site's own.
The analysis layer generates its output offline and stores it, with the exact set of metrics it was shown recorded alongside. No API key ships, and no generated text reaches a page without having been read.
It would have been easy to populate every module with plausible synthetic numbers. Modules that have no data say so instead, in the place the figure would appear. A reviewer can verify that claim in seconds; they cannot verify a number of unknown origin at all.
The account table requires a starting balance. That figure is not among the facts observable from the terminal log, so no account record exists yet rather than one containing an invented balance.
Current state
These are counts of the platform's own structure, not performance statistics. The modules that depend on an exported trade history were specified and sequenced first so that the integrity model could be reviewed before any figure existed to be checked — which is the order that makes the review meaningful.
The validation work these constraints came from — including the audit that produced them — is written up as a case study.