KNOWLEDGE / PROVENANCE STREAM

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?”

SOURCE SYSTEMS

Start from the system.

Systems with more linked notes surface naturally, but the count is context — not a ranking.

LATEST / WITH PROVENANCE

A stream of engineering records

Each entry keeps its producing system visible so reading can move in both directions.

01
WORKBENCH / UNLINKED
Retiring my Harbor arm64 fork: the day upstream caught up

Why I forked Harbor for multi-arch images after Bitnami's free images stopped, why I shut it down when v2.16.0 shipped official arm64, and what 11 months of running a fork taught me

02
WORKBENCH / UNLINKED
Distilling a 23-Playbook Plugin into 30 Lines: pstack and Engineering Judgment

A record of installing the pstack skill collection, removing it, and moving only its new ideas into the global prompts of three coding agents, with the selection criteria and how loading was verified

03
kube-ready-box
I Rebuilt My Vagrant Boxes for Rising OS CVEs, and Found Vagrant Cloud Shutting Down

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.

04
kube-ready-box · narwhal · nfs-quota-agent · narwhal-portal · clusterdeck · openforge · kubemetal
AI Agents and Vertical Integration of a Kubernetes Platform: Talk Notes

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.

05
kubemetal
KubeMetal featured as an AI agent reference in XERJ Corpus Hub

A KubeMetal implementation separating Colima VM profiles is now available as an AI agent reference in XERJ Corpus Hub.

06
beluga
Why we consolidated beluga-manager into the beluga monorepo

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.

07
narwhal · kubemetal
Soongsil Guest Lecture Recap: What Humans Should Hold in the Age of AI Agents

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.

08
clusterdeck
The Manual Steps I Kept Repeating on Every Cluster Rebuild, So I Built ClusterDeck

Why re-creating a Kubernetes cluster kept breaking SSH, kubeconfig, hosts, and CA trust by hand, and how a Profile fixed it

09
WORKBENCH / UNLINKED
A CI Job Can Print FAIL and Still Report Success

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

10
egovframe-launcher
Getting Started with eGovFrame Contribution: Lessons from Real PRs and Reviews

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.

11
WORKBENCH / UNLINKED
Proving Completion in Agent-Assisted Open Source Engineering

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

12
WORKBENCH / UNLINKED
📚 Re-documenting 10 OSS Projects — From Source State to First Verified Success

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.

TRACE RULE

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.