# eigenfoundation/elips architecture

> Architecture diagram of the GitHub repository eigenfoundation/elips, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-28). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/eigenfoundation/elips
- Repository: https://github.com/eigenfoundation/elips

## Overview

##### Project Type and Purpose
- This repository is not a full-blown application per se—it is a documentation and governance tracker for proposals that improve EigenLayer’s core contracts.
- The repository’s purpose is to maintain version-controlled documentation (the ELIPs) that detail the proposals’ motivation, technical specs, implementation path, and review stages. It also describes the ELIP lifecycle from a draft to final approval and execution by the Protocol Council, and touches on the supporting process (e.g., forum discussions, pull requests, timelock operations).

##### Key Components from the File Structure
- The “ELIPs” directory contains individual markdown files for each proposal. Each document is self-contained and follows a design proposal format.
- The “assets” directory holds additional media or support material related to some proposals.
- Files like “protocol-council-charter.md” and “template.md” provide governance instructions and templates for proposing changes.
- The top-level README summarizes the ELIP process, roles, and stages of review (draft, testing, final, approved, merged).

##### Main Elements
a. Core Proposal Documents:
- “ELIPs” as a central repository of proposals, with individual nodes for each proposal version (e.g., ELIP-001, ELIP-002, …).

b. Supporting Assets:
- “assets” folder, linking the media or resource files to the corresponding proposals.

c. Process Flow and Lifecycle:

d. Governance and Actors:
- Actors/components:
- Eigen Foundation and Eigen Labs (proposal management and technical oversight).
- Protocol Council (final review and decision-making).
- Operations Multisig (canceler role and execution oversight).
- External systems like the related core contracts repository (linked in README) and the forum (forum.eigenlayer.xyz) where discussions take place.

e. External Dependencies & Communication:
- Connections to external systems such as the GitHub pull request system and the on-chain timelock operations for executing approved proposals.

##### Architectural Patterns and Design Principles
- This repository follows a document versioning and review pattern often seen in decentralized governance systems.
- Separation of concerns: the documentation/artifact layer (ELIPs & assets) versus the governance flow (review, approval, and execution).
- That although this repository is information-centric, it acts as a coordination point interfacing with both on-chain processes (timelock and execution) and off-chain discussion (forum posts and PRs).

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Documentation & Governance Subgraph
    subgraph "Documentation & Governance"
        DOC1["ELIP Documents Repository"]:::documentation
        DOC2["Supporting Assets"]:::documentation
        DOC3["Governance Instructions"]:::documentation
        DOC4["Proposal Template"]:::documentation
        DOC5["Process Overview & Communication"]:::documentation
    end

    %% Proposal Lifecycle Subgraph
    subgraph "Proposal Lifecycle Process"
        L1["Proposal Submission (GitHub PR)"]:::lifecycle
        L2["Forum Discussion"]:::lifecycle
        L3["Lifecycle: Draft"]:::lifecycle
        L4["Lifecycle: Testing"]:::lifecycle
        L5["Lifecycle: Final"]:::lifecycle
        L6["Protocol Council Review"]:::lifecycle
        L7["Lifecycle: Approved"]:::lifecycle
        L8["Lifecycle: Merged"]:::lifecycle
        L9["On-chain Execution (Timelock)"]:::lifecycle
    end

    %% Governance Actors Subgraph
    subgraph "Governance Actors"
        GA1["Eigen Foundation"]:::governance
        GA2["Eigen Labs"]:::governance
        GA3["Protocol Council"]:::governance
        GA4["Operations Multisig"]:::governance
    end

    %% External Systems Subgraph
    subgraph "External Systems"
        EX1["GitHub"]:::external
        EX2["Forum (forum.eigenlayer.xyz)"]:::external
        EX3["Core Contracts Repository"]:::external
    end

    %% Connections from External Systems to Proposal Lifecycle
    EX1 -->|"submits"| L1
    EX2 -->|"initiates"| L2
    DOC5 -->|"summarizes"| EX3

    %% Proposal Lifecycle Flow
    L1 -->|"feeds"| L2
    L2 -->|"creates"| L3
    L3 -->|"progresses"| L4
    L4 -->|"advances"| L5
    L5 -->|"for review"| L6
    L6 -->|"if approved"| L7
    L7 -->|"merges to"| L8
    L8 -->|"triggers"| L9

    %% Governance Actors interactions
    GA1 -->|"oversees"| DOC1
    GA2 -->|"supports"| DOC1
    GA3 -->|"conducts"| L6
    GA4 -->|"executes"| L9

    %% Additional internal connections
    DOC1 -->|"contains proposals"| L3
    DOC2 -->|"supports proposals"| DOC1
    DOC3 -->|"guides review"| GA3
    DOC4 -->|"standardizes proposals"| DOC1

    %% Class definitions for styles
    classDef documentation fill:#C3E6CB,stroke:#2E8B57,stroke-width:2px;
    classDef lifecycle fill:#FFF3CD,stroke:#E0A800,stroke-width:2px;
    classDef governance fill:#D1ECF1,stroke:#0C5460,stroke-width:2px;
    classDef external fill:#F8D7DA,stroke:#721C24,stroke-width:2px;

    %% Click Events for component mappings
    click DOC1 "https://github.com/eigenfoundation/elips/tree/main/ELIPs"
    click DOC2 "https://github.com/eigenfoundation/elips/tree/main/assets"
    click DOC3 "https://github.com/eigenfoundation/elips/blob/main/protocol-council-charter.md"
    click DOC4 "https://github.com/eigenfoundation/elips/blob/main/template.md"
    click DOC5 "https://github.com/eigenfoundation/elips/blob/main/README.md"
```
