> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/freelucy/reference/architecture.md).

# Architecture

YouDesign Freelucy is a **scoped ServiceNow application** that runs entirely inside your ServiceNow instance. It introduces no custom tables, requires no integrations, and reads only the tables your administrators authorize through cross-scope privileges.

{% hint style="warning" %}
🖼️ **Screenshot needed — `v26-architecture-diagram.png`** The Freelucy v26 application architecture diagram: the scoped app running on the Now Platform, reading core CMDB tables, with the multi-view editor on top.
{% endhint %}

***

## What this means in practice

* **100% on ServiceNow.** Freelucy runs natively. There is no external service, no integration to configure, and no data leaving your instance.
* **No custom tables.** Freelucy uses core ServiceNow constructs, such as `cmdb_rel_ci`, `cmdb_rel_type`, scoped roles, and cross-scope privileges. Nothing new is introduced into your data model.
* **No additional licenses.** Because no custom tables are added, no additional ServiceNow end-user licenses are required to use Freelucy.
* **Governed access.** Administrators control which tables Freelucy can read, through cross-scope privileges, and which class pairs users can connect, through suggested relationships. Users only see what your governance allows.
* **Built on Now™ certified.** Freelucy holds ServiceNow's highest technical designation for partner applications, meaning it has been designed and tested for fast, agile, resilient, and secure interaction on the Now Platform.

***

## How the editor is built

Freelucy presents one record through three views, and they all share the same editing state.

* **One editing model, many views.** Classic, Flow, and List are interchangeable views over the same record. Your staged changes live in one shared place, so switching views never loses work.
* **Stage then commit.** Edits are held as pending changes and written to ServiceNow only when you commit, as a single batch.
* **Rule-driven.** A relationship-rule resolver decides which sides and relationship types are valid for any given pair of records, so every view offers only the relationships your metamodel permits.

***

## What's next

* See [Configuration overview](/freelucy/configuration/configuration.md) for the administrator setup that activates this architecture for your users.
* See the [Glossary](/freelucy/reference/glossary.md) for the terms used throughout this documentation.


---

# 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://docs.ins-pi.com/freelucy/reference/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.