Every article
has a source.
The primary question is not “which category is this?” but “which system, decision, incident or external signal made this knowledge necessary?”
Start from the system.
Systems with more linked notes surface naturally, but the count is context — not a ranking.
A stream of engineering records
Each entry keeps its producing system visible so reading can move in both directions.
Notes on kube-ready-box v0.3.0: a rebuild that took shipped Vagrant boxes to zero fixable CVEs, the HCP Vagrant shutdown discovered during upload, the move to GitHub Release + Pages, and a weekly scan for vulnerabilities that are not patched yet.
A write-up of the talk at Kubernetes Korea Group Meetup, Session 2 on October 28, 2026. Project roles seen through a Day-0/1/2 frame, the OpenForge verification system, outside-developer cases, and failures of an AI agent team.
A KubeMetal implementation separating Colima VM profiles is now available as an AI agent reference in XERJ Corpus Hub.
Two repositories joined by pins had drifted 118 commits apart, and cross-repo changes could not land atomically. This post summarizes the decision to fold beluga-manager into beluga's manager/ directory, the alternatives, and the consequences, based on ADR-0005.
A write-up of 'AI Agents and the Role of the Human Developer', presented in Soongsil University's 2026 Software Special Topics 2. Silent failures drawn from my own incident logs, and a rule for what to hand off versus what to keep.
Why re-creating a Kubernetes cluster kept breaking SSH, kubeconfig, hosts, and CA trust by hand, and how a Profile fixed it
How OpenForge's false-green detector grew from a swallowed `|| true` pattern to a second, structurally different shape, and the real narwhal/beluga bugs it caught along the way
A 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.
Why I introduced ADRs while managing shared OSS engineering standards in OpenForge, and how ADR → Standard → Automation → Adoption keeps decisions traceable.
System → Decision / Incident → Note → Architecture / Release
The goal is a traceable engineering record. A lesson should always have a path back to the context that produced it.