> For the complete documentation index, see [llms.txt](https://docs.fabriq.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabriq.network/the-protocol/architecture.md).

# Architecture

Fabriq has an number of actors within the system including:

**Users** — For Fabriq, a user is primarily those actors in the system transmitting intents. This will include users making transfers and swaps and applications which work on their behalf.

**Applications** — Fabriq applications are smart contracts which use credible commitment devices and provide state transitions through intents.

**Counterparties** — solvers are the formal counterparty of the transmitted intents. Solvers will look over available intents and work to provide routing.

These parties interact with a few key components:

* [**Intentpool** ](/the-protocol/architecture/intentpool.md)— an intentpool is a sort of transaction pool, serving to store and progagate intents. Intentpools are operators who provides users with an endpoint for transmitting intents and find fillers.
* [**Credible Commitment Device**](/the-protocol/architecture/credible-commitment-device.md) **—** credible commitment devices are contracts that are used to secure a financial instrument with collateral. This is currently done through the swap intent.
* [**Oracles**](/the-protocol/architecture/oracles.md) — Oracles provide finalization for the Fabriq network. Oracles work to provide attestation of the state of credible commitment devices deployed on the executing networks to confirm, lock and unlock funds during the lifecycle of an intent.


---

# 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://docs.fabriq.network/the-protocol/architecture.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.