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

# Architecture

<img src="/files/a42gNk46B5AoyPGlW7DM" alt="FPS design architecture" class="gitbook-drawing">

The diagram illustrates the architecture of the Forge Proposal Simulator. It is composed of various components that interact with each other to simulate, execute, and test governance proposals.

## Proposal Generic Contract

At its core, the FPS features a [Proposal.sol](https://github.com/solidity-labs-io/forge-proposal-simulator/blob/main/src/proposals/Proposal.sol) contract that defines [functions](/forge-proposal-simulator/overview/architecture/proposal-functions.md) that can be overridden to adapt to specific governance architectures. The `run` function serves as the entry point to execute a proposal using the `forge script`.

## Governance Specific Contracts

FPS supports different Governance types (e.g., Timelock, Multisig, Governor Bravo, OZ Governor) through proposal contract types inheriting from [Proposal.sol](https://github.com/solidity-labs-io/forge-proposal-simulator/blob/main/src/proposals/Proposal.sol), customizing their functions to unique governance requirements. New proposal types can be included to support different governance contracts.

## Proposal Specific Contract

Protocols using FPS must create their own Proposal Specific Contracts, conforming to FPS standards. These contracts override functions relevant to the particular proposal, such as `deploy()` and `preBuildMock()` for proposals involving new contract deployments. For more details, refer to [proposal functions](/forge-proposal-simulator/overview/architecture/proposal-functions.md).

{% content-ref url="/pages/kpo3UA4utyJUUPqdohhO" %}
[Proposal Functions](/forge-proposal-simulator/overview/architecture/proposal-functions.md)
{% endcontent-ref %}

{% content-ref url="/pages/3BV8nS5LRedMkoNovzXP" %}
[Addresses](/forge-proposal-simulator/overview/architecture/addresses.md)
{% endcontent-ref %}


---

# 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.soliditylabs.io/forge-proposal-simulator/overview/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.