The Road to the AI-Native Free Person — Choices at the Individual Level

The Role of This Chapter

Across Parts II and III, we have traced the structure of the AI revolution, the feudalism the IT revolution built, the contradictions that feudalism produced, the self-destruction of the lord class, and the mechanics of its dismantling. This chapter is the practical section.

"The analysis is clear — what do I actually do starting today?" This chapter answers that question. The choice that changes your class is not an abstraction. It is determined by a specific combination of tools and formats.

Five Choices That Move Together

There are five choices required to stand as an AI-native free person. The critical point is that these are not independent choices but a single interconnected structural choice.

Only when all five are aligned does AI-native work become possible. Leave even one on the old side and translation labor appears at that point, blocking the flow.

For example, "switched to Linux but kept C#" leaves an impedance mismatch with the AI-native base layer. "Switched to Python but kept .xlsx" breaks the structure in round-trips with Excel. The choices move together.

A Realistic Staircase for the Transition

That said, switching all five simultaneously is hard. In practice, the transition happens in stages. This series maps that staircase concretely:

Each step takes weeks to months. The full "vassal to builder" transition completes in one to two years. No rush, but steady progress — that is the practical rhythm at the individual level.

Step 1 in Detail — Migrating to Markdown

The easiest entry point is switching your documents to Markdown.

This alone achieves:

• Dramatically improved interaction with AI (Markdown can be passed directly)
• Full version control working with git
• Search working with grep
• A guarantee of readability ten years from now (plain text)
• Escape from vendor lock-in

As a first step, migrating to Markdown has the lowest friction and the highest impact. Your daily workflow changes within a week.

Step 2 in Detail — Combining AI with Python

The next step is to start using Python. Even for non-programmers, Python in the AI era is worth learning as "the second language after English."

The starting point is not "study programming" but "automate my work in Python." In an era where AI assists you, this is the most efficient way to learn.

Chapter 2 ("Python") of Part I in the "AI-Native Ways of Working" series covers this path.

Step 3 in Detail — Migrating to Debian

The largest step is switching your OS to Linux. It can be done in a day, but the psychological barrier is high.

The "Learning Debian with Claude" series (prologue + 23 chapters) is the complete guide for advancing this migration through dialogue with Claude.

In particular, the Chapter 00 prologue — "Why Linux Now — Structures That Work in the AI Era, Structures That Don't" — aligns directly with this series (Insights Parts II and III).

Step 4 in Detail — Cutting the Office Dependency

You do not need to abandon Office entirely. Simply reframe it as "the final compatibility layer":

Office-compatible only at the entry and exit points; structured text throughout — this is the consistent policy of this series.

ONLYOFFICE (available from Flathub) has high visual compatibility with Microsoft Office and can run JavaScript macros locally. Acknowledging Office as good software while escaping hostage-taking by the vendor (Nadella) — this position is structurally the strongest.

Step 5 in Detail — The Transition to Builder

The final step is the transition from vassal (employed) to builder (creating value independently). This takes the most time and is the most individual.

This is not "take a risk and start a company." It is a process of gradually reducing dependence on an organization. If you can do AI-native work, you can cover multiple specialties alone, so "the client who commissioned a specialist team" can become "the builder who builds it themselves."

All 14 chapters of the "AI-Native Ways of Working" series cover the specific tools and practices for this path.

Three Misconceptions to Avoid

Finally, three misconceptions that are easy to fall into during the transition:

Misconception 1: "It's meaningless unless I change everything at once." Incremental is sufficient. Markdown alone changes your daily workflow. Move up the staircase — Python next, then Linux — and you will get there.

Misconception 2: "Linux is difficult." By 2026, the AI era has inverted this. Ask Claude and you understand journalctl in seconds. "Memorizing what you don't know" has been replaced by "asking AI what you don't know" as the default.

Misconception 3: "I need to fully separate from Big Tech." Complete separation is unnecessary. Certain services — GitHub, AWS, Anthropic — are used. What matters is not being fully held hostage by any single vendor. Maintain multiple options and keep the ability to switch at any time.

The Individual's Position in Structural Change

Integrating the analysis so far, the stance an individual should take today becomes clear:

The options are already in place. This series — the structural analysis in insights, the practical guide in claude-debian, the ways of working in ai-native-ways — is the toolset to support that choice.

The Conclusion of This Chapter — The Choices Are a Single Interconnected Structural Choice

OS, language, format, AI, tools — the five choices are not independent. They are a single interconnected structural choice. Align them and you can stand as an AI-native free person. Leave them misaligned and only half-results emerge.

And this choice belongs to no one but you. Big Tech will not prepare it for you. It is the same kind of choice that citizens of the late-medieval free cities made, one by one — whether to remain under a lord or migrate to a rising city.

As a Close to the Series

From Part II Chapter 4, "What the AI Revolution Really Is — A Two-Layer Simultaneous Change," through to this Part III Chapter 6, "The Road to the AI-Native Free Person," the second half of this series has developed its structural analysis. The consistent argument is as follows:

• The AI revolution is not only about LLMs. New types and languages evolved simultaneously (Part II, Ch. 4)
• Python becoming the center of AI-native languages was a structural inevitability (Part II, Ch. 5)
• The massive workforce demand in software development was caused by translation labor arising from weak types (Part II, Ch. 6)
• The social consequence of the IT revolution was the construction of a new feudalism (Part I, Ch. 10)
• Feudalism produced five structural contradictions in exchange for its technical success (Part I, Ch. 11)
• The Big Tech lord class cannot retreat; their self-destruction is confirmed (Part I, Ch. 12)
• The AI revolution dismantles this feudalism, and builders emerge as the new class (Part II, Ch. 7)
• Design is not "adding" but "reading" — the isomorphism of AI and agriculture (Part III, Ch. 4)
• The liberation of the free person is a historical movement progressing simultaneously across four layers: individual, tools, enterprise, and thought (Part III, Ch. 5)
• Individuals can stand as free citizens through concrete choices (Part III, Ch. 6)

This is a structural analysis series of the Second Renaissance. The individuals of the AI era are making, right now in front of them, choices isomorphic to those made by citizens of Italian city-states at the end of the Middle Ages.

The practical sections of this series are deployed as two separate series:

• Learning Debian with Claude (prologue + 23 chapters) — A complete guide to migrating from OS to daily environment
• AI-Native Ways of Working (14 chapters) — Concrete practices for working alongside AI

Use the structural analysis (insights) for the overall picture, and the practice series for the specific steps — combine both to walk the road to becoming an AI-native free person.