> For the complete documentation index, see [llms.txt](https://hyperflow.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperflow.sygnal.com/apps/hyperflow-llms/future.md).

# Future

## Improved Markdown Support

Allowing raw chunks of static markdown

```html
<script type="hf/md">
... raw markdown
</script> 
```

## Configs

Support either internal configs for upstream, or controller-driven configs&#x20;

Smart failure for unconnected RPC's at DEV&#x20;

## YAML

There is currently **no formal specification** for `llms.txt` that defines support for YAML frontmatter or structured blocks like that. However:

* LLMS crawlers like **OpenAI**, **Anthropic**, **Perplexity**, etc., **are starting to read `llms.txt`** files with simple key-value lines.
* There's growing **community consensus** around a flexible, plaintext-friendly structure that is easy to parse and human-readable.

#### ✅ Recommended Format for `llms.txt` (as of 2024–2025)

The most commonly observed structure follows simple `key: value` pairs, like:

```txt
txtCopyEditpage: https://example.com/about
source: https://example.com/about.md
license: CC-BY-4.0
llm: openai
```

You can see examples and early proposals from:

* [OpenAI’s LLM training data documentation](https://openai.com/llms)
* [GitHub repos](https://github.com/search?q=llms.txt) exploring `llms.txt` format (some maintained by AI transparency advocates)
* Discussions on Hacker News, [GitHub Issues](https://github.com/topics/llms.txt), and community forums