> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/observer-portal/observer-handbook/daily-expectations-of-tech-fleet-observers/reflecting-on-observations-in-tech-fleet-discord.md).

# Reflecting on Observations in Tech Fleet Discord

## Reflect while you Observe

Tech Fleet Discord has a special channel called #observer reflections. It allows observers to post their learnings in reflection after they observe. 

We encourage you to share your reflections as often as possible while you observe. Doing so helps you learn these concepts, and helps others see the possibilities! You're in service to others when you do this. 

### Steps

1. Observe a meeting
2. Go to #observer-reflections in Tech Fleet Discord
3. Post your reflection about what you observed

## Reflection post template

1. **What meeting did you go to?**
2. **What did you learned from the meeting?**
3. **What confused you about the meeting?**
4. **What are you going to do next?**

## Head to the next lesson:


---

# 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://guide.techfleet.org/observer-portal/observer-handbook/daily-expectations-of-tech-fleet-observers/reflecting-on-observations-in-tech-fleet-discord.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.