Reconstructing Bosun PKM with evidence

This retrospective covers recovery work from August 29, 2026. It was prepared after the event; its metadata and RSS entry record the actual first-publication time rather than the event date.

Bosun PKM began with a practical question: how can people keep useful notes, tables, and recipes accessible when the applications around them change?

That question has led us toward a small set of portability tools. FreENEXt is focused on note exports, FreeMyData on difficult tabular information, and FreeMyRecipes on recipe collections. Bosun PKM connects that work to a broader goal: durable personal archives built from files people can inspect and carry forward.

During this reconstruction, we found promising code alongside ambitious descriptions of what it could do. Rather than repeat those descriptions, we started tracing each claim back to source code, fixtures, tests, deployment layouts, and public evidence.

That work is less dramatic than a launch announcement, but it matters. A parser is not proven merely because a function exists. A public tool is not ready merely because a branch was merged. File formats have edge cases, browser behavior differs from test harnesses, and deployment details can separate working code from a working service.

What reconstruction means here

Our recovery work has centered on a few habits:

• preserve useful implementation history before reorganizing it;
• separate implemented behavior from ideas and historical claims;
• add tests around the formats and paths we can actually demonstrate;
• make deployment layouts explicit instead of assuming local and public environments match;
• describe unfinished work as unfinished.

This evidence-first approach is helping us turn scattered experiments into projects that can be reviewed, maintained, and tested with other people.

Where we are going

We want these tools to make common portability jobs more approachable: recovering notes from exports, extracting useful tables, and preserving recipe collections in reusable files. We are preparing those paths for public testing, but deployment and public verification still come before any release claim.

If you have an awkward export, an old archive, or a workflow that became difficult to move, your experience can help us choose better tests and notice assumptions we missed.

Join the Bosun PKM testing community. We will share test invitations there once the relevant builds and public surfaces have been verified.