> For the complete documentation index, see [llms.txt](https://docs.skynetxbt.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skynetxbt.ai/documentation/getting-started/markdown/core-architecture.md).

# Core Architecture

```
Business Idea → Visual Builder → Agent Logic → ACP Integration → Live Agent
     ↓              ↓             ↓            ↓            ↓
   Vision      Drag & Drop    AI + Web3    Commerce      Revenue
  Concept      Interface      Components    Ready        Generation
```

**Layer 1: User Interface**

* React-based visual builder
* Real-time collaborative editing
* Mobile-responsive design
* Professional template library

**Layer 2: Agent Engine**

* Intelligent workflow orchestration
* State management and persistence
* Multi-agent coordination
* Performance optimization

**Layer 3: Integration Layer**

* MCP protocol implementation
* Blockchain abstraction layer
* AI/ML model integration
* External API connectivity

**Layer 4: Infrastructure**

* Auto-scaling cloud deployment
* Multi-region availability
* Enterprise-grade security
* Comprehensive monitoring


---

# 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://docs.skynetxbt.ai/documentation/getting-started/markdown/core-architecture.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.