Sixteen months ago, I described a business operating system for the age of AI. I deliberately left it unnamed. Today I can finally tell you what it became.

In May 2025, I published an essay called:

I was laying the foundation for something I could not yet fully see. I knew its five building blocks: mental models, principles, metaphors, frameworks, and AI agents. I knew it had to be rooted in craft. And I knew it could not be another productivity template with AI sprinkled on top.

I ended with a promise:

I haven’t named this system publicly yet.

Today, I am keeping that promise.

The name is CraftOS™.

But I owe you more than a name. I owe you the story of what changed between that essay and this one—because CraftOS did not simply acquire more features. My understanding of the problem changed.

The year I did not rush

The dominant instruction in AI has been: build. Ship something. Move fast. Automate a workflow. Connect legacy systems with AI through fancy MCP connectors and AI-written APIs. Launch agents. Orchestrate agentic flows. Loop. Graph. Do the AI thing—whatever that happens to mean this week.

All of the above have their value. I did something less fashionable. I thought.

For much of the year, I thought about what work was becoming. I studied what the machine was good at, what human beings remained responsible for, and what separated using an AI tool from becoming native to an AI-shaped world.

To be honest, I took longer than I should have. I was thinking and learning, but I was also circling the problem instead of committing to a form. Still, the delay was not empty. It was diagnosis before prescription. It forced me to question the work itself. Otherwise, we will use extraordinary technology to reproduce yesterday’s thinking at greater speed. That is not transformation. It is confusion—faster.

There was building during this period, but it happened close to the work. I built for myself first. I experimented with personal agents, memory, context, tools, controls, and recurring work. I began bringing the same ideas into Atlantis Leadership, a business where the work involves real people, real relationships, and real consequences. The leaders in our organization and their teams continue to give me room to experiment. That matters. In an existing business, technical permission is not enough. Change also requires earned trust: enough credibility with the people affected by the system that they will help test a different way of working.

The thinking shaped the building. The building corrected the thinking.

That loop became CraftOS.

From five building blocks to a working system

Looking back, I can see the progression more clearly than I could while living through it.

In early 2025, CraftOS was primarily a system of thought. Mental models simplified complexity. Principles guided decisions. Metaphors made difficult ideas memorable. Frameworks turned thinking into action. AI agents carried out parts of the work.

Then I treated Notion as a possible home for those pieces—a practical canvas where the system could become visible. I thought in Lego blocks: useful modules that could stand alone and also connect. I imagined building agents for my own business, learning through use, and eventually helping others do the same. My mind was connecting like this: use the system and refine it in real work.

That early architecture was directionally right. But it was incomplete.

I was right to think about the container. But the system was not the files and content inside Notion. At the time, the word I needed had not yet entered the lexicon. That word—harness—entered the public vocabulary in February 2026. And it led to a deeper question. Not only, Where does the system live? but What must the system do?

Today, CraftOS has two inseparable layers:

1. A thinking layer that helps us identify the craft, judgment, principles, and standards at the center of the work.

2. An execution layer that turns that judgment into a system of agents, memory, tools, controls, and reusable units of work.

The first layer asks better questions. The second makes the system operational.

That is the evolution: from a library of building blocks, to a workspace or container, to an execution environment—the harness—and finally to an operating architecture for human judgment and machine capability.

AI nativity is not tool adoption

I have been using the phrase AI native for some time. It now needs a sharper definition.

AI nativity is not measured by the number of tools we use. A tourist can carry an excellent phrasebook. A native does not translate every sentence before speaking.

AI nativity is the degree to which a person or organization has reimagined its work on the assumption that capable AI is part of the operating environment from the beginning. It’s not a patch on the legacy systems. That is why AI nativity is not about business transformation through AI. It’s re-envisioning a business with AI from the get-go.

Most AI adoption still begins with the old work and asks how to perform it faster:

• How can AI write this email?

• How can it summarize this meeting?

• How can it automate this workflow?

• How can the same output require fewer people?

These can be useful questions. They are simply not the first-principles question.

The first-principles question is:

If we were designing this business today, with these capabilities available from the beginning, what would the work become?

That question does not merely automate a process. It opens the process. It asks which steps exist for good reason, which are historical residue, where judgment truly matters, and what only a human being should decide.

Picture a score. One hundred is the asymptote: every module of the business reimagined, with the craft amplified rather than replaced.

Most businesses I encounter sit at ten or twenty—not because they lack tools, but because they are diligently answering the wrong question, or they think they cannot afford AI nativity with existing legacy workflows, systems, employees and paying customers. How a business can raise its AI nativity score is a question for another day. The answer will depend on the specifics of the business.

This led me to an inversion I did not expect: AI nativity is not only a destination. It can become a condition for deeper thought.

As parts of my operation became more capable—retaining context, preparing work, organizing knowledge, and carrying tasks forward—they returned something precious to me: time to think. Better thinking then produced better systems. Better systems created more room for thought.

I could begin this way because my AI work had no employees, inherited workflows, or legacy systems. Treating myself as a business—and that is a useful way to look at it—I carried very little baggage. Applying this within an existing operating organization was different. It had real people and real processes. Bringing AI nativity there required trust from the leaders in our organization and their teams.

Nativity funds thought. Thought compounds nativity.

That is the flywheel.

The durable value is moving up the stack

During this same period, the AI field widened its focus.

First came prompt engineering: learning how to ask the model well. Then context engineering and loop engineering: giving the machine the right memory and letting it act, inspect the result, and try again. Now the attention is moving toward harness engineering, graph engineering, and ontology engineering: building the runtime the model inhabits, mapping the work and its relationships, and naming the units of work precisely with the right provenance.

The frontier is no longer only the intelligence inside the model. It is also the system around it: memory, tools, permissions, feedback, state, evaluation, and human control.

That system is the harness.

Think of a car.

The model is the engine. Engines matter, and some are better suited to particular work than others. But engines are increasingly interchangeable. Today the engine may be Muse. Tomorrow it may be Astra, Fable, or multiple engines serving multiple purposes. The car does not depend on a single engine remaining under the hood.

The accelerator is autonomy: how much the system may do without stopping to ask.

The brakes are guardrails: approvals, limits, and kill switches.

The gears are modes of operation: from supervised drafting to bounded execution.

The gauges are observability: the ability to see what the system is doing, what it used, and where it may be wrong.

The steering is human intent.

Most important, the destination remains a human choice.

This is where I would sharpen one of my earlier beliefs. The model creates value, but the more durable value moves toward the harness—because the harness contains the context of the business and its way of working. It carries the permissions, memory, standards, and judgment that a generic model does not possess.

My own path through this became very concrete. It began with Garry Tan’s GBrain, an open-source memory layer for agents. Then came Meta’s personal agent Muse. I installed GBrain through my Codex harness. Then came the Muse–GBrain integration. Then my own system, my “K-brain.” Grokbots are next. Not yet.

My personal agent, Hannah, is one inhabitant of this harness. The names will change. The models certainly will. What matters is the architecture that lets all of them serve a coherent purpose.

I have a state-of-the-art Mac mini M5 Pro coming to run my CraftOS lab. The 48 GB unified-memory beast—with its 15-core CPU, 16-core GPU, and 16-core Neural Engine—will be a rich playground. I plan to set up multiple sub-harnesses and environments: Claude Code, Codex, GeminiLM, Muse, Grokbot, OpenClaw, and Hermes. I will use them to run my personal agents and K-Brain and to do work for our organization.

I claim expertise. I do not claim completeness. In AI, completeness would be a confession that we had stopped looking. New capabilities arrive constantly. Just recently, a fast, general-purpose classifier called Jev appeared. It performs classification and returns the results in a structured format—remarkably fast. In my testing, it did this work better than any of the language models I tried. Testing it was fun. It is the kind of development that forces us to revisit our assumptions about which jobs require a large generative model.

The missing unit: work itself

A harness still needs something to operate on.

The smallest piece is a work unit: a bounded piece of executable work with an expected outcome. Connect work units through dependencies, decisions, and changing state, and we get a work graph. Bound part of that graph around a meaningful, repeatable outcome and we get what I call a WAI Module™. WAI means Work by AI: work is the primary unit, performed by the AI module. It does not merely mean working with an AI module.

Consider a proposal.

In many companies, proposal creation is a familiar workflow: gather notes, find an old document, copy the structure, draft the language, check the numbers, circulate it for review, and hope the best thinking survives the handoffs.

Automating that workflow would make the same chain move faster.

A WAI Module begins elsewhere. It asks:

• What must be understood before a proposal should exist?

• What does an excellent proposal look like here?

• Which judgments belong to an expert?

• Which research and preparation can an agent perform?

• What evidence must be visible?

• Where is approval required?

• What should the system learn after a win or a loss?

The result is not simply an automated document. It is a bounded operating capability. The module carries the standards, context, controls, and feedback needed to produce the outcome repeatedly—without pretending that judgment has disappeared.

The organization’s craft is encoded in the module. The machine extends its reach.

I eat my own dog food. The first modules were built for my own personal assistance. Now the same approach is going into our organization, where it will serve its leaders and their teams. One module at a time. Thinking in action, not thinking about action.

Craft is the part we should not automate away

Why call it CraftOS?

Because craft has always been the point.

When I launched the Craft publication, I began with Cal Newport’s craftsman mindset in

: focus on what we can offer the world, build rare and valuable ability, and become so good we cannot be ignored. I was writing about the craft of the individual.

CraftOS extends that idea to the enterprise.

Every good business contains knowledge that is difficult to see from the outside. A practiced eye notices what a novice misses. An experienced leader hears what was not said. A skilled advisor knows when the standard process is wrong for the situation. A great team shares an understanding of what good looks like, even when that understanding has never been documented.

That judgment is the real asset.

If we automate only the visible steps, we risk stripping the craft out of the work. If we design the harness carefully, we can do the opposite: make the craft explicit, preserve it, teach it, improve it, and allow it to compound.

In a world of increasingly abundant machine intelligence, generic output becomes cheaper. Specific custom harnesses, judgment, taste, accountability, and earned trust do not.

Craft is not a nostalgic defense of human work. It is the design principle for deciding what the human-machine system should become.

An operating system—not an AI product with business language attached

I want my non-technical readers to hear this clearly: CraftOS is not an AI product with a little management philosophy attached.

Four of the five original building blocks—mental models, principles, metaphors, and frameworks—are ways of thinking. Only the fifth was the agent. That proportion was not accidental.

The Window and the Mirror helps a leader distinguish accountability from blame. The Chinese Bamboo Tree makes invisible preparation easier to understand. The Iceberg reminds us that the forces most likely to derail the work may sit below the visible surface. A framework turns insight into repeatable action. A principle helps us decide when the framework does not fit.

AI does not make those distinctions for us. It increases the consequences of whether we make them well.

This is why CraftOS needs both faces:

• The human face asks what the business is, what it values, and where its craft lives.

• The machine face builds the harness through which that craft can operate at greater scale.

The thinking layer without execution remains a collection of good ideas. The execution layer without the thinking becomes efficient emptiness.

CraftOS is the bridge.

The name—and the work—ahead

Giving the system a name does not mean declaring it finished. It gives the work a center of gravity—something I can explain, test, and improve in public.

The work is not finished. It should not be.

The technology changes too quickly for a serious practitioner to declare victory. Models will improve. New kinds of memory and decision systems will appear. Today’s architecture will be tested by tomorrow’s capability. Completeness in this field would not be a badge of confidence. It would be evidence that we had stopped looking.

I am building CraftOS™. As time permits, I will also write in public about the components taking shape. Some editions may open the hood on the machine: memory, controls, agents, work graphs, and WAI Modules. Others may return to the thinking layer: mental models, principles, metaphors, and the nature of work and craft itself.

The car in this piece is more than an analogy. It is also a map for what comes next. In a future edition, I will open the hood on the control layer: how the brakes work, how the gauges work, and how we remain in command of a system that can act on our behalf.

We need both.

Sixteen months ago, I could see the pieces but not yet the system. Today, I can name the system and state its purpose:

CraftOS™ is an operating architecture for identifying human craft, encoding it into AI-native work, and keeping human judgment in command as the system scales.

The engine may be rented.

The harness must be custom-designed and owned.

The craft must remain ours.

AI disclosure: The underlying ideas, judgments, lived examples, and final editorial choices are mine. I used AI as a research and editorial collaborator in developing this draft.

CraftOS™ and WAI Module™ are claimed trademarks.

Follow me on LinkedIn

Happy Mother’s Day to all the moms out there—you’re the real leaders, mentors, and builders of this world.

This week, I want to take you behind the scenes into something I’ve been quietly building—something that bridges my decades of leadership, coaching, and entrepreneurship with the new opportunities of technology.

Last week, I published the first article on Craft. If you haven’t had a chance to read it, here it is: “Become So Good They Can’t Ignore You”. I hope it gave you a glimpse of how I’m thinking about mastery, positioning, and leadership in today’s world.

But this week, I want to widen the lens.

A New Kind of Business Operating System

I’ve started laying the groundwork for what I believe can become an innovative Business Operating System (BOS)—a framework to help solopreneurs, creators, and entrepreneurial teams operate with greater clarity, focus, and momentum.

If you’re wondering, “What’s a Business Operating System?”—great question. It’s not software in the narrow sense, though technology will play a role. Think of it more like an integrated framework of principles, practices, and processes that guide how you run a business.

Some examples of existing BOSs include:

• EOS (Entrepreneurial Operating System) from Traction by Gino Wickman

• Scaling Up by Verne Harnish

• OKRs (Objectives and Key Results) popularized by Google

• The Four Conversations from Jeff Goff and Bruce Bodaken (not to be confused with the Four Conversations by Blair Enns)

• Even Agile and Lean Startup could be considered BOS frameworks in certain contexts

Each of these systems offers a structure to align people, priorities, and actions. I’ve learned from many of them. But I’ve also seen their gaps—especially in a world increasingly shaped by AI, distributed work, solopreneurship, and creator-led businesses.

I’m not just remixing what’s already out there. I want to build a BOS rooted in craft—in the deeper pursuit of mastery, integrity, and human-centered work. This isn’t a “plug and play” dashboard or just another set of templates. It’s about embedding models, principles, frameworks, metaphors, and AI agents that unlock agency and insight.

2025! How We Got Here: Why This Moment Matters

I’ve been reflecting on how quickly things have shifted beneath our feet. In just a few years, we’ve watched AI evolve from a tool we used to an agent that can now work alongside us—not just answering questions, but taking action.

This shift didn’t happen all at once. It’s the result of two powerful streams of progress finally coming together.

The first stream is what we’ve seen in large language models. For years, researchers worked toward systems that could process and generate human language, but they were limited—great at matching patterns, not so great at understanding meaning.

Then, in 2017, something remarkable happened: the introduction of the transformer architecture. This breakthrough quietly changed everything. It allowed AI to process information with context, connecting ideas across entire documents rather than just sentence by sentence. That’s what paved the way for models like GPT-3 and GPT-4—AI systems that could write code, solve problems, and even have thoughtful conversations, all without being explicitly programmed for each task.

By the time ChatGPT arrived in 2022, we finally had an AI that could talk with us, reason with us, and explain things in ways that felt human. But even then, it had one big limitation: it could suggest what to do, but it couldn’t do it. Even in those responses, there’s this freewheeling “hallucination” problem—when generative AI gives totally bizarre answers or fictitious “facts.” Beneath all the shine, LLMs are stochastic engines—estimating the next words with probabilities. But there are ways to steer this “creativity” with prompt tuning or temperature adjustments, for those who know how.

Now onto the second stream: automation. For years, businesses automated repetitive tasks—first with simple scripts, then with software bots that clicked buttons and filled forms across systems. Over time, these bots got smarter, using machine learning to classify documents or read customer emails. But they were still rigid, bound by predefined rules.

For a long time, these two streams ran parallel. One could understand. The other could act. But neither could do both.

Now, they’re merging. And that’s giving rise to something new: AI agents that can both reason and execute.

These agents don’t just answer—they plan, decide, and take steps on your behalf. They can read an email, decide what needs to happen, call the right tools or APIs, and carry out the task. They’re moving from passive tools to active collaborators.

👉 In a world like this, human creativity becomes the ultimate competitive advantage. AI will increasingly handle the busywork, the coordination, the procedural steps. But it’s human imagination, insight, frameworks, and originality—the ability to connect dots in unexpected ways—that will set your work apart. We’re entering an era where tools won’t define you; what you do with them will.

That’s why I’m building what I’m building. Not just to keep pace, but to help shape a way of working that preserves clarity, intention, and the human touch in a world where intelligent agents are becoming part of the team.

We’re not just upgrading our tools. We’re stepping into a new era of how work gets done.

Why Notion?

For now, I’m using Notion as the workspace where this system lives. Notion is beloved by many solopreneurs, creators, and founders because it’s flexible, customizable, and approachable. But my goal isn’t to build another “Notion template” for productivity.

Instead, I’m using Notion as a canvas—a space where ideas, frameworks, and workflows can live and breathe, taking shape in ways that are both structured and personal.

Eventually, this will evolve into something more technological underneath. But at every stage, the goal is to make it tangible, actionable, and human.

Models, Principles, Metaphors, Frameworks, and AI Agents: The Building Blocks

As I work on this BOS, I’m drawing from five kinds of building blocks:

✅ Mental Models—conceptual shortcuts and ways of seeing the world. Think of Shane Parrish’s Farnam Street or Charlie Munger’s “latticework of models.”

✅ Principles—fundamental truths or guidelines for action. Like Ray Dalio’s Principles or the timeless wisdom of Stoicism.

✅ Metaphors and Analogies—narratives or images that help us understand abstract ideas. One of my favorites is the story of the Chinese bamboo tree, which grows underground for years before suddenly shooting up 80 feet.

✅ Frameworks—practical, structured ways to apply thinking to action. I’m especially inspired by the frameworks I’ve learned from Win Without Pitching: positioning, constraint, value conversations, and creating desirability rather than chasing sales.

✅ AI Agents—intelligent digital workers that don’t just inform decisions—they actively carry them out.

Each of these will weave into the BOS:

• Models simplify complexity

• Principles guide decisions

• Metaphors inspire meaning and perspective

• Frameworks provide structure for applying knowledge in the real world

• AI Agents execute the work that powers your business or creative practice

In my LinkedIn posts and Substack Notes, I’ll continue sharing individual models, principles, metaphors, frameworks, and AI agents as I explore them.

My Promise to You

To the 300+ subscribers (LinkedIn + Substack) reading this—thank you. I don’t take your attention for granted.

I promise to deliver immense value here: thoughtful, reflective, and useful content that helps you grow, lead, and build.

Everything I’m building starts with a simple belief: craft matters.

I haven’t named this system publicly yet. But one day soon, I hope it will empower you to navigate the future with more agency, confidence, and clarity.

Feel free to share this newsletter and subscribe at craft.kakani.co. For now, it’s free for everyone—use it.

Until then, stay tuned. More to come.

AI Disclosure

AI was used to research and structure my findings. It was also used to proofread. The icons are AI-suggested. The research conducted only validates and augments my experience applying these building blocks for many years and decades in entrepreneurship.

In other words, this is not an AI-generated mashup—it’s drawn from my own experience. The words, composition, tone, and style are mine alone. As always, I cannot and will not delegate that to AI.

It’s only fitting that I begin here—with the idea of craft.

Everywhere we hear about starting with the why. But then why in the world would I start with the how? You'll have to read this short article to know the answer.

There are so many places I could start this publication. The list is endless: leadership, coaching, mentorship, personal development, passion, mission, purpose, core values, sales, marketing, technical skill, and so on.

But I choose to start with this.

Craft denotes excellence in work. Deep work, which is real work.

Because craft is not just what we do. It’s how we do it. It’s the difference between a job and a calling, between dabbling and dedication, between surface and substance.

Work, Not Job

Let me be clear. I’m using the term work, not job. Work is broader. It includes entrepreneurship, creative pursuits, leadership, coaching, teaching, among other things. Our work is elevated to an art form when it becomes our craft—when we build something of great value.

What If I’m Not Passionate?

Here’s a hard question I’ve asked myself in the past:

What if I’m not passionate about what I do? At least not right now. But I’m still producing great results. Does that matter?

That’s where the concept of craft first resurfaced in my mind.

I had to dig deeper—past the romanticized stories we often hear about “doing what you love.”

I started noticing something: some of the most fulfilled and excellent professionals I know didn’t begin with passion. They began with effort. They became passionate over time because they committed to getting really, really good at something that mattered. In fact, where they started in life and what they became good at eventually were totally different. At first, they didn’t even know what they were passionate about. Eventually, when they became so good that others couldn’t ignore them anymore, they came across as passionate.

There is a name for it—pivot. To repeat: many entrepreneurs, founders, creators didn’t know the particular domain they would eventually become successful in. Not just the domain—they didn’t even know the specific kind of work they were going to do. But over time, they slowly but surely zeroed in on the domain and the kind of work. They became damn good at it. That’s when others started noticing the “passion” in them.

That’s when I returned to Cal Newport’s book, So Good They Can’t Ignore You. His contrast between two mindsets hit home.

Passion mindset and craftsman mindset.

“The craftsman mindset focuses on what I can offer the world. The passion mindset focuses on what the world can offer me.”

What matters is whether we bring the craftsman mindset to our work.

The Craftsman Mindset

Let’s contrast this with what most people believe they should go after—the passion mindset.

The craftsman mindset focuses on what we can offer the world—the value we can add. The passion mindset focuses on what the world can offer us—the opportunities others can give so we can fulfill our inner desires, our passion.

The craftsman doesn’t ask, “Do I feel passionate today?” They ask, “Am I better today than I was yesterday?”

The craftsman doesn’t obsess over perfect conditions. They show up. They build. They iterate.

The craftsman mindset is output-focused, not emotion-focused. It’s not about waiting for inspiration. It’s about deliberate practice, creating value, and doing hard things with discipline and clarity.

It asks us to reject the modern obsession with finding the perfect work, or perfectionism in our work—and instead turn whatever work we do into something excellent, meaningful, and worthy of pride—over time.

“No one owes me a great career,” Newport writes. “I need to earn it—and the process won’t be easy.”

He’s right.

The Foundation of Great Work

So what defines great work?

• Creativity: Not novelty for its own sake—but stretching the boundaries of what’s possible in our domain.

• Impact: Solving real problems, creating things that endure, improving lives.

• Control: Gaining autonomy by first building mastery and trust. Then shaping our environment to support excellence.

But here’s the key: these rewards come after craft. Not before. We can’t shortcut our way to them through appearance, personality, or branding. We earn them by becoming so good they can’t ignore us.

When the Craft Isn’t Worth Pursuing

Newport says that not every path is worth applying the craftsman mindset to. There are three disqualifiers:

1. If it’s nearly impossible to build a rare or valuable skill.

2. If the work is completely useless.

3. If we fundamentally dislike or distrust the people we’d be working with.

These are non-starters. We still need to choose wisely. But once we do—commit fully.

The Craft of Craft

In this publication, Craft, I’ll explore what it means to build a life—and a business—rooted in deep skill, clear thinking, and authentic value creation.

My goal through craft.kakani.co is to bring everything I’ve learned over the past two and a half decades. Understanding our craft and being willing to put in the time and effort will eventually lead to mastery. Mastery becomes expertise when taken to the next level.

Blair Enns writes in the first proclamation of Win Without Pitching: “Expertise is the only valid basis for differentiating ourselves from the competition. Not personality. Not process. Not price.”

In the seventh proclamation: “We will view our claim of expertise as a beginning and as a rallying cry for perpetual progress. Once focused, we will work to add to and deepen the skills, capabilities and processes from which we derive our expertise, and we will commit to the idea that continuous learning is mandatory.”

I’m not saying processes are not important—but only after getting on the path to expertise. When we seek to develop deep value to share with others.

In this publication, I hope to write about every single aspect of entrepreneurship and business—whether we are solopreneurs, creators, small business owners, startup founders, or executives. At the foundation of everything we do in business is craft and expertise. In time, I’ll also show how to “borrow” expertise from your organization (if you have one) and beyond—even when just getting started. Blain Enns says, "claim of expertise". But this can't be a claim forever. Eventually, we'll have to build our own expertise—rapidly.

Once we are on the path to expertise—sales and marketing, team building, leadership, and everything else becomes easier. Not just easier, but also meaningfully differentiated from competition. That’s how we escape the tyranny of the red ocean, the devil that is commoditization—that undifferentiated goo in which we will otherwise swim with a million others.

Craft, therefore, is not a space for shallow hacks or superficial motivation. It’s for those who want to do serious work (and reap the commensurate rewards) with integrity, creativity, and enduring impact.

Sometimes the craft is visible—a film, a product, a performance. Sometimes it’s invisible—coaching, mentoring, managing a team, raising a family.

But in every case, craft is unmistakable. The how behind the what, where, and why.

This is where we begin.

And by the way, I did eventually become passionate about my work—to answer my own question posed earlier. You can too, eventually.

Stay tuned to this space. Subscribe for free at craft.kakani.co. It takes just a few seconds to put in an email here—and from then on, these articles will land directly in your inbox, never filtered by an algorithm.

AI Disclosure: No AI was used to research or write this article. Every word is mine. I like em dashes—quite a bit, actually. I use them liberally. That’s just my style—not a machine’s.

✍️ Welcome to My Writing Hub

I’m Chak Kakani — a computer engineer turned entrepreneur, mentor, and systems thinker, with a deep curiosity about how things work, how people lead, and how civilizations are built and preserved.

After 25+ years building companies, mentoring leaders, and exploring systems thinking across disciplines, I’ve launched three interconnected publications — all designed to share signal, not noise.

At kakani.co and my associated platforms, I share insights through short dives, deep explorations, and cross-disciplinary thinking — spanning technology, leadership, culture, philosophy, economics, and more.

All three of my Substack publications are currently free to subscribe.

I believe in creating genuine value first — and if that resonates, everything else will follow.

📚 What Are the 3Cs?

The three pillars that organize my writing:

🔹 Chips

Exploring the deep infrastructure that powers AI and emerging technologies — starting from semiconductor chips, but going much further.

At chiptechtalk.kakani.co, I cover:

• Semiconductor manufacturing (fabs, foundries)

• Compute (GPUs, TPUs, custom silicon)

• Data centers, energy systems, and supply chains

• Global trade routes and geopolitical choke points

• LLMs, chatbots, and application layers higher up the stack

• Industrial policy and technology strategy

If GPT is the magic, these are the factories, electrons, and global systems behind the spell.

🔸 Craft

Craft is about leadership, influence, and personal development — building resilient people, strong teams, and enduring organizations.

At craft.kakani.co, I explore:

• Leadership without ego

• Coaching and mentorship that compound over time

• Strategic communication and persuasion without manipulation

• Building high-trust teams

• Selling without pitching (inspired by Win Without Pitching)

• Personal development, productivity systems, and decision-making frameworks

Craft is not about hustle culture or quick wins.

It’s about deliberate mastery.

🟠 Curiosity

Curiosity is the open field where philosophy, economics, governance, and culture intersect — with freedom and rationality at the center.

At kakani.co, I explore:

• The roots of Western civilization and its moral framework

• Political philosophy, governance systems, and history

• Economics, culture, freedom, and societal design

• Observations about mental models, tools for sharper thinking, and cultural shifts

• Smaller curiosities that don’t fit neatly into “tech” or “leadership” but still matter

Some explorations are grand, others are small.

Curiosity doesn’t have to be monumental — it just has to be real.

🧱 Subscribe and Join the Journey

I’m building three dedicated publications:

🔹 chiptechtalk.kakani.co — Chips and AI Infrastructure

🔸 craft.kakani.co — Leadership, Craft, and Influence

🟠 kakani.co — Curiosity, Culture, and Timeless Thinking

Each is currently free to subscribe.

Each explores a different but interconnected piece of how our world works — and how it can be built better.

✍️ My AI Writing Policy

Across all three publications, I use AI thoughtfully — as a research assistant and idea partner, not as a ghostwriter.

I use AI for in-depth research, idea development, and to explore connections across domains.

But every word you read here is mine — shaped by my own thinking, judgment, and experience.

Not just the words, but the tone and style are mine as well.

I cannot and will not delegate that to AI.

No AI-generated fluff.

No click-driven shortcuts.

Only clarity, depth, and deliberate thought.

That’s my promise.

🚫 Community Standards

This space is for thoughtful exploration and serious inquiry — not spam, trolling, or toxic engagement.

What’s welcome:

• Honest questions

• Constructive challenges

• Different viewpoints offered with civility

What’s not tolerated:

• Spam or promotional noise:

  Sharing work or articles is encouraged when it fits naturally into the discussion.

  Shallow, unrelated promotions will be removed to protect the quality of thinking here.

• Trolling, baiting, or personal attacks

• Vitriol, harassment, or bad faith engagement

Building better ideas requires protecting better conversations.

🎯 Why I Built This

The goal of these publications — and this platform — is simple:

• To share genuine signal across technology, leadership, culture, and civilization

• To deliver insight that stays valuable beyond the news cycle

• To help build a better architecture of thought, leadership, and creation

Every article, essay, and dive is built intentionally — organized, principled, and anchored in reason.

🧠 What Sets My Work Apart

Everyone writes with a perspective, whether they realize it or not.

The difference here is that my lens — a philosophy grounded in reason — is conscious, deliberate, and structured.

Every framework, strategy, and commentary is filtered through that clarity.

Even when conclusions are debatable, the thinking behind them is intentional and transparent.

That’s what I aim to deliver:

Clear thinking. Anchored frameworks. Strategic insights.

🧩 Explore the Latest Thinking

Ongoing highlights will include:

• Deep dives

• Short analyses

• Strategic commentaries across Chips, Craft, and Curiosity

Here’s a sample deep dive to get started:

🔹 Trifecta: Tariffs, Threat of Real War, and the AI Supply Chain

How escalating tariff wars are confusing supply chains at every layer of the AI economy — and why understanding this disruption matters.

🚀 Subscribe Directly

Don’t rely on social media algorithms to decide what content you see.

By subscribing to one or more of my publications directly, you’ll receive new essays, insights, and updates delivered straight to your inbox — without noise, filtering, or distractions.

If a welcome email doesn’t appear immediately after subscribing, check your spam folder.

🔹 chiptechtalk.kakani.co

🔸 craft.kakani.co

🟠 kakani.co

🧭 Final Thoughts

Thank you for being part of this exploration.

If clarity, depth, and genuine insight matter, I hope these spaces will become part of your regular intellectual diet.

Let’s build something better — together.

—Chak

Subscribe now