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

# 👨‍👨‍👧‍👦 Entities

{% content-ref url="/pages/-M5p1I0BHCgbIS-MiysA" %}
[Broken mention](broken://pages/-M5p1I0BHCgbIS-MiysA)
{% endcontent-ref %}

You will start seeing the ecosystem once you look beyond suppliers, distributors and wholesalers—beyond direct contribution to the creation and delivery of a product, service, or experience.

There will be parties that in some way provide a means for your business to function in the first place: financing, foundational technologies, or complementary products. There are competitors and customers with actions and responses that make best laid plans go astray. Regulatory agencies and media outlets can have the same kind of influence—indirect perhaps but not less impactful.

Uncovering the ecosystem in this way is very much a quantitative exercise: get a sheet of paper and write down *any* name that springs to mind, and keep writing. More *is* better and there is *always* more: the suppliers and partners behind your providers, the customer tiers served by your customers, and so on.

The [Ecosystem Ecology Map](/workshop/canvases.md#ecology-map) can help in structuring this process of discovery. With this map, you uncover and then explore domains, sectors, or segments one by one. The AirBnB ecosystem, for example, points to a few of these worth exploring in some detail:

![Mapping the AirBnB ecosystem](/files/-M60-muooHRCJA4_0IEv)


---

# 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://position.futuring-architectures.com/position/frame/entities.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.