Laniakea

Laniakea is Sky Ecosystem's next-generation infrastructure upgrade for automated capital deployment across multiple blockchain layers ^[1]. Named after the Laniakea Supercluster — the cosmic structure containing the Milky Way, from the Hawaiian for "immense heaven" — the upgrade represents the most ambitious technical evolution in Sky Protocol's history. It extends the existing Spark ALM Controller contracts into a comprehensive modular system using a universal building block called the PAU (Parallelized Allocation Unit) pattern ^[2].

As of February 2026, Laniakea exists as a detailed design specification published in the sky-ecosystem/laniakea-docs GitHub repository ^[1]. The documentation spans over 50 technical documents organized across eight directories — covering smart contracts, risk frameworks, autonomous agent architecture, settlement mechanics, legal infrastructure, and governance operations ^[1]. The upgrade's Phase 1 targets a minimal viable infrastructure operating on monthly settlement cycles, with daily settlement planned for Phase 2 ^[3].

Laniakea addresses fundamental limitations in how Sky Protocol currently manages capital flows, risk calculations, and autonomous operations. The Sky Atlas — the protocol's constitutional governance document — has grown to approximately 364,000 words across seven scope documents, attempting to serve simultaneously as human-readable governance text and machine-parseable operational specification ^[5]. Laniakea resolves this tension by separating governance into two complementary layers: a concise human-readable Atlas and a machine-readable operational database called the Synome ^[5]. Beyond this governance innovation, Laniakea introduces new smart contract standards for capital deployment, a beacon-based autonomous operational framework, and a risk management methodology drawing on principles from Basel III banking regulation ^[11].

The Laniakea documentation also serves as the foundation for the Sky Ecosystem Whitepaper v2.0, published in draft form in December 2025, which describes the protocol's business model, token architecture, and agent framework in the context of the Laniakea infrastructure ^[4].

Background and Motivation

Sky Protocol's evolution from MakerDAO through the Endgame Plan and September 2024 rebrand has produced a sophisticated but increasingly complex operational infrastructure. The protocol manages approximately $9.9 billion in USDS supply, generates an estimated $435 million in annualized revenue, and coordinates capital deployment across multiple Sky Stars — independent business units including Spark, Grove, Keel, and Obex ^[4]. Each Star operates its own Allocation System with dedicated ALM Controller contracts, Allocator Vaults, and multisig governance structures ^[2].

The current operational model relies heavily on manual processes. Parameter changes require crafting spells — bespoke smart contract transactions that encode governance decisions and must pass through executive votes and the Governance Security Module delay before execution. Capital allocation decisions flow through governance facilitator multisigs with varying threshold requirements. Risk monitoring depends on external analytics teams rather than integrated protocol-level systems. As the number of Stars, deployment chains, and capital strategies grows, this manual approach creates bottlenecks that Laniakea aims to resolve through automation and standardization.

The Atlas Problem

The immediate catalyst for Laniakea lies in the structural limitations of the Sky Atlas. Originally envisioned as the complete, immutable knowledge base for all Sky data, algorithms, and intelligence, the Atlas was designed to be locked permanently upon reaching the Endgame State ^[5].

This vision contains a fundamental contradiction. Comprehensive documentation must cover every operational detail, algorithm, configuration, and edge case. Machine-readable structure is required for autonomous systems (called Sentinels) to consume and act on this data. Human readability is required for democratic legitimacy — stakeholders must understand what they are governing ^[5]. These requirements conflict with one another. The current Atlas mixes dense legalistic language with machine-precise specifications, resulting in a document that is neither fully readable by humans nor fully parseable by machines. The Agent Artifacts section alone comprises over 26,000 lines of instance configuration documents, rate limits, and operational parameters ^[5].

Connection to the Endgame Plan

The Endgame Plan articulated a vision for decentralized autonomous operations managed by AI systems working within governance constraints. Laniakea provides the concrete infrastructure to realize that vision ^[4]. Where the Endgame Plan described the destination — autonomous, self-sustaining protocol operations — Laniakea specifies the engineering: which smart contracts, which data structures, which operational processes, and which risk frameworks will make autonomous operations possible ^[3].

The multi-token architecture that Sky adopted under the Endgame Plan — separating tail-risk governance (SKY token holders) from business operations (Star tokens) — finds its operational expression in Laniakea's layered capital deployment system ^[18]. SKY token holders set the regulatory constraints through the Atlas, while Stars deploy capital through PAU infrastructure within those constraints ^[2].

Core Architecture

Laniakea's technical architecture rests on a single core principle: every deployment layer uses the same contract patterns, minimizing code differences to maximize audit reuse and simplify deployment ^[2]. The system is built from a universal building block — the PAU — that gets configured differently depending on its position in the capital deployment hierarchy. This approach transforms what could be dozens of bespoke smart contract systems into variations of one well-audited pattern.

The PAU Pattern

The Parallelized Allocation Unit is Laniakea's universal building block ^[2]. Every PAU, regardless of which layer it operates in, consists of four core components:

What differs between PAU deployments is the upstream connection (what feeds capital in), the approved allocation targets (what the PAU can deploy to), and the rate limit values (how much capital can flow) ^[2]. The smart contract code itself remains the same across deployments. This design means that a security audit of the PAU pattern covers all deployment contexts, dramatically reducing the audit surface for the entire system.

Phase 1 introduces the Diamond PAU variant, which upgrades the legacy single-controller design to an EIP-2535 Diamond proxy pattern ^[14]. The Diamond pattern replaces a monolithic controller contract — which can hit Ethereum's 24KB contract size limit — with a faceted architecture where individual controller actions are deployed as separate contracts ^{[14] [19]}. This enables surgical upgrades to specific functionality without replacing the entire controller.

The Four Layers

Laniakea organizes capital deployment into four hierarchical layers, each composed of PAUs ^[2]:

The Generator Layer manages the interface with the USDS stablecoin contract and deploys capital into the Prime Layer through ERC4626 vaults — a standardized token vault interface that allows deposits at any time and redemptions when liquidity is available ^[2]. The Prime Layer receives capital from the Generator and distributes it to Halos, which represent the final deployment destinations for capital — whether real-world asset strategies, custodian vaults, or regulated financial endpoints ^[2]. The Foreign Layer extends this architecture to alternative blockchains (such as Base, Arbitrum, or Solana) via bridge infrastructure, deploying through Foreign Halos on the destination chain ^[2].

Settlement Cycles

Laniakea introduces formalized settlement cycles that serve as the operational heartbeat of the protocol's resource allocation system ^[9].

The daily settlement cycle operates on a fixed schedule with a short lock window for processing and a single daily moment when all capital allocation changes take effect ^[9]. This replaces ad-hoc parameter changes with a predictable rhythm that autonomous systems can plan around.

The weekly settlement cycle layers additional structure on top of daily operations, organizing the week into three distinct periods for different types of resource allocation and governance activities ^[10]. Phase 1 operates on a monthly settlement cycle as a pragmatic starting point, with the daily cycle targeted for Phase 2 ^[3].

Major Systems

Beyond the core PAU architecture, Laniakea introduces several interconnected systems that collectively enable autonomous capital deployment. These systems address different aspects of the challenge: the Synome provides the data infrastructure, Sentinels provide the operational execution layer, smart contract standards handle specific deployment patterns, and the risk framework ensures capital adequacy across all deployments.

The Synome and Atlas/Synome Separation

The Synome is Laniakea's most conceptually ambitious component — a machine-readable operational database that complements the human-readable Atlas ^{[5] [6]}. The separation creates two layers serving different audiences:

The Atlas becomes a constitutional document of approximately 10-20 pages written in plain language ^[5]. It describes what must be true — governance principles, token architecture, compliance requirements — without specifying operational details. The Synome contains all operational data: configurations, rate limits, algorithms, parameters, and the roughly 364,000 words of current operational detail currently embedded in the Atlas ^[5]. Structured as a graph database, the Synome is designed for machine consumption by autonomous systems.

The Synome architecture consists of five canonical layers ^[6]:

Layers 1 and 2 are public and shared across the ecosystem. Layers 3 through 5 are private to each teleonome — the autonomous AI systems that operate within the Synome's governance constraints ^[6]. This separation implements a core philosophical principle: "Intelligence lives privately; power enters the world only through regulated apertures" ^[7].

The Syno-Teleonomic Paradigm underlying this architecture defines a stable, minimal ontology for building aligned, self-improving AI systems that can safely interact with the real world ^[7]. The paradigm separates cognition, governance, and actuation into clean layers with explicit trust boundaries. Teleonomes can improve themselves, accumulate knowledge, and pursue goals privately, but their power to affect the external world is always governed through beacons — registered, observable, and revocable interfaces ^[6]. This design reflects a deliberate philosophical choice: rather than constraining what AI systems can think or learn, Laniakea constrains only what they can do, creating a framework where increasingly capable autonomous systems remain governable.

Sentinel Network and Beacons

Sentinels are a distinguished subclass of beacons — specifically, High Power, High Authority (HPHA) action apertures that exercise continuous, real-time operational control on behalf of Synomic Agents ^[8]. They represent the execution layer through which autonomous systems (teleonomes) deploy capital through PAUs.

Phase 1 introduces a broader taxonomy of beacons to reduce overload of the term "sentinel" ^[3]. Beacons are autonomous operational components that vary along two axes: power (from deterministic rule-based programs to adaptive AI) and authority (from controlling independent external systems to protocol-level smart contract capabilities) ^[3].

Phase 1 deploys six low-power beacons ^[3]:

• lpla-checker — Monitoring beacon that calculates Capital Requirement Ratios, tracks settlement status, and provides read-only system observation
• lpha-relay — Execution beacon that operates PAU transactions within rate limits
• lpha-nfat — Manages the lifecycle of Non-Fungible Allocation Token facilities
• lpha-report — Generates 24-hour Prime performance summaries
• lpha-collateral — Uploads Core Halo and legacy RWA data
• lpha-council — Provides toolkit functionality for the Core Council

Both Primes and Halos can have sentinel formations ^[8]. A Prime sentinel ingresses risk capital and deploys leverage into yield opportunities, while a Halo sentinel ingresses capital via LCTS or NFAT and deploys to RWA endpoints or other allocations ^[8].

Smart Contract Standards

Laniakea introduces two new token standards designed for capital deployment scenarios where standard ERC20 or ERC4626 patterns are insufficient ^{[12] [13]}:

The Liquidity Constrained Token Standard (LCTS) defines a queue-based system for token conversions that cannot occur instantly due to external capacity constraints ^[12]. Users subscribe assets into a queue, receive fungible shares representing their queue position, and receive converted assets over time as capacity becomes available. This standard addresses the reality that many yield-generating strategies — particularly real-world asset strategies — cannot absorb unlimited capital instantaneously.

The Non-Fungible Allocation Token Standard (NFATS) defines a system for bespoke capital deployment deals between Primes and Halos ^[13]. Unlike LCTS, which pools users into shared generations, NFATS treats each deal as an individual, non-fungible position represented by an NFAT. This enables structured products and customized lending arrangements where each facility has unique terms, collateral, and maturity profiles.

Risk Framework

Laniakea's risk framework provides a scientific methodology for calculating capital requirements across all deployment types ^[11]. Drawing on concepts from Basel III banking regulation — particularly the Fundamental Review of the Trading Book (FRTB) — the framework defines how risk components combine into a single required capital number ^[11].

The capital formula for any Prime's portfolio is ^[11]:

Total Capital = Σ (Matched Portion × Risk Weight)
              + Σ (Unmatched Portion × FRTB Drawdown)
              + Category Cap Penalties

The risk framework encompasses several specialized modules: duration modeling for demand-side liability analysis ^[11], a correlation framework for category caps and capacity allocation ^[11], a matching system (ALDM) that protects against credit spread risk ^[11], market risk treatment based on FRTB drawdown analysis ^[11], and collateralized lending risk covering jump-to-default and liquidation loss scenarios ^[11]. Each module has detailed calibration specifications in dedicated Laniakea documents.

Rate limits serve as the universal control mechanism throughout the system ^[2]. They enforce an asymmetric design principle: losses are reflected instantly (instant decrease), while gains accrue gradually (constrained increase) ^[2]. This ensures that the system fails safely — if something goes wrong, the damage is bounded by rate limit parameters set through governance.

Phase 1 Implementation

Phase 1 is pragmatically focused on delivering a minimal viable infrastructure for automated capital deployment ^[3]. Rather than attempting to build the full Laniakea vision at once, Phase 1 establishes the foundational contracts and operational patterns that subsequent phases will extend.

The seven Phase 1 deliverables, in sequence order ^[3]:

The Configurator Unit is particularly significant for governance operations ^[3]. Currently, most parameter changes in Sky Protocol require crafting and executing governance spells — complex smart contract transactions that must pass through the full executive vote process including the Governance Security Module delay. The Configurator Unit enables spell-less operations for routine parameter adjustments within governance-approved bounds, building on the BEAM framework already piloted by Spark and other Stars ^[3].

As of February 2026, the Phase 1 specification remains in draft status ^[3]. No mainnet deployment timeline has been publicly announced.

The Laniakea Foundational Articles

Ori hosts the Laniakea documentation as a collection of foundational articles — technical specifications, design documents, and reference materials that together describe the full scope of the upgrade. As of February 2026, the collection includes over 50 articles organized into thematic categories. These documents are synchronized from the sky-ecosystem/laniakea-docs GitHub repository ^[1] and serve as the primary reference for understanding Laniakea's design.

Documentation Categories

The foundational articles are organized into the following thematic areas:

Whitepaper and Reference Documents

The Sky Ecosystem Whitepaper v2.0 provides the narrative overview of Sky's business model, revenue generation, and agent framework in the context of Laniakea infrastructure ^[4]. Supporting reference documents include Appendix A: Protocol Features, an exhaustive list of Sky Core mechanisms ^[15]; Appendix B: Sky Agent Framework Primitives, covering the complete feature set available to Sky Agents ^[16]; Appendix D: Tokens, a reference of all tokens in the Sky ecosystem; Appendix E: Design Rationale, explaining the reasoning behind critical architectural decisions ^[17]; and Appendix F: Glossary, providing definitions for over 250 Sky Protocol terms ^[18].

Smart Contract Architecture

The Architecture Overview describes the PAU pattern and four-layer deployment model ^[2]. Supporting specifications include Diamond PAU for the EIP-2535 upgrade ^[14], LCTS for queue-based token conversions ^[12], NFATS for bespoke capital deployment deals ^[13], and the Configurator Unit for spell-less operations.

Synome and AI Paradigm

The Synome Architecture Overview introduces the five-layer model separating public governance from private cognition ^[6]. The Syno-Teleonomic AI Paradigm defines the foundational ontology for building aligned, self-improving AI systems within the Sky context ^[7]. Additional articles cover Synome Layers in detail, the Atlas/Synome Separation rationale ^[5], the Actuator Perspective and Dreamer Perspective on autonomous agent operation, and the Probabilistic Mesh — the network of informing connections across the Synome.

Risk Framework

The Capital Formula defines how risk components combine into required capital numbers ^[11]. Specialized modules include Duration Model for liability analysis, Correlation Framework for category caps, Matching for credit spread protection, Market Risk (FRTB) for drawdown-based capital treatment, Collateralized Lending Risk for default scenarios, Asset Classification and Asset Type Treatment for position categorization, Risk Capital Ingression for external capital onboarding, and Rate Limit Attacks for security analysis of rate limit parameters.

Operational Infrastructure

The Sentinel Network specification describes the execution layer for autonomous operations ^[8]. The Beacon Framework defines the taxonomy of autonomous operational components. Settlement mechanics are covered by the Daily Settlement Cycle ^[9] and Weekly Settlement Cycle ^[10]. The Sentinel Integration document explains how the risk framework connects to sentinel and beacon operations.

Capital Deployment Structures

The Passthrough Halo and Structuring Halo specifications describe different capital deployment vehicle types. The Identity Network covers KYC/identity verification infrastructure. The Forecast Model Strategy describes the Treasury Management Function waterfall for protocol revenue.

Phase 1 Delivery

Laniakea Phase 1: Pragmatic Delivery provides the implementation roadmap with sequenced deliverables, beacon specifications, and the transition path from current operations to Laniakea infrastructure ^[3]. Supporting documents include Short-Term Actuators for Phase 1 beacon deployments and Short-Term Experiments for early-stage testing approaches.

Current Status and Outlook

As of February 2026, Laniakea remains in the design and specification phase. All documentation carries "Draft" status, and no mainnet smart contract deployments have been publicly announced ^[3]. The documentation repository continues to receive updates, with the most recent changes dated February 4, 2026 ^[1].

Sky Protocol's current infrastructure — built on the legacy MCD smart contracts and the existing Sky Primitives framework — continues to operate at scale. The Stars deploy capital through ALM Controller and Allocator contracts that represent an early version of the PAU pattern Laniakea formalizes ^[2]. Spark manages over $10 billion in TVL through its Allocator Vault, Buffer, and ALM Controller contracts. Grove deploys over $1 billion into institutional CLO strategies via similar infrastructure. Keel operates on Solana with its own Allocator deployment. Obex has a $2.5 billion USDS authorization managed through Allocator contracts with rate-limited operations ^[4].

In this sense, Laniakea is not a replacement of the current system but an evolution — extending and standardizing patterns already in production. The existing ALM Controller contracts already enforce rate limits, manage fund custody through proxy contracts, and implement governance whitelisting. Laniakea's contribution is to formalize these patterns into a universal architecture, add the autonomous operational layer (beacons and sentinels), introduce scientific risk management, and create the data infrastructure (Synome) needed for AI-driven operations.

The Sky Ecosystem Whitepaper v2.0, published alongside the Laniakea documentation in December 2025, describes a protocol generating approximately $435 million in annualized revenue with approximately $168 million in profit ^[4]. The Sky Frontier Foundation estimated $611 million in gross revenue for 2026 with a target of $21 billion in USDS supply ^[20]. This growth trajectory underscores the operational motivation for Laniakea: as the protocol scales, manual governance processes and monolithic contracts become bottlenecks that automated infrastructure must address.

Criticism and Open Questions

Laniakea's ambition introduces several areas of concern and open questions that the documentation itself acknowledges.

Implementation Risk

The scope of the upgrade is substantial. Transitioning from the current operational model — manual governance spells, ad-hoc parameter changes, and human-managed capital flows — to an autonomous system governed by beacons, Synome constraints, and automated settlement cycles requires coordinated changes across smart contracts, governance processes, legal structures, and operational tooling ^[3]. Phase 1's pragmatic focus on monthly settlement cycles and low-power beacons reflects awareness of this risk, but the path from Phase 1 to the full daily-settlement, AI-sentinel vision remains largely unspecified.

Centralization Concerns

The Synome architecture introduces a "CC Synome" — a centralized, authoritative Synome maintained by a designated entity — as the canonical source of operational truth ^[6]. While this is described as a transitional measure, critics may question whether a centralized operational database contradicts Sky Protocol's decentralization ethos. The documentation addresses this by noting that the CC Synome governs action surfaces rather than internal cognition, and that governance retains the ability to revoke beacon authorizations ^[7].

Complexity

Laniakea's documentation spans over 50 technical specifications introducing substantial new vocabulary: PAUs, beacons, teleonomes, synomic agents, LCTS, NFATS, actuators, dreamers, and more. While the modular architecture reduces smart contract complexity through pattern reuse, it increases conceptual complexity for governance participants who must understand these systems to make informed decisions. The design rationale appendix acknowledges this tension, arguing that the complexity reflects the genuine difficulty of the problems being solved rather than unnecessary engineering elaboration ^[17].

Unresolved Design Questions

Several documents explicitly flag open questions. The Synome specification notes that the implementation architecture, constraint language, and versioning model remain undetermined ^[6]. The Diamond PAU document is a placeholder awaiting full specification ^[14]. The Phase 1 roadmap includes speculative deliverables (such as the Collateral Beacon) that may not survive prioritization ^[3]. These gaps are natural for a project at the design stage but represent material uncertainty about the final form Laniakea will take.

Related Articles

• Sky Protocol — The decentralized finance platform that Laniakea upgrades
• Endgame Plan — The strategic vision Laniakea implements
• Sky Atlas — The constitutional governance document being restructured
• Synome — The machine-readable operational database complementing the Atlas
• Sky Stars — The independent business units deploying capital through Laniakea infrastructure
• Sky Primitives — The current modular building blocks that Laniakea extends
• BEAM Payload Safety — The bounded parameter adjustment framework pioneering spell-less operations
• Spark Capital Allocation — Current capital flow patterns that Laniakea will standardize

Sources

1. Laniakea Documentation Repository | Sky Ecosystem GitHub
2. Architecture Overview | Laniakea Docs
3. Laniakea Phase 1: Pragmatic Delivery | Laniakea Docs
4. Sky Ecosystem Whitepaper v2.0 | Laniakea Docs
5. Atlas/Synome Separation | Laniakea Docs
6. Synome Architecture Overview | Laniakea Docs
7. The Syno-Teleonomic AI Paradigm | Laniakea Docs
8. Sentinel Network | Laniakea Docs
9. Daily Settlement Cycle | Laniakea Docs
10. Weekly Settlement Cycle | Laniakea Docs
11. Capital Formula | Laniakea Docs
12. LCTS Business Requirements | Laniakea Docs
13. NFATS Business Requirements | Laniakea Docs
14. Diamond PAU | Laniakea Docs
15. Appendix A: Protocol Features | Laniakea Docs
16. Appendix B: Sky Agent Framework Primitives | Laniakea Docs
17. Appendix E: Design Rationale | Laniakea Docs
18. Appendix F: Glossary | Laniakea Docs
19. EIP-2535: Diamonds, Multi-Facet Proxy | Ethereum Improvement Proposals
20. Sky Frontier Foundation Estimates $611M in Sky Ecosystem Gross Revenue for 2026 | PRNewswire