From e1b4f61051cc20631263f868e44805b85bc8f96e Mon Sep 17 00:00:00 2001
From: Wei Wang <62213594+weiw11@users.noreply.github.com>
Date: Wed, 26 Nov 2025 12:46:11 -0500
Subject: [PATCH] docs: clarify blueprint behavior with docker

---
 manage/blueprints.mdx | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/manage/blueprints.mdx b/manage/blueprints.mdx
index 97917d1..10edf3d 100644
--- a/manage/blueprints.mdx
+++ b/manage/blueprints.mdx
@@ -177,6 +177,10 @@ client-resources:
 
 For containerized applications, you can define blueprints using Docker labels.
 
+<Note>
+Blueprints will **continuously apply** from changes in the docker stack, newt restarting, or when viewing the resource in the dashboard.
+</Note>
+
 ### Enabling Docker Socket Access
 
 To use Docker labels, enable the Docker socket when running Newt:
@@ -193,6 +197,10 @@ DOCKER_SOCKET=/var/run/docker.sock
 
 ### Docker Compose Example
 
+<Note>
+The compose file will be the source of truth, any edits through the resources dashboard will be **overwritten** by the blueprint labels defined in the compose stack.
+</Note>
+
 ```yaml
 services:
   newt: