docs: update readme

Author: dieppa

README.md

@@ -31,15 +31,26 @@
   </a>
 </p>
 
-**Flamingock** is an open-source engine for the governed and synchronized evolution of distributed systems — and the foundation of a broader Change-as-Code platform.
+**Flamingock** brings *Change-as-Code (CaC)* to your entire stack.  
+It applies **versioned, auditable changes** to the external systems your application depends on — such as schemas, message brokers, databases, APIs, cloud services, and any other external system your application needs.
 
-With Flamingock, your application and the systems it interacts with — including databases, message queues, feature flags, configurations, APIs, and cloud resources — evolve together, in lockstep.
+Unlike infrastructure-as-code tools, Flamingock runs **inside your application** (or via the **CLI**).  
+It ensures these systems evolve **safely, consistently, and in sync with your code at runtime**.
 
-**All changes are versioned, auditable**, and applied as part of the same deployment lifecycle.
 
-No more post-deploy scripts or manual tweaks: every change is declared alongside your code and applied safely during application startup.
+### What Flamingock manages
+Flamingock focuses on **application-level changes** that your code requires to run safely:
 
-<br />
+- Database schemas and reference data
+- Message queues and schemas
+- APIs and configuration values
+- Cloud service resources directly tied to your application
+- Configuration changes (feature flags, secrets, runtime values)
+
+### What Flamingock does *not* manage
+Flamingock is **not an infrastructure-as-code tool**. It does not provision servers, clusters, or networks — those belong in Terraform, Pulumi, or similar. Instead, Flamingock **complements them by handling the runtime changes your application depends on**.
+
+---
 
 ## 📦 Editions
 Flamingock is open source at its core, and powers three editions:
@@ -56,9 +67,9 @@ Flamingock is open source at its core, and powers three editions:
 
 **Automate changes. Version changes. Control changes.**
 
-Flamingock is built around the principle of **Change-as-Code (CaC)** — the idea that **every change to your system’s behavior** (whether it's a schema update, config toggle, or infrastructure change) should be authored, versioned, and reviewed like application code.
+Flamingock is built around the principle of **Change-as-Code (CaC)** — the idea that **every change to your system’s behavior** (whether it's a schema update, config toggle, or database change) should be authored, versioned, and reviewed like application code.
 
-This enables true **lockstep evolution** between your application and the systems it relies on — ensuring everything stays compatible, consistent, and in sync across environments.
+This enables true **lockstep evolution between your application and the systems it relies on** — ensuring everything stays compatible, consistent, and in sync across environments.
 
 No more fragile scripts or untracked console changes. With CaC: