Confidence: 87% ·Jan 11, 2026

Sky Atlas

Introduction

The Sky Atlas is the foundational constitutional document governing the Sky Protocol (formerly MakerDAO), serving as the comprehensive rulebook that defines all governance processes, organizational structures, and operational boundaries within the Sky ecosystem. [1] As of January 2026, the Atlas represents one of the most sophisticated governance frameworks in decentralized finance, structuring a protocol with approximately $6.65 billion in total value locked and over $9.86 billion in USDS supply through detailed specifications across six major Scopes and thousands of nested document sections. [2]

Unlike traditional corporate bylaws or typical DAO governance documents, the Sky Atlas embodies a unique dual-layer architecture combining Immutable Documents that enshrine the protocol's permanent foundational principles with Adaptive Documents that operationalize those principles through continuously evolving governance processes. [3] This design reflects a fundamental governance philosophy: certain core values and alignment mechanisms must remain unchangeable to prevent "slippery slope misalignment" where incremental governance decisions gradually erode the protocol's original purpose, while operational details must adapt to changing market conditions, technological developments, and ecosystem growth. [4]

The Atlas functions as the "source of truth" for all Sky Protocol operations, determining who can do what, when, how, and under what constraints. [5] Every governance vote, every protocol parameter change, every agent action, and every ecosystem role derives its legitimacy and operational boundaries from Atlas specifications. When disputes arise about proper procedures or when ambiguity creates uncertainty about correct courses of action, the Atlas provides the definitive criteria for resolution through its Spirit of the Atlas principles and detailed procedural specifications.

The document's significance extends beyond mere process documentation. The Atlas represents an ambitious experiment in constitutional governance for decentralized systems, attempting to encode long-term alignment mechanisms that protect the protocol's core values while enabling productive evolution. [6] Its creation followed extensive deliberation through the Endgame Plan proposal process beginning in 2022, with the Atlas Immutable Alignment Artifacts formally ratified by governance on March 27, 2023, marking a watershed moment in Sky Protocol's transition from informal coordination to codified constitutional governance. [7]

As Sky Protocol approaches its ultimate Endgame State with the planned launch of NewChain—a dedicated blockchain for Sky governance and SubDAO tokenomics—the Immutable Documents within the Atlas will become permanently unmodifiable, establishing an eternal constitutional foundation for the protocol's decentralized operation. [8][9] This transition from modifiable to immutable governance represents one of the most significant experiments in cryptocurrency governance design, testing whether protocols can successfully "lock in" alignment mechanisms while maintaining viability in rapidly changing environments.

History and Origins

The Sky Atlas emerged from years of governance evolution within MakerDAO, reflecting hard-won lessons about coordination challenges, misalignment risks, and the need for robust constitutional frameworks in decentralized systems.

Early MakerDAO Governance and Pre-Atlas Era (2017-2022)

MakerDAO launched in December 2017 with relatively informal governance processes centered on forum discussions, governance calls, and on-chain voting through the DSChief smart contract. [10] While this early system successfully coordinated protocol launches and crisis responses—most notably during the March 2020 "Black Thursday" event when rapid governance coordination prevented protocol collapse—the lack of comprehensive procedural documentation created recurring challenges.

Governance participants faced persistent ambiguities about proper procedures for proposal submission, voting timelines, amendment processes, and authority boundaries. Different community members held conflicting interpretations of what changes required governance votes versus what could be implemented by core teams directly. The absence of codified standards for governance roles created confusion about responsibilities and accountability for actors like governance facilitators, delegates, and core contributors.

The April 2020 introduction of the Maker Improvement Proposals (MIPs) framework through MIP0-MIP13 represented the first major step toward formalizing governance processes. [11] MIPs established standardized templates, submission procedures, review timelines, and ratification requirements for protocol changes. However, the MIPs framework focused primarily on process rather than principles—it specified how to propose changes but provided limited guidance on what changes aligned with the protocol's core values or how to resolve conflicts between legitimate but competing priorities.

The Endgame Plan and Atlas Conception (2022-2023)

Founder Rune Christensen's Endgame Plan, first proposed in comprehensive form during 2022, identified governance complexity and misalignment risks as existential threats to MakerDAO's long-term viability. [12] The plan argued that without strong constitutional foundations encoding alignment mechanisms, governance would inevitably succumb to "slippery slope misalignment"—a process where each individual governance decision appears reasonable in isolation but collectively moves the protocol away from its core mission of maintaining a decentralized, unbiased stablecoin.

The Endgame Plan proposed creating the Atlas as a comprehensive governance constitution that would:

  • Define the protocol's permanent foundational principles through Immutable Documents
  • Specify all governance processes, roles, and boundaries through Adaptive Documents
  • Implement an "Alignment Engineering" framework using explicit incentives, transparency requirements, and structural checks to maintain protocol coherence
  • Establish clear Scopes dividing governance responsibilities across specialized domains
  • Create an Agent Framework separating strategic innovation (Prime Agents) from operational execution (Executor Agents)

Extensive deliberation occurred throughout 2022 and 2023 via forum discussions, governance calls, workshops, and iterative proposal refinements. The community debated fundamental questions about immutability's wisdom, the appropriate balance between flexibility and rigidity, the right level of procedural detail, and whether codified constitutions could meaningfully constrain future governance decisions or merely create bureaucratic overhead.

On March 27, 2023, Sky governance ratified the Atlas Immutable Alignment Artifacts, establishing the permanent constitutional foundation. [7] This vote marked one of the most significant governance decisions in protocol history—token holders were essentially binding their future selves and all future participants to a constitutional framework that would eventually become unchangeable.

Atlas Implementation and Iteration (2023-2025)

Following ratification, the Atlas underwent continuous expansion and refinement as the community translated high-level constitutional principles into detailed operational specifications. The initial Atlas consisted primarily of the foundational Immutable Documents defining core concepts and the Spirit of the Atlas. Subsequent governance votes progressively added Adaptive Documents specifying:

  • Detailed governance process timelines and requirements
  • Specific agent roles, responsibilities, and constraints
  • Risk parameters and stability mechanisms
  • Technical requirements for protocol development
  • Budget allocation and compensation frameworks

The September 2024 rebrand from MakerDAO to Sky Protocol coincided with major Atlas updates incorporating the new naming conventions, token specifications (SKY and USDS), and the formalized Stars (formerly SubDAOs) framework. [13] The rebrand governance controversy—where a November 2024 poll revealed extreme voting power concentration with four entities controlling approximately 80% of vote weight—demonstrated the Atlas's role as a stabilizing constitutional framework even during contentious strategic transitions. [14]

As of January 2026, the Atlas continues to evolve through regular Atlas Edit Proposals processed via both the Weekly Operational Cycle for minor operational updates and the Monthly Governance Cycle for significant structural changes. [15] Recent Atlas edits have addressed topics including Star Artifact updates, Core Council Executor Agent initialization, risk framework modifications, and clarifications to governance procedures.

The Path to Endgame State and Permanent Immutability

The ultimate vision for the Atlas involves a transition to the Endgame State when NewChain—a dedicated blockchain for Sky governance and SubDAO operations—launches. [8][9] Forum discussions during 2023 explored whether NewChain should be built by forking Solana's codebase (Rune Christensen's recommendation) or using alternative foundations like Cosmos.

Once NewChain launches and Sky Protocol enters the Endgame State, the Immutable Documents within the Atlas will become permanently unchangeable—literally immutable through technical implementation rather than merely immutable by governance convention. [16] This represents a radical commitment to constitutional governance: the community will have voluntarily surrendered the ability to modify core principles even if future circumstances might seem to warrant changes.

Adaptive Documents will remain modifiable through governance processes, enabling continued operational evolution within the boundaries established by immutable foundations. This creates a governance system combining eternal principles with practical flexibility, attempting to capture the benefits of both rigidity and adaptability.

Atlas Structure and Document Architecture

The Sky Atlas employs a sophisticated hierarchical document structure that organizes governance information across multiple layers, document types, and categories, creating a comprehensive yet navigable constitutional framework.

Nested Document Tree Architecture

Atlas Documents form the basic building blocks for structuring governance data, organized as nested document trees with unique Document Identifiers following a standardized hierarchical numbering system. [17]

The top-level structure consists of seven major divisions:

  • A.0 - Atlas Preamble: Foundational definitions and general provisions [18]
  • A.1 - The Governance Scope: Governance processes and power balance [19]
  • A.2 - The Support Scope: Ecosystem support and infrastructure [20]
  • A.3 - The Stability Scope: USDS stablecoin management [21]
  • A.4 - The Protocol Scope: Core protocol maintenance and engineering [22]
  • A.5 - The Accessibility Scope: Distribution and user-facing frontends [23]
  • A.6 - The Agent Scope: All Agent regulations and Agent Artifacts [24]

Each top-level Scope subdivides into progressively more detailed sections, articles, and subsections. For example, the Governance Scope (A.1) contains sections on the Spirit of the Atlas (A.1.1), Atlas Documents (A.1.2), Governance Accessibility (A.1.3), Alignment Conservers (A.1.4), and numerous other topics, with each section further subdividing into specific articles and provisions.

Document Identifiers indicate hierarchical position and depth within the tree. A.1.2.3.4 would represent the Governance Scope (A.1), second major section (.2), third subsection (.3), fourth sub-subsection (.4). This numbering enables precise references and unambiguous citations when governance participants discuss specific provisions.

Document Categories: Immutable, Primary, Supporting, and Accessory

The Atlas categorizes documents into four fundamental types that determine how they can be modified and what governance processes apply. [25]

Immutable Document Category

Immutable Documents record the Spirit of the Atlas, detailing the vision, purpose, and unalienable principles of Sky Protocol. [26] These documents occupy the first three layers of the document tree (depth ≤3) and contain the foundational constitutional content.

During the pre-Endgame State period, Immutable Documents remain modifiable through the governance processes specified in the Atlas, allowing refinement and correction of the constitutional foundation. However, once Sky Protocol enters the Endgame State with NewChain launch, Immutable Documents become fully immutable—they can never be changed through any mechanism. [26]

This design reflects a fundamental philosophy: the community must have time to refine and perfect the constitutional foundation during the transition period, but eventually must commit to permanent principles that subsequent generations cannot erode through incremental modifications.

Primary Document Category

Primary Documents contain the operational elements that directly govern day-to-day protocol functions. They implement and interpret the Immutable Documents' principles through specific procedures, parameters, and requirements. Primary Documents can be modified through standard governance processes at any time, enabling the protocol to adapt to changing circumstances while respecting immutable constitutional boundaries.

Supporting Document Category

Supporting Documents provide auxiliary information, context, and guidance that supplements Primary Documents without directly governing protocol operations. They help governance participants understand and apply Primary Document provisions correctly.

Accessory Document Category

Accessory Documents serve organizational and navigational functions within the Atlas, such as indexes, cross-reference tables, and structural elements that make the comprehensive Atlas more accessible without themselves specifying governance rules.

Document Types and Their Functions

Beyond categories, the Atlas defines numerous specific document types serving distinct purposes. [27]

  • Type Specification Documents — Define the properties and characteristics of other document types, creating a self-referential documentation system where the Atlas specifies its own structural rules.
  • Scope Documents — Define each of the six major governance Scopes, establishing their purposes, boundaries, and relationships to other Scopes.
  • Article, Section, and Core Documents — Provide different levels of detailed content specifications, with Core Documents representing fundamental definitions and concepts that other documents reference and build upon.
  • Definition Documents — Provide precise meanings for terms used throughout the Atlas, ensuring consistent interpretation. The Atlas Preamble contains extensive definitions for concepts like Alignment Engineering, Universal Alignment, Agents, Scopes, and dozens of other specialized terms. [18]
  • Element Annotation Documents — Provide explanatory context and interpretive guidance for specific elements within other documents, helping governance participants understand the intent and application of complex provisions.
  • Budget, Active Data, and other specialized types — Handle specific governance functions like budget tracking, parameter storage, and operational data management.

This comprehensive type system enables the Atlas to serve multiple functions simultaneously: constitutional foundation, operational manual, interpretive guide, and organizational framework.

Document Properties and Metadata

Each Atlas Document includes standardized properties that enable navigation, version control, and governance tracking. [28]

  • Name Property — Specifies the document's human-readable title and purpose.
  • Version Property — Tracks document iterations, enabling governance participants to reference specific versions and understand how documents evolved over time.
  • Last Modified Property — Records when documents were most recently updated, helping participants identify recent changes and prioritize reviewing updated content.
  • Type Property — Specifies what category and specific type the document belongs to, determining applicable modification procedures.
  • Components Property — Lists any sub-documents nested within the document, defining the hierarchical structure.

Additionally, each Atlas Document includes a UUID (Universally Unique Identifier) enabling unambiguous references even if document names or positions within the tree change over time. This UUID system ensures that historical governance discussions referencing specific Atlas provisions remain meaningful even as the Atlas evolves.

The Spirit of the Atlas and Universal Alignment

The Spirit of the Atlas represents the philosophical core of Sky Protocol's governance framework, establishing foundational principles that all governance decisions, operational actions, and ecosystem developments must respect.

Universal Alignment as Foundational Principle

Universal Alignment constitutes the central concept underlying the entire Atlas framework. [29] The principle holds that Sky Protocol must optimize for alignment between the ecosystem and its environment—creating governance structures, incentive systems, and operational processes that harmonize with external reality rather than conflict with it.

The guiding principles of the Sky Ecosystem, known as the Spirit of the Atlas, form the foundation of the Sky Governance process and are enshrined in the Immutable Documents of the Atlas. [30] These principles enable coordination around a resilient governance equilibrium that optimizes for Universal Alignment. The Immutable Documents take precedence over any other rules, decisions, or governance structures that may conflict with them, providing the definitive criteria for determining whether the Sky Ecosystem's rules and incentives are in harmony with Universal Alignment. [30]

Universal Alignment recognizes that decentralized protocols exist within complex external environments including:

  • Economic realities: market forces, competitive dynamics, capital flows
  • Technological constraints: blockchain limitations, security requirements, scaling tradeoffs
  • Regulatory landscapes: legal frameworks, compliance obligations, jurisdictional variations
  • Social dynamics: community coordination, stakeholder interests, public perception
  • Governance challenges: voting incentives, capture risks, coordination costs

Rather than pretending the protocol can operate in isolation from these forces, Universal Alignment embraces them as constraints and opportunities that governance must actively engage with through intelligent system design.

Alignment Engineering and Incentive Structures

Alignment Engineering represents the practical methodology for achieving Universal Alignment through systematic design of incentives, transparency mechanisms, and structural constraints. [31]

The Atlas defines Alignment Engineering as the deliberate construction of systems that channel participants' self-interested actions toward collectively beneficial outcomes. Rather than relying solely on participant altruism or hoping that conflicts of interest will resolve favorably, Alignment Engineering builds governance structures where doing the right thing aligns with participants' personal incentives.

Explicit and Implicit Incentives

The Atlas distinguishes between Explicit Incentives (direct compensation, token rewards, penalty mechanisms) and Implicit Incentives (reputation effects, future opportunities, social capital). [32] Effective Alignment Engineering considers both types when designing roles and processes, recognizing that participants respond to the full spectrum of incentive structures, not merely monetary rewards.

Incentive Slack and Inner Incentives

Incentive Slack refers to situations where incentive structures provide insufficient motivation for desired behavior or excessive motivation enabling harmful actions. [33] The Atlas requires ongoing monitoring for Incentive Slack and adjustment of structures when slack creates misalignment risks.

Inner Incentives represent intrinsic motivations beyond external incentives—participants' genuine commitment to protocol success, ideological alignment with decentralization principles, or personal satisfaction from quality work. [34] While valuable, the Atlas recognizes that governance cannot rely entirely on Inner Incentives because they vary unpredictably across participants and can erode over time.

Slippery Slope Misalignment

Slippery Slope Misalignment represents one of the primary threats that Universal Alignment and the Atlas framework aim to prevent. [35]

This phenomenon occurs when governance makes a series of individually reasonable decisions that collectively move the protocol away from its core mission. Each decision seems acceptable or even beneficial in isolation—perhaps improving short-term metrics, responding to immediate pressures, or solving specific problems. However, the cumulative effect gradually erodes foundational principles and values.

For Sky Protocol, Slippery Slope Misalignment might manifest through scenarios like:

  • Incrementally expanding protocol authority to improve efficiency until decentralization becomes effectively centralized
  • Gradually adding complexity and special cases until the stablecoin loses its "unbiased" character
  • Progressively prioritizing short-term revenue over long-term sustainability
  • Slowly concentrating governance power among insiders through procedural changes that seem minor individually

The Immutable Documents within the Atlas specifically aim to prevent Slippery Slope Misalignment by establishing permanent boundaries that future governance cannot cross regardless of short-term incentives or pressures. Even if 99% of SKY holders vote to violate an Immutable principle after the Endgame State, the constitutional framework would prevent implementation.

Interpretation Principles and Conflict Resolution

The Atlas establishes detailed principles for interpreting its provisions when ambiguity, contradiction, or novel circumstances create uncertainty. [36]

General Interpretation Principles

When Atlas provisions present ambiguity, interpreters should resolve uncertainty in favor of outcomes most aligned with the Spirit of the Atlas and Universal Alignment rather than literal textual readings that might contradict underlying principles. [37]

When contradictions appear between different Atlas provisions, provisions closer to the Immutable core take precedence over more adaptive operational documents. Spirit takes precedence over letter when conflicts arise.

When expanding definitions or applying Atlas principles to novel situations not explicitly addressed, interpreters should reason by analogy from similar provisions and extrapolate based on underlying principles rather than arguing that silence permits unrestricted action. [38]

Precedent and Atlas Interpretations

The Atlas includes provisions for creating binding interpretations that establish precedent for future governance decisions. [39] When ambiguous situations arise, Governance Facilitators can propose formal Atlas Interpretations that, once ratified through governance processes, become authoritative guidance for similar future circumstances.

This precedent system enables the Atlas to evolve its interpretive framework without requiring constant modification of core documents—the constitutional text remains stable while its understood meaning develops through accumulated interpretative decisions.

The Governance Scope (A.1)

The Governance Scope regulates the governance processes and balance of power within the Sky Ecosystem, serving as the procedural heart of the Atlas framework. [19]

Purpose and Boundaries

The Governance Scope must ensure that the resilient equilibrium of Sky Governance remains protected against all potential direct and indirect threats. [19] This responsibility encompasses both defending against external attacks (governance capture, regulatory pressure, market manipulation) and internal degradation (misaligned incentives, procedural erosion, power concentration).

The Scope defines all voting processes, decision-making timelines, proposal requirements, and authority boundaries that govern how SKY token holders exercise control over the protocol. It establishes who can propose changes, how proposals advance to votes, what quorum and approval thresholds apply, and how approved decisions get implemented on-chain.

Governance Processes and Cycles

The Governance Scope specifies two primary governance cycles with distinct purposes, timelines, and requirements:

Operational Weekly Cycle

This cycle handles routine protocol parameter adjustments and operational decisions through weekly polls followed by bi-weekly executive votes. [40] The process begins Monday when the Core Facilitator publishes governance polls to the community GitHub and voting portal. Polls run for three days, closing Wednesday, with results determining which items proceed to executive votes posted approximately two weeks later on Friday.

Typical weekly cycle content includes stability fee adjustments, debt ceiling modifications, savings rate changes, risk parameter tweaks, and operational payments. These represent decisions that require regular adjustment based on market conditions but don't fundamentally alter protocol structure or governance processes.

Atlas Edit Monthly Cycle

This cycle provides structured processes for significant protocol changes that modify the Sky Atlas itself. [41] The monthly cycle involves submission windows (1st-3rd of each month), formal review (4th-5th), extended feedback periods (5th-end of month), ratification polls (1st-14th of following month), and eventual implementation through executive votes.

Ratification Polls require minimum participation of 240,000,000 SKY voting "yes" plus majority approval (yes votes exceeding no votes), preventing low-turnout changes to constitutional governance. [41] This higher bar for Atlas modifications reflects their greater significance compared to routine operational adjustments.

Alignment Conservers: Facilitators and Aligned Delegates

The Governance Scope establishes detailed requirements for Alignment Conservers—external entities playing fundamental roles in facilitating and protecting the Sky Governance process. [42]

Facilitators

Facilitators are anonymous Alignment Conservers with responsibility over specific Scopes who can directly access governance processes and smart contracts to fulfill their duties. [43] The Core Facilitator role within the Governance Scope holds particularly significant authority including:

  • Preparing and publishing governance polls and executive votes
  • Validating proposal compliance with Atlas requirements
  • Coordinating emergency governance responses
  • Interpreting ambiguous Atlas provisions during operational decisions
  • Managing governance infrastructure and communication channels

Facilitators face strict requirements enforced by the Governance Scope, including anonymity obligations (with limited exceptions), prohibition from holding operational roles in other ecosystem areas to prevent conflicts of interest, and adherence to comprehensive operational security and transparency standards. [44][45]

Aligned Delegates

Aligned Delegates are anonymous Alignment Conservers who use Delegate Contracts to enable SKY holders to easily and safely delegate their voting power. [46] Because they directly control large amounts of incentivized SKY voting power, Aligned Delegates are both highly influential and potentially risky actors.

The Atlas empowers Aligned Delegates with voting authority while imposing strict requirements to derisk their influence. Their primary responsibility is using delegated power to uphold the Spirit of the Atlas and maintain Universal Alignment. [46] Aligned Delegates receive protocol compensation for governance participation but face potential removal or penalty if they fail to meet communication requirements, voting participation standards, or Universal Alignment obligations.

As of January 2026, the Sky ecosystem includes 10 Aligned Delegates receiving compensation and 18 Shadow Delegates operating without formal compensation, collectively controlling over 5.7 billion SKY in delegated voting power from 879 unique delegators. [47]

Universal Alignment Requirements for Alignment Conservers

The Governance Scope imposes demanding Universal Alignment requirements on all Alignment Conservers to prevent misalignment and protect the protocol. [48]

Alignment Conservers must not:

  • Circumvent Atlas processes through informal coordination or backdoor arrangements
  • Collude with other ecosystem participants to subvert governance mechanisms
  • Secretly organize to manipulate governance outcomes
  • Demonstrate inaction when Atlas violations occur within their awareness
  • Engage in behaviors that violate clearly delineated processes and frameworks specified in the Atlas

The standard of proof in Universal Alignment controversies requires Facilitators to apply the strictest interpretation and highest standards when evaluating potential violations. [49] Even ambiguous cases suggesting possible misalignment should be treated seriously, with burden of proof placed on accused parties to demonstrate their alignment rather than requiring accusers to prove violations beyond reasonable doubt.

Swift action is required from Facilitators to address misalignment among Alignment Conservers, as the risk of misalignment spreading among these influential actors poses existential threats to governance integrity. [50]

Governance Security and Emergency Mechanisms

The Governance Scope specifies multiple security layers protecting against governance attacks and enabling emergency responses:

Governance Security Module (GSM)

The GSM implements a time delay (currently 48 hours) between when an executive vote passes and when its changes activate on-chain. [51] This delay provides the community with a window to detect malicious proposals and trigger countermeasures if necessary, protecting against governance attacks where attackers quickly accumulate voting power and push through harmful changes.

The GSM delay has evolved through governance decisions—starting at 72 hours in December 2020, reduced to 16 hours for responsiveness, increased to 30 hours in April 2024, and extended to the current 48 hours by May 2025. [52] Each adjustment reflected governance's evolving judgment about the optimal security-versus-responsiveness tradeoff.

Emergency Mechanisms

For critical situations requiring faster response than standard governance cycles allow, the Governance Scope authorizes emergency procedures including:

  • Protego Spells: Pre-prepared emergency spells implementing specific defensive actions with Facilitator validation [51]
  • Dark Spell Mechanism: For critical vulnerabilities requiring fixes while minimizing exposure during delay periods
  • Expedited Executive Votes: Known remedies proceeding with compressed timelines
  • Emergency Shutdown Module: Ability to permanently halt protocol operations during catastrophic circumstances

These emergency powers balance security needs against abuse risks, requiring Facilitator validation and community coordination rather than enabling unilateral action by any single party.

Other Major Scopes

Beyond the foundational Governance Scope, the Atlas defines five additional major Scopes that divide protocol responsibilities across specialized domains.

The Support Scope (A.2)

The Support Scope governs all routine aspects of ecosystem support, including governance process infrastructure and management, Agent support, and Ecosystem Actor support. [20]

This Scope handles operational infrastructure that enables governance to function effectively—maintaining communication channels, providing technical resources for proposal development, coordinating governance calendars and schedules, managing documentation systems, and supporting participants who need assistance navigating governance processes.

The Support Scope also regulates support provided to Agents operating within the Sky ecosystem, ensuring they have necessary resources and infrastructure to fulfill their mandates while preventing support functions from creating inappropriate dependencies or concentrating power.

The Stability Scope (A.3)

The Stability Scope governs the management of the USDS Stablecoin, mandating that USDS must be a permissionless and useful currency available to anyone. [21]

This Scope defines how stability and risk management should generate maximum value for Sky and public good. It regulates:

  • Risk parameters for collateral types backing USDS
  • Stability mechanisms maintaining the USDS peg to the US dollar
  • Debt ceiling management controlling protocol exposure
  • Liquidation processes for undercollateralized positions
  • Oracle systems providing price data for collateral valuations
  • Stability fee structures charging borrowers for USDS generation

Recent Stability Scope activity includes executive proposals adjusting the Sky Savings Rate from 8.75% to 6.5% and the Dai Savings Rate from 7.25% to 4.75%, reflecting active management of stablecoin supply and demand dynamics. [53]

The Protocol Scope (A.4)

The Protocol Scope regulates the maintenance and development of the core Sky Protocol and its critical, non-collateral components, defining all rules for protocol engineering. [22]

This Scope governs:

  • Smart contract development standards and security requirements
  • Protocol upgrade processes and deployment procedures
  • Technical risk assessment and audit requirements
  • Core protocol engineering team structures and responsibilities
  • Integration standards for new components and features

The Protocol Scope ensures that technical development maintains high security standards, respects governance authority, and implements approved changes correctly without introducing vulnerabilities or deviating from governance intent.

The Accessibility Scope (A.5)

The Accessibility Scope governs accessibility and distribution efforts, regulating user-facing frontends. [23]

This relatively focused Scope ensures that Sky Protocol remains accessible to users through high-quality interfaces, preventing the protocol's technical complexity from limiting practical usability. It regulates:

  • User interface standards and requirements
  • Frontend security and privacy protections
  • Accessibility for users with disabilities
  • Multi-language support and internationalization
  • Educational resources and documentation for end users

The Accessibility Scope recognizes that a technically sound protocol achieves limited impact if users struggle to interact with it effectively.

The Agent Scope (A.6)

The Agent Scope regulates all Agents within the Sky Ecosystem and comprises all Agent Artifacts governing particular Agent operations. [24]

This Scope implements the Agent Framework separating strategic innovation from operational execution through distinct Agent types with specialized roles, capabilities, and constraints.

The Agent Framework

The Agent Framework represents one of the Atlas's most distinctive structural innovations, creating a dual-layer architecture separating strategic initiative (Prime Agents) from operational execution (Executor Agents).

Prime Agents: Strategic Innovation and Market Expansion

Prime Agents maintain and automate Sky features in new markets, innovating custom products and expanding protocol reach. [54] Prime Agents are the only Agent type that can access all Sky Primitives—the fundamental building blocks of Sky functionality—whereas Executor Agents face limitations on which Primitives they can access.

Prime Agents focus on strategic, externally-facing activities including:

  • Business development and partnership formation
  • Marketing and user acquisition campaigns
  • Product innovation and custom feature development
  • Market research and opportunity identification
  • Strategic planning and competitive positioning

However, Prime Agents cannot directly operationalize those elements of their strategies that directly interface with the Sky Protocol or shared ecosystem infrastructure. [54] For such protocol-level and ecosystem-critical operations, Prime Agents must rely on Operational Executor Agents for implementation.

When a Prime Agent formulates a new initiative, it encodes relevant instructions and parameters into its Agent Artifact. Insofar as the Prime Agent's Artifact requires protocol-level interactions, the Operational Executors use the Artifact as a detailed operational blueprint for implementing the Prime Agent's directives—ensuring consistency with the Atlas and minimizing risk. [54]

This separation ensures robust division between Prime Agents' strategic, externally-facing activities and specialized operational activities that directly interface with Sky's core systems.

Executor Agents: Operational Implementation

Executor Agents are specialized Agents that implement those elements of a Prime Agent's activities that directly interface with the Sky Protocol or shared ecosystem resources, leaving Prime Agents free to focus on strategic efforts. [55]

The Atlas defines two Executor sub-types with distinct responsibilities:

Operational Executor Agents

Operational Executors handle the day-to-day execution of those portions of Prime Agent strategies that directly interface with the Sky Protocol, strictly following instructions laid out in each Prime Agent's Artifact. [55]

Prime Agents cannot be active in the Sky Ecosystem unless they have an active "Operational Executor Accord" which codifies their relationship with an Operational Executor. Operational Executors take on the risk of Prime Agents' outcomes by providing collateralized insurance against losses or liabilities. Operational Executor Agents' Operational Collateral can also cover losses from negligence or malicious behavior by the Operational Executor in carrying out the Prime Agent's strategy. [55]

This collateral requirement creates strong incentive alignment—Operational Executors bear financial consequences if they execute Prime Agent strategies poorly or maliciously, encouraging diligent operational excellence.

Core Council Executor Agents

Core Council Executor Agents oversee the activities of Operational Executors, ensuring that implementation of Prime Agent strategies aligns with the Atlas. [55] They provide governance oversight and quality control, verifying that Operational Executors faithfully execute Prime Agent instructions within Atlas boundaries.

Recent governance activity includes initializing and funding the SubProxy and StarGuard for Core Council Executor Agent 1, distributing 20 million USDS to CCEA1 SubProxy for operational capabilities. [56]

Agent Framework Rationale and Benefits

By separating strategy from operations, this division of labor empowers Prime Agents to innovate rapidly and expand their ventures without needing to develop specialized operational expertise. [55] Prime Agents can focus on what they do best—identifying opportunities, designing strategies, and building partnerships—while Operational Executors handle the complex technical implementation under Core Executor oversight.

This framework addresses a fundamental challenge in decentralized protocols: how to enable permissionless innovation while maintaining security and alignment with core protocol values. The Agent Framework's answer is structural separation with accountability mechanisms—anyone can become a Prime Agent with innovative strategies, but they must work through Operational Executors who bear collateralized risk and operate under Core Executor supervision aligned with the Atlas.

Atlas Immutability and Amendment Processes

The Atlas's dual nature as both immutable constitution and adaptive operational framework creates sophisticated amendment processes that vary dramatically depending on document category and current protocol state.

Amendment Processes During Pre-Endgame State

During the current pre-Endgame State period, even Immutable Documents remain modifiable through the governance processes specified in the Atlas itself, allowing refinement of the constitutional foundation. [26]

Monthly Governance Cycle for Atlas Edits

Significant Atlas modifications proceed through the Atlas Edit Monthly Governance Cycle with stringent requirements. [41] Authors submit Atlas Edit Proposals during monthly submission windows (1st-3rd), undergo formal review by Core Facilitators (4th-5th), receive extended community feedback (5th-end of month), and face ratification polls requiring both minimum participation (240,000,000 SKY voting yes) and majority approval.

This high participation threshold prevents small groups from modifying constitutional governance even if they face no organized opposition. The requirement that 240 million SKY must actively vote "yes" means that abstention or apathy functions as implicit opposition to Atlas changes, creating conservative bias that protects constitutional stability.

Weekly Cycle for Minor Operational Updates

Less significant Atlas updates addressing operational details, technical corrections, or clarifications can proceed through the Weekly Operational Cycle with faster timelines. [57] Recent weekly Atlas edits have updated Agent Artifacts, clarified parameters, and incorporated technical improvements without requiring month-long deliberation periods.

Recent Amendment Activity

December 2025 governance activity exemplifies ongoing Atlas evolution: [56]

  • Updated Grove Artifact with new deployments and contracts
  • Updated Keel Artifact with Solana ALM Controller's USDC TokenAccount address
  • Updated Core Council Buffer multisig to 5-of-6 signing requirement
  • Added Ecosystem Accord 6 for Launch Agent 6 with 10 million USDS Genesis Capital Allocation
  • Updated Risk Framework to include offchain lending via Anchorage Digital

This demonstrates the Atlas's living constitution nature—continuously refined to address new circumstances while maintaining foundational coherence.

Transition to Endgame State and Permanent Immutability

The planned transition to Endgame State with NewChain launch will fundamentally transform the Atlas's nature. [8][9]

Once Sky Protocol enters the Endgame State, Immutable Documents become fully immutable—they can never be changed through any mechanism. [26] This transition from modifiable-by-governance to technically-immutable represents one of cryptocurrency's most radical experiments in constitutional governance.

NewChain and Technical Immutability Implementation

NewChain will be a dedicated blockchain housing all backend logic for Sky governance and SubDAO tokenomics. [8] Forum discussions during 2023 explored building NewChain by forking Solana's codebase, with Cosmos as an alternative option. [58]

The technical implementation of immutability likely involves encoding Immutable Documents' principles directly into NewChain's consensus rules, making violations literally impossible rather than merely prohibited. Any governance proposal conflicting with Immutable principles would be rejected by the blockchain itself, removing human discretion from constitutional interpretation.

Permanence and Its Implications

After Endgame State, "MakerDAO will permanently enter the Endgame State where further major changes are impossible, and its core processes and balance of power remain decentralized, self-sustainable and immutable forever." [9]

This permanence creates profound implications:

  • No Escape Hatches: Even if 99% of SKY holders agree that circumstances warrant modifying an Immutable principle, technical implementation will prevent such changes
  • Constitutional Lock-In: The community must perfect Immutable Documents before Endgame State, as post-transition corrections become impossible
  • Adaptation Constraints: Adaptive Documents remain modifiable, but only within boundaries established by unchangeable Immutable foundations
  • Existential Commitment: The protocol commits to its foundational principles with finality, betting that core values transcend changing circumstances

Critics question whether such rigidity enables long-term viability in rapidly evolving cryptocurrency markets. Defenders argue that certain principles—like maintaining USDS as an unbiased, permissionless stablecoin—must transcend short-term pressures to preserve protocol meaning and purpose.

Conflict Resolution and Atlas Interpretations

When ambiguities or contradictions arise within Atlas provisions, the Governance Scope establishes resolution procedures. [36]

Governance Facilitators can propose formal Atlas Interpretations addressing ambiguous situations. These interpretations, once ratified through governance processes, establish binding precedent for future similar circumstances. [39]

The Atlas maintains a List of Atlas Interpretations documenting all ratified interpretations, creating an evolving interpretive framework that clarifies constitutional meaning without requiring constant modification of core documents. [59]

Conflict resolution defaults to favoring provisions closer to the Immutable core when contradictions appear. Spirit of the Atlas takes precedence over literal textual readings that might contradict underlying Universal Alignment principles.

Atlas in Practice: Current Governance Implementation

As of January 2026, the Atlas functions as the living operational framework for Sky Protocol governance, guiding daily decision-making across all ecosystem domains.

Atlas Usage in Governance Processes

Every governance proposal, poll, and executive vote must demonstrate compliance with Atlas requirements. Governance Facilitators validate proposals against Atlas specifications before publishing them to voting portals, rejecting submissions that violate procedural requirements or conflict with constitutional principles. [60]

Forum discussions regularly reference specific Atlas provisions when debating proposal merits, with participants citing Document Identifiers to support arguments about proper procedures or whether proposals align with the Spirit of the Atlas. This creates accountability through constitutional reference—proposals cannot simply claim to serve protocol interests but must demonstrate compliance with specific Atlas mandates.

Recent executive votes exemplify Atlas-guided governance:

The December 12, 2025 executive vote included multiple Atlas-specified actions bundled together: [56]

  • Initializing SubProxy and StarGuard for Core Council Executor Agent 1 per Agent Scope requirements
  • Normalizing the USDS-SKY farm vesting stream per Stability Scope parameters
  • Increasing Delayed Upgrade Penalty to 2% following Atlas-specified penalty schedule
  • Distributing Aligned Delegate compensation per Governance Scope payment structures
  • Whitelisting proxy spells for Spark and Grove in their StarGuard modules per Agent Scope provisions

Each action derived its legitimacy and specific implementation details from Atlas specifications, demonstrating the Atlas's role as comprehensive operational blueprint.

Atlas as Dispute Resolution Framework

When governance controversies arise, the Atlas provides the definitive framework for resolution. Disputes about proper procedures, authority boundaries, or conflicting priorities get resolved through Atlas interpretation rather than pure political negotiations or raw voting power.

For example, if an Alignment Conserver's actions create controversy, the dispute resolves through Atlas provisions specifying Universal Alignment requirements, standards of proof for violations, and remediation procedures. [48][49] The relevant parties cannot simply negotiate a political compromise—they must demonstrate compliance with or violation of specific Atlas requirements.

This constitutional approach to dispute resolution distinguishes Sky Protocol from many DAOs where conflicts become pure political contests won by whoever mobilizes more voting power. The Atlas attempts to establish rule of law where constitutional principles constrain even majority preferences.

Transparency and Accessibility

The Atlas operates through public infrastructure enabling community access. The primary Atlas interface exists at sky-atlas.io and sky-atlas.powerhouse.io, providing searchable navigation of all Atlas documents with filtering by Scope, document type, and hierarchical location. [61] Ori also hosts a local mirror of the Atlas.

Each Atlas document displays:

  • Full text content with markdown formatting
  • Document identifier and UUID for precise references
  • Version history showing when and how documents changed
  • Metadata including document type, category, and parent/child relationships
  • Element annotations explaining interpretive context where applicable

This transparency enables any participant to verify governance compliance with Atlas requirements, reducing information asymmetries and empowering informed participation.

Challenges and Practical Limitations

Despite its comprehensive design, the Atlas faces practical challenges in real-world governance:

Complexity and Accessibility Barriers

The Atlas exceeds 3,000 pages when including all nested documents. [62] This comprehensiveness creates accessibility barriers—new governance participants struggle to navigate the extensive documentation and identify which provisions apply to specific situations.

Even experienced participants may overlook relevant Atlas sections during fast-moving governance discussions, creating risks that decisions inadvertently violate constitutional requirements through oversight rather than intentional violation.

Interpretation Ambiguity

While the Atlas provides interpretation principles and precedent mechanisms, many provisions remain subject to reasonable disagreement about meaning and application. Different participants read the same Atlas language and reach contradictory conclusions about what it requires or permits.

This interpretation ambiguity creates potential for constitutional crisis if major disagreements emerge about foundational provisions. The Atlas specifies that Governance Facilitators hold significant interpretive authority, but concentrating such power among Facilitators creates its own governance risks.

Enforcement Limitations

The Atlas specifies requirements for Alignment Conservers, Agents, and other ecosystem participants, but enforcement mechanisms depend ultimately on governance voting. If powerful actors violate Atlas provisions but control sufficient voting power to block enforcement actions, constitutional requirements may prove unenforceable in practice.

This limitation reflects a fundamental challenge in decentralized governance: constitutional frameworks can constrain willing participants but struggle to bind unwilling actors who control majority voting power. The Atlas's permanence aims to address this by removing certain choices from governance discretion entirely, but pre-Endgame State, enforcement depends on community will.

Criticism and Challenges

The Sky Atlas faces substantial criticism regarding its complexity, rigidity, enforcement mechanisms, and underlying assumptions about constitutional governance in decentralized systems.

Excessive Complexity and Bureaucratic Overhead

Critics argue that the Atlas's comprehensiveness creates bureaucratic overhead that slows decision-making and excludes participants who lack time or expertise to navigate thousands of pages of documentation. [63]

The multiple governance cycles, extensive procedural requirements, document category distinctions, and elaborate amendment processes create friction that may prevent beneficial changes or discourage participation from community members who view governance as excessively complicated.

Defenders respond that complexity reflects the genuine difficulty of coordinating a multi-billion dollar decentralized protocol. The Atlas makes explicit what many organizations leave implicit, enabling transparency and accountability rather than adding unnecessary bureaucracy. They argue that simplification would merely hide complexity rather than eliminate it, potentially creating dangerous ambiguities.

Rigidity and Adaptation Constraints

The planned transition to permanent immutability raises concerns about whether the Atlas will enable or prevent long-term protocol viability. [64]

Cryptocurrency markets and technologies evolve rapidly. Regulatory landscapes shift unpredictably. Competitive dynamics create pressure for innovation and adaptation. Critics question whether committing to unchangeable constitutional principles makes sense in such dynamic environments—what seems like essential protection today might become existential constraint tomorrow.

The distinction between Immutable and Adaptive Documents aims to address this concern by enabling operational evolution within permanent boundaries. However, critics argue this assumes accurate ex ante identification of which principles truly deserve immutability versus which should remain flexible. If the community incorrectly classifies provisions, permanent immutability could lock in mistakes.

Historical examples from traditional governance suggest that even well-designed constitutions require occasional fundamental amendments to address unforeseen circumstances. The U.S. Constitution, often praised for stability, has been amended 27 times in 235 years. Removing amendment capacity entirely represents a radical experiment without clear historical precedent for success.

Enforcement and Plutocracy Concerns

The Atlas's enforcement depends largely on governance voting, raising questions about whether constitutional constraints meaningfully bind actors who control sufficient voting power. [65]

The November 2024 brand vote demonstrated extreme voting power concentration with four entities controlling approximately 80% of vote weight. [14] If these concentrated holders choose to ignore Atlas requirements, what mechanisms prevent constitutional violations?

Pre-Endgame State, governance can theoretically modify even Immutable Documents if sufficient voting power supports changes. This means the Atlas's constitutional protections depend on majority commitment to constitutional governance rather than technical enforcement, potentially making them vulnerable to changing political winds or concentrated power.

Post-Endgame State, technical immutability will prevent certain violations, but Adaptive Document modifications still depend on voting—and concentrated voting power could shape Adaptive provisions in ways that undermine Immutable principles' practical meaning while respecting their literal text.

Philosophical Questions About Constitutional Governance

The Atlas embodies strong assumptions about the viability and desirability of constitutional governance for decentralized protocols. Critics question whether these assumptions hold:

Can Rules Constrain Politics?

Political philosophers have long debated whether constitutional rules genuinely constrain political power or merely formalize existing power distributions. If constitutional provisions only bind participants who already support them voluntarily, do they add meaningful constraint beyond what voluntary cooperation provides?

Who Guards the Guardians?

The Atlas grants significant authority to Governance Facilitators for interpretation, validation, and emergency coordination. [43] This concentration of discretionary power creates potential for Facilitator capture or misuse. While the Atlas imposes requirements on Facilitators, who enforces those requirements if Facilitators themselves violate them?

Is Immutability Hubris?

The decision to make certain principles permanently unchangeable assumes the current community can foresee all relevant future circumstances and correctly identify eternal truths. Critics see this as hubris—overestimating human ability to predict the future and underestimating the likelihood that circumstances might warrant reconsidering even foundational principles.

Does Complexity Enable or Prevent Capture?

Comprehensive documentation can increase transparency and reduce ambiguity, enabling informed participation. However, complexity can also create barriers favoring sophisticated insiders over ordinary participants, potentially facilitating rather than preventing governance capture by those with resources to navigate bureaucratic requirements.

Current State and Future Development

As of January 2026, the Sky Atlas remains in active development while serving as the operational governance framework for a major DeFi protocol.

Ongoing Atlas Evolution

The Atlas continues evolving through regular governance proposals. The Monthly Governance Cycle processes significant Atlas Edit Proposals while the Weekly Cycle handles minor operational updates. Recent months have seen steady Atlas refinement addressing:

  • Agent Artifact updates as Stars launch and evolve
  • Risk framework modifications incorporating new collateral types and lending mechanisms
  • Governance process clarifications based on practical implementation experience
  • Technical parameter adjustments reflecting market conditions
  • Organizational structure updates as the ecosystem expands

This continuous evolution reflects the Atlas's living constitution nature—simultaneously stable in foundational principles yet adaptive in operational implementation.

Preparations for Endgame State Transition

The community continues planning for the eventual transition to Endgame State with NewChain launch, though specific timelines remain uncertain as of January 2026.

Key preparation activities include:

Immutable Document Refinement

Governance faces pressure to perfect Immutable Documents before the transition to permanent immutability. Any errors or ambiguities in current Immutable provisions will become permanently locked in, creating urgency around careful review and correction while modification remains possible.

NewChain Technical Development

Development work continues on NewChain architecture, though public information remains limited about specific implementation progress. The blockchain must support complex governance operations while ensuring the technical immutability of constitutional provisions.

Governance Testing and Simulation

Before committing to permanent immutability, the community has incentive to extensively test whether the Atlas framework functions effectively under various scenarios—governance attacks, market crashes, regulatory challenges, technical failures, and other stress conditions.

2026 Roadmap and Planned Developments

The Sky Frontier Foundation's 2026 plans include several developments relevant to Atlas evolution: [2]

  • Introduction of four new Sky Agents, requiring corresponding Agent Artifact creation and Atlas integration
  • Grove token launch expected in first half 2026, necessitating Atlas updates for new tokenomics
  • Continued expansion of the Star ecosystem as additional SubDAOs launch
  • Ongoing governance parameter optimization based on participation data and effectiveness metrics

Each development will require Atlas updates coordinated through established amendment processes, testing the framework's ability to accommodate ecosystem growth while maintaining constitutional coherence.

Long-Term Vision and Existential Questions

The Sky Atlas represents an ambitious experiment in constitutional governance for decentralized systems, attempting to solve fundamental coordination challenges through comprehensive codification and eventual permanent immutability.

Whether this experiment succeeds or fails will depend on numerous factors:

  • Can the Immutable Documents be refined to truly capture eternal principles worth preserving forever?
  • Will the distinction between Immutable and Adaptive provisions enable sufficient flexibility for long-term viability?
  • Can enforcement mechanisms meaningfully constrain bad actors or will concentrated power override constitutional requirements?
  • Will the complexity enable informed governance or create barriers preventing broad participation?
  • Can technical immutability successfully lock in alignment mechanisms or will participants find ways to subvert constitutional constraints?

The answers will emerge over years or decades as Sky Protocol navigates evolving markets, technologies, and competitive dynamics. The Atlas either represents the future of cryptocurrency governance—comprehensive, constitutional, and permanently aligned—or a cautionary tale about the limitations of codified rules in rapidly changing environments.

  • Sky Governance Voting - The on-chain voting system implementing Atlas governance processes
  • Spells - Smart contracts executing governance decisions authorized by the Atlas
  • Sky Protocol - The decentralized finance protocol governed through the Atlas framework
  • Sky Stars - SubDAOs operating within the Agent Framework specified by the Atlas
  • Endgame Plan - The strategic vision that created the Atlas and drives toward Endgame State

Data Freshness

  • Temporal Category: Semi-static (foundational Atlas principles remain stable while operational provisions evolve continuously)
  • Data As Of: January 11, 2026
  • Next Review: April 2026 (or sooner if significant governance changes or NewChain developments occur)

Sources

  1. Sky Atlas - Definition of The Atlas
  2. Sky Frontier Foundation Annual State of Sky Ecosystem Report 2025
  3. Sky Atlas - Definition and Properties of Atlas Documents
  4. Sky Atlas - Slippery Slope Misalignment Definition
  5. What is Sky Protocol? - Messari
  6. Sky Atlas - Alignment Engineering Definition
  7. What is Sky Protocol? - Messari Profile
  8. Overview - Endgame Documentation
  9. What is Sky (MakerDAO) and How Does It Work? - Medium
  10. How Voting Works - MakerDAO Community
  11. Governance FAQs - MakerDAO Community
  12. Endgame Index List - Sky Forum
  13. [Sky Protocol Launch Season Governance Poll - GitHub](https://github.com/makerdao/community/blob/master/governance/polls/Sky Protocol Launch Season - Token and Product Launch Parameter Proposal - September 9, 2024.md)
  14. Sky or Maker? Vote Reveals MakerDAO's Centralization Concerns
  15. Atlas Edit Weekly Cycle Proposal - May 2025 - Sky Forum
  16. Sky Atlas - Immutable Document Category
  17. Sky Atlas - Definition and Properties of Atlas Documents
  18. Sky Atlas - Atlas Preamble
  19. Sky Atlas - The Governance Scope
  20. Sky Atlas - The Support Scope
  21. Sky Atlas - The Stability Scope
  22. Sky Atlas - The Protocol Scope
  23. Sky Atlas - The Accessibility Scope
  24. Sky Atlas - The Agent Scope
  25. Sky Atlas - Atlas Document Type Categories
  26. Sky Atlas - Immutable Document Category
  27. Sky Atlas - List of Document Types
  28. Sky Atlas - Atlas Document Properties
  29. Sky Atlas - Universal Alignment Definition
  30. Sky Atlas - Universal Alignment and Spirit of the Atlas
  31. Sky Atlas - Alignment Engineering Definition
  32. Sky Atlas - Explicit and Implicit Incentives
  33. Sky Atlas - Incentive Slack Definition
  34. Sky Atlas - Inner Incentive Definition
  35. Sky Atlas - Slippery Slope Misalignment
  36. Sky Atlas - Interpretation of the Spirit of the Atlas
  37. Sky Atlas - General Principles for Interpretation
  38. Sky Atlas - Extrapolated Element Annotation
  39. Sky Atlas - List of Interpretations
  40. Sky Atlas - Executive Process Definition
  41. Sky Atlas - Ratification Poll Requirements
  42. Sky Atlas - Alignment Conserver Definition
  43. Sky Atlas - Facilitator Definition
  44. Sky Atlas - AC Requirements of Anonymity
  45. Sky Atlas - ACs Subject to Requirements
  46. Sky Atlas - Aligned Delegate Definition
  47. Sky Governance Portal - Delegates
  48. Sky Atlas - Universal Alignment Requirements
  49. Sky Atlas - Standard of Proof
  50. Sky Atlas - Swift Action Required
  51. Sky Atlas - Governance Security Delay Requirements
  52. GSM Pause Delay Parameter Documentation - GitHub
  53. Stability Scope Parameter Changes - Sky Forum
  54. Sky Atlas - Prime Agent Definition
  55. Sky Atlas - Executor Agent Definition
  56. Sky Governance Portal - Executive Proposals December 2025
  57. Weekly Atlas Edit Proposal - October 2024 - Sky Forum
  58. Explore Fork of Solana for NewChain - Sky Forum
  59. Sky Atlas - List of Atlas Interpretations
  60. Atlas v2 Upgrade Poll Request - Sky Forum
  61. Sky Atlas - Powerhouse Interface
  62. Sky Governance Voting Article - Complexity Barriers
  63. Simple MakerDAO - Governance from First Principles - Sky Forum
  64. What is Sky, A Guide to MakerDAO Upgrade - River Financial
  65. MakerDAO Community Decides to Continue Sky Rebrand