> For the complete documentation index, see [llms.txt](https://evomimic.gitbook.io/map-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evomimic.gitbook.io/map-book/component-architecture.md).

# Component Architecture

\ <mark style="color:orange;">**\<THIS SECTION IS UNDER CONSTRUCTION>**</mark>

## Overview <a href="#overview" id="overview"></a>

### Components

#### Reliable Data Storage Layer

This component provides storage and retrieval of persistent data that is:

* resilient in the presence of failures of computing nodes and network infrastructures.
* evolvable
* validating
* eventually consistent
* self-describing -- the structure of the data managed relies on descriptions managed by the Type Descriptions component.
*

#### Type Descriptions

This component manages the type descriptions of the data that is:

* stored by the Data Storage Layer
* used to express access control policies managed by the Data Access layer
* referenced in offers and agreements managed by the Agreements component
* presented by the Human Interface Services component.
* used by the weSpaces component to validate service requests against service agreements

#### Agreements

This component provides access to Service Agreements.

#### Data Access Layer

This component mediates access to the data storage services, enforcing access policies

#### Service Access Points

This components exposes interface points for services, enforcing security policies aligned with the requested service's agreement.

#### iSpace

This component maintains:

* the active agents that belong to an iSpace and their assigned capabilities,&#x20;
* the weSpaces this iSpace agent participates in. This includes the persona(s) the iSpace agent exposes to each weSpace

#### weSpace

This component maintains:

* the apps assigned to that weSpace
* the active agents that belong to the weSpace and permissions each agent has with respect to each app assigned to that weSpace
* authorizes inbound and outbound services requests
* manages inter-agent communication across membraned boundaries.

#### Service Logic

This is the custom logic for a given service. Each service has its own Service Logic component.

#### Human Interface Services

This component provides visualization and interaction to human users of information and actions offered by the set of services available to that person's iSpace.

### Component Interactions

Copyright (c) 2022, this book is offered to the world under Creative Commons license [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/)

<br>


---

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

```
GET https://evomimic.gitbook.io/map-book/component-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.