I build systems.
Then I keep watching them.
Architecture is only the starting point. The lab follows how systems evolve through commits, releases, regressions, incidents and the knowledge produced by operating them.
Standards → Baseline → Platform → Capabilities → Workloads
The map is intentionally read top-to-bottom on mobile: engineering rules create a reproducible baseline, the platform integrates shared capabilities, and workloads expose the seams that need verification.
Systems under observation
Open a system to inspect problem, architecture, engineering decisions, development pulse, proof and lessons.
All systemsA reproducible and verifiable Kubernetes Internal Developer Platform
A local Kubernetes data platform connecting Kafka, CDC, Flink, Iceberg, Trino, Superset, and Airflow
An Apple Silicon hybrid MLOps desktop app separating Kubernetes control from native macOS MLX compute
Knowledge with provenance
A note matters more when the system, decision or failure that produced it remains visible.
Open KnowledgeA 2026 field guide and slide deck on contributing to the Korean e-Government Standard Framework (eGovFrame), from spotting small issues to review handling and verification.
An implementation-backed record of treating resolved invocation, CI, runtime evidence, post-state verification, and portfolio publication—not code generation or merge alone—as proof of OSS completion
A source- and evidence-based documentation review of Narwhal, Narwhal Portal, NFS Quota Agent, ldapium, kube-ready-box, ClusterDeck, Beluga, Beluga Manager, KubeMetal, and OpenForge, redesigned around Time to First Verified Success.
A main-branch, evidence-based update on Narwhal, NFS Quota Agent, KubeMetal, ldapium and OpenForge as of August 2026.
How the judgement evolved
Framework → DevOps → Cloud Native → Platform → OSS → AI-assisted engineering. The tools changed; the operating principles became clearer.