Sovereign Ecosystem

The Sovereign Ecosystem is a local-first personal operating system for thinking, planning, creating, and evolving with an AI interface.

It is built around one simple idea: your files are yours, your structure is yours, and your AI should work inside your world rather than pulling you into someone else's.

This is meant to become lived infrastructure, not admired architecture. The point is not to design a perfect system and stare at it. The point is to build a strong foundation and then do real things with it.

What This Is

This is a template for:

governance
capture and routing
planning
session rhythm
archival
optional modules you can add later

It is not a rigid brand kit or a fixed belief system. The Foundation is meant to be edited. The Constitution is yours. The codices are yours. The governance layer is yours.

The best plan that never gets implemented is still just a plan. This ecosystem is designed to be operationalized. It should earn its refinement through real use.

Sovereignty Direction

This ecosystem is built for progressive sovereignty.

Obsidian is recommended because your files stay local and readable.
Claude Code and Codex are the recommended starting tools right now because they are strong enough to build with today.
The long horizon is more sovereign tooling: local models, personal hardware, and platform-agnostic interfaces as they become more practical.

Build now. Iterate toward the horizon.

Local-first does not mean friction-first. Use the tools that help you get moving now, while keeping the deeper sovereignty horizon visible.

What You Will Need

You need four things before you begin.

Obsidian — a free, local-first markdown app where this ecosystem lives. Download it at obsidian.md. Once installed, open the downloaded Sovereign Ecosystem folder as a vault using "Open folder as vault."

Claude Code — Anthropic's AI coding assistant that acts as your AI interface inside the vault. The easiest path for most people is to install it as a VS Code extension: download VS Code first, then install the Claude Code extension from the VS Code Extensions marketplace. If you prefer the terminal, install it with npm install -g @anthropic-ai/claude-code (requires Node.js). Claude Code uses the Anthropic API, which has a small per-session cost. Full onboarding typically runs in the range of $10–25 USD total at a comfortable pace. See Session 0 for more detail on cost and setup options.

Git — version control tool used by the Ecosystem Update Check skill to fetch updates and by the scripts folder if you use the backup automation. Most Mac and Linux users already have it. Windows users can download it at git-scm.com or install GitHub Desktop for a GUI version.

A GitHub account — free at github.com. Needed if you want to receive notifications when new ecosystem updates are published, or if you eventually want to publish your own version. Not required to complete the Foundation build.

Once these are in place, continue below.

Start Here

Read Getting Started/Index.md.
Complete Getting Started/Session 0 - Prerequisites.md.
Name your ecosystem and AI interface early if you can.
Use MODULES.md later, after the Foundation is stable enough to understand.

If you think you may want to use old AI history during setup, start that export process as early as possible. Large exports from prior AI tools can take hours or longer to arrive. If you start early, Session 0.5 can use the material when you get there instead of making you wait.

Expect this to take more than one sitting. For some people this will be familiar. For others it will be a first encounter with tools like Obsidian, AI coding interfaces, or local-first workflows.

That is fine. Sleep on it. Take a walk. Take a break. Do a somatic practice. The build can take a few days and still be moving exactly as it should.

Name It Early

The framework is called Sovereign Ecosystem. That is the canonical architecture name.

Your version does not need to stay named that way in the user-facing layer. You are encouraged to choose:

an ecosystem name
an AI interface name

Examples:

[Name] OS
Kingdom
another name that actually feels like yours

If you do not know the name yet, keep the placecards for now. You will hit a Foundation naming checkpoint before module selection.

Foundation First

Do not install everything at once.

Start with the Foundation:

governance
core protocols
core skills
core templates
activation and closeout surfaces

Then add modules only when they solve a real need.

Examples:

add Transcription if you think by speaking
add Expression if you are actively writing or publishing
add Weekly Review after the basic system has enough lived data

Full boundary map: MODULES.md

The Foundation-first rule is not there to slow you down. It is there so the system becomes usable before it becomes elaborate.

Build the foundation. Use it in real life. Let reality teach you what wants refinement next.

AI Naming Note

You will see Jarvis in some inherited Foundation behavior as the shipped baseline. That does not mean you have to keep the name.

Early renaming is recommended. Deep interaction-style customization is a later layer by default.

If you want to rename your AI interface, start here: Getting Started/rename-ai-interface.md

Practical Rule

Use the Foundation as a working starting point. Do not force a total rewrite before you have lived inside it.

If something feels obviously off, adjust it. If not, let the system earn its refinements through real use.

This is also an opportunity for an upgrade in how you work. Do not only recreate the habits you already have in cleaner folders. Use the build to notice how your most alive, curious, and authentic way of working actually wants to function.

Staying Updated

The Sovereign Ecosystem is a living template. New modules, refinements and improvements are published over time.

Running the update check: Use the Ecosystem Update Check Skill from inside your vault. Your AI will fetch the current update index, show you what is new and help you apply only what fits your build. Nothing is applied without your approval.

Ambient reminder: Your CLAUDE.md is set to notice if you have not checked for updates in more than 30 days. Your AI will mention it lightly at the start of a session. No alarm. Just a signal.

End-of-Week: If you run an End-of-Week review, the skill includes a check for overdue ecosystem updates before the review begins.

GitHub notifications: To receive a notification when new updates are published, go to the Sovereign Ecosystem repository and click Watch. Select Releases only to get one notification per release rather than one per commit. Repository: github.com/infinitegameplayer/sovereign-ecosystem

Working with Lane

Built by Lane Belone.

If this sparked something and you want to bring this kind of thinking into your organization, or want a guided experience building it, workshops, retreats and advisory work are available at sidequesthq.co.

Released as a public template. Licensed under MIT. See LICENSE for details.