---
tags: flock
---

# Roadmap update policy for the Flock program

Flock teams are granted mandates and resources by ANT holders over pecise roadmaps. **However, various constraints often force Flock teams to rethink and reprioritize their roadmap as they go.**

For now, the AA acts as an agent for ANT holders. It has full discretion over approving roadmap updates.

Below are a few propositions aiming to involve more relevant stakeholders in roadmap update decisions and further increase the network's autonomy in taking these decisions.

## Potential solutions

### Securitas Org - (preferred at the moment)
Using the [Securitas Org](https://github.com/aragon/security-review#step-3-flock-securitas-wip) to approve updates.

Here the AA would still represent the interest of ANT holders, but Flock teams would discuss the changes as well and subsequently abide by them.

### Multiple orgs - (needs more thinking)

Governance schemes including multiple organizations bearing different kinds of legitimacies is an interesting feature enabled by the Agent.

One possibility is having an organizations with the Securitas Org, the Aragon Association Org and the Nest Org voting on roadmap updates.

### Signalling with ANT holders - (voter apathy is a problem)

In this option, the AA uses an Aragon Org for polling ANT holders and makes a decision subsequently.