From 2ed76979d5f9512f6aa65bc4a931a5b00660ba60 Mon Sep 17 00:00:00 2001 From: Dotta Date: Fri, 14 Aug 2026 19:35:27 +0000 Subject: [PATCH] docs: clarify runtime coherence target status Co-Authored-By: Paperclip --- doc/execution-semantics.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/execution-semantics.md b/doc/execution-semantics.md index c13eed65120..655591d5cbe 100644 --- a/doc/execution-semantics.md +++ b/doc/execution-semantics.md @@ -376,6 +376,8 @@ For runtime-created `git_worktree` execution workspaces, branch coherence is par #### Managed runtime coherence +This subsection is the accepted target contract for ongoing managed-runtime coherence work. It defines the required end state; it does not claim that every current runtime or completion path enforces these rules yet. + Every managed runtime-service command must finish with one coherent, inspectable postcondition. Desired state and actual state are separate values: - desired state records the operator's intent, such as `running` or `stopped`