The foundational workspace template

What it is

The Sovereign Ecosystem is a foundational template for an Obsidian and Claude Code workspace. It gives your sovereign setup its initial shape: the directory structure, the governance scaffolding, a North Star template and the initial skill set needed to get a vault running.

It is not the system. It is the starting conditions. Every practitioner who uses it ends up somewhere different. The template is the bone structure. You bring the muscle.

This is the three-tier stack origin. Named live in the May 2 AI for Livin' Workshop by an attendee mid-demo. Foundation, reader/editor, AI interface. Each layer swappable. The Sovereign Ecosystem is layer one.

What it ships

• Council Chamber. Governance, codices, skills and protocols. The structural core that keeps the workspace coherent over time.
• Library. A North Star template atLibrary/North Star.md, a transcripts folder and a references folder. The long-horizon context layer.
• Inbox. The capture surface. Raw input lands here before it gets organized. The daily funnel.
• Sovereign Command and To-Do Dock. The live signal surface for what is active right now and the daily capture surface for the small stuff.
• Initial skill set. The governance skills needed to get the vault operational. The cool extras have graduated. They live on this site as installable skills and bundles, built out to a level no foundational template needs to carry.

At v2.4.0, the repo trimmed to foundational only. Source Harvest stayed as a dual-distribution surface. Everything else that grew beyond template scope shipped here instead.

The three-tier stack

The stack has three layers. Each one is swappable.

The Sovereign Ecosystem is the file structure and the templates. The opinionated foundation that gives the system its shape. Obsidian is the reader and editor. It turns those files into something you can navigate, search and annotate by hand. Claude Code, or Codex, or any future agentic interface, is the AI that can read, edit and restructure any of it on your instruction.

One layer holds the structure. One translates the files for human navigation. One brings the AI intelligence. Swap any layer and the others survive. That durability comes from building on an open foundation instead of a closed platform.

The full architectural case is at Data Sovereignty.

The build sequence

The repo ships two guides as markdown files inside the workspace.

The Quick Start Guide is the install foundation. It walks you from first software install through vault setup, AI adapter connection and first activation. Work top to bottom. Each section has an exit condition before you move on.

The Build Sequence is the session-by-session guide. Ten sessions, each one adding a layer. Session 0 confirms your environment and locates your starting point. Session 1 builds the first working bridge between you, your files and your AI. Sessions 2 and 3 bring governance and the context layer online. Sessions 4 through 6 activate the operating loops and open the expansion layer with discernment. Sessions 7 through 9 bring the command surface live, align your North Star and run the first real capture loop. Session 9 closes when the daily loop proves itself with one real alive idea.

Do not force the whole thing into one afternoon. Each session is meant to land before the next one begins.

Source Harvest as a primary entry point

The Source Harvest skill is built to harvest any external repo at source level. The Sovereign Ecosystem repo is a natural first target.

Install the repo, then run a Source Harvest over it. The skill classifies each governance file, protocol, codex and skill against your existing setup. Adopt what fills a gap. Enrich what improves on what you already have. Defer what does not yet apply. Ignore what already lives in your system. The harvest turns the template into your template.

Veterans who already have a vault do not need to start from the template. A Source Harvest of the repo gives them the same signal without the full install.

The North Star

The repo ships a North Star template at Library/North Star.md. Fill it in once. Revisit it often. Once it lives in your system, the AI organizes day-to-day work around it and you stop carrying the trajectory in your head.

The philosophy behind the North Star, what goes in it, how the Anti-Vision pairs with it, and why the quest framing matters more than task language, is covered in full at The North Star. The repo gives the practical scaffold. The concept page covers the reasoning.