From 7df3dab5e8259dd98a5ce44f040b656489d856e2 Mon Sep 17 00:00:00 2001
From: Alexey <247128645+axkurcom@users.noreply.github.com>
Date: Sat, 18 Jul 2026 14:30:03 +0300
Subject: [PATCH] Update API.md

Co-Authored-By: brekotis <93345790+brekotis@users.noreply.github.com>
---
 docs/Architecture/API/API.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/Architecture/API/API.md b/docs/Architecture/API/API.md
index 4301a3e..18f9927 100644
--- a/docs/Architecture/API/API.md
+++ b/docs/Architecture/API/API.md
@@ -1474,6 +1474,10 @@ Returns `ReloadStatus` with `state` equal to `accepted`, `preparing`, `activatin
 
 Runtime generation activation rebuilds statistics, upstream routing, replay and buffer state, TLS-front cache, IP tracking, admission/route state, and Middle-End orchestration. Per-user quota accounting is process-scoped and remains continuous across generations. API, metrics, client TCP/Unix listeners, PID ownership, and logging remain process-scoped; changed bind/path fields are reported as deferred and do not cause Maestro to invoke systemd, containerd, or another process supervisor.
 
+Reload preparation requires every configured TLS-front domain to have a non-default cached profile and requires a ready Middle-End pool when direct fallback is disabled. A candidate that does not satisfy either readiness condition fails without replacing the active generation.
+
+The revision is verified again after preparation. With `failure_policy=rollback`, a changed revision or revision read failure rolls the candidate back; with `failure_policy=keep_new`, the condition is reported in `warnings` and activation continues.
+
 ## Mutation Semantics
 
 | Endpoint | Notes |