There's a version of "building in public" that is pure performance — carefully curated progress updates designed to build an audience. That's not what I'm doing here.

The version that matters to me is building in public as a form of inquiry. When I commit to publishing work-in-progress frameworks like the Autonomy Chain or the Discipline Stack, I'm forced to articulate what I actually think and why. That articulation is itself a research act. It reveals gaps, contradictions, and unstated assumptions that stay hidden in private notes.

Writing about a half-formed framework often reveals its structure. The Capability-Governance Gap, for example, didn't start as a named concept. It emerged from trying to explain to myself why certain experiments in OpenEnterprise kept failing in the same way. The act of writing made the pattern visible.

This is different from peer review, which evaluates finished work. Building in public is more like thinking aloud — it creates opportunities for course correction before ideas calcify into commitments.

The risk is premature judgment. Not all frameworks survive first contact with articulation, and some ideas need incubation before exposure. I keep some work as drafts — ideas that are real but not yet ready for scrutiny. The practice requires judgment about what to share and when.

But on balance, I believe the researcher who publishes provisional thinking discovers more than the one who waits for certainty. The friction of explanation is a feature, not overhead.