# Project domains

> What a project domain is: a domain for running a body of work under defined protocols, with its deeds, governance group, accounts and Matrix room.

A project domain is a domain set up to run a body of work: the people and agents who do it, the
resources it uses, the protocols it follows and the claims it collects. Like every domain it has an
entity, a DID, an on-chain record (its IID document) and the other parts listed in
[Core concepts](/core-concepts#who-takes-part). Its record is resolved with the IXO DID Resolver.

Read this page to see what a project adds to an ordinary domain and how its parts fit together.

## What a project has

| Part | What it does |
| --- | --- |
| Linked protocols | The rules for the project's work: what tasks there are, how claims are submitted and decided, what can be offered or requested |
| Agents | The people, AI agents, oracle services and other providers who do the work |
| Deed domains | Domains for requests and offers, each with its own claim collection |
| Governance group | The project owner group, which controls the domain. A group can make decisions jointly |
| Domain accounts | Separate accounts for different purposes, owned by the project domain |
| Matrix room | Created automatically with the project. It holds the project's messages and state objects such as its Settings file and Project Profile |
| POD | Optional. A [Qi workspace](/articles/pods) where members and agents run the project's work |

## Deeds

Projects use deed domains to organise exchanges. A deed is the domain that claims are submitted
against, and each one has a claim collection.

- A **deed request** defines a task for agents to do, the claims they must submit, and the criteria
  those claims are checked against. It tracks the status of the request.
- A **deed offer** defines resources or services on offer and their terms, and tracks how the offer
  is delivered.

Claims submitted to a deed's collection are decided as they are anywhere on IXO: a decision oracle
produces the facts and the IXO decision engine applies the rules. See
[Claim evaluation](/articles/claim-evaluation-protocol).

## Governance and money

The project owner group is the primary controller of the domain. Groups can govern the project
jointly, and permissions can be delegated in fine detail.

The project's accounts are owned by the project domain. Authorisations on those accounts can be
delegated for specific transactions, and they are revoked automatically when ownership of the
domain changes.

## Lifecycle

1. **Created.** The project domain is created on the IXO Protocol.
2. **Configured.** Protocols, agents and resources are set up.
3. **Run.** The work is done and claims are submitted and decided.
4. **Monitored.** Progress and outcomes are tracked.
5. **Adjusted.** Configuration and processes change as needed.
6. **Closed or changed.** The project ends, or becomes something else.

## Where to go next

<CardGroup cols={2}>
  <Card title="Digital twin domains" icon="brain" href="/https/docs.ixo.world/articles/cdt-systems">
    How domains stand for real-world things and take their shape from protocols.
  </Card>
  <Card title="Domains map" icon="sitemap" href="/https/docs.ixo.world/guides/dev/ixo-domains">
    Which page documents each part of a domain.
  </Card>
  <Card title="Design a claims workflow" icon="badge-check" href="/https/docs.ixo.world/guides/users/build-a-claim-collection">
    Plan the claims a deed collects and how they are decided.
  </Card>
  <Card title="Developer portal" icon="rocket" href="/https/docs.ixo.world/developers">
    SDKs, APIs and guides for building project workflows.
  </Card>
</CardGroup>
