# Architecture Overview

LES is architected as a genuine enterprise system. The same structural principles applied in corporate ERP implementations — separation of concerns, defined integration contracts, layered security, data sovereignty — are applied without simplification.

The full architecture is documented across several pages in this section. This page provides a brief orientation to the layers and the governing principles.

***

### System Layers

| Layer          | Components                                                                  |
| -------------- | --------------------------------------------------------------------------- |
| Presentation   | Dashboard (LES-DASH), website, this GitBook                                 |
| Intelligence   | Agent orchestrator, department agents, analytics (LES-INT)                  |
| Application    | Module services, central API gateway (LES-API), shared libraries (LES-CORE) |
| Data           | Azure SQL, Azure Blob Storage, per-module data models                       |
| Infrastructure | Microsoft Azure (primary cloud), IaC in LES-INFRA                           |

***

### Governing Principles

Three constraints shape every architectural decision:

**Understanding before implementation.** No component is built until it is understood. This applies without exception.

**Long-term optionality.** The architecture preserves the option to scale LES to a deployable product. Design choices that would require fundamental restructuring are avoided (Decision 14).

**Security by design.** Security is considered at every architectural decision from Phase 0 — not added after the fact (Decision 8).

***

### Technology Stack

The confirmed technology decisions are documented in full in the Master Roadmap — Technology Stack page. Key confirmed items: Microsoft Azure as primary cloud, custom-built multi-agent system (not a pre-packaged framework), GitHub for version control, draw\.io for all diagrams.

***

### Diagramming Standards

All diagrams follow: C4 Model (architecture), BPMN 2.0 (process), ERD (data), Azure Architecture icons (infrastructure). Produced in draw\.io (Decision 62).

***

* [Module Overview](https://app.gitbook.com/o/tbne7ZtUlyqO49hsY3QC/s/Nb5M0j365A1RgeUSUy4w/03-architecture/module-overview)
* Master Roadmap — Technology Stack
* Master Roadmap — Repository Architecture
* **GitHub:** [github.com/NikiDigitals](https://github.com/NikiDigitals)
* **Website:** [nikidigitals.com](https://nikidigitals.com)


---

# 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://nikidigitals.gitbook.io/les/03-architecture/architecture-overview.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.