# Position a Platform

- [From Frame to Challenge](https://position.futuring-architectures.com/position/layers.md): Five layers of platform epiphany
- [Frame](https://position.futuring-architectures.com/position/frame.md): Discover the ecosystem to design for
- [👨‍👨‍👧‍👦 Entities](https://position.futuring-architectures.com/position/frame/entities.md)
- [Roles](https://position.futuring-architectures.com/position/frame/roles.md)
- [Motivations](https://position.futuring-architectures.com/position/frame/motivations.md)
- [Experience](https://position.futuring-architectures.com/position/experience.md): Define the platform's pull with the ecosystem
- [Interaction](https://position.futuring-architectures.com/position/interaction.md): Develop the structure of value exchange on the platform
- [Tools](https://position.futuring-architectures.com/position/tools.md): Develop the means of participation on the platform
- [Challenge](https://position.futuring-architectures.com/position/challenge.md): Deliver the platform challenge to the organisation


---

# Agent Instructions: 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:

```
GET https://position.futuring-architectures.com/position.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.