> For the complete documentation index, see [llms.txt](https://project-ade.gitbook.io/project-ade-framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://project-ade.gitbook.io/project-ade-framework/overview.md).

# Overview

> **Note:** ADE is not a replacement for existing calendars. It is a shared framework that connects them, similar to how GPS provides a universal reference while allowing different maps to exist.

### The Problem

Humanity currently has many ways of measuring time:

* Gregorian calendar
* Religious calendars
* National calendars
* Scientific time systems
* Business calendars
* Future planetary calendars

Each serves a purpose, but there is no shared timeline representing the journey of humanity itself.

### The Core Idea

ADE proposes adding this missing layer: **a Human Timeline Reference**, a way to answer:

> "Where are we in the story of humanity?"

### Operating Framework

The framework is based on recurring human cycles, applicable at the individual, organizational, civilizational, and (eventually) interplanetary level:

| Phase          | Meaning                                                              |
| -------------- | -------------------------------------------------------------------- |
| **Learn**      | Discovery, education, understanding, acquiring knowledge             |
| **Build**      | Creating, developing, innovating, applying knowledge                 |
| **Contribute** | Sharing value, helping society, advancing humanity                   |
| **Renew**      | Reflection, improvement, restoration, preparation for the next cycle |

### Proposed Structure

#### 1. ADE Timeline

The universal reference layer:

```
ADE Year-Quarter-Day
ADE 125-Q2-D45
```

This coexists with Earth, religious, Mars, and lunar calendars. ADE is the connection point between them.

#### 2. ADE Calendar Framework

* **Four Year Cycle**, a long term human development cycle
* **Four Annual Quadrants**, Q1 Learn, Q2 Build, Q3 Contribute, Q4 Renew
* **Daily Human Phases**, a framework for understanding daily activity cycles

#### 3. Universal Free Days

Days that exist outside the normal calendar count, serving as global synchronization points for rest, reflection, maintenance, reconciliation, planning, and celebration. Societies keep their own holidays; Universal Free Days establish a minimum shared rhythm recognized across Earth and future settlements.

### Guiding Principles

* **Open**, available for humanity to use
* **Neutral**, not owned by any religion, nation, or political group
* **Collaborative**, built through many disciplines
* **Transparent**, clear standards and governance
* **Long Term**, designed for future generations

### Adoption Path

Evolutionary, not revolutionary:

1. Technical and interoperability standard for software, AI systems, commerce, research
2. Institutions publish ADE references alongside existing dates
3. Optional civic calendar overlay, while existing traditions remain fully intact


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://project-ade.gitbook.io/project-ade-framework/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.