Yesterday I wrote about building.

Today reminded me what building actually means.

It is not just ideas coming together. It is not just clean screenshots, working features, and that good feeling when something finally starts looking like what I pictured in my head. Sometimes building means something breaks, the import works but the media does not display, or the thing that tested well yesterday exposes another problem today.

That is the part people do not usually see.

They see the release, but they do not see the audit. They do not see the cleanup. They do not see the small fixes, the wrong turns, the broken displays, the speed issues, the theme problems, or the long process of making something stable enough to trust.

But that is the work.

A tool is not real because it exists. It becomes real when it survives testing, frustration, correction, cleanup, and actual use. That is where I am right now with Bonumark Stream and the other things I have been building.

Still building. Still breaking things. Still fixing them. Still learning the difference between an idea that sounds good and a system that actually works.

One of the main things I’ve been working on lately is Bonumark Stream, a lightweight microblog system I’m building for people who want their short posts, notes, photos, and updates on a site they own instead of feeding everything into social media.

It is still early, but it is getting stronger.

Importers are coming together. WordPress import is working. X archive import is planned. Bluesky is next. Carceris is getting cleaned up for a future public release. Capsarium is becoming more than an idea.

It feels different than grinding out another article almost nobody may see.

This still connects to the same mission though.

Ownership. Portability. Independence. Building tools instead of just talking about standards.

Sometimes the work is not another post.

Sometimes the work is the system behind the post.

I’ve felt lighter since saying this out loud.

Not because everything is figured out, but because I stopped trying to force every part of my life into a public role.

I still care about the writing. I still care about recovery. I still care about helping people rebuild.

But I also care about living my life without turning every thought, project, lesson, or hard-earned piece of clarity into content.

Some things can just be lived.

That might be the part I needed to remember.

I released Carceris today.

It is an open-source, AGPLv3, self-hosted daily logging system for correctional facilities. Built with PHP and MariaDB. Designed for internal deployment, audit trails, role-based access, correction and void history, exports, backup/restore, and log delivery.

This started as a tool I needed. Now it is public.

https://github.com/jimlunsford/carceris

A little more clarity has come from this break.

I don’t think I’m stepping away from writing, coaching, or recovery work. I think I’m getting honest about the center of it.

At my core, I’m not a content machine or a polished recovery brand.

I’m a man who rebuilt his life, leads by example, tells the truth about what worked and what didn’t, builds useful things, and helps people when the moment is real.

That is the part I do not want to lose.

The writing still matters. The frameworks still matter. The recovery work still matters.

But I want the public version of me to match the real version of me.

Over a week ago, I paused publishing on JimLunsford.com.

I needed a break from the grind of adjusting to my new full-time role while also creating content for the site. I also needed time to work on the behind-the-scenes structure of the site itself. There were tasks I had been neglecting because I was caught in the constant churn of publishing new content.

Thankfully, those tasks are now complete, and I have a clearer outlook on what comes next.

My long-form article and essay cadence will slow down. Not because I am stepping away from the work, but because a lot of the work I have already put in now stands on its own. The core message is out there. The foundation has been built.

I do plan on resuming The Discipline Dispatches and Recovery Standards soon. Those shorter pieces still matter, and I believe they serve an important purpose.

The bigger picture is this: the content I create on JimLunsford.com is becoming the foundation for what I will teach through Disciplined Recovery. I already coach clients using the frameworks I have published. The next step is taking that published content and turning it into structured teaching modules that can be used on the Disciplined Recovery site.

Over the next few weeks, I will be building out Disciplined Recovery. There is a lot of research, planning, and execution ahead, but my goal is to have the foundation completed within the next 30 days.

I also want to be transparent about something else.

During this break from content creation, I have been working on a side project called Bonumark.

Bonumark is a Markdown-first content management system built around a simple idea: your work should stay readable, movable, and yours.

In the last 24 hours, it has actually become two projects: Bonumark Publishing and Bonumark Stream.

Bonumark Publishing will continue to be developed as I described in my previous post. Bonumark Stream will use the core of Bonumark, but it will be built for short-form posting, just like this microblog.

Right now, this site runs on WordPress with a custom theme I built about six months ago. As soon as Bonumark Stream is functioning the way I want it to, I plan to move this site over to it and release the project on GitHub.

I have a lot going on. That is obvious.

But all of it connects.

JimLunsford.com is becoming the source material. Disciplined Recovery is becoming the teaching system. Bonumark is becoming the publishing tool.

It is a lot of work, but it is the right work.

And I am good with that.

You don’t need a title to lead.

You’re already leading.

Your coworkers are watching. Your neighbors are watching. Your kids are watching.

They are learning what standards look like by watching how you live when nobody forces you to do the right thing.

So show them.

Own your choices. Stand on purpose. Keep moving with resilience. Live with integrity. Practice discipline. Empower people by becoming proof.

That’s leadership.

Not a title. Not a position. Not a badge.

A standard.

Now live it.

I’m building something called Bonumark.

It’s a Markdown-first content management system built around a simple idea: your work should stay readable, movable, and yours.

I don’t want content trapped inside a heavy platform where the system owns the structure, and the user has to beg for access later. Bonumark is being built for clean, durable publishing and portable content ownership.

The admin area will handle the normal CMS work: content, media, settings, appearance controls, users, roles, revisions, trash, imports, exports, system checks, and upgrades.

But the source stays clean.

Write inside the admin. Edit raw Markdown. Preview the final page. Import Markdown, text, HTML, RTF, DOCX, or ODT. Turn those files into editable Markdown drafts. Organize them. Clean them up. Publish them.

The public site publishes as fast static HTML.

The writing stays readable as Markdown. The media stays as real files. The site can be exported.

That matters to me.

Bonumark is being built around this line:

Write, import, organize, and publish clean content that deserves to stand.

When it’s ready, I’ll put the public release on GitHub.

I use AI in my work.

Some people hear that and immediately think the machine is doing everything.

Wrong.

AI did not get sober for me at 2:33 a.m. AI did not live through my addiction. AI did not lose what I lost. AI did not rebuild my body, my mind, my marriage, my discipline, or my identity. AI did not sit with the pain. AI did not carry the consequences. AI did not earn the scars.

I did.

What AI does is sit in the workshop with me.

I bring the lived experience. I bring the doctrine. I bring the standards. I bring the direction. I bring the correction when something sounds weak, fake, too soft, too polished, too generic, or not true to what I believe.

And trust me, there is a lot of correction.

This is not me typing one lazy prompt and pretending I created something. This is hours of back and forth. It is arguing with ideas. It is tightening language. It is forcing the work to line up with my actual life and not some empty motivational garbage.

If I told AI to create something without me thinking, challenging, correcting, and owning the final product, then yes, that would be a problem.

But that is not what I do.

I use AI like a tool.

The story is mine. The pain is mine. The discipline is mine. The standard is mine. The final call is mine.

AI helps me organize the fire.

It does not create the fire.

I love how people assume discipline means I have everything under control.

No.

Discipline means I keep moving while everything is not under control.

There is a difference.

Some days I am dialed in.

Some days I am holding my life together with black coffee, pushups, protein, stubbornness, and a cat staring at me like I owe him money.

But I still show up.

That is the whole point.