BlackMesa Labs

Engineering notes: what we built, what we broke, what we took away.

  1. Every key has a sky

    The starting idea was to invent a cryptography based on constellations. It does not hold, and we explain why. What was left of it does: Stellar draws a site's public key as a constellation with a name, so that a human notices the day it changes. Then we had that sky announced by the DNS of our own sites, signed, and followed at every certificate renewal. Here is what that proves, and above all what it does not.

  2. A date nobody has to believe

    In October we took the date of our reports off our own clock and handed it to three timestamping authorities. The report itself admits the limit: their tokens are worth nothing beyond the RSA that signs them. Here is the sequel: a proof of date made of SHA-256 alone, ending in a Bitcoin block, that anybody can check without trusting anybody. And what it does not prove, because that is half of the subject.

  3. You cannot secure Luhn. That is why your card has a CVV.

    The Luhn formula has been explained a thousand times. What gets explained less is that it protects against nothing, that making it "more secure" is a category error, and that the payment industry understood this back in the 1990s. We also checked what our own tool sees when code uses it as a lock: nothing. That is fixed, in part, and here is what remains.

  4. We named the branch. The commit landed on main.

    In a GitOps repository, main is production. One night in October, manifests nobody had approved landed there, with an image tag that did not exist, and nobody had typed "main". Two Git settings, each reasonable, and a command that is right everywhere else.

  5. Your document and its signature do not travel together

    A signed artefact published on the web is at least two HTTP resources. The verifier downloads them separately, and nothing guarantees they come from the same generation. When they do not, verification fails exactly as it would on a forgery. Here is the mechanism, what it breaks, and the three ways to close it.

  6. An agent can do anything. It cannot answer for what it did.

    Where development ends, where operations begin, and who decides when an AI writes half of both. The answer is not in the tooling or the org chart: it is in reversibility, and European law has already written it down for cybersecurity. Here is the line, and what it demands in practice.

  7. Cryptography: we put our one question to a real company director. He understood none of it.

    Our tool reads a project, says how long each protection will hold, and asks the business for one thing only. Here is what it produces, and what happened when we put that question to somebody who is not an engineer: three sessions, three failures, and 986 words to read in order to answer two questions.

  8. A signature proves who and what. Never when.

    The "signed at" field of a signed document comes off your own clock. The signature covers it, so it cannot be edited afterwards — and it can be chosen beforehand. Backdating costs nothing, and a chain of signatures does not help either. The answer is four moves, it checks with stock openssl, and it divides across jurisdictions for thirty-two bytes.

  9. "We say what we do": three times in two days, this blog said something false.

    A signature that did not cover the page it sealed. Three digests where the document promised one. A piece cited as published that never ran. Each found by doing what the sentence described, and this is how — because transparency is not an intention, it is an apparatus.

  10. Our domain layer contains nothing but exceptions. On purpose.

    Nine contexts, twenty-nine commands, a single query handler, zero ports. What we kept of DDD and hexagonal architecture, what we turned down, and the five places infrastructure crosses the boundary anyway. This is not purist DDD, it is time to market.

  11. We were our own best customer. That was a bug.

    Our company publishes on our platform — and was counting itself in our revenue, our funnel and our follow-up lists. How we took it out of the statistics without taking it off the site.

  12. The cheapest feature is the one you don't build

    Three signals that say 'do not write this code' — and what they saved us in a single day.

  13. Upgrading the OS under Docker: what is still coupled, and what nothing validates

    The application lives in an image, so the distribution cannot touch it. Four coupling points remain — and one of them sits in a blind spot no pipeline covers.

  14. Building a complete, production-ready SaaS with a coding agent

    Zero-downtime deploys, real payments, passwordless sign-in — paired with an AI.

  15. Guaranteeing legitimate case studies without a moderation team

    Betting on verified identity rather than censorship — and the two bugs that made us doubt it.