diff --git a/docs/browser-automation.md b/docs/browser-automation.md
index 098028c8..2b10c23f 100644
--- a/docs/browser-automation.md
+++ b/docs/browser-automation.md
@@ -23,7 +23,7 @@ enabled. A recent Chrome update alone is not sufficient.
 The managed `ccs-browser` runtime currently exposes seven tool groups:
 
 - **Session inspection**: `browser_get_session_info`, `browser_get_url_and_title`, `browser_get_visible_text`, `browser_get_dom_snapshot`
-- **Navigation and interaction**: `browser_navigate`, `browser_click`, `browser_type`, `browser_press_key`, `browser_scroll`, `browser_select_page`, `browser_open_page`, `browser_close_page`, `browser_take_screenshot`, `browser_drag_element`, `browser_pointer_action`, `browser_start_replay`, `browser_get_replay`, `browser_cancel_replay`
+- **Navigation and interaction**: `browser_navigate`, `browser_click`, `browser_type`, `browser_press_key`, `browser_scroll`, `browser_select_page`, `browser_open_page`, `browser_close_page`, `browser_take_screenshot`, `browser_drag_element`, `browser_pointer_action`, `browser_start_replay`, `browser_get_replay`, `browser_cancel_replay`, `browser_start_orchestration`, `browser_get_orchestration`, `browser_cancel_orchestration`
 - **Hover diagnostics**: `browser_hover`, `browser_query`, `browser_take_element_screenshot`
 - **Readiness and page evaluation**: `browser_wait_for`, `browser_eval`
 - **Event observation**: `browser_wait_for_event`
@@ -109,6 +109,14 @@ Phase 10B capability details:
 - replay reuses existing Browser MCP action semantics rather than introducing a new replay DSL
 - only one active replay session is allowed per MCP runtime; orchestration remains out of scope for Phase 10B
 
+Phase 10C capability details:
+
+- `browser_start_orchestration`, `browser_get_orchestration`, and `browser_cancel_orchestration` add a minimal fixed-block orchestration workflow
+- orchestration state is session-local and is not persisted across runtime restarts
+- fixed orchestration blocks reuse existing wait / replay / action / query semantics rather than introducing a general DSL
+- orchestration runs blocks sequentially and stops on the first failure
+- block nesting, branching, loops, and workflow-engine behaviors remain out of scope
+
 Minimal multi-tab workflow examples:
 
 ```json