202602241602-sky-atlas-overview

🎯 Core Idea

Sky Atlas is a structured governance document for the Sky ecosystem. It reads less like a blog and more like a specification: a numbered hierarchy of scopes, articles, and definitions intended to be referenced and updated over time.

The Atlas is organized into a preamble plus six scopes:

• Governance Scope
• Support Scope
• Stability Scope
• Protocol Scope
• Accessibility Scope
• Agent Scope

A useful way to think about the Atlas is that it tries to do two things at once:

• Define a shared vocabulary and value framing (for example, definitions around alignment and misalignment).
• Define a modular rulebook by scope, so different parts of the ecosystem can evolve with clear boundaries.

What makes it unusually helpful (and why the design matters)

• It is navigable like a technical manual. The numbered structure encourages precise references.
• It separates concerns by scope. You can reason about changes without mixing everything into one governance blob.
• It treats governance as an engineered system: definitions, boundaries, and explicit artifacts.

How I use it to understand the ecosystem

1. Start from the scope list

• If you are trying to understand who can do what, start at Governance Scope.
• If you are trying to understand product and distribution, look at Accessibility Scope.
• If you are trying to understand technical responsibilities, look at Protocol Scope.

2. Read definitions as a glossary
   The definitions in the preamble act like a dictionary for how the ecosystem wants to describe itself. Even if you disagree with the framing, it tells you what concepts the ecosystem considers important.

3. Treat it like an interface
   The Atlas is an interface between:

• ideals and narrative
• actual processes and permissions
• incentives and practical operations

The more you treat it like an interface, the easier it is to map real-world proposals and decisions back to the document.

🌲 Branching Questions

➡ What is the Atlas trying to be: a constitution, a governance handbook, or an operational spec?

From its structure and writing style, Sky Atlas reads most like an operational specification for governance. It uses a numbered hierarchy, explicit scopes, and definitional sections that are intended to be referenced precisely.

It also has constitution-like intent in two ways:

• it frames values and concepts in the preamble, especially around alignment and misalignment
• it aims to define long-lived boundaries by separating the ecosystem into scopes

A good working model is: Atlas is a spec for how Sky wants to govern, written in a style that can later support more constitution-like immutability.

➡ What are the six scopes, and what kinds of decisions belong in each scope?

The Atlas defines six scopes:

• Governance Scope
• Support Scope
• Stability Scope
• Protocol Scope
• Accessibility Scope
• Agent Scope

A practical way to map decisions:

• Governance Scope

  • balance of power, interpretation of alignment artifacts, appeals, and the rules that govern governance itself

• Support Scope

  • ecosystem support functions, governance process infrastructure, and support activities

• Stability Scope

  • financial stability rules, stablecoin-related mechanisms, and parameters that impact stability

• Protocol Scope

  • technical development, maintenance, and security of the core protocol

• Accessibility Scope

  • frontends, distribution, and user-facing access pathways

• Agent Scope

  • rules and artifacts for agents

Even without reading all articles, this scope list is already a useful mental index: if you cannot place a decision into a scope, you likely do not understand what the decision affects.

➡ How do the definitions in the preamble shape the way Sky talks about alignment and governance?

The preamble definitions act like a glossary with strong normative framing. Examples that stand out:

• Universal Alignment

  • described as a spectrum and tied to human morality, values, and the natural world
  • misalignment is defined as acting in opposition to universal alignment

• Ecosystem Intelligence

  • frames the ecosystem as a single entity whose intelligence depends on alignment across participants

• Alignment Engineering

  • presented as a philosophy of organizational design and as the source of alignment artifacts

This matters because it encourages a specific way of arguing about governance:

• not only efficiency or votes, but alignment versus misalignment
• not only incentives, but the spirit of rules versus the letter of rules

If you adopt the Atlas vocabulary, it changes how proposals are justified and criticized.

➡ How should I use the Atlas when reading a proposal or a governance vote?

A practical workflow:

1. Identify the scope

• classify the proposal under one of the six scopes

2. Extract the relevant definitions

• look for terms in the proposal that appear in the Atlas definitions
• translate proposal claims into Atlas language when possible

3. Look for the implied rule type

• is this a parameter change, a process change, a new role, or a new artifact

4. Look for boundary crossings

• the biggest confusion in large ecosystems is when one domain quietly changes another
• the Atlas scopes are intended to make those crossings visible

5. Record references

• treat Atlas sections like an API. Link the proposal to the relevant doc numbers

This method is useful even if you disagree with the framing, because it maps reality to the system the ecosystem claims to follow.

➡ What parts of the Atlas feel immutable in spirit versus likely to change frequently in practice?

Immutable in spirit tends to mean:

• core definitions and values in the preamble
• the boundary decomposition into scopes
• the meta-rules that define how governance should preserve alignment

Likely to change frequently:

• operational details that adapt to new products and distribution channels
• role definitions and process mechanics as the ecosystem iterates
• technical and economic parameters as markets and protocol design evolve

This is a common pattern: stable vocabulary and principles, adaptive implementation.

➡ What are the most important terms to learn first, and what are common misreadings?

High leverage terms to learn first:

• Scope
• Alignment Artifact
• Universal Alignment
• Misalignment
• Slippery Slope Misalignment
• Alignment Engineering

Common misreadings:

• treating Atlas terms as purely technical

  • many definitions are normative and value-laden

• treating scope boundaries as descriptive only

  • the intent is to enforce boundaries and reduce cross-scope ambiguity

• assuming alignment equals incentives

  • the Atlas explicitly distinguishes the spirit of rules from the letter, and talks about inner incentive versus explicit incentives

If you internalize these terms, the rest of the Atlas becomes much easier to parse because you recognize repeated patterns across sections.

📚 References

• https://sky-atlas.io/
• https://sky-atlas.io/?exportScopeTreesWithoutAgents=1

🔗 Links to other cards

• 202602241600-phoenix-labs
• 202512161454-spark
• 202510201919-gitcoin-governance