Section 1 – Preface

I have worked in software development and information technology for more than three decades, across roles that span engineering, system design, deployment, support, and organizational decision-making. During this time, computing has advanced dramatically in technical capability.

At the same time, I have repeatedly observed how everyday computing has failed to evolve in ways that respect human work: its rhythms, its limits, its need for clarity and meaning. Many modern systems are powerful, yet leave people fragmented, fatigued, and disengaged. The quiet joy that once accompanied building and using software has often been replaced by constant pressure and cognitive noise.

This white paper is a first attempt to articulate a clean-slate approach to a digital system whose primary purpose is to support human reasoning, collaboration, and intent. The ideas presented here draw on long practical experience, extended reflection, and the Human Code Principles. They are offered not as a product announcement, but as an invitation to rethink what operating systems could, and should, optimize for.

JanOS (for January OS, as in “a new start” or “doorway”) is an attempt to restore joy in computing. You are welcome to join the open discussion to shape the future of this vision.

How to Read This Paper

This paper is not a product specification, implementation guide, or manifesto. It presents a conceptual framework for rethinking operating systems around human work, intent, and long-term coherence.

Readers are not expected to read this document linearly or in full. Different sections are intended for different audiences:

• Sections 2–4 establish scope, intent, and boundaries.
• Sections 5–10 describe the core architectural principles of JanOS.
• Sections 11–16 explore consequences and implications of those principles.
• Sections 17–23 provide context, positioning, open questions, and closure.

Some sections are deliberately more conceptual, while others are more structural or technical. Repetition across sections is intentional where it reinforces core ideas from different perspectives.

The paper favors clarity and restraint over completeness. Many questions are left open by design. Readers are encouraged to approach the text as a basis for reflection and discussion rather than as a finished design or technical implementation plan.