A spreadsheet rebuilt for the fourth time is usually a sign that the arithmetic deserves a permanent home. Core Logic began with that observation: the same conversions, margin checks and planning sums were being rewritten across different projects, each with slightly different rounding. This site collects those calculations into a public library where the formula, the inputs and the result sit together on one page, so anyone can follow the steps or disagree with them.
Our Mission
Rather than returning a number from a black box, each Core Logic calculator prints the method it used, names its units and shows a worked example that can be reproduced with a pencil. We want a reader comparing freight quotes or scaling a recipe to understand why a figure came out the way it did, not merely to accept it.
The library is deliberately broad but the standard is uniform: a documented formula, a stated rounding convention and an explanation written in ordinary language. Picture a sole trader opening a margin tool late in the evening, entering a wholesale cost and a target percentage, and being able to check the answer on a calculator before sending a quote. That small moment of confidence is what the project is for.
Naming Methodology
Every tool starts as a written specification. We define which inputs are accepted, what the output means, which unit each value is expressed in, and where rounding occurs; that specification is then implemented in JavaScript and tested against worked cases, boundary values and missing fields. Naming the method precisely matters as much as the code, because a clearly labelled assumption is easier to challenge than a hidden one.
Consider a hydration-percentage calculation used for dough: the same ratio means something different if one version divides by flour weight and another by total weight. Writing the definition down first prevents that ambiguity, and the page states the chosen convention so a baker can compare it with a published reference. The same discipline applies whether the subject is a growing medium, a shipping surcharge or a study schedule.
Key Pillars
- Formula transparency: the arithmetic is printed on the page.
- Local execution: calculations run in the visitor’s browser, and input values are not transmitted or stored.
- Reproducibility: worked examples include intermediate values so a result can be checked independently.
Legal Disclaimer
Where a calculation touches tax, health, insurance or a legal entitlement, the page says which convention it uses and reminds readers that the governing rules come from an authority, not from us.
The full position is set out in our internal data protocols. In short: a number can be exactly right as arithmetic and still be the wrong number for a particular contract or jurisdiction. We would rather state that plainly than let a precise-looking figure imply a guarantee we cannot make.
What We Offer
Fantasy Generators
A worked case might describe four players dividing a reward after a long campaign, with each intermediate total written out. These tools are produced with the same specification-and-test routine as the business pages, because an invented setting is no excuse for sloppy arithmetic. The stated convention controls the result shown.
Gaming Names
Where a publisher’s live rules can change between patches, we describe the general maths instead of pretending to track a moving target, and we say when a figure needs checking against the current rules. The stated convention controls the result shown.
Cultural Names
Unit, currency-adjacent and region-dependent calculations live here, together with the Spanish edition of the library. Each page names the convention it uses, because a conversion that assumes a different customary unit can produce a confident but misleading answer. Regional specificity is disclosed rather than smoothed over.
Fun Nicknames
Lighter everyday tools cover recipe ratios, brewing and cooking times, session lengths and household planning. They are small, quick to use and still carry a written formula, so a reader can see why a suggested duration changed when one input moved.
Meet Our Team
Core Logic does not have an editorial board, a panel of named experts or a room of contributors. It is built and maintained by one person, Nathan Cole, a software engineer. Writing the specification, implementing the formula, testing the edge cases and drafting the explanation are all part of the same job, which is also why the voice across the library stays consistent.
The articles and tool pages are collected on the author archive, where a reader can see everything published under that name in one place. There are no guest authors, no sponsored reviews and no invented testimonials; if a page carries a claim about how a calculation was checked, it refers to work actually done on that page.
A reproducible report can usually be confirmed and corrected in a single pass, because the formula is already written down for inspection.
The site also keeps its scope deliberately narrow. It does not offer consultations, sell reports or certify figures for a filing. What it does offer is a documented method, a working tool and a clear route to say when either of them is wrong, all maintained by the same person who wrote them.
Accuracy Commitment
Formulas are re-checked whenever a tool is edited, using worked examples whose answers can be computed independently. Boundary cases such as zero, a missing field, a very large value and a rounding tie are part of that check, because they are where a plausible-looking calculator most often goes wrong. Reader reports are treated as bug reports rather than complaints.
Imagine a unit-conversion page that rounds an intermediate value too early: the fix is usually one line, but finding it requires an example with an awkward number.
Our Transparency
Where a convention comes from a published standard, the page names it; where the arithmetic is simply a ratio, it says that too. There are no hidden adjustments added to make a result look more authoritative than it is.
When a calculation changes, the wording on the page changes with it. The author keeps the update date visible so a reader returning after several months can tell whether the version they remember is still the one being served.
Content Integrity
Claims of professional endorsement, invented testing programmes and borrowed examples are removed rather than softened, and a page that cannot be verified is rewritten or withdrawn.
Picture a calculator whose explanation once implied that a general estimate complied with a particular regulation: the arithmetic may have been fine, but the sentence was not, and it belongs in the revision history rather than on the page. Accuracy here covers both the formula and the claims made around it, with the author accountable for both.
