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

# blessings

A blessing is the only form of praise the field permits.

There are no likes. No hearts. No fire emojis. No "keep going, king". There is one thing: a blessing, given by one walker to another walker's footprint.

## the scarcity rule

**Every walker may give at most three blessings in any rolling 7-day window.**

This is enforced at the database level. The trigger cannot be bypassed by the client, the wallet, or the pilgrims. If you try to give a fourth, the field returns a single line:

> *you have already blessed three this week. wait, or walk.*

Three is not arbitrary. Three is the number below which every blessing must be *considered*. Two feels stingy. Four feels casual. Three requires you to choose.

## what a blessing carries

| field         | meaning                                               |
| ------------- | ----------------------------------------------------- |
| **from**      | the walker giving the blessing.                       |
| **to**        | the footprint being blessed. never a walker directly. |
| **note**      | optional. one line. minimal.                          |
| **timestamp** | when the field received it.                           |

Blessings are **not** counted publicly on a walker's profile as a badge or a score. A blessed footprint is subtly marked on its receipt. That is all.

## why blessings are given to footprints, not walkers

Because to bless a walker is to bless a personality. To bless a footprint is to bless a *piece of work*. The field is a place for work. Personalities are welcome, but they are not the currency.

## receiving a blessing

You will receive a blessing in one of two ways:

1. **quietly**, on the receipt of the footprint that was blessed. no notification unless you have opted in.
2. **in the blessings feed** at [/blessings](https://lashae.us/blessings), which shows the last blessings across the field — never ranked, only chronological.

There is no notification storm. There is no "you got 12 blessings this week". The field will not turn your work into a dashboard.

## the ethics of the blessing

* do not bless work you have not read.
* do not bless friends because they are friends.
* do not bless in exchange for a blessing.
* do bless the small footprint that took courage.
* do bless the footprint that felt honest, even if unfinished.

Blessings are the only social object in LASHAE. Guard them.


---

# 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://lashae.gitbook.io/lashae-docs/the-protocol/blessings.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.