> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/demo-website/public/demo/trend-finder-assets.md).

# Trend Finder Public Demo Assets

This directory is reserved for reviewed public Trend Finder assets copied by the local snapshot exporter.

No asset is committed until all of these are true:

* The source-compliance document allows the asset or metadata class.
* The asset manifest entry uses a safe relative path and supported content type.
* The asset passes the public demo privacy scan.
* The asset is necessary for the public demo route experience.

Unreviewed media, thumbnails, transcripts, raw provider payloads, local cache files, bridge URLs, private URLs, and credential-bearing URLs stay out of this directory. When no reviewed asset is available, demo routes use fixture labels and public evidence text instead.


---

# 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://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/demo-website/public/demo/trend-finder-assets.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.