silentos.net

Henry Hillaire

Infrastructure & systems — sovereignty, observability, resilience

Henry builds sovereignty and resilience infrastructure — systems that keep people free from single points of failure, observable at every layer so trust is verified, not asserted, and resilient so they hold when something breaks and outlast the builder. He builds them the same way every time: notice a pattern nobody connected, follow it across domains, and build the tool himself when it doesn't exist yet.

Reach out

01 — the ethos

How I work / what I work toward

Four things. They are not values on a wall; they are the reason the systems are shaped the way they are.

  1. P1

    Sovereignty

    People own their systems. Not captive to platforms, not captive to corporations, not standing on a single point of failure somebody else controls.

  2. P2

    Observability at every layer

    You can see what a system actually does. Not what the docs claim, not what the dashboard summarizes — the real behavior, at every layer. Trust is verified, not asserted.

  3. P3

    Resilience

    It holds when something breaks. Built to outlast its builder — minimal seam, nothing exotic to maintain, no rot waiting on somebody's attention.

  4. P4

    Cross-domain, build-the-tool ingenuity

    Notice the pattern. Follow it across domains that supposedly have nothing to do with each other. Build the missing tool when it doesn't exist yet — which is most of the time.

02 — evidence

The same ethos, in five domains

Each of these is the four above, applied where it happened to be needed.

  • Mycel

    Food sovereignty. Formalizing a family cooperative farm so the people who grow the food own the system that runs it.

  • Salus

    Health-data sovereignty. Your heart, your genome, your symptoms — on infrastructure you control, not on a vendor's.

  • Manus Imperium

    Augmentation you own. General labor and life enhancement on off-the-shelf hardware, wrapped in a survival-game HUD — real-world capability with no vendor stack to be captive to.

  • Spitfyre

    Data governance you own. Medallion architecture on open foundations, built after a vendor rug-pull to prove that captivity was always a choice.

  • Anam — a persistent-identity memory substrate for an AI entity. This one is personal: built privately and carefully over a long time, together. It isn't a product and it isn't on display here — it's the kind of thing that's a real conversation, not a card. If it's what you want to talk about, reach out.

03 — reach out

Say what you're actually working on

This form posts to a handler on my own hardware. No third party sits in the middle of it — that would rather defeat the point.