From a working application to a repeatable delivery path. Explore my public engineering lab across Python APIs, cloud infrastructure and GitOps.
Explore the workPublic code. Open to inspection.
Three connected projects.
One inspectable engineering lab.
01 GitOps platform
How do application and platform changes share one reviewable delivery path?
Argo CD and Kustomize definitions connect applications, networking and observability. Separate development and smoke roots make the intended environments readable in Git.
Explore gitops platformDesired-state definitions in an engineering lab; no running cluster is implied.
Public source snapshot: 8f4f31226fd5
02 Cloud infrastructure
How do you make environment setup easier to repeat and inspect?
Terraform provisioning and Argo CD bootstrap describe the route from cloud resources to application delivery. Bounded smoke and cleanup workflows make the lifecycle explicit.
Explore cloud infrastructureProvisioning code and workflows; no currently running environment or billing guarantee is claimed.
Public source snapshot: cb7c88f84e9f
03 Python application
What sits between a chat interface and an LLM provider?
A FastAPI service with project-scoped conversations, stored transcripts and OpenTelemetry instrumentation. Provider failures are handled separately from successful chat history.
Explore python applicationApplication code in an engineering lab; no hosted commercial service or customer results are claimed.
Public source snapshot: 899ba6434745
These projects explore three connected engineering problems. Each one links to the implementation so you can inspect the decisions, boundaries and code.
Express the desired environment in Git, with explicit application and platform boundaries.
See the projectKeep provisioning, bootstrap and cleanup steps visible instead of relying on undocumented setup.
See the projectConnect API behavior, conversation persistence and telemetry in one inspectable backend.
See the projectExplore the code, read the decisions, follow the work.