> For the complete documentation index, see [llms.txt](https://df-manual.gitbook.io/df-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://df-manual.gitbook.io/df-book/operations-circle/structure-and-governance.md).

# Structure and Governance

#### What is the Operations Circle?

The Operations Circle is the heart of Deep Funding, a direct nexus with the Core Team that ensures all behind‑the‑scenes operations run so smoothly they feel invisible ([Operations Circle – Community](https://community.deepfunding.ai/circle/operations-circle/)).

#### Mission Statement:

To deliver seamless, proactive operational support and foresight, enabling the Deep Funding community to thrive without friction.

#### Primary Objectives:

1. Ensure Accuracy and Timeliness Across Operational Processes
2. Oversee and Execute Timely and Transparent Payments
3. Maintain and Update Community-Facing Platforms
4. Support and Maintain Data for Awarded Teams
5. Drive Development of Automation and Operational Tools

#### Structure & Roles

The Operations Circle follows a decentralized structure, where leadership is distributed and members collaborate fluidly based on capacity, context, and expertise. While each member leads specific areas, responsibilities are shared across the team to ensure continuous progress and mutual support.

#### Circle Coordinators:

* Responsible for reporting circle updates to Deep Funding staff.
* Leads coordination efforts within the circle, ensuring smooth communication and workflow across all roles.
* Manages records of awarded teams and facilitates ongoing coordination and communication with them.
* Handles all payment processes and resolves any issues related to funding disbursements.
* Oversees updates to the DF community website and ensures accurate, up-to-date information is shared with the community.
* Accepts, assigns, reviews, and audits tasks to ensure quality delivery and accountability across the team.<br>

#### Collaborative Approach:

While members take initiative in their lead roles, tasks are often shared. When a lead is unavailable or a workload spikes, other members step in to ensure continuity. This fosters a resilient and adaptable workflow aligned with our decentralized ethos.

#### Collaboration Cadence:

* Retrospective Team Call (First Tuesdays of the month)
* Async Communication (Mattermost)
* Kanban board on Openprojects for tasks

<br>

#### Key Stakeholders Roles:

1. IT Circle

The IT Circle is responsible for maintaining and managing key tools supporting operational efficiency. They currently oversee:

* OpenProject, the task management system used by all circles.
* Mautic, the platform handling email communications and outreach automation.

2. Solutions Architect

Deep's solutions architect creates and manages internal automation tools that streamline repetitive tasks and reduce manual workload. Notable contributions include:

* Payment automation systems
* Milestones automation systems
* Other internal tools that enhance coordination and efficiency within the Operations Circle

3. DeepFunding Chief Operations Manager

He ensures strategic alignment across circles, facilitates decision-making, and supports the overall effectiveness of the decentralized operational framework.


---

# 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://df-manual.gitbook.io/df-book/operations-circle/structure-and-governance.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.