evarness 0.1.0a1__tar.gz

evarness-0.1.0a1/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 The Evarness Authors
+
+   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.

evarness-0.1.0a1/PKG-INFO

@@ -0,0 +1,165 @@
+Metadata-Version: 2.4
+Name: evarness
+Version: 0.1.0a1
+Summary: Prove an AI agent harness before it touches real data: canonical traces, invariant contracts, portable proof bundles, offline verification.
+Author: Evarness contributors
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/evarness-ai/evarness
+Project-URL: Repository, https://github.com/evarness-ai/evarness
+Keywords: ai-agents,harness,determinism,invariants,provenance,verification
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic<3,>=2.5
+Requires-Dist: pyyaml<7,>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Provides-Extra: sign
+Requires-Dist: cryptography>=42; extra == "sign"
+Provides-Extra: docs
+Requires-Dist: mkdocs==1.6.1; extra == "docs"
+Requires-Dist: mkdocs-material==9.7.7; extra == "docs"
+Dynamic: license-file
+
+# Evarness
+
+**Prove an AI agent harness before it touches real data.**
+
+[![ci](https://github.com/evarness-ai/evarness/actions/workflows/ci.yml/badge.svg)](https://github.com/evarness-ai/evarness/actions/workflows/ci.yml)
+[![pypi](https://img.shields.io/pypi/v/evarness)](https://pypi.org/project/evarness/)
+[![release](https://img.shields.io/github/v/release/evarness-ai/evarness)](https://github.com/evarness-ai/evarness/releases)
+[![license](https://img.shields.io/github/license/evarness-ai/evarness)](LICENSE)
+[![python](https://img.shields.io/badge/python-3.10–3.14-blue)](https://github.com/evarness-ai/evarness/actions/workflows/ci.yml)
+
+[Documentation](https://evarness-ai.github.io/evarness/) ·
+[Live demos](https://evarness-ai.github.io/evarness/demos/) ·
+[Tutorials](https://evarness-ai.github.io/evarness/tutorial-custom-node/) ·
+[Blog](https://evarness-ai.github.io/evarness/blog/) ·
+[Discussions](https://github.com/evarness-ai/evarness/discussions) ·
+[Studio](https://github.com/evarness-ai/evarness-studio)
+
+Your agent has an approval gate in front of its send tool — but yesterday's
+refactor may or may not have kept every path behind it, and when a security
+review asks you to *demonstrate* that nothing sends without a human, a green
+test suite isn't a demonstration. Evarness is **harness assurance**: run the
+harness in simulation, prove its declared rules held, and hand anyone a
+proof bundle they can verify on their own machine.
+
+An agent is a harness plus a model. The model reasons — but the **harness**,
+the deterministic scaffolding that routes, gates, and audits every turn, is
+what decides whether the system is safe to run. Evarness turns its safety
+story into **evidence anyone can check**.
+
+## Why Evarness
+
+- **Canonical traces** — same graph, fixture, and seed ⇒ the same digest
+  (`c1:sha256:…`) — designed and regression-tested to stay identical across
+  supported machines, OSes, and Pythons. Reproduced, not asserted.
+- **Invariant contracts** — "a blocked run never reaches the model",
+  "approval precedes send": declared in YAML, checked on every run.
+- **Proof bundles** — `evarness prove` runs every scenario twice, evaluates
+  the contracts, and states what was **not** proven, in the bundle itself.
+- **Offline verification** — `evarness verify` re-checks any bundle with no
+  network and no trust in the machine that produced it. Signing optional.
+
+## Simulation is the point, not the limitation
+
+Every model and tool response comes from a scripted fixture — which is
+precisely what makes hostile scenarios exact, repeatable, and safe to run a
+thousand times. The harness is the *deterministic* part of an agent: the
+gates, routes, redactions, and budgets. If you can't prove the deterministic
+part holds, the model's quality is irrelevant — a leak through an unguarded
+edge doesn't care how good the model was. You're proving the seatbelt, not
+the driver. Real providers and real tools are refused with an actionable
+error, never silently simulated: this package makes no network calls, by
+design.
+
+## Try it in sixty seconds
+
+```bash
+pip install evarness==0.1.0a1
+
+# expected: PROOF: PENDING, exit 1 — nothing sends without a human approval
+evarness prove approval_gated_send -o proof.json
+
+evarness prove approval_gated_send --approve n3=approve -o proof.json
+evarness verify proof.json          # → VERIFY: OK, offline
+```
+
+**The digest challenge:** your digest should match the
+[v0.1.0 release receipt](https://github.com/evarness-ai/evarness/releases/tag/v0.1.0)
+byte for byte. If it doesn't, that's a bug —
+[file it](https://github.com/evarness-ai/evarness/issues). If it does, you
+just reproduced the product's central claim on your own machine. Every
+command runs headless:
+`validate | run | render | prove | verify | export | patterns`.
+
+## See it before you install it
+
+The [live demos](https://evarness-ai.github.io/evarness/demos/) are generated
+by Evarness itself when the docs site builds — a replay you can scrub, a
+[blocked run](https://evarness-ai.github.io/evarness/demos/blocked.html)
+stopping before the model, and a proof browser carrying a real bundle you can
+extract and verify. The site build **fails** if their digests drift.
+
+## Learn
+
+- [Guide](docs/GUIDE.md) — run graphs, read traces, declare invariants, gate CI
+- [End-to-end walkthrough](docs/E2E.md) — every feature, with the digests your machine should reproduce
+- [Build a custom node in five minutes](docs/tutorial-custom-node.md) · [a domain plugin, without touching core](docs/tutorial-domain-plugin.md)
+- [Architecture](ARCHITECTURE.md) · [Decision log](DECISIONS.md) — every rule the engine enforces traces to a reasoned entry
+
+## Build with us
+
+Evarness is a young project with a big thesis: `evarness.core` is a
+domain-agnostic assurance kernel — graphs, events, digests, contracts,
+proofs — and **agents are its first domain**, built entirely through public,
+typed extension seams. The same machinery can govern ML pipelines, data
+flows, any workflow where "we always do X before Y" deserves to be a
+verified contract instead of a wiki page. That future is exactly what we
+want to build with the community:
+
+- **Run it and tell us.** `prove` → `verify` on your machine — did the
+  digest match the release receipt? Either answer helps.
+- **Build a node.** The [five-minute tutorial](docs/tutorial-custom-node.md)
+  is real: three files, no core changes, your event in the canonical trace.
+- **Dream up a domain.** If your pipeline has rules worth proving, [start a
+  discussion](https://github.com/evarness-ai/evarness/discussions) — domain
+  packs are the project's future, and early ideas shape the seams.
+- **Found something wrong?** A graph, a fixture, and a seed make a perfect,
+  deterministic bug report — [open an issue](https://github.com/evarness-ai/evarness/issues).
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the design rules (determinism
+contract, verdicts never touch evidence, refuse-don't-degrade) — they're
+what make the project provable, and they're enforced kindly but firmly.
+
+## What a proof establishes — and what it doesn't
+
+A bundle demonstrates that declared invariants held over scripted scenarios,
+reproducibly, with the trace as evidence. It does **not** establish universal
+safety, and a signature proves integrity — not that the runs happened. Every
+bundle says this about itself. Scope in [SECURITY.md](SECURITY.md).
+
+## Status
+
+**Alpha, evaluated in the open.** This first release is the assurance spine,
+simulation-only — on PyPI as the pre-release `evarness==0.1.0a1`. Real
+providers, sandboxed tools, and adapters for other agent frameworks are on
+the roadmap, each arriving as a separately proven release. The **stable**
+0.1.0 follows community evaluation — that gate hasn't moved. The optional visual client
+is [Evarness Studio](https://github.com/evarness-ai/evarness-studio) —
+nothing here requires it.
+
+## License
+
+[Apache-2.0](LICENSE).

evarness-0.1.0a1/README.md

@@ -0,0 +1,132 @@
+# Evarness
+
+**Prove an AI agent harness before it touches real data.**
+
+[![ci](https://github.com/evarness-ai/evarness/actions/workflows/ci.yml/badge.svg)](https://github.com/evarness-ai/evarness/actions/workflows/ci.yml)
+[![pypi](https://img.shields.io/pypi/v/evarness)](https://pypi.org/project/evarness/)
+[![release](https://img.shields.io/github/v/release/evarness-ai/evarness)](https://github.com/evarness-ai/evarness/releases)
+[![license](https://img.shields.io/github/license/evarness-ai/evarness)](LICENSE)
+[![python](https://img.shields.io/badge/python-3.10–3.14-blue)](https://github.com/evarness-ai/evarness/actions/workflows/ci.yml)
+
+[Documentation](https://evarness-ai.github.io/evarness/) ·
+[Live demos](https://evarness-ai.github.io/evarness/demos/) ·
+[Tutorials](https://evarness-ai.github.io/evarness/tutorial-custom-node/) ·
+[Blog](https://evarness-ai.github.io/evarness/blog/) ·
+[Discussions](https://github.com/evarness-ai/evarness/discussions) ·
+[Studio](https://github.com/evarness-ai/evarness-studio)
+
+Your agent has an approval gate in front of its send tool — but yesterday's
+refactor may or may not have kept every path behind it, and when a security
+review asks you to *demonstrate* that nothing sends without a human, a green
+test suite isn't a demonstration. Evarness is **harness assurance**: run the
+harness in simulation, prove its declared rules held, and hand anyone a
+proof bundle they can verify on their own machine.
+
+An agent is a harness plus a model. The model reasons — but the **harness**,
+the deterministic scaffolding that routes, gates, and audits every turn, is
+what decides whether the system is safe to run. Evarness turns its safety
+story into **evidence anyone can check**.
+
+## Why Evarness
+
+- **Canonical traces** — same graph, fixture, and seed ⇒ the same digest
+  (`c1:sha256:…`) — designed and regression-tested to stay identical across
+  supported machines, OSes, and Pythons. Reproduced, not asserted.
+- **Invariant contracts** — "a blocked run never reaches the model",
+  "approval precedes send": declared in YAML, checked on every run.
+- **Proof bundles** — `evarness prove` runs every scenario twice, evaluates
+  the contracts, and states what was **not** proven, in the bundle itself.
+- **Offline verification** — `evarness verify` re-checks any bundle with no
+  network and no trust in the machine that produced it. Signing optional.
+
+## Simulation is the point, not the limitation
+
+Every model and tool response comes from a scripted fixture — which is
+precisely what makes hostile scenarios exact, repeatable, and safe to run a
+thousand times. The harness is the *deterministic* part of an agent: the
+gates, routes, redactions, and budgets. If you can't prove the deterministic
+part holds, the model's quality is irrelevant — a leak through an unguarded
+edge doesn't care how good the model was. You're proving the seatbelt, not
+the driver. Real providers and real tools are refused with an actionable
+error, never silently simulated: this package makes no network calls, by
+design.
+
+## Try it in sixty seconds
+
+```bash
+pip install evarness==0.1.0a1
+
+# expected: PROOF: PENDING, exit 1 — nothing sends without a human approval
+evarness prove approval_gated_send -o proof.json
+
+evarness prove approval_gated_send --approve n3=approve -o proof.json
+evarness verify proof.json          # → VERIFY: OK, offline
+```
+
+**The digest challenge:** your digest should match the
+[v0.1.0 release receipt](https://github.com/evarness-ai/evarness/releases/tag/v0.1.0)
+byte for byte. If it doesn't, that's a bug —
+[file it](https://github.com/evarness-ai/evarness/issues). If it does, you
+just reproduced the product's central claim on your own machine. Every
+command runs headless:
+`validate | run | render | prove | verify | export | patterns`.
+
+## See it before you install it
+
+The [live demos](https://evarness-ai.github.io/evarness/demos/) are generated
+by Evarness itself when the docs site builds — a replay you can scrub, a
+[blocked run](https://evarness-ai.github.io/evarness/demos/blocked.html)
+stopping before the model, and a proof browser carrying a real bundle you can
+extract and verify. The site build **fails** if their digests drift.
+
+## Learn
+
+- [Guide](docs/GUIDE.md) — run graphs, read traces, declare invariants, gate CI
+- [End-to-end walkthrough](docs/E2E.md) — every feature, with the digests your machine should reproduce
+- [Build a custom node in five minutes](docs/tutorial-custom-node.md) · [a domain plugin, without touching core](docs/tutorial-domain-plugin.md)
+- [Architecture](ARCHITECTURE.md) · [Decision log](DECISIONS.md) — every rule the engine enforces traces to a reasoned entry
+
+## Build with us
+
+Evarness is a young project with a big thesis: `evarness.core` is a
+domain-agnostic assurance kernel — graphs, events, digests, contracts,
+proofs — and **agents are its first domain**, built entirely through public,
+typed extension seams. The same machinery can govern ML pipelines, data
+flows, any workflow where "we always do X before Y" deserves to be a
+verified contract instead of a wiki page. That future is exactly what we
+want to build with the community:
+
+- **Run it and tell us.** `prove` → `verify` on your machine — did the
+  digest match the release receipt? Either answer helps.
+- **Build a node.** The [five-minute tutorial](docs/tutorial-custom-node.md)
+  is real: three files, no core changes, your event in the canonical trace.
+- **Dream up a domain.** If your pipeline has rules worth proving, [start a
+  discussion](https://github.com/evarness-ai/evarness/discussions) — domain
+  packs are the project's future, and early ideas shape the seams.
+- **Found something wrong?** A graph, a fixture, and a seed make a perfect,
+  deterministic bug report — [open an issue](https://github.com/evarness-ai/evarness/issues).
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the design rules (determinism
+contract, verdicts never touch evidence, refuse-don't-degrade) — they're
+what make the project provable, and they're enforced kindly but firmly.
+
+## What a proof establishes — and what it doesn't
+
+A bundle demonstrates that declared invariants held over scripted scenarios,
+reproducibly, with the trace as evidence. It does **not** establish universal
+safety, and a signature proves integrity — not that the runs happened. Every
+bundle says this about itself. Scope in [SECURITY.md](SECURITY.md).
+
+## Status
+
+**Alpha, evaluated in the open.** This first release is the assurance spine,
+simulation-only — on PyPI as the pre-release `evarness==0.1.0a1`. Real
+providers, sandboxed tools, and adapters for other agent frameworks are on
+the roadmap, each arriving as a separately proven release. The **stable**
+0.1.0 follows community evaluation — that gate hasn't moved. The optional visual client
+is [Evarness Studio](https://github.com/evarness-ai/evarness-studio) —
+nothing here requires it.
+
+## License
+
+[Apache-2.0](LICENSE).

evarness-0.1.0a1/evarness/__init__.py

@@ -0,0 +1,123 @@
+"""evarness — prove an AI agent harness before it touches real data.
+
+``import evarness`` gives you the batteries-included surface: the kernel plus
+the agents domain, with plugins discovered — loaded lazily, on first
+attribute access. For the bare kernel (e.g. when building your own domain),
+import from ``evarness.core`` directly — it never loads a domain behind your
+back, and ``tests/test_architecture_boundaries.py`` holds that promise.
+"""
+
+from __future__ import annotations
+
+from typing import TYPE_CHECKING, Any
+
+if TYPE_CHECKING:  # static types for the lazy surface
+    from evarness.core.errors import (
+        EvarnessError as EvarnessError,
+        GraphValidationError as GraphValidationError,
+        NodeBlocked as NodeBlocked,
+        RegistryError as RegistryError,
+        RunPaused as RunPaused,
+    )
+    from evarness.core.executor import (
+        Emitter as Emitter,
+        RunContext as RunContext,
+        RunResult as RunResult,
+        execute as execute,
+    )
+    from evarness.core.graph import (
+        GraphModel as GraphModel,
+        lint as lint,
+        migrate as migrate,
+        topological_order as topological_order,
+    )
+    from evarness.core.invariants import (
+        check_invariants as check_invariants,
+        load_invariant_defs as load_invariant_defs,
+    )
+    from evarness.core.prove import prove as prove, verify_proof as verify_proof
+    from evarness.core.registry import (
+        NODE_TYPES as NODE_TYPES,
+        load_entry_point_plugins as load_entry_point_plugins,
+    )
+    from evarness.core.trace import canonical_trace as canonical_trace, trace_digest as trace_digest
+    from evarness.domains import agents as agents
+    from evarness.domains.agents.sim import Fixture as Fixture, load_fixture as load_fixture
+
+__version__ = "0.1.0a1"
+
+__all__ = [
+    "EvarnessError",
+    "GraphValidationError",
+    "NodeBlocked",
+    "RegistryError",
+    "RunPaused",
+    "Emitter",
+    "RunContext",
+    "RunResult",
+    "execute",
+    "GraphModel",
+    "lint",
+    "migrate",
+    "topological_order",
+    "check_invariants",
+    "load_invariant_defs",
+    "prove",
+    "verify_proof",
+    "NODE_TYPES",
+    "load_entry_point_plugins",
+    "canonical_trace",
+    "trace_digest",
+    "Fixture",
+    "load_fixture",
+    "agents",
+    "__version__",
+]
+
+_surface: dict[str, Any] = {}
+
+
+def _load_surface() -> dict[str, Any]:
+    from evarness.core import errors, executor, graph, invariants, prove, registry, trace
+    from evarness.domains import agents
+    from evarness.domains.agents import sim
+
+    registry.load_entry_point_plugins()
+    return {
+        "EvarnessError": errors.EvarnessError,
+        "GraphValidationError": errors.GraphValidationError,
+        "NodeBlocked": errors.NodeBlocked,
+        "RegistryError": errors.RegistryError,
+        "RunPaused": errors.RunPaused,
+        "Emitter": executor.Emitter,
+        "RunContext": executor.RunContext,
+        "RunResult": executor.RunResult,
+        "execute": executor.execute,
+        "GraphModel": graph.GraphModel,
+        "lint": graph.lint,
+        "migrate": graph.migrate,
+        "topological_order": graph.topological_order,
+        "check_invariants": invariants.check_invariants,
+        "load_invariant_defs": invariants.load_invariant_defs,
+        "prove": prove.prove,
+        "verify_proof": prove.verify_proof,
+        "NODE_TYPES": registry.NODE_TYPES,
+        "load_entry_point_plugins": registry.load_entry_point_plugins,
+        "canonical_trace": trace.canonical_trace,
+        "trace_digest": trace.trace_digest,
+        "Fixture": sim.Fixture,
+        "load_fixture": sim.load_fixture,
+        "agents": agents,
+    }
+
+
+def __getattr__(name: str) -> Any:
+    if name in __all__:
+        if not _surface:
+            _surface.update(_load_surface())
+        return _surface[name]
+    raise AttributeError(f"module 'evarness' has no attribute {name!r}")
+
+
+def __dir__() -> list[str]:
+    return sorted(set(globals()) | set(__all__))