NO. 001
Omnia ex Machina
01 / 07
ABSTRACT
My portfolio as a computing artifact: Swiss composition, a photographed Apple II and CRT material turn the website itself into a demonstration of design and engineering.

Preparing the machine.
P / 02
07 PROGRAMS
OWN PRODUCTS
My own products and open source.
My own products: native Apple apps, open-source libraries and systems software, built and maintained independently. Not client work. The systems inside the machine.
07 / 07
SIDE A
SERVICES
SIDE B
SOURCE
Open source, libraries, servers and experiments live on GitHub, public as soon as they are ready to be read.
LiqUIdify, BoutiqueDB-Swift and the tools behind this site are filed there.
IDENTITY PENDING
Colors.swift light-mode tokens. No verified image mark or running application was available; these plates document implemented source.
A native macOS container platform on Apple virtualization: one app, engine and CLI for containers, Linux machines and Kubernetes.
The engineering surface includes daemon and client architecture, container runtime control, Linux machines, SSH, networking, certificates, local persistence and Kubernetes provisioning.
It is treated here as an engineering-heavy case rather than a polished commercial product. The stack is Swift and Apple system frameworks, not a generic desktop shell around Linux tooling.
The app composes Shell and feature targets. Engine and CLI directly depend on Networking, Containers, Persistence and Shared. Networking depends on Containers, Persistence and Hummingbird. Containers depends on Apple Containerization; Persistence uses GRDB. These are implemented package target relationships, not proof of release readiness.
Source: flying-dutchman-app/Package.swift. Selected direct target dependencies.
END OF RECORD