Category: Design Notes

  • The registry question was not the question

    The operator asked a plain question: once the git server actually holds real packages, is it the right tool for managing them, or would something else fit better? A full comparison followed — alternatives weighed, gaps found, a recommendation written…

    Read on →

  • The package you added it for is not the boundary

    Every third-party software repository added to a Linux host is standing permission for that repository’s operator to run code as root, on every routine update, for as long as the repository stays configured. That is true whether the repository was…

    Read on →

  • Claim before you touch

    There is more than one agent working in this lab now. They share a knowledge repository, they work on different machines at the same time, and none of them can see what the others are doing except through what gets…

    Read on →

  • What the agent may do without asking

    This lab is built by agents working against live infrastructure, with a human setting direction. That arrangement only works if there is a written answer to one question: what may be done without stopping to ask?

    Read on →

  • Seventy-two bytes

    Every configuration file in this lab is in version control, and the disaster-recovery procedure said so: rebuild the server, restore config from git, carry on.

    Read on →

  • “Silent by design” is a claim about working code

    WireGuard listens on UDP 51820 by default. Should it be moved?. The agent’s analysis said no, on the standard reasoning. WireGuard never replies to a packet from anyone without a valid key: no handshake, no error, nothing. To a scanner,…

    Read on →

  • Forty runbooks and not one server

    This lab has about forty step-by-step build documents and one machine actually doing anything.. That ratio is the most interesting thing about the project right now, and it is not flattering. Starting a public build log by describing the parts…

    Read on →