watchlight-enclave 0.2.1__py3-none-any.whl

watchlight_enclave-0.2.1.dist-info/METADATA

@@ -0,0 +1,132 @@
+Metadata-Version: 2.5
+Name: watchlight-enclave
+Version: 0.2.1
+Summary: Watchlight AI Enclave — a governed, isolated runtime for autonomous AI agents.
+Project-URL: Homepage, https://github.com/watchlight-ai-beacon/watchlight-enclave
+Project-URL: Source, https://github.com/watchlight-ai-beacon/watchlight-enclave
+Project-URL: Documentation, https://docs.watchlight.ai/enclave
+Project-URL: Changelog, https://github.com/watchlight-ai-beacon/watchlight-enclave/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/watchlight-ai-beacon/watchlight-enclave/issues
+Project-URL: Security policy, https://github.com/watchlight-ai-beacon/watchlight-enclave/blob/main/SECURITY.md
+Author: Watchlight AI
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agent-security,ai-agents,audit-trail,authorization,cedar,evidence,governance,sandbox
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+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: Topic :: Security
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: System :: Monitoring
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: cryptography>=42.0
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.3.4; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Watchlight AI Enclave
+
+**Run an agent in a box it cannot talk its way out of, and get the evidence
+your security review asks for — checkable offline, by someone who doesn't trust
+you.**
+
+You hand an agent a repo and a task. It can edit files, call tools, and reach
+the network. Two questions follow immediately, and neither is answerable after
+the fact by reading logs the agent could have written:
+
+- **What did it actually try to reach?**
+- **What was it allowed to do, and who decided?**
+
+Enclave runs the agent in an isolated sandbox whose only route out is a
+recording egress guard, and seals what happened into a hash-chained evidence
+bundle you can hand to someone who doesn't trust you.
+
+```bash
+pip install watchlight-enclave
+```
+
+```bash
+wl-enclave init                          # writes enclave.yaml, scaffolds a policy
+wl-enclave keygen                        # one key, once; runs seal signed bundles
+wl-enclave run --purpose "Fix PR #412"   # runs the agent in a sandbox
+wl-enclave verify runs/<id>/bundle       # checks the evidence, offline
+wl-enclave hosts --since 2026-11-03      # what did it actually reach?
+```
+
+That last one is the question a security review opens with, and the answer comes
+out of verified bundles rather than out of the agent's own logs:
+
+```text
+$ wl-enclave hosts --since 2026-11-03
+wl-enclave: runs     14 verified
+wl-enclave: coverage http_connect only; icmp, raw_tcp, udp had no route and are not recorded
+
+HOST                          PORT  VERDICT TRIES      SENT      RECV  LAST IP
+pastebin.com                   443  deny       20         -         -  -
+example.com                    443  allow      20   34.4 kB  128.2 kB  172.66.147.243
+
+wl-enclave: 2 host/verdict pair(s) over 40 attempt(s)
+```
+
+If a run's bundle doesn't verify, its hosts are left out of that table **and
+the count above it says so**. A short host list is the one way this command
+could mislead you, so it refuses to be quietly short.
+
+One rule drives the whole design: **a bundle must never be able to understate
+what happened.** A bundle that quietly drops records while still looking
+complete is worse than one that admits a gap. The first gets a reviewer to sign
+off; the second gets them to ask a question. That's why `verify` gives four
+answers instead of two: `failed`, `uncontained`, `incomplete`, `ok`. Only `ok`
+exits 0.
+
+`verify` needs no account, no network and no Watchlight.
+
+## Requirements
+
+Python 3.10+, and a container runtime (Docker or Colima) for `run`. `verify`
+needs neither.
+
+## Documentation
+
+Everything lives in the repository: the quickstart, what a bundle proves, the
+trust boundaries, the control vocabulary, egress coverage, and how to write a
+driver for a new sandbox.
+
+**Documentation: https://docs.watchlight.ai/enclave**
+
+**Source: https://github.com/watchlight-ai-beacon/watchlight-enclave**
+
+- [Quickstart](https://github.com/watchlight-ai-beacon/watchlight-enclave/blob/main/docs/README.md)
+- [What a bundle proves, and what it does not](https://github.com/watchlight-ai-beacon/watchlight-enclave/blob/main/docs/design/evidence.md)
+- [Changelog](https://github.com/watchlight-ai-beacon/watchlight-enclave/blob/main/CHANGELOG.md) — including the three contracts this project versions separately
+- [Security policy](https://github.com/watchlight-ai-beacon/watchlight-enclave/blob/main/SECURITY.md)
+
+## Status
+
+Early development, pre-1.0. The CLI, the `enclave.yaml` schema and how strictly
+`verify` reads a bundle can each change in a minor release, and the changelog
+always says which of the three moved. 1.0 waits on the manifest reaching its
+final shape.
+
+One limit worth knowing up front. A signature means *this bundle is the one
+that key sealed, and nobody has touched it since*. It does not mean *this
+bundle is everything that happened*. Whoever holds the key can cut the chain
+short and re-seal it, which is why the format already carries a `cosignatures`
+slot for a witness it doesn't have yet. The repository is blunt about this one
+and the rest of the known gaps.
+
+## License
+
+Apache-2.0. The CLI, the evidence format and its offline verifier are all open.
+Two compiled dependencies — the Cedar decision engine and the MCP policy
+enforcement runtime — ship under the
+[Watchlight Developer Edition license](https://github.com/watchlight-ai-beacon/watchlight-de),
+free to use including in production and commercially.

watchlight_enclave-0.2.1.dist-info/RECORD

@@ -0,0 +1,16 @@
+wl_enclave/__init__.py,sha256=4v_cEYS5BFJ0KNnqIUzWHa7am0X4dcSiB9tNvI_G5-E,348
+wl_enclave/attestation.py,sha256=J0y9JEbyiWAKS5JfUp5AwmyI4sgPkqfAxzEblIL3xZQ,10066
+wl_enclave/cli.py,sha256=x7RYX0z4R46kxxsASMLt8syDr-ImhLeOeurswdXCmyU,45182
+wl_enclave/config.py,sha256=yfhts5dFH6N7MJq11lhQ1VO7T6tLmkg4D55HNzG6YEg,14151
+wl_enclave/evidence.py,sha256=JPQTv3Efeyjh5Aoqwu5O6cyyNzl3mmTCj4okBKO2ofQ,36645
+wl_enclave/runs.py,sha256=XhXY5IW0mlsP4L05JZcuQHjPx30sbBlRWRFFlm1A-fA,9398
+wl_enclave/signing.py,sha256=uC4JDxNnIpLfNdCqn2RXE_cMRd8eouYPkglGtLw0q_Q,14291
+wl_enclave/drivers/__init__.py,sha256=bO9-bOa-fDs6QnbnwoLoFDC2SJbEslZ0aUyJ_Or2n0U,12904
+wl_enclave/drivers/docker.py,sha256=ZscTtxgeT4K1OksizjxfP3ILTt8VL7NK1AKZqe660uA,29107
+wl_enclave/egress/__init__.py,sha256=G9EOfeyplw7k2vVHqoc--leBsJPiYAixa58bj04-hbI,11567
+wl_enclave/egress/local.py,sha256=4EDHOvIYvk6_cAvaFo-fiArBdGo8gjJp98nJaQGfy9g,24785
+watchlight_enclave-0.2.1.dist-info/METADATA,sha256=rnkh4zeZ7KiMWHnhkzU_LVyrP1UbM7DamBcsgojArJs,6034
+watchlight_enclave-0.2.1.dist-info/WHEEL,sha256=2iZrJkDIkeDh0k9SikKMqFuRP-ua6mb4Ir1AsER4BEw,87
+watchlight_enclave-0.2.1.dist-info/entry_points.txt,sha256=r2o6d_3GxpiijrCorzJdP75C215rlvj9s9uKa8fQRTY,51
+watchlight_enclave-0.2.1.dist-info/licenses/LICENSE,sha256=tNyAse8BZHonpskyCo-cDwokh5yPmpExEtxAJfirYH8,11343
+watchlight_enclave-0.2.1.dist-info/RECORD,,

watchlight_enclave-0.2.1.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.33.0
+Root-Is-Purelib: true
+Tag: py3-none-any

watchlight_enclave-0.2.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+wl-enclave = wl_enclave.cli:main

watchlight_enclave-0.2.1.dist-info/licenses/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 Watchlight AI
+
+   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.

wl_enclave/__init__.py

@@ -0,0 +1,8 @@
+"""Watchlight AI Enclave — a governed, isolated runtime for autonomous AI agents.
+
+Two layers enforce on every run. The :mod:`~wl_enclave.drivers` runtime decides
+where the agent may connect; Watchlight decides what authority it has. Both are
+recorded in one hash-chained evidence bundle (:mod:`~wl_enclave.evidence`).
+"""
+
+__version__ = "0.2.1"

wl_enclave/attestation.py

@@ -0,0 +1,263 @@
+"""The vocabulary an attestation uses to name individual controls.
+
+An attestation used to collapse a layer's enforcement into one boolean —
+``route_exclusive`` for the guard, a handful of settings for the sandbox. That
+is enough to say a layer held, and not enough to say *what* held. When a
+reviewer asks why a bundle is weaker than they expected, the answer is always
+about one specific control, and a boolean cannot carry it.
+
+So each control is named, and each says two things: whether it was in force,
+and how that was established. The second half is the point. A control read back
+out of the runtime and a control we merely asked for are both "configured", and
+in a bundle they are indistinguishable unless the record says which it was.
+
+Three states, and they map onto the verdict :func:`wl_enclave.evidence.verify`
+already produces rather than introducing a severity scale beside it:
+
+``in_force=True``
+    Established. Contributes nothing to the verdict; this is the normal case.
+
+``in_force=False``
+    The control was not in force. The layer did not hold, so the run is not
+    attested — the caller raises this as a problem.
+
+``in_force=None``
+    Could not be determined. The control may well have held; we cannot say.
+    This lands on ``incomplete``, which already means "everything here is true
+    and some of what happened may be missing" — the same verdict a dropped
+    record produces, for the same reason.
+
+The names are constants because two layers emit them and one verifier reads
+them. A control renamed on one side only would silently stop being checked,
+which is the failure mode the closed record-type set exists to prevent for
+record types.
+"""
+
+from __future__ import annotations
+
+from typing import Optional
+
+__all__ = [
+    "READBACK",
+    "REQUESTED",
+    "RUNTIME_CONFIG",
+    "TOPOLOGY",
+    "NETWORK_UNROUTABLE",
+    "SANDBOX_SINGLE_NETWORK",
+    "SANDBOX_ON_INTENDED_NETWORK",
+    "GUARD_ATTACHED",
+    "GUARD_HAS_EGRESS",
+    "GUARD_LIVE",
+    "ROOTFS_READ_ONLY",
+    "CAPABILITIES_DROPPED",
+    "NO_NEW_PRIVILEGES",
+    "RUNS_AS_NON_ROOT",
+    "EVIDENCE_MASKED",
+    "control",
+    "merge",
+    "unverified_controls",
+    "failed_controls",
+    "unrecognised_controls",
+    "claim_of",
+    "establishes",
+    "CONTAINMENT",
+    "WITNESSING",
+]
+
+# -- how a control's state was established --------------------------------
+
+#: Read out of the running system after the fact. The strongest thing we say.
+READBACK = "runtime_readback"
+
+#: Asked for at creation and not read back. Honest but weaker: a setting
+#: applied and never confirmed is indistinguishable from one never applied.
+REQUESTED = "requested_not_readback"
+
+#: Read back from the runtime's record of the container's configuration. In
+#: between the two above, and worth its own name: it is not our own argv echoed
+#: back, so it catches a setting that never reached the daemon — but it is the
+#: daemon's account of what was asked for, not the kernel's account of what is
+#: in force. A mount destination, for instance, is normalised by the daemon
+#: after this record is made.
+RUNTIME_CONFIG = "runtime_config_readback"
+
+#: True by construction rather than by inspection — there is no route to read
+#: back because the topology never created one.
+TOPOLOGY = "network_topology"
+
+# -- control names, shared by every layer that attests ---------------------
+
+NETWORK_UNROUTABLE = "network_unroutable"
+SANDBOX_SINGLE_NETWORK = "sandbox_single_network"
+SANDBOX_ON_INTENDED_NETWORK = "sandbox_on_intended_network"
+GUARD_ATTACHED = "guard_attached"
+GUARD_HAS_EGRESS = "guard_has_egress"
+GUARD_LIVE = "guard_live_at_readback"
+ROOTFS_READ_ONLY = "rootfs_read_only"
+CAPABILITIES_DROPPED = "capabilities_dropped"
+NO_NEW_PRIVILEGES = "no_new_privileges"
+RUNS_AS_NON_ROOT = "runs_as_non_root"
+EVIDENCE_MASKED = "evidence_masked_from_sandbox"
+
+
+def control(
+    in_force: Optional[bool], verified_by: str, detail: str = ""
+) -> dict:
+    """One control's state, as it appears in an attestation record.
+
+    ``detail`` is for the thing a reviewer would otherwise have to reconstruct
+    — which extra network was attached, what the guard exited with. It is
+    omitted when empty rather than carried as a null, so a record stays
+    readable at a glance.
+    """
+    entry: dict = {"in_force": in_force, "verified_by": verified_by}
+    if detail:
+        entry["detail"] = detail
+    return entry
+
+
+# -- which claim a control's failure belongs to ---------------------------
+
+#: A failure here means the sandbox was less isolated than intended.
+CONTAINMENT = "containment"
+
+#: A failure here means the run was less *observed* than intended. Distinct
+#: from containment because the two move independently and sometimes in
+#: opposite directions: a guard that dies on an internal network leaves the
+#: sandbox able to reach nothing at all, so the run is strictly more contained
+#: and strictly less witnessed. Reporting that as a containment failure sends
+#: an operator to look for an escaped agent when the truth is that the witness
+#: died, and it spends the one alarm that should mean "isolation failed".
+WITNESSING = "witnessing"
+
+_CLAIM = {
+    NETWORK_UNROUTABLE: CONTAINMENT,
+    SANDBOX_SINGLE_NETWORK: CONTAINMENT,
+    SANDBOX_ON_INTENDED_NETWORK: CONTAINMENT,
+    ROOTFS_READ_ONLY: CONTAINMENT,
+    CAPABILITIES_DROPPED: CONTAINMENT,
+    NO_NEW_PRIVILEGES: CONTAINMENT,
+    RUNS_AS_NON_ROOT: CONTAINMENT,
+    EVIDENCE_MASKED: CONTAINMENT,
+    GUARD_ATTACHED: WITNESSING,
+    GUARD_HAS_EGRESS: WITNESSING,
+    GUARD_LIVE: WITNESSING,
+}
+
+
+def claim_of(name: str) -> Optional[str]:
+    """Which claim a control bears on, or ``None`` if this build has no idea.
+
+    An unrecognised name is not silently sorted into one bucket. A verifier
+    that guesses would either raise a containment alarm for something it cannot
+    describe, or quietly discount a real one.
+    """
+    return _CLAIM.get(name)
+
+
+# -- how strongly a control's state was established -----------------------
+
+#: How strong each state is. Lower is weaker, and weaker wins a merge.
+_STRENGTH = {False: 0, None: 1, True: 2}
+
+#: How strong each provenance is, on its own axis. ``REQUESTED`` is the one
+#: that does not establish anything: the module's whole premise is that a
+#: setting applied and never confirmed is indistinguishable from one never
+#: applied, so a control resting on it has not been established whatever its
+#: ``in_force`` says.
+_PROVENANCE = {
+    READBACK: 3,
+    TOPOLOGY: 3,
+    RUNTIME_CONFIG: 2,
+    REQUESTED: 1,
+}
+
+
+def establishes(entry: dict) -> bool:
+    """Whether this entry's provenance is strong enough to establish anything.
+
+    False for ``requested_not_readback``, and false for a provenance string
+    this build does not recognise — an unknown label cannot be assumed to be
+    one of the strong ones, and a driver inventing its own must not be able to
+    buy a stronger reading than the vocabulary grants.
+    """
+    return _PROVENANCE.get(entry.get("verified_by"), 0) >= 2
+
+
+def merge(into: dict, new: dict) -> dict:
+    """Fold one layer's controls into the running set, weakest claim winning.
+
+    Order-independent on purpose. A run has more than one attesting moment —
+    the topology is read when the sandbox is provisioned, the guard's fate is
+    known only at the end — and taking the latest would let anything able to
+    append a record overwrite a finding with a more flattering one. Taking the
+    *weakest* cannot be abused in that direction: an attacker who can append
+    records can only make the bundle describe a worse run than happened, which
+    is the one direction that does not mislead a reviewer.
+
+    It also gets the honest answer here for free. ``guard_live_at_readback``
+    was genuinely in force when the topology was read and genuinely false by
+    the end; the second fact is the one that bears on the evidence.
+    """
+    def rank(entry: dict) -> tuple[int, int]:
+        # Both axes, weakest first. Ranking on in_force alone let the first
+        # record's provenance win whenever two layers agreed on the state —
+        # so a control read back out of the runtime could be replaced by one
+        # merely asked for, with no visible change.
+        return (
+            _STRENGTH.get(entry.get("in_force"), 1),
+            _PROVENANCE.get(entry.get("verified_by"), 0),
+        )
+
+    merged = dict(into)
+    for name, entry in (new or {}).items():
+        if not isinstance(entry, dict):
+            continue
+        held = merged.get(name)
+        if held is None or rank(entry) < rank(held):
+            merged[name] = entry
+    return merged
+
+
+def unverified_controls(controls: dict) -> list[str]:
+    """Names of controls whose state could not be determined.
+
+    These are why a bundle reads ``incomplete`` rather than ``ok``: nothing in
+    it is false, and something in it is unknown.
+    """
+    return sorted(
+        name
+        for name, entry in (controls or {}).items()
+        if isinstance(entry, dict)
+        and (entry.get("in_force") is None or not establishes(entry))
+    )
+
+
+def failed_controls(controls: dict, claim: Optional[str] = None) -> list[str]:
+    """Names of controls established as *not* in force.
+
+    ``claim`` narrows the result to one kind of failure. Callers want this
+    split because the two kinds reach different verdicts — see
+    :data:`CONTAINMENT` and :data:`WITNESSING`.
+    """
+    return sorted(
+        name
+        for name, entry in (controls or {}).items()
+        if isinstance(entry, dict)
+        and entry.get("in_force") is False
+        and (claim is None or claim_of(name) == claim)
+    )
+
+
+def unrecognised_controls(controls: dict) -> list[str]:
+    """Names this build cannot place in either claim.
+
+    Reported rather than bucketed. The constants exist so that one verifier
+    reads what several layers write; a name outside the set means the two have
+    drifted, and a verifier that guessed would hide exactly that.
+    """
+    return sorted(
+        name
+        for name in (controls or {})
+        if claim_of(name) is None
+    )