# Methodology

Every Techolm tool computes its results with its own code, and automated tests check that code against known-good values from a cited source. Examples on a tool page are computed by the same code, never typed by hand. Money, official rates, random values, limits and files follow the rules below.

## Results come from the tool's own code

Each tool computes its results with its own code. Automated tests check that code against known-good values taken from a cited source, such as a standard or an official publication, including values at the edges of what the tool accepts. The tests run on every change to the code.

When the site is built, the examples on a tool page are computed by that same code, never typed by hand, so they show what the tool really returns.

## Exact values such as money

Money and other values that must be exact are never computed with binary floating-point numbers, the approximate number format that computers use by default, which cannot store most decimal fractions exactly. These tools use whole numbers of the smallest unit, such as cents or paise, or exact decimal arithmetic instead. Each of them states its rounding rule, and tests check it.

## Official rates, rules and constants

Every statutory or published value that a tool uses, such as a tax rate, a threshold, a unit definition, a formula constant or a due date, is stored as data with the date it takes effect and its primary source: a government body or a standards body. For units of measurement, these include the BIPM, which maintains the International System of Units (SI), and NIST, the US National Institute of Standards and Technology. When a law changes, the new value is added with its own effective date, and the old value keeps its dates.

## Random values

Tools that create secrets, such as passwords and tokens, take their random values from a cryptographic random number generator (`crypto.getRandomValues`), which is built for secrets. Examples and tests use a seeded generator instead: one that starts from a fixed value, so it gives the same results every time.

## Limits and error messages

A tool's limits on input, such as file size, number of files or text length, appear in the facts on its page. Input over a limit gets a clear message; a tool never cuts your input short without telling you. Error messages say what is wrong and how to fix it, and never show the tool's internal details.

## How files are checked

A tool that accepts files identifies each file's format from its first bytes, never from its name or extension alone. The number and size of the files are checked before any file is read. In the browser, each run of a tool that converts or shows files starts a fresh worker, a separate background task that is closed when the run ends and keeps nothing from earlier runs.

## Health, money, legal and safety tools

Tools on these topics state their assumptions, cite official sources and never claim to replace a professional, such as a doctor, an accountant or a lawyer. Treat their results as general information, and check any decision that matters with a qualified person.

## Rules for AI features

Dewiride's rules for any feature that uses artificial intelligence (AI): AI never computes official figures, such as tax, financial or medical values; anything AI produces is a suggestion for you to review; and each AI feature can be turned off on its own by whoever runs the site or the installation.

## Report a wrong result

If a tool gives a result you believe is wrong, contact Dewiride through [its website](https://dewiride.com) with the tool's page address, the input you used and the result you expected, with its source if you have one. Use made-up data where you can, and never send personal or confidential files.

---

Updated: 2026-10-23