diff --git a/docs/api/kitchen-ops-workflows.md b/docs/api/kitchen-ops-workflows.md
index c328f11..0d63661 100644
--- a/docs/api/kitchen-ops-workflows.md
+++ b/docs/api/kitchen-ops-workflows.md
@@ -31,5 +31,6 @@ This BFF exposes kitchen board, claim or release, transition, and priority workf
 
 - `kitchen-service` currently exposes claim but not a dedicated release contract, so the release route reuses the claim validation path and projects a release-oriented response for the BFF edge.
 - Transition requests now forward `ContextId` to `kitchen-service` so kitchen actions land in the correct shared restaurant lifecycle context.
+- Board reads now rely on the lifecycle-driven kitchen ticket materialization in `kitchen-service`, which means newly accepted restaurant orders can appear without a stack reset.
 - The BFF keeps temporary edge-state compatibility for existing web clients by translating `Cooking|Ready|Served` to the canonical kitchen-service states `Preparing|ReadyForPickup|Delivered`.
 - Correlation IDs are preserved through Thalos session checks and kitchen-service calls.
diff --git a/tests/Kitchen.Ops.Bff.Application.UnitTests/KitchenWorkflowServiceClientTests.cs b/tests/Kitchen.Ops.Bff.Application.UnitTests/KitchenWorkflowServiceClientTests.cs
index f4dc5f7..cb3e1cd 100644
--- a/tests/Kitchen.Ops.Bff.Application.UnitTests/KitchenWorkflowServiceClientTests.cs
+++ b/tests/Kitchen.Ops.Bff.Application.UnitTests/KitchenWorkflowServiceClientTests.cs
@@ -124,7 +124,7 @@ public sealed class KitchenWorkflowServiceClientTests
     private const string BoardPayload = """
         {
           "contextId": "demo-context",
-          "summary": "Kitchen board shows queued, preparing, and ready lanes for the current service context.",
+          "summary": "Kitchen board now reflects persisted tickets linked to shared restaurant orders.",
           "lanes": [
             {
               "lane": "queued",