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

# About Logos

Logos is pioneering a fully decentralised technology stack designed to empower self-sovereign virtual territories within the Logos cybernation. Staying true to the original vision of web3, Logos comprises three core protocols: Codex (a durable storage protocol), Waku (a decentralised messaging protocol), and Nomos (a fully private layer-1). Together, these protocols lay the groundwork for truly decentralised applications, onchain societies, and borderless public institutions.

{% embed url="<https://x.com/i/status/1831683953528324542>" %}

Sovereign communities within the Logos cybernation form the grassroots movement needed to build the social, economic, and governing institutions that will live on the technology stack.

Eventually, these institutions will populate a competitive marketplace that can fill gaps in governance in the real world, providing trust-minimised, corruption-resistant public services wherever the internet can reach.


---

# 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://gitbook.logos.co/logos/about-logos.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.