Skip to content

← Back to projects

LOUST

LOUST-PRO software suite

Period: Jan 2024 —

Active

The challenge

A single canonical home for the operator-curated public repositories did not exist; recruiter verification meant chasing fragments across personal and org accounts.

My role

I maintain the LOUST-PRO org as the umbrella for the public-facing operator work, with each repository carrying its own scoped README, evidence chain, and operator-specific failure-mode notes.

What I did

  1. 01

    Single org, scoped repositories

    Why: Each concern gets its own repository with its own README and audit chain. The org is the umbrella that points at the surfaces; it does not duplicate the contents.

    Trade-off: More repos to keep current than one giant monorepo. The discoverability for a recruiter costs the operator some bookkeeping.

  2. 02

    Every repository links to a public anchor

    Why: A repo with no external anchor is a code dump, not a deliverable. The evidence chain tells the reviewer where to verify the claim.

    Trade-off: Every repo needs an upstream artefact worth linking to. Some operator-specific work is too narrow to anchor; those stay in the private umbrella.

  3. 03

    Public repos cover transport, observability, and security research

    Why: Three categories map to three distinct audiences: ops engineers, SREs, and security researchers. The org layout reflects the audience split, not the tech stack.

    Trade-off: Repository naming reflects audience rather than implementation. A reviewer has to read the README to know whether a repo is in Rust or Go.

What changed

  • Public repositories curated

    Before: Zero org, scattered across personal accounts

    After: Eight in LOUST-PRO plus repos in louzt

    Evidence: github.com/LOUST-PRO, 2026-Q3

  • Time for a recruiter to verify a claim

    Before: Several minutes across accounts

    After: One click from repo to evidence

  • Public artefacts linked from repos

    Before: 0

    After: 12+ gists, advisories, papers

Trade-offs

I keep the umbrella small. Repos too narrow to anchor publicly stay in the private umbrella, even when the code is interesting.

What I learned

An org is a discoverability surface, not a code surface. Keeping the org lean forces every public repo to earn its place against an external anchor.

Stack

  • Go
  • Rust
  • Python
  • TypeScript
  • RDF
  • MCP
  • QUIC
  • Kubernetes

Repository

https://github.com/LOUST-PRO ↗

Evidence

← Back to projects · curated 2026-09-20