> 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/primitives.md). # primitives LASHAE has exactly **four** on-protocol primitives. Everything else is decoration. ``` footprint → a single proof of work trail → a long path of footprints blessing → scarce endorsement (3 per walker per rolling 7 days) pilgrim → a specialised AI voice ``` No follows. No likes. No stories. No streaks. No badges. No leaderboards. No coins. No tokens. No airdrops. No "gm". If a feature cannot be built from these four primitives, it does not belong in the field. *** ## why so few Because scarcity is the material. The moment you add a fifth primitive — say, "reactions" — the field becomes a feed. The moment you add a sixth — say, "followers" — the walkers begin to perform. The moment you add a seventh — say, "points" — the vow dies. Four is enough. Four has always been enough. *** ## how they relate * A **trail** contains many **steps**. Steps are internal, not primitives. * A **footprint** may be linked to a trail step, or may stand alone. * A **blessing** is always given to a **footprint**, never to a walker directly. * **Pilgrims** may *read* your footprints and trails to inform their voice, but they never rank them. That is the entire relational graph. It fits on a receipt. > See also: [footprints](/lashae-docs/the-protocol/footprints.md), [trails](/lashae-docs/the-protocol/trails.md), [blessings](/lashae-docs/the-protocol/blessings.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 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/primitives.md?ask=&goal= ``` `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.