deterministic-scenario-engine 2.0.0__tar.gz → 2.1.0__tar.gz

{deterministic_scenario_engine-2.0.0 → deterministic_scenario_engine-2.1.0}/MANIFEST.in

@@ -4,6 +4,7 @@ include pyproject.toml
 recursive-include src *.py
 recursive-include docs *.md
 recursive-include examples *.yaml
+include examples/phase3_ecommerce_evidence.py
 recursive-include tests *.py
 global-exclude *.py[cod]
 global-exclude __pycache__

{deterministic_scenario_engine-2.0.0/src/deterministic_scenario_engine.egg-info → deterministic_scenario_engine-2.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deterministic-scenario-engine
-Version: 2.0.0
+Version: 2.1.0
 Summary: Reproducible, state-consistent business scenarios with deterministic ground truth
 License-Expression: Apache-2.0
 Keywords: deterministic,scenario,testing,fixtures,replay
@@ -35,10 +35,11 @@ Dynamic: license-file
 
 Deterministic Scenario Engine (DSE) creates reproducible, state-consistent
 business histories and deterministic scenario suites with ground truth for
-testing. The Phase 2 contract is frozen in this source tree as an unpublished
-2.0.0 release candidate; no PyPI or GitHub release has occurred yet. Its
-distribution version is 2.0.0 while its deterministic compatibility version
-remains `ENGINE_VERSION == "1.0.0"` and its DSL version remains integer 1.
+testing. The published distribution is `deterministic-scenario-engine` 2.0.0.
+Phase 3 evidence-interchange capabilities are implemented on `main` and the
+current source release candidate reports distribution version 2.1.0, while 2.1.0
+is not published. Its deterministic compatibility version remains
+`ENGINE_VERSION == "1.0.0"`, and its DSL version remains integer 1.
 
 ## Why it exists
 
@@ -66,14 +67,18 @@ make expected behavior explicit.
 - ordered Cartesian matrices with stable case IDs and original indexes
 - immutable ordered batch plans and worker-independent results
 - structured, redacted inspect/explain evidence and typed RFC 6901 semantic diff
-- nine-command `scenario` CLI for local and CI workflows
+- twelve-command `scenario` CLI for local and CI workflows, including bounded
+  local evidence export, verification, and lossless migration
 - explicit immutable Domain Pack registries and pure Oracle Assertions
+- canonical evidence bundles, ordered JSON/JSONL export, compatibility reports,
+  explicit adapters, closed lossless migrations, and fixture-directory export
 
 Core execution does not require a database, network service, plugin, or property
 testing framework. See [security assumptions and non-goals](docs/security-and-non-goals.md).
-Phase 2 adds no hidden discovery, network, randomness, wall-clock, or ambient
-environment semantics. Its public imports, CLI contract, bounds, compatibility
-posture, and adoption guidance are frozen in the [Phase 2 public contract](docs/phase2-public-contract.md).
+Neither Phase 2 nor Phase 3 adds hidden discovery, network, randomness,
+wall-clock, or ambient environment semantics. The historical Phase 2 contract
+is frozen in the [Phase 2 public contract](docs/phase2-public-contract.md); the
+additive evidence surface is frozen in the [Phase 3 public contract](docs/phase3-public-contract.md).
 
 ## Installation
 
@@ -93,7 +98,7 @@ Install only the named optional integrations you need:
 /tmp/scenario-engine-docs-venv/bin/python -m pip install '.[schemathesis]'
 ```
 
-The release-candidate distribution is `deterministic-scenario-engine` 2.0.0. Install the package
+The published distribution is `deterministic-scenario-engine` 2.0.0. Install the package
 with `pip install deterministic-scenario-engine`, or select an optional integration
 with a command such as `pip install 'deterministic-scenario-engine[pytest]'`.
 
@@ -153,12 +158,13 @@ Unsupported cross-version replay fails explicitly. See the [determinism model](d
 - [Security assumptions and non-goals](docs/security-and-non-goals.md)
 - [Compatibility contract](docs/compatibility.md)
 - [Phase 2 public contract, CLI, and hard bounds](docs/phase2-public-contract.md)
+- [Phase 3 public contract and evidence interchange](docs/phase3-public-contract.md)
 
 ## Status
 
 Distribution release identity and deterministic engine compatibility are
-separate contracts: this unpublished candidate has distribution version 2.0.0,
-but generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. Phase 2
-suite, composition, matrix, inspection, diff, Domain Pack, and Oracle Assertion
-contracts keep their own explicit schema versions. No 2.0.0 tag or publication
-has occurred. The project is licensed under Apache-2.0.
+separate contracts. Version 2.0.0 has been published to PyPI and as a GitHub
+Release. This source tree reports the unpublished 2.1.0 release candidate;
+generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. No 2.1.0 tag,
+GitHub Release, or package-index publication exists. The project is licensed
+under Apache-2.0.

{deterministic_scenario_engine-2.0.0 → deterministic_scenario_engine-2.1.0}/README.md

@@ -4,10 +4,11 @@
 
 Deterministic Scenario Engine (DSE) creates reproducible, state-consistent
 business histories and deterministic scenario suites with ground truth for
-testing. The Phase 2 contract is frozen in this source tree as an unpublished
-2.0.0 release candidate; no PyPI or GitHub release has occurred yet. Its
-distribution version is 2.0.0 while its deterministic compatibility version
-remains `ENGINE_VERSION == "1.0.0"` and its DSL version remains integer 1.
+testing. The published distribution is `deterministic-scenario-engine` 2.0.0.
+Phase 3 evidence-interchange capabilities are implemented on `main` and the
+current source release candidate reports distribution version 2.1.0, while 2.1.0
+is not published. Its deterministic compatibility version remains
+`ENGINE_VERSION == "1.0.0"`, and its DSL version remains integer 1.
 
 ## Why it exists
 
@@ -35,14 +36,18 @@ make expected behavior explicit.
 - ordered Cartesian matrices with stable case IDs and original indexes
 - immutable ordered batch plans and worker-independent results
 - structured, redacted inspect/explain evidence and typed RFC 6901 semantic diff
-- nine-command `scenario` CLI for local and CI workflows
+- twelve-command `scenario` CLI for local and CI workflows, including bounded
+  local evidence export, verification, and lossless migration
 - explicit immutable Domain Pack registries and pure Oracle Assertions
+- canonical evidence bundles, ordered JSON/JSONL export, compatibility reports,
+  explicit adapters, closed lossless migrations, and fixture-directory export
 
 Core execution does not require a database, network service, plugin, or property
 testing framework. See [security assumptions and non-goals](docs/security-and-non-goals.md).
-Phase 2 adds no hidden discovery, network, randomness, wall-clock, or ambient
-environment semantics. Its public imports, CLI contract, bounds, compatibility
-posture, and adoption guidance are frozen in the [Phase 2 public contract](docs/phase2-public-contract.md).
+Neither Phase 2 nor Phase 3 adds hidden discovery, network, randomness,
+wall-clock, or ambient environment semantics. The historical Phase 2 contract
+is frozen in the [Phase 2 public contract](docs/phase2-public-contract.md); the
+additive evidence surface is frozen in the [Phase 3 public contract](docs/phase3-public-contract.md).
 
 ## Installation
 
@@ -62,7 +67,7 @@ Install only the named optional integrations you need:
 /tmp/scenario-engine-docs-venv/bin/python -m pip install '.[schemathesis]'
 ```
 
-The release-candidate distribution is `deterministic-scenario-engine` 2.0.0. Install the package
+The published distribution is `deterministic-scenario-engine` 2.0.0. Install the package
 with `pip install deterministic-scenario-engine`, or select an optional integration
 with a command such as `pip install 'deterministic-scenario-engine[pytest]'`.
 
@@ -122,12 +127,13 @@ Unsupported cross-version replay fails explicitly. See the [determinism model](d
 - [Security assumptions and non-goals](docs/security-and-non-goals.md)
 - [Compatibility contract](docs/compatibility.md)
 - [Phase 2 public contract, CLI, and hard bounds](docs/phase2-public-contract.md)
+- [Phase 3 public contract and evidence interchange](docs/phase3-public-contract.md)
 
 ## Status
 
 Distribution release identity and deterministic engine compatibility are
-separate contracts: this unpublished candidate has distribution version 2.0.0,
-but generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. Phase 2
-suite, composition, matrix, inspection, diff, Domain Pack, and Oracle Assertion
-contracts keep their own explicit schema versions. No 2.0.0 tag or publication
-has occurred. The project is licensed under Apache-2.0.
+separate contracts. Version 2.0.0 has been published to PyPI and as a GitHub
+Release. This source tree reports the unpublished 2.1.0 release candidate;
+generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. No 2.1.0 tag,
+GitHub Release, or package-index publication exists. The project is licensed
+under Apache-2.0.

{deterministic_scenario_engine-2.0.0 → deterministic_scenario_engine-2.1.0}/docs/api.md

@@ -1,15 +1,15 @@
 # Public Python API
 
 This is the canonical top-level Phase 1.0 contract, preserved unchanged by the
-Phase 2 freeze. Importable implementation symbols not listed here are not
-implicitly promoted to top-level public API. Specialized Phase 2 APIs are
-public through the explicit subpackages documented below, not package-root
-convenience exports.
+Phase 2 and Phase 3 freezes. Importable implementation symbols not listed here
+are not implicitly promoted to top-level public API. Specialized APIs are public
+through the explicit subpackages documented below, not package-root convenience
+exports.
 
 ## Constants and value objects
 
 - `ENGINE_VERSION` — engine compatibility version recorded in manifests; for
-  the 1.0 release candidate it intentionally equals distribution version 1.0.0.
+  current manifests it remains 1.0.0 independently of distribution version.
 - `MISSING` — singleton semantic missing value, distinct from null.
 - `LogicalID(value: str)` — deterministic logical identifier value; users
   normally receive it from `$id` generation.
@@ -185,3 +185,39 @@ paths are stable while helpers outside `__all__` are intentionally internal.
 
 The schema/version constants and all exact export manifests are executable
 contract tests. See the [complete Phase 2 contract](phase2-public-contract.md).
+
+## Phase 3 evidence APIs
+
+Phase 3 adds no package-root names. Its stable APIs are the names in `__all__`
+of `scenario_engine.evidence` and `scenario_engine.reference_packs`; helpers in
+their implementation modules are intentionally internal. Typical imports are:
+
+```python
+from scenario_engine.evidence import (
+    ArtifactDescriptor,
+    EvidenceBundle,
+    EvidenceEntry,
+    EvidenceProvenance,
+    EvidenceRelationship,
+    EvidenceType,
+    compatibility_report,
+    export_evidence_bundle,
+    plan_migration,
+    read_evidence_bundle,
+)
+from scenario_engine.reference_packs import (
+    EcommerceEvidenceWorkflow,
+    ecommerce_domain_pack,
+    export_ecommerce_evidence,
+)
+```
+
+The evidence subpackage exposes immutable bundle/entry/relationship/provenance
+models and canonicalization; bounded local reading and atomic export; canonical
+JSON/JSONL records; explicit adapter capability/publication/receipt contracts;
+finite compatibility reports and metadata-only migration plans; six closed,
+lossless executable wrapper routes; and deterministic fixture-directory export.
+`scenario_engine.reference_packs` exposes the ecommerce demonstrator and its
+existing registry factory, not a generic workflow framework. The exact public
+names, errors, schemas, limits, and compatibility posture are normative in the
+[Phase 3 public contract](phase3-public-contract.md).

{deterministic_scenario_engine-2.0.0 → deterministic_scenario_engine-2.1.0}/docs/determinism.md

@@ -81,5 +81,17 @@ evidence. Worker scheduling, filesystem enumeration, host paths, locale defaults
 environment variables, network responses, and process history are not semantic
 coordinates.
 
+Phase 3 evidence identity is the SHA-256 of canonical bundle index bytes. Entries
+bind explicit artifact paths, sizes, schemas, and content SHA-256 values;
+canonical export preserves those bytes and publishes an absent destination
+atomically. JSONL records follow caller order. Compatibility reports and
+migration plans use finite tables and deterministic canonical bytes; migration
+results bind source/target hashes and an ordered transformation tuple. Fixture
+IDs are explicit and stable, adapter receipts retain submission ordinal, and the
+ecommerce reference bundle identity is independent of destination path and
+worker scheduling. None of these downstream identities changes Phase 2 result
+or manifest semantics.
+
 See [reproducibility](reproducibility.md) for recorded context and
-[compatibility](compatibility.md) for the normative replay contract.
+[compatibility](compatibility.md) for the normative replay contract, and the
+[Phase 3 public contract](phase3-public-contract.md) for evidence identity.

{deterministic_scenario_engine-2.0.0 → deterministic_scenario_engine-2.1.0}/docs/phase2-public-contract.md

@@ -1,13 +1,16 @@
 # Phase 2 Public Contract Freeze
 
-This document defines the upcoming Phase 2 / 2.0 public contract implemented in
-this source tree. It is an unpublished 2.0.0 release candidate; no PyPI or
-GitHub release has occurred yet. Distribution metadata is 2.0.0, while the
+This document defines the historical Phase 2 / 2.0 public contract. Version
+2.0.0 has since been published to PyPI and as a GitHub Release. Distribution
+metadata remains 2.0.0 in the current source tree, while the
 deterministic core compatibility token recorded in manifests remains
 `ENGINE_VERSION == "1.0.0"`. DSL version remains integer 1. Distribution release
 identity and engine compatibility are distinct concepts. Composition, matrix,
 suite, inspection, diff, Domain Pack, and Oracle Assertion contracts retain
 their independent schema versions and do not reinterpret valid v1 documents.
+The additive, currently unreleased Phase 3 evidence contract is documented
+separately in the [Phase 3 public contract](phase3-public-contract.md); its
+eventual distribution target is 2.1.0.
 
 ## Supported product surface