Skip to main content
/ projects

Abstract Software Factory

I build to learn. Each project ships with a decision record: what I chose, on what basis, and why.

Field notes

System context diagram for the image-signing experiment.
SYSTEM OF INTEREST
FILE 01 · supply chain security · 10 min

Readable Tags, Verified Digests

Developers name images by tag, but a tag can be repointed without anyone noticing. One pipeline signs and attests the image; another, given only the tag, resolves, verifies and runs the exact digest. It worked.

closed · next: keyless signing
Read the field notes →
PrepEntryAdjustExitMMAMuay ThaiKickboxingBoxing
THE LENS
FILE 02 · applying systems analysis to martial arts

In the Squared Circle

A systematic approach to problem solving in martial arts

A striking exchange read as a movement problem: preparation, entry, adjustment, exit. The lens does not fight for you; it makes you name the problem first, relative to the opponent, then pick the phase where your strength meets their weakness. Worked through Volkanovski against Holloway, checked against fights after the fact.

drafting · scored by exchange, not by fight
Field notes in progress

Arc 1 · Down the stack

Three related projects, each one layer deeper than the last. Run a real system, then the runtime under it, then the platform under that.

Invidious on GCPOperate a real system.applicationbuilding

A self-hosted, multi-backend Invidious deployment, fully automated, with a public health dashboard. The benchmark: match a well-known public instance, then beat it.

GKE · Terraform · Ansible · OIDC · SLSA · Prometheus · decision record · project page
  • Infrastructure as code: GCP, GKE
  • Signed images, pulled by digest (written up)
  • Multi-backend deployment
  • Secrets via OIDC, none stored
  • Public health dashboard
  • Load-tested scaling
Planned architecture (C4, level 2)
Invidious on GCP · container diagramC4 level 2
Viewer
[Person]
Watches videos without tracking
↓ HTTPS
GitHub Actions
[Container: CI/CD]
Builds, signs and attests images
Ingress
[Container: GKE load balancer]
Routes and spreads requests
Grafana
[Container]
Public instance-health dashboard
↓ pushes signed image
↓ HTTP
↑ queries
Artifact Registry
[Container: image store]
Images pulled by digest →
Invidious × N
[Container: Crystal on GKE]
Serve the frontend and API
Prometheus
[Container]
← Scrapes metrics
↓ SQL    ↘ HTTPS
Secret Manager
[Container: GCP]
Secrets via OIDC, no stored keys
PostgreSQL
[Database: Cloud SQL]
Users and subscriptions
YouTube
[External system]
Video source
Terraform + Ansible [Infrastructure as code] · provisions everything above
personruntimedeliverydata and secretsexternal
Planned containers and how they talk. Every image is signed and pulled by digest. Select to enlarge.
Container engineUnderstand what runs it.runtimenext

Build, run and manage OCI containers from first principles, behind one web UI. A mini Portainer.

OCI · Go · Linux namespaces · project page
Own deploy platformBuild what runs everything.platformlater

A small Render-like platform on Kubernetes. First job: deploy GitLab, fully automated.

Kubernetes · GitOps · project page

Select a stop to open it.

Index