Write down the why behind the build.
Architecture, implementation notes, workflows and technical decisions. Built for reference, not for release notes.
Static finding aid
All notes are available below without JavaScript. Browse a category, select a tag anchor, or use your browser’s Find command for a keyword. Interactive live search and shareable filters are available after enabling enhancements.
Lab Review
MiniX lab review: keeping a multi-host application kernel inspectable
A public lab review of MiniX: how contracts, controllers, host adapters and manifests create a visible boundary between shared application intent and H5 or WeChat runtime behavior.
PlumeGo lab review: using reference services to test HTTP boundaries
A public lab review of PlumeGo reference services: how runnable examples and bounded use cases test whether a small Go HTTP kernel remains explicit under application pressure.
Architecture
PlumeGo architecture: explicit Go HTTP boundaries for humans and agents
How PlumeGo combines a standard-library-only Go kernel, explicit route wiring, stable modules, and machine-readable specifications for inspectable HTTP services.
Designing system boundaries before service boundaries
A practical way to turn an ambiguous product surface into stable technical seams before choosing infrastructure.
Engineering Notes
Treating engineering content as an interface
Why a technical article should expose a stable, useful structure for humans, search systems, and future maintainers.
Workflow
Static-first systems for developer-facing sites
How we keep a content-heavy technical surface fast, deployable, and easy to maintain without introducing an application backend.
Best Practice
Maintaining a small interface as a product scales
A field note on keeping technical surfaces understandable when projects, tools, and experiments begin to multiply.