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
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.

02
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

03
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.

04
WORKBENCH / UNLINKED
August 2026 OSS Implementation Update — What Is Actually on main

A main-branch, evidence-based update on Narwhal, NFS Quota Agent, KubeMetal, ldapium and OpenForge as of August 2026.

05
WORKBENCH / UNLINKED
Why Does Code Survive While Engineering Decisions Disappear?

Why I introduced ADRs while managing shared OSS engineering standards in OpenForge, and how ADR → Standard → Automation → Adoption keeps decisions traceable.

06
WORKBENCH / UNLINKED
How I Reworked the CNE UI with AI and a Design System

How Projects, Project Detail, Notes, Tech Digest, Docs, Speaking, and shared navigation were brought under one design language, with AI used as an execution partner.

07
WORKBENCH / UNLINKED
GitHub Pages Deployment Concurrency After the Bun Migration

A practical record of how an older Pages deployment was cancelled after a newer main revision arrived, and how to interpret that state correctly.

08
WORKBENCH / UNLINKED
Migrating from npm to Bun — From the First Failure to CI Evidence

A practical record of migrating dasomel.github.io from npm to Bun 1.4, including the first failed deployment, measured CI performance, and the removal of duplicate production builds.

09
WORKBENCH / UNLINKED
Bun 1.4 Migration — Visual CI Evidence

A visual companion to the Bun migration case study, using measured GitHub Actions timings and pipeline diagrams.

10
WORKBENCH / UNLINKED
AI-Era Open Source: Build the Bathhouse, Not the County Office

A review of my OSS projects through a user-friction lens inspired by the bathhouse metaphor: Narwhal, Beluga, KubeMetal, eGovFrame Launcher, nfs-quota-agent, and ldapium.

11
WORKBENCH / UNLINKED
🧭 Operating Seven OSS Projects as One Engineering Portfolio — Building a Common Standard with OpenForge

How Narwhal, Beluga, KubeMetal, kube-ready-box, ldapium, nfs-quota-agent, and OpenForge became one OSS Engineering Portfolio with shared engineering and supply-chain standards.

12
WORKBENCH / UNLINKED
🤖 How I Build Open Source with AI — Lessons from Developing Narwhal

How I use ChatGPT, Claude, Gemini, and Copilot together in real open-source development, and how AI is changing my role as an engineer while building Narwhal and other Cloud Native projects.

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.