# Architecture

Before we begin discussing about how the architecture will evolve to accomodate our vision, let's first discuss state of current architecture

## Current Dapp Architecture

<figure><img src="/files/t1hnpvwPYjnMQaaSQo4b" alt="" width="375"><figcaption><p>Current Architecture of Desights (LIVE)</p></figcaption></figure>

## Upcoming Protocol Architecture

<figure><img src="/files/23lxVj4FifQIwcMuHSgs" alt=""><figcaption><p>New Protocol Architecture</p></figcaption></figure>

The architecture above show interactions between various components of Desights Protocol. Lets expand a bit more on this .

### **User Profile**&#x20;

Any individual (human or bot) operating within Desights Protocol needs to have an Account. Each Account has a Profile that contains human readable metadata of that account. Collectively we call this account + profile metadata as Profile.&#x20;

User Profile at the core is a [Universal Profile](https://docs.lukso.tech/standards/universal-profile/introduction) managed by a [Key Manager](https://docs.lukso.tech/standards/universal-profile/lsp6-key-manager) that manages usage permissions. You can think of User Profile as the onchain digital twin or any human or bot. All assets created and co-owned by the user are managed by  this User Profile. Within Desights Protocol, both [Solvers](/core-components/solvers.md) and [Funders](/core-components/funders.md) can be considered Users and are represented onchain by their User Profiles.\ <br>

### Team Profile

Just like User Profile, there is Team Profile. Key difference between User Profile and Team Profile is, Team Profile is co-owned and managed by multiple User Profiles. Although the underlying structure remains same, Team Profiles are much more powerful. They allow multiple owners and manages their [Ownership structure](/core-components/ownership-split.md) within a [Team](/core-components/teams.md). All [Assets](/core-components/asset.md) created by this Team shares the same Ownership Structure as defined within Team Profile. Team Profile establishes the [Collaborative](/concepts/collaborate.md) aspect of Desights Protocol.&#x20;

### Registry

Registry component is better explained [here](/core-components/registry.md)

### Challenge

Challenge is better explained [here](/core-components/challenge.md)

### Asset

Assets are better explained [here](/core-components/asset.md)


---

# Agent Instructions: 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:

```
GET https://docs.desights.ai/the-protocol/architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.