sergent-py-runtime 0.1.0__tar.gz

sergent_py_runtime-0.1.0/.gitignore

@@ -0,0 +1,21 @@
+AGENTS.md
+.codex/
+.tmp/
+.venv/
+.env
+*.ignored
+*.ignore
+
+# knowledge curation infra
+**/synopsis.xml
+
+# workflow artifacts
+HANDOFF*.md
+
+# python
+.ruff_cache/
+.pytest_cache/
+__pycache__/
+*.egg-info/
+build/
+dist/

sergent_py_runtime-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [2026] [Sergent Pty Ltd]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

sergent_py_runtime-0.1.0/PKG-INFO

@@ -0,0 +1,101 @@
+Metadata-Version: 2.5
+Name: sergent-py-runtime
+Version: 0.1.0
+Summary: Sergent Python reference implementation: the Run execution engine with live Scene state, cancellation, observer delivery, and the opt-in Run Record harness
+Project-URL: Homepage, https://github.com/sergentbuild/sergent-py
+Project-URL: Documentation, https://github.com/sergentbuild/sergent-py/blob/v0.1.0/docs/KNOWLEDGE.md
+Project-URL: Repository, https://github.com/sergentbuild/sergent-py
+Project-URL: Issues, https://github.com/sergentbuild/sergent-py/issues
+Author-email: Sergent Pty Ltd <info@sergent.build>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent,agentic,asyncio,llm,run-record,runtime,sergent
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: AsyncIO
+Classifier: Framework :: Pydantic :: 2
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Requires-Dist: pydantic-core<3,>=2.46.5
+Requires-Dist: pydantic<3,>=2.13.5
+Requires-Dist: sergent-py-core==0.1.0
+Description-Content-Type: text/markdown
+
+# sergent-py-runtime
+
+This package is the execution engine of the Sergent Python reference implementation. It is
+the only package in the stack that may change application data. The specification's rule that
+[the model only proposes](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/framework.md#the-model-only-proposes) is kept here
+or nowhere: every decode, every check, the rehearsal, and the single commit happen inside this
+package.
+
+## Why this package carries the weight
+
+Three properties give the runtime its architectural position.
+
+**It holds mutation authority alone.** The core package holds values and interfaces, the
+providers package holds transport, and the battery package holds wiring. None of them touches
+a Scene. An application therefore reasons about data safety by reasoning about one engine.
+
+**It knows nothing about providers.** Concrete model transport reaches the runtime only
+through a core interface, so this package never imports the providers package. That one
+restriction keeps provider changes out of the safety path and lets the whole engine run under
+test with scripted clients and no network. It is the layering the specification recommends
+in [for implementers](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/for-implementers.md).
+
+**It owns the asynchronous shape of a Run.** Model calls are the Run's only suspension points,
+exactly as [async execution](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/execution-model.md#async-execution) expects. The
+deterministic tail never suspends, so the stretch from Patch validation to commit cannot
+interleave with another Run on the same event loop.
+
+What the runtime does not decide is just as fixed: Scene shape, Target meaning, Intent
+semantics, the Operation vocabulary, prompt text, and evidence retention all belong to the
+application. The engine contributes order, isolation, and evidence.
+
+## A Run in Python
+
+`SergentRuntime` is the [Sergent Runtime](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/terminology.md#sergent-runtime).
+One instance is built from a model client, the Scene Actions, and the Recipe, and it may drive
+many Runs concurrently.
+
+A caller starts a Run in one of two ways. `run()` is the asynchronous entry point and returns
+the terminal result. `start()` schedules the same pipeline on an asyncio task and returns a
+`RunHandle` that reports progress, requests cancellation, and awaits the result. There is no
+synchronous execution twin.
+
+The caller also chooses the Scene authority, and that choice is the application's
+[writer model](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/framework.md#writer-model-and-revision-policy) rather than a
+detail of its user interface. A plain Scene is a snapshot input: the runtime clones it once and
+commits to the isolated clone. A `SceneState` is shared live authority: many Runs may hold the
+same one, and commit compares the observed revision against the current revision before it
+mutates anything.
+
+Between those two ends the Run follows the specification's
+[flow](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/execution-model.md#the-sergent-run-flow) with at most two awaited model
+calls. The first may propose the Intent; recipes that skip it receive the runtime-provided
+[pass-through](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/terminology.md#pass-through) proposal instead. The second
+proposes the Execution Plan. Every remaining step, including the admissibility pass, Patch
+validation, the dry-run, and commit, is a plain synchronous function.
+
+The Run ends with a [Sergent Result](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/terminology.md#sergent-result), not with
+an exception. The result carries the terminal Scene, the closed Run Record, the last reached
+stage, the terminal facts, and any contained observer failures. Ordinary failures inside the
+pipeline become that structured value, and the Scene stays untouched unless commit succeeded.
+
+Persisting the evidence stays optional. When an application opts in, the runtime's Run Record
+harness writes [Run Record files](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/run-record-file-format.md) and the
+application keeps the surrounding policy that
+[observability ownership](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent/docs/observability.md#ownership) assigns to it.
+
+## Where to read next
+
+[docs/KNOWLEDGE.md](https://github.com/sergentbuild/sergent-py/blob/v0.1.0/sergent-py-runtime/docs/KNOWLEDGE.md) walks the whole engine: which Python owner performs each
+step of the Run flow, how this package meets the core and providers packages, and how it
+handles side effects, failure, cancellation, concurrency, and durability.

sergent_py_runtime-0.1.0/README.md

@@ -0,0 +1,71 @@
+# sergent-py-runtime
+
+This package is the execution engine of the Sergent Python reference implementation. It is
+the only package in the stack that may change application data. The specification's rule that
+[the model only proposes](../sergent/docs/framework.md#the-model-only-proposes) is kept here
+or nowhere: every decode, every check, the rehearsal, and the single commit happen inside this
+package.
+
+## Why this package carries the weight
+
+Three properties give the runtime its architectural position.
+
+**It holds mutation authority alone.** The core package holds values and interfaces, the
+providers package holds transport, and the battery package holds wiring. None of them touches
+a Scene. An application therefore reasons about data safety by reasoning about one engine.
+
+**It knows nothing about providers.** Concrete model transport reaches the runtime only
+through a core interface, so this package never imports the providers package. That one
+restriction keeps provider changes out of the safety path and lets the whole engine run under
+test with scripted clients and no network. It is the layering the specification recommends
+in [for implementers](../sergent/docs/for-implementers.md).
+
+**It owns the asynchronous shape of a Run.** Model calls are the Run's only suspension points,
+exactly as [async execution](../sergent/docs/execution-model.md#async-execution) expects. The
+deterministic tail never suspends, so the stretch from Patch validation to commit cannot
+interleave with another Run on the same event loop.
+
+What the runtime does not decide is just as fixed: Scene shape, Target meaning, Intent
+semantics, the Operation vocabulary, prompt text, and evidence retention all belong to the
+application. The engine contributes order, isolation, and evidence.
+
+## A Run in Python
+
+`SergentRuntime` is the [Sergent Runtime](../sergent/docs/terminology.md#sergent-runtime).
+One instance is built from a model client, the Scene Actions, and the Recipe, and it may drive
+many Runs concurrently.
+
+A caller starts a Run in one of two ways. `run()` is the asynchronous entry point and returns
+the terminal result. `start()` schedules the same pipeline on an asyncio task and returns a
+`RunHandle` that reports progress, requests cancellation, and awaits the result. There is no
+synchronous execution twin.
+
+The caller also chooses the Scene authority, and that choice is the application's
+[writer model](../sergent/docs/framework.md#writer-model-and-revision-policy) rather than a
+detail of its user interface. A plain Scene is a snapshot input: the runtime clones it once and
+commits to the isolated clone. A `SceneState` is shared live authority: many Runs may hold the
+same one, and commit compares the observed revision against the current revision before it
+mutates anything.
+
+Between those two ends the Run follows the specification's
+[flow](../sergent/docs/execution-model.md#the-sergent-run-flow) with at most two awaited model
+calls. The first may propose the Intent; recipes that skip it receive the runtime-provided
+[pass-through](../sergent/docs/terminology.md#pass-through) proposal instead. The second
+proposes the Execution Plan. Every remaining step, including the admissibility pass, Patch
+validation, the dry-run, and commit, is a plain synchronous function.
+
+The Run ends with a [Sergent Result](../sergent/docs/terminology.md#sergent-result), not with
+an exception. The result carries the terminal Scene, the closed Run Record, the last reached
+stage, the terminal facts, and any contained observer failures. Ordinary failures inside the
+pipeline become that structured value, and the Scene stays untouched unless commit succeeded.
+
+Persisting the evidence stays optional. When an application opts in, the runtime's Run Record
+harness writes [Run Record files](../sergent/docs/run-record-file-format.md) and the
+application keeps the surrounding policy that
+[observability ownership](../sergent/docs/observability.md#ownership) assigns to it.
+
+## Where to read next
+
+[docs/KNOWLEDGE.md](docs/KNOWLEDGE.md) walks the whole engine: which Python owner performs each
+step of the Run flow, how this package meets the core and providers packages, and how it
+handles side effects, failure, cancellation, concurrency, and durability.

sergent_py_runtime-0.1.0/pyproject.toml

@@ -0,0 +1,71 @@
+[build-system]
+requires = ["hatchling>=1.32.0,<2", "hatch-fancy-pypi-readme>=25.1.0,<26"]
+build-backend = "hatchling.build"
+
+[project]
+name = "sergent-py-runtime"
+version = "0.1.0"
+description = "Sergent Python reference implementation: the Run execution engine with live Scene state, cancellation, observer delivery, and the opt-in Run Record harness"
+dynamic = ["readme"]
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Sergent Pty Ltd", email = "info@sergent.build" }]
+requires-python = ">=3.11"
+keywords = [
+    "sergent",
+    "agentic",
+    "agent",
+    "llm",
+    "runtime",
+    "asyncio",
+    "run-record",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Framework :: Pydantic :: 2",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Framework :: AsyncIO",
+]
+dependencies = [
+    "sergent-py-core==0.1.0",
+    "pydantic>=2.13.5,<3",
+    "pydantic-core>=2.46.5,<3",
+]
+
+[project.urls]
+Homepage = "https://github.com/sergentbuild/sergent-py"
+Documentation = "https://github.com/sergentbuild/sergent-py/blob/v0.1.0/docs/KNOWLEDGE.md"
+Repository = "https://github.com/sergentbuild/sergent-py"
+Issues = "https://github.com/sergentbuild/sergent-py/issues"
+
+[tool.uv.sources]
+sergent-py-core = { workspace = true }
+
+[tool.hatch.metadata.hooks.fancy-pypi-readme]
+content-type = "text/markdown"
+fragments = [{ path = "README.md" }]
+
+[[tool.hatch.metadata.hooks.fancy-pypi-readme.substitutions]]
+pattern = '(\]\()\.\./'
+replacement = '\1https://github.com/sergentbuild/sergent-py/blob/v$HFPR_VERSION/'
+
+[[tool.hatch.metadata.hooks.fancy-pypi-readme.substitutions]]
+pattern = '(\]\()docs/'
+replacement = '\1https://github.com/sergentbuild/sergent-py/blob/v$HFPR_VERSION/$HFPR_PACKAGE_NAME/docs/'
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/sergent_py_runtime"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src/sergent_py_runtime", "README.md"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

sergent_py_runtime-0.1.0/src/sergent_py_runtime/execution/deterministic.py

@@ -0,0 +1,102 @@
+"""Provide the pure synchronous Patch execution core. @sergent/docs/execution-model.md
+@sergent-py-runtime/docs/KNOWLEDGE.md"""
+
+from __future__ import annotations
+
+import collections.abc as cabc
+import typing
+
+import sergent_py_core.operation as core_operation
+import sergent_py_core.patch as core_patch
+import sergent_py_core.scene as core_scene
+import sergent_py_core.scene_actions as core_scene_actions
+import sergent_py_core.target as core_target
+import sergent_py_runtime.execution.errors as runtime_errors
+
+SceneT = typing.TypeVar("SceneT")
+
+
+def _validate_operations(
+    scene_actions: core_scene_actions.SceneActions[SceneT],
+    scene: SceneT,
+    intent: object,
+    target: core_target.Target,
+    operations: cabc.Sequence[core_operation.Operation],
+) -> None:
+    """Reject the first Operation inadmissible for one bounded pass. @sergent/docs/framework.md
+    @sergent-py-runtime/docs/KNOWLEDGE.md"""
+    for index, operation in enumerate(operations):
+        isolated_scene = scene_actions.clone(scene)
+        try:
+            operation.validate_for(isolated_scene, intent, target)
+        except ValueError as exc:
+            metadata = {"index": index, "call": operation.call, "operation_id": operation.op_id}
+            raise runtime_errors._OperationAdmissibilityError(str(exc), metadata) from exc
+
+
+def validate_patch(
+    scene: core_scene_actions.SceneActions[SceneT],
+    snapshot: SceneT,
+    identity: core_scene.SceneIdentity,
+    target: core_target.Target,
+    patch: core_patch.Patch,
+) -> None:
+    """Reject a Patch unsafe for its captured Scene context. @sergent/docs/framework.md
+    @sergent-py-runtime/docs/KNOWLEDGE.md"""
+    if patch.base.scene_id != identity.scene_id:
+        raise runtime_errors.PatchValidationError("patch scene mismatch")
+    if patch.base.revision != identity.revision:
+        raise runtime_errors.StalePatchError(
+            "stale patch",
+            base_revision=patch.base.revision,
+            current_revision=identity.revision,
+        )
+    if not patch.operations:
+        raise runtime_errors.PatchValidationError("no-op patch")
+    if not scene.has_target(snapshot, target):
+        raise runtime_errors.PatchValidationError("missing target")
+    if len(patch.operation_trace) != len(patch.operations):
+        raise runtime_errors.PatchValidationError("operation trace must match operations")
+
+    seen_ops: set[str] = set()
+    for trace, operation in zip(patch.operation_trace, patch.operations):
+        if not isinstance(operation, core_operation.Operation):
+            raise runtime_errors.PatchValidationError("operation must subclass Operation")
+        op_id = operation.op_id
+        if op_id in seen_ops:
+            raise runtime_errors.PatchValidationError("duplicate op_id")
+        seen_ops.add(op_id)
+        if trace.op_id != op_id:
+            raise runtime_errors.PatchValidationError("operation trace op_id mismatch")
+
+
+def dry_run(
+    scene: core_scene_actions.SceneActions[SceneT],
+    snapshot: SceneT,
+    identity: core_scene.SceneIdentity,
+    target: core_target.Target,
+    patch: core_patch.Patch,
+) -> SceneT:
+    """Rehearse a Patch without source mutation. @sergent/docs/execution-model.md
+    @sergent-py-runtime/docs/KNOWLEDGE.md"""
+    after = scene.apply(scene.clone(snapshot), target, list(patch.operations))
+    report = scene.verify(snapshot, after, target, list(patch.operations))
+    if not report.ok:
+        raise runtime_errors.DryRunError(
+            "dry-run verification failed: " + "; ".join(report.issues),
+            metadata={"verification_issues": list(report.issues)},
+        )
+    if scene.identity(after).scene_id != identity.scene_id:
+        raise ValueError("dry-run scene mismatch")
+    return after
+
+
+def commit(
+    snapshot: SceneT,
+    target: core_target.Target,
+    patch: core_patch.Patch,
+    scene: core_scene_actions.SceneActions[SceneT],
+) -> SceneT:
+    """Apply a Patch to an isolated plain Scene. @sergent/docs/execution-model.md
+    @sergent-py-runtime/docs/KNOWLEDGE.md"""
+    return scene.apply(scene.clone(snapshot), target, list(patch.operations))