# Interaction

{% content-ref url="/pages/-M6LVWJa6uH\_5VzL5sMd" %}
[Broken mention](broken://pages/-M6LVWJa6uH_5VzL5sMd)
{% endcontent-ref %}

The core experiences [attract](/position/experience.md#pull) key roles to exchange value—goods, services, social currency—on the platform. It's through the actions the roles take in these exchanges that experiences actually unfold. These experiences will converge on the [designed ones](/position/experience.md#experiences) only by purposefully aligning and connecting the roles' individual actions. 

You have two types of building blocks at your disposal in structuring the exchange of value on the platform:

* **Touchpoints** - points of interaction between roles. Each takes place at a certain moment in time, in a certain context, and with the intention of meeting roles' specific needs.
* **Channels** - media of interaction between roles, either on-platform or off-platform. Channels both create opportunities and set constraints around a touchpoint.

The [Platform Transaction Engine](/workshop/canvases.md#platform-transaction-engine) helps in piecing these building blocks, left-to-right and right-to-left, into the interactions taking place on the platform:

![The AirBnB transaction engine](/files/-M7CwK7u3EI8i-mR0Ogy)

Use touchpoints to pinpoint any exchange of some value between roles engaging in the [key relationship](/position/experience.md#pull). The roles' *gives-to* connections on the [Motivation Matrix](/position/frame/motivations.md) are a good source for these value items. 

Place channels to lower the barrier for a role to bring its assets to bear in each such interaction. Channels are also good for raising the barrier for less desirable—or unwanted, or even illegal—exchanges. 

Take care for all roles to provide some item of value in every single interaction—whether it's goods, services, social currency or information thereof. If not, some roles may not feel incentivised enough to engage in the interaction repeatedly. 


---

# 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/interaction.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.