Editorial Policy
This policy explains how content is created, checked and maintained on Surpass Tech. The objective is to publish material that is useful, accurate and traceable to something a reader can open.
Every page on this site is written by Joseph Kudomo-Abasi, the founder, who also designs, builds and maintains the apps and calculators it describes. There is no editorial team to defer to and no freelance pool writing around a subject: the person who writes the page is the person who hit the bug, measured the latency or checked the arithmetic.
The author's profile, including contact details, is on the author page. If a page is wrong, the same person is responsible for correcting it — that is the point of putting a name on it.
We publish three kinds of page, and nothing else. Product pages describe an app we run: what it does, how it works, and what it does not do. Tool pages carry a working calculator, the formula behind it, a worked example and the limits of the model. Write-ups describe one piece of work in first person — what broke, what was measured, what changed because of it.
We do not publish pages that exist to hold a keyword. No aggregated product lists we have not used, no rewritten vendor documentation, no "top ten" pages assembled from other sites, no pages that restate their own title for four paragraphs. If a page cannot say something the reader could not get from the first search result, it does not ship.
Product and tool pages begin with the thing itself, not with the copy. The calculator is built and tested first; the product page is written after the screens exist and the measurement has been taken. That ordering is deliberate: it is why a product page can name a limitation with a date on it instead of describing an intention.
Where a page makes a factual claim about a platform — a caching header, a redirect status, a failure mode — the claim comes from running the thing and reading the result, and the page says what was measured. The changelog records what shipped and when, so a claim in a write-up can be checked against the state of the repository rather than being taken on trust.
Tool pages cite the primary references their explanation was checked against — a standard formula, a regulator's guidance, a reference implementation — and each page states the date it was last checked. Sources are chosen so a reader can open them: a link that 403s or 404s is not a source, and pages have been rewritten when a citation stopped resolving.
External references support our analysis; they do not replace it. Where a claim is our own measurement, the page says so and gives the method, because a number with a method can be challenged and a number without one cannot.
Every figure in a worked example is produced by the same formula the calculator uses, and the calculator is covered by a test runner rather than trusted on inspection. When a page states a comparison — what two years of extra term costs, what a deadline needs per month — the figures are computed for the page rather than estimated, and they are reproducible from the formula printed beside them.
Where an estimate depends on an assumption (a rate, an inflation figure, a benchmark), the assumption is named next to the number. A result that only holds for an unstated input is a claim in disguise.
When something is wrong, it is corrected in place and dated — not silently deleted and reposted where the original link used to point. The changelog carries a dated entry for corrections that change what a reader would conclude, and for anything a reader might have acted on.
Content is reviewed when the platform it describes changes: a new framework major version, a changed ad or caching policy, a deprecated API. A page is retired rather than left to rot when its subject no longer exists — the blog index and its topic archives were removed for exactly that reason, while the write-ups that had substance survive on the product pages they describe.
AI tools may be used while drafting, and some of this site's copy has been drafted with assistance. Every published page is reviewed, edited and signed off by the named author, and technical claims are checked against the thing itself rather than against a model's recollection of it. We do not publish unreviewed generated pages, and we do not use generated text to inflate a page to a word count — the length of a page here is the length of what it has to say.
The site is funded by the products it describes. It carries no paid placements and no sponsored posts, and nothing on a product page has been bought by a third party. If display advertising is enabled in future, it will be marked as such, it will not appear inside calculator results or worked examples, and no advertiser will be given influence over a calculation, a ranking or a recommendation.
Corrections, bug reports and questions go to kuyana57@gmail.com. A report that names the page and the specific claim is acted on fastest; where a correction is warranted, the page is updated and the change is recorded in the changelog.