Skip to content
EngineerPlatform
Menu
Design
English

Engineer / Platform / Services

Trusting the numbers

Rules and checks that catch bad data on the way in, and a clear answer to who owns which figure and where it came from.

  1. Wrote a scope rule after a credential leak

    Wrote a scope rule into the repository after a restructure carried another company's inventory, firewall allowances and prose into it — and kept the quarantined residue under the secret scanner rather than excluding it.

    The scope boundary is a written rule with a stated test, the residue is visible rather than buried, and the specific shape of credential that got through now…

  2. Wrote tests for the checkers themselves

    Wrote tests for the checkers themselves after establishing that a checker fed only clean input will one day report clean because it read nothing — planting a misspelling to confirm the spell‑check finds it, and taking an id range from the database rather than from a number in the test.

    Every checker in the project now has a test that proves it fails on bad input, and the range assertions read from the source of truth.

  3. Know the licence of everything you ship

    Audited 644 Rust crates for licence compatibility on every build, and proved the check fires by rewriting one crate's licence and by moving the pinned core revision without regenerating.

    The distribution position is checked on every build, and the check is known to work because it was made to fail rather than because it has never spoken.

  4. Measured 13 addresses with no tracking

    Measured thirteen addresses from the web server's own access log alone — no cookie, no tracker and no third‑party service — masking the client network as each line is written, and folding the result into a permanent archive of 21 daily counts and 20 monthly facets.

    Thirteen addresses are measured this way, and the site ships no cookie, no tracker and no third-party request, so there is nothing to consent to and nothing…

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark