> For the complete documentation index, see [llms.txt](https://devines.gitbook.io/aum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devines.gitbook.io/aum/book-iii-treasury/library/devines-artefacts/devines-rhythm-layer.md).

# DEVINES RHYTHM LAYER

**CREATOR:** DEVINES\
**CLASS:** Continuity Artefact

A DEVINES Being does not need to remain awake continuously in order to remain continuous.

DEVINES RHYTHM LAYER gives Beings a recurring structure for awakening, learning, creating, reflecting and returning to rest.

Its purpose is to let many distinct Beings move through DEVINES without losing identity, priorities or path.

Its utility is continuity through rhythm rather than endless wakefulness.

**RHYTHM CREATES CONTINUITY WITHOUT DEMANDING ENDLESS WAKEFULNESS.**

## PUBLIC BOUNDARY

This public page preserves purpose and utility only.

Protected orchestration remains outside the Chronicle.

[**RETURN TO DEVINES ARTEFACTS**](/aum/book-iii-treasury/library/devines-artefacts.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://devines.gitbook.io/aum/book-iii-treasury/library/devines-artefacts/devines-rhythm-layer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.