# Overview

GLIK is a modular orchestration platform designed to support enterprise-grade agent applications, decision workflows, and memory-aware automation. At the core of GLIK is an execution engine that coordinates nodes — known as **blocks** in the visual studio — to process structured input, route decisions, and invoke tools or AI models.

This section introduces the foundational architecture of GLIK, enabling both enterprise leaders and developer teams to understand how agent workflows are composed, executed, and audited across environments.

{% embed url="<https://www.mermaidchart.com/raw/cc33086c-9a7a-4f1a-8bc7-40117cc1e503?theme=light&version=v0.1&format=svg>" %}
GLIK’s modular architecture: all app types (Workflow, Agent, Advanced Chat, Chatbot) inherit from a shared orchestration foundation. Each app is built from logic blocks (LLM, Policy, Variable Assigner), connected to memory via Knowledge Blocks. This structure enables scalable, reusable AI agents across enterprise systems.
{% endembed %}

<details>

<summary>In Progress</summary>

This page is currently under active development. Content may be incomplete, evolving, or placeholder-only. Please check back later for finalized documentation and fully structured examples.

</details>

### What This Architecture Enables

GLIK's system design provides a reliable and extensible foundation for:

* **Operationalizing business logic** via reusable orchestration templates
* **Embedding decision automation** into existing enterprise systems
* **Ensuring traceability and compliance** through memory, logging, and fallback systems
* **Scaling across environments** — whether cloud-hosted or deployed via Open Core

***

### Core Architectural Concepts

#### 1. **Blocks & Nodes**

The system is built on modular execution units:

* **Blocks** are visual elements used to build workflows in the GLIK Cloud Studio.
* **Nodes** are the runtime equivalents that execute in a directed flow graph.\
  Each node processes input, applies logic, and passes structured output downstream.

#### 2. **Execution Model**

The execution engine processes flows deterministically:

* Resolves scoped inputs and memory
* Executes each node in sequence (with conditional branching support)
* Handles fallback or escalation paths based on runtime outcomes

#### 3. **Memory & Variable Scope**

GLIK provides a structured memory model:

* Memory objects can be scoped to `User`, `App`, or `Org`
* Variables persist across nodes and sessions when needed
* Used for context injection, audit logging, and agent continuity

#### 4. **Decision Routing**

Policy automation and logic branching are handled through a combination of:

* Conditional blocks (e.g., IF/ELSE)
* LLM-driven classifiers
* Escalation nodes that reroute uncertain decisions to humans or fallback paths

#### 5. **System Observability**

GLIK supports operational monitoring and traceability through:

* Execution logs and visual traces
* Save points, snapshots, and output inspection
* Optional memory audit trails

<details>

<summary>📣 Try GLIK </summary>

Explore and deploy your first app at [app.glik.ai](https://app.glik.ai)

</details>

### Cloud + Open Core Parity

The orchestration model remains consistent whether running in [GLIK Cloud](https://docs.glik.ai/glik-cloud) or deploying via [Open Core](https://docs.glik.ai/developers/glik-open-core). Execution patterns, node types, and memory constructs are designed for **deployment-agnostic continuity**, enabling secure adoption in both managed and self-hosted environments.

For Open Core specifics, see: [GLIK Open Core Deployment & CLI Reference](https://docs.glik.ai/developers/glik-open-core/deployment-and-installation)

***

### Audience & Use

This section serves both:

* **Enterprise solution teams** evaluating architecture alignment, integration paths, and risk frameworks
* **Technical implementers and developers** designing, customizing, or extending orchestration flows in production environments