From 0d86a012b400a2990d5eaaf8355efe6960eca315 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jos=C3=A9=20Ren=C3=A9=20White=20Enciso?=
 <jrenewhite@gmail.com>
Date: Tue, 24 Feb 2026 05:26:54 -0600
Subject: [PATCH] docs(furniture-bff): add service boundary notes

---
 docs/architecture/bff-service-boundary.md        | 13 +++++++++++++
 docs/migration/correlation-propagation-checks.md |  6 ++++++
 docs/migration/post-domain-contract-alignment.md |  9 +++++++++
 3 files changed, 28 insertions(+)
 create mode 100644 docs/architecture/bff-service-boundary.md
 create mode 100644 docs/migration/correlation-propagation-checks.md
 create mode 100644 docs/migration/post-domain-contract-alignment.md

diff --git a/docs/architecture/bff-service-boundary.md b/docs/architecture/bff-service-boundary.md
new file mode 100644
index 0000000..94e2558
--- /dev/null
+++ b/docs/architecture/bff-service-boundary.md
@@ -0,0 +1,13 @@
+# Furniture BFF Service Boundary
+
+## Purpose
+Preserve BFF as an edge adapter layer that depends on service contracts only.
+
+## BFF Responsibilities
+- REST edge exposure
+- Service client adaptation
+- Correlation/tracing propagation
+
+## Prohibited
+- Direct DAL access
+- Domain business decision ownership
diff --git a/docs/migration/correlation-propagation-checks.md b/docs/migration/correlation-propagation-checks.md
new file mode 100644
index 0000000..3b5ba08
--- /dev/null
+++ b/docs/migration/correlation-propagation-checks.md
@@ -0,0 +1,6 @@
+# Correlation Propagation Checks
+
+## Checks
+- Correlation identifiers are preserved across BFF -> Service calls.
+- No new correlation behavior is introduced at edge.
+- Trace metadata pass-through remains stable.
diff --git a/docs/migration/post-domain-contract-alignment.md b/docs/migration/post-domain-contract-alignment.md
new file mode 100644
index 0000000..cc147eb
--- /dev/null
+++ b/docs/migration/post-domain-contract-alignment.md
@@ -0,0 +1,9 @@
+# Post-Domain Contract Alignment
+
+## Goal
+Align BFF adapter usage with service contracts after domain extraction.
+
+## Steps
+1. Map current BFF contract usage to updated service contracts.
+2. Keep edge contract behavior stable.
+3. Validate adapter compatibility.