> 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/data/readme_data.md).

# Data Folder

This folder holds repo-local AI OS data files that are useful during local development.

## Tracked Templates

* `openai-account-auth.example.json` - sanitized shape for OpenAI account auth runtime credentials.
* `ai-os.time-saved.example.json` - example per-skill or per-workflow saved-time estimates, in minutes.
* `ai-os.hourly-rate.example.json` - example hourly rate used for local value calculations.
* `ai-os.scheduler.example.json` - sanitized local scheduler timer-intent and cadence settings.
* `trend-finder.visibility.example.json` - example per-view Trend Finder visibility overrides.
* `trend-finder.apify-actors.example.json` - sanitized editable template for Trend Finder Apify Actor source configuration.

## Private Local Files

These matching local files are gitignored and should not be committed:

* `openai-account-auth.json`
* `ai-os.time-saved.json`
* `ai-os.hourly-rate.json`
* `ai-os.scheduler.json`
* `trend-finder.visibility.json`
* `trend-finder.apify-actors.json`

Use the example files as templates when creating private local config. Keep real tokens, account details, operator rates, personal saved-time settings, and personal scheduler timer choices, and personal Trend Finder visibility layouts in the gitignored files only.

Apify Actor source files should not contain `APIFY_TOKEN`; keep that token in `.env.local` or the shell environment.

Scheduler settings in `ai-os.scheduler.json` may only select reviewed scheduler job IDs, reviewed cadence IDs, booleans, and strict `HH:MM` Dream times. Keep secrets, command bodies, private paths, raw systemd calendar expressions, and provider runtime values in `.env.local` or private runtime state 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/data/readme_data.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.