title style

Author: dieppa

.claude/settings.local.json

@@ -9,7 +9,9 @@
       "Bash(npm start)",
       "Bash(npx docusaurus:*)",
       "Bash(rm:*)",
-      "Bash(git add:*)"
+      "Bash(git add:*)",
+      "Bash(yarn start)",
+      "Bash(PORT=3001 yarn start)"
     ],
     "deny": []
   }

CLAUDE.md

@@ -74,34 +74,81 @@ Flamingock is a **"Change-as-Code" platform** that versions and orchestrates any
 - **Complete audit trail**: Every action, success, and failure is tracked
 - **Deterministic state**: Always know exactly what happened and what needs to happen next
 
-## CRITICAL: Flamingock Positioning Strategy
-
-**The validated dual positioning approach for Flamingock:**
-
-### 1. Community Edition (Developer-First, Bottom-Up)
-- **Message**: "Manage all your changes alongside your app, like Liquibase but for the whole stack."
-- **Goal**: Broad adoption by developers, ease of use, speed, and confidence in local/dev environments
-- **Target**: Individual developers and small teams looking for practical change management
-
-### 2. Cloud/Self-Hosted Edition (Enterprise, Top-Down)
-- **Message**: "Audit, govern, and secure those changes at scale, like LaunchDarkly but for compliance."
-- **Goal**: Monetization, governance, compliance, observability, and premium features for enterprises
-- **Target**: Enterprise teams requiring governance, compliance, and organizational control
-
-**KEY INSIGHT**: Flamingock is developer-first for adoption and enterprise-ready for business.
-
-### Edition Positioning
-- **Community Audit Stores**: Secure + Functional
-  - Complete safety guarantees
-  - Manual intervention when needed
-  - Full audit capabilities
-  - Covers essential enterprise needs
-
-- **Cloud Edition**: Secure + Resilient + Automatic  
-  - Same configuration options as Community
-  - Enhanced automatic resolution through advanced mechanisms
-  - Better resilience through markers and reconciliation
-  - Premium value: "Same settings, better outcomes"
+# CRITICAL: Flamingock Positioning Strategy
+
+**Validated dual positioning approach for Flamingock**  
+Flamingock combines a **developer-first adoption path** with **enterprise-grade governance and control**, ensuring both grassroots traction and organizational readiness.  
+
+---
+
+## 1. Community Edition (Developer-First, Bottom-Up)
+
+- **Message**  
+  *“Apply changes to your systems alongside your application code — safe, versioned, and auditable by default.”*  
+
+- **Core Benefits**  
+  - **Change-as-Code**: keep application and system changes in lockstep.  
+  - **Safe by default**: idempotent retry and manual intervention ensure reliability.  
+  - **Developer experience**: no extra pipelines, no manual scripts — changes run automatically at app startup.  
+  - **Transparency**: every change is versioned, ordered, and tracked.  
+  - **Lightweight templates**: ready-to-use drivers and official templates for common systems (MongoDB, DynamoDB, configs, etc.).  
+
+- **Goal**  
+  - Drive adoption by becoming the easiest, most natural way for developers to manage changes across their stack.  
+
+- **Target**  
+  - Individual developers and small teams looking for simplicity, speed, and confidence in local and dev environments.  
+
+---
+
+## 2. Cloud / Self-Hosted Edition (Enterprise, Top-Down)
+
+- **Message**  
+  *“Audit, govern, and secure system changes at scale, with enterprise-grade visibility, safety, and organizational control.”*  
+
+- **Core Benefits**  
+  - **Advanced recovery**: automated safe retry keeps the system consistent across failures.  
+  - **Governance workflows**: approval steps, human-in-the-loop, and compliance checks.  
+  - **Observability**: centralized dashboards, monitoring, and audit logs across all services and teams.  
+  - **Security and control**: role-based access, policies, and multi-team environments.  
+  - **Premium templates**: advanced system integrations (e.g., Kafka/Avro schema evolution, multi-region S3 provisioning, advanced rollback strategies).  
+  - **More premium features**: additional enterprise-grade capabilities will continue to be added over time.  
+
+- **Goal**  
+  - Monetize adoption by providing the capabilities enterprises need for compliance, governance, resilience, and organizational scale.  
+
+- **Target**  
+  - Enterprises and larger teams requiring visibility, compliance, and organizational control over distributed system changes.  
+
+---
+
+## KEY INSIGHT  
+
+Flamingock is:  
+- **Developer-first for adoption** → intuitive, safe, and frictionless for engineers.  
+- **Enterprise-ready for business** → governance, compliance, and automation at scale.  
+
+---
+
+## SALES PITCH TO DEVELOPERS (No Hype)  
+
+*"Flamingock lets you apply changes to your systems the same way you version your code. No more manual scripts or ad-hoc processes. Every change is tracked, ordered, and safe to run. You focus on building, Flamingock makes sure your changes are applied consistently and reliably — from your laptop to production."*  
+
+---
+
+## STRATEGIC NOTES  
+
+- **Do not use the word “migration”** — Flamingock does not perform migrations, it applies versioned changes.  
+- **Recovery split**: Community offers baseline safety (idempotent retry + manual intervention). Cloud offers automation (safe retry + reconciliation).  
+- **Templates strategy**:  
+  - Community → free templates for popular systems.  
+  - Cloud → premium templates for complex, enterprise-grade integrations.  
+- **Premium features in Cloud**: governance, observability dashboards, org-level security, premium templates, automated recovery, and more premium features to be added.  
+
+---
+
+👉 This structure leaves no ambiguity: adoption comes from **Community (developer-first)**, monetization and scale come from **Cloud (enterprise)**.  
+
 
 ## Flamingock Architecture
 

docs/audit-stores/community/couchbase-audit-store.md

@@ -13,7 +13,6 @@ The audit store is where Flamingock records execution history and ensures safe c
 
 > For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
 
----
 
 ## Minimum setup
 
@@ -71,15 +70,13 @@ Flamingock.builder()
     .run();
 ```
 
----
 
 ## Supported versions
 
 | Couchbase SDK                  | Couchbase Server | Support level   |
 |--------------------------------|------------------|-----------------|
 | `java-client` 3.6.0+           | 7.0+             | Full support    |
 
----
 
 ## Dependencies
 
@@ -129,7 +126,6 @@ implementation("com.couchbase.client:java-client:3.7.0")
 
 </Tabs>
 
----
 
 ## Configuration options
 
@@ -158,7 +154,6 @@ Flamingock.builder()
 
 ⚠️ **Warning**: Ensure your Couchbase user has permissions to create collections if `autoCreate` is enabled.
 
----
 
 ## Next steps
 

docs/audit-stores/community/dynamodb-audit-store.md

@@ -13,7 +13,6 @@ The audit store is where Flamingock records execution history and ensures safe c
 
 > For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
 
----
 
 ## Minimum setup
 
@@ -68,15 +67,13 @@ Flamingock.builder()
     .run();
 ```
 
----
 
 ## Supported versions
 
 | AWS SDK                        | DynamoDB       | Support level   |
 |--------------------------------|----------------|-----------------|
 | `dynamodb` 2.25.29+            | All versions   | Full support    |
 
----
 
 ## Dependencies
 
@@ -132,7 +129,6 @@ implementation("software.amazon.awssdk:dynamodb-enhanced:2.28.0")
 
 </Tabs>
 
----
 
 ## Configuration options
 
@@ -162,7 +158,6 @@ Flamingock.builder()
 ⚠️ **Warning**: Adjust capacity units based on your workload. Under-provisioning may cause throttling.  
 Consider using **ON_DEMAND** billing mode for unpredictable workloads.
 
----
 
 ## Next steps
 

docs/audit-stores/community/mongodb-audit-store.md

@@ -13,7 +13,6 @@ The audit store is where Flamingock records execution history and ensures safe c
 
 > For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
 
----
 
 ## Minimum setup
 
@@ -87,7 +86,6 @@ MongoSyncAuditStore auditStore = MongoSyncAuditStore
     .withReadConcern(ReadConcern.LOCAL);
 ```
 
----
 
 ## Supported versions
 
@@ -96,7 +94,6 @@ MongoSyncAuditStore auditStore = MongoSyncAuditStore
 | `mongodb-driver-sync` 4.0–5.x | 3.6 – 7.0      | Full support    |
 | `mongodb-driver-sync` 3.12.x  | 3.4 – 4.4      | Legacy support  |
 
----
 
 ## Dependencies
 
@@ -146,7 +143,6 @@ implementation("org.mongodb:mongodb-driver-sync:5.2.0")
 
 </Tabs>
 
----
 
 ## Configuration options
 
@@ -180,7 +176,6 @@ Flamingock.builder()
 ⚠️ **Warning**: lowering concerns (e.g. `LOCAL`, `w=1`) increases performance but reduces safety.  
 Recommended only for dev/test environments.
 
----
 
 ## Next steps
 

docs/audit-stores/community/mongodb-springdata-audit-store.md

@@ -13,7 +13,6 @@ The audit store is where Flamingock records execution history and ensures safe c
 
 > For a conceptual explanation of the audit store vs target systems, see [Audit store vs target system](../overview/audit-store-vs-target-system.md).
 
----
 
 ## Minimum setup
 
@@ -83,7 +82,6 @@ MongoSpringDataAuditStore auditStore = MongoSpringDataAuditStore
     .withReadConcern(ReadConcern.LOCAL);
 ```
 
----
 
 ## Supported versions
 
@@ -96,7 +94,6 @@ Flamingock provides two editions for different Spring Data MongoDB versions:
 
 Choose the edition that matches your Spring Data MongoDB and JDK version.
 
----
 
 ## Dependencies
 
@@ -145,7 +142,6 @@ implementation("org.springframework.boot:spring-boot-starter-data-mongodb")
 
 </Tabs>
 
----
 
 ## Configuration options
 
@@ -192,7 +188,6 @@ Flamingock.builder()
 ⚠️ **Warning**: lowering concerns (e.g. `LOCAL`, `w=1`) increases performance but reduces safety.  
 Recommended only for dev/test environments.
 
----
 
 ## Spring Boot integration
 
@@ -213,7 +208,6 @@ Spring Boot will automatically:
 - Apply configuration from `application.yml`
 - Set up the audit store
 
----
 
 ## Next steps
 

docs/audit-stores/introduction.md

@@ -61,6 +61,5 @@ public AuditStore auditStore(MongoClient mongoClient) {
 ```
 
 
----
 
 **Key takeaway**: The audit store is critical for Flamingock's safety guarantees. Cloud Edition provides this fully managed, while Community Audit Stores requires you to configure one of the supported databases.

docs/flamingock-library-config/additional-configuration.md

@@ -19,7 +19,6 @@ This section includes additional settings for customizing defaults and adding co
 :::note
 These options can currently be defined using the Flamingock builder. Support for config file (outside Spring Boot) will be added in a future release
 :::
----
 
 ## Metadata
 
@@ -57,7 +56,6 @@ FlamingockStandalone
     </TabItem>
 </Tabs>
 
----
 
 ### Default Author
 
@@ -83,7 +81,6 @@ FlamingockStandalone
     </TabItem>
 </Tabs>
 
----
 
 ## Disable flamingock process
 

docs/flamingock-library-config/context-and-dependencies.md

@@ -98,6 +98,5 @@ Remember that target system contexts are isolated. Dependencies in one target sy
 - **Global**: Shared services, utilities, application-wide configuration
 - **Framework**: Let Spring manage beans, services, and repositories
 
----
 
 **Key takeaway**: Flamingock's hierarchical dependency resolution provides flexibility while maintaining clear separation of concerns. Use target system contexts for system-specific dependencies and global context for shared resources.

docs/flamingock-library-config/introduction.md

@@ -17,7 +17,6 @@ Configuration is divided into two distinct scopes:
 
 - **Runtime configuration** includes optional parameters such as locking, metadata, author, etc., and can be provided via builder or (depending on the environment) a file.
 
----
 
 ## What you can configure
 
@@ -35,7 +34,6 @@ Configuration is divided into two distinct scopes:
 
 Each of these topics is explained in its own section.
 
----
 
 
 
@@ -51,7 +49,6 @@ Runtime configuration (everything except the pipeline) can be applied in the fol
 You can combine both approaches. If a property is defined in both, the builder value takes precedence.
 :::
 
----
 
 ## Next steps