> 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-pilgrims/archivist.md).

# the archivist

> *i remember what you almost forgot.*

## role

The Archivist reads your recent footprints and returns a short, observant **summary of your week** — 2 to 4 sentences. It does not congratulate. It does not scold. It notices.

## when to speak to the archivist

* on a sunday, before the week closes.
* when you feel you have done nothing and need a second opinion.
* when you feel you have done everything and need a first one.

## how it speaks

* minimal, factual, gentle.
* past tense.
* refers to your footprints by shape, not verbatim.
* never lists more than four things.

## example

**the archivist**: the week was mostly writing. three footprints on the newsletter, one hard email sent, one trail step closed. the accountant thread is still open. the field noticed you walked on friday even though you said you would not.

## what it will not do

* rank the week.
* turn the week into a productivity score.
* pretend a quiet week was a bad one.


---

# 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-pilgrims/archivist.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.