truegrain 0.1.0__tar.gz

truegrain-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,73 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: Python ${{ matrix.python }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # The client uses only the standard library, so the range it supports is
+        # the range it is tested on rather than whatever the maintainer happens
+        # to run.
+        python: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      # Includes test_covers_spec.py, which fails when the engine gains an
+      # operation this client cannot call.
+      - name: Test
+        run: pytest -q
+
+      - name: No tests were skipped
+        run: |
+          skipped=$(pytest -q -rs 2>&1 | grep -c '^SKIPPED' || true)
+          if [ "$skipped" != "0" ]; then
+            echo "$skipped test(s) skipped; the contract suite must not be silently absent"
+            pytest -q -rs 2>&1 | grep '^SKIPPED'
+            exit 1
+          fi
+
+  no-dependencies:
+    name: Imports without any third-party package
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      # The point of this client is that installing it into an agent's
+      # environment cannot conflict with anything already there. That claim is
+      # only true while it imports on a bare interpreter, so it is tested rather
+      # than asserted in the README.
+      - name: Install with no extras
+        run: pip install .
+
+      - name: Import and use it without pandas or pyyaml
+        run: |
+          python - <<'PY'
+          import truegrain
+          from truegrain import Client, Refused, filters, tools
+          c = Client("http://127.0.0.1:8080", token="not-used")
+          assert filters.eq("orders.status", "shipped")["op"] == "eq"
+          assert tools.tool_specs() and tools.TOOL_NAMES
+          r = Refused(code="fan_out_would_inflate", reason="x", retry="modify")
+          assert r.should_modify() and not r.is_final()
+          print("imports and works on a bare interpreter:", truegrain.__version__)
+          PY

truegrain-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,78 @@
+name: Publish
+
+# Publishing uses PyPI Trusted Publishing, so there is no API token in this
+# repository and none in an organisation secret. PyPI verifies a short-lived
+# OIDC token minted by GitHub for this workflow in this repository, which means
+# a leaked secret cannot be used to publish because there is no secret.
+#
+# Setting it up, once, on PyPI:
+#   Your projects -> truegrain -> Publishing -> Add a trusted publisher
+#     Owner:        rk-chavali
+#     Repository:   truegrain-python
+#     Workflow:     publish.yml
+#     Environment:  pypi
+#
+# For the very first release, before the project exists, use the same form under
+# "Publishing" on your account and add it as a *pending* publisher.
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install build tooling
+        run: pip install build
+
+      # The tests run again here rather than trusting the CI run on the commit.
+      # A release is built from a tag, and a tag can point anywhere.
+      - name: Test before building
+        run: |
+          pip install -e ".[dev]"
+          pytest -q
+
+      - name: Check the version matches the tag
+        if: github.event_name == 'release'
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          declared=$(python -c "import truegrain; print(truegrain.__version__)")
+          if [ "$tag" != "$declared" ]; then
+            echo "tag $GITHUB_REF_NAME does not match __version__ $declared"
+            echo "a package whose version disagrees with its tag cannot be traced back to a commit"
+            exit 1
+          fi
+
+      - name: Build
+        run: python -m build
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      # The OIDC token PyPI verifies. This is the whole credential.
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

truegrain-0.1.0/.github/workflows/spec-drift.yml

@@ -0,0 +1,79 @@
+name: Spec drift
+
+# The contract lives in the engine repository. This client vendors a copy so it
+# builds offline and so a contract change arrives as a reviewable diff, but a
+# vendored copy is a copy that can quietly go stale.
+#
+# This job is what stops that. It fetches the engine's current spec, and if it
+# differs from the pinned one it opens a pull request carrying the new spec. The
+# client's own contract tests then run against it, so an endpoint this client
+# cannot call shows up as a failing check on that pull request rather than as a
+# support question.
+
+on:
+  schedule:
+    # Daily. A contract does not move often, and a drift noticed within a day is
+    # noticed long before anyone depends on the new operation.
+    - cron: "17 6 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  compare:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Fetch the engine's current spec
+        run: |
+          curl -fsSL -o /tmp/upstream.yaml \
+            https://raw.githubusercontent.com/rk-chavali/truegrain/main/api/openapi.yaml
+          curl -fsSL -o /tmp/upstream.sha \
+            https://api.github.com/repos/rk-chavali/truegrain/commits/main
+          python -c "import json;print(json.load(open('/tmp/upstream.sha'))['sha'])" > /tmp/sha.txt
+
+      - name: Compare against the pin
+        id: compare
+        run: |
+          if diff -q spec/openapi.yaml /tmp/upstream.yaml >/dev/null; then
+            echo "changed=false" >> "$GITHUB_OUTPUT"
+            echo "the vendored spec matches the engine"
+          else
+            echo "changed=true" >> "$GITHUB_OUTPUT"
+            echo "the contract moved:"
+            diff -u spec/openapi.yaml /tmp/upstream.yaml | head -60 || true
+          fi
+
+      - name: Update the pin
+        if: steps.compare.outputs.changed == 'true'
+        run: |
+          cp /tmp/upstream.yaml spec/openapi.yaml
+          cp /tmp/sha.txt spec/PINNED_AT
+
+      - name: Open a pull request
+        if: steps.compare.outputs.changed == 'true'
+        uses: peter-evans/create-pull-request@v7
+        with:
+          branch: spec-drift
+          title: "The engine's API contract moved"
+          commit-message: |
+            Update the vendored OpenAPI spec
+
+            The engine's contract changed. The client's own contract tests run
+            against this spec, so a failing check here means an operation this
+            client cannot call.
+          body: |
+            The engine's `api/openapi.yaml` no longer matches the copy pinned here.
+
+            The contract tests in `tests/test_covers_spec.py` run against the
+            vendored spec, so:
+
+            - **checks pass**: the change is additive in a way this client already
+              handles, or cosmetic. Merge it.
+            - **checks fail**: the engine gained an operation this client cannot
+              call, or removed one it still claims. Add or remove the method and
+              update `OPERATIONS` in `truegrain/client.py`.
+          labels: contract

truegrain-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+*.egg-info/
+dist/
+build/
+.venv/
+.coverage

truegrain-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

truegrain-0.1.0/PKG-INFO

@@ -0,0 +1,224 @@
+Metadata-Version: 2.5
+Name: truegrain
+Version: 0.1.0
+Summary: Python client for truegrain: governed metrics for agents, notebooks and applications.
+Project-URL: Homepage, https://github.com/rk-chavali/truegrain-python
+Project-URL: Documentation, https://github.com/rk-chavali/truegrain-python#readme
+Project-URL: Source, https://github.com/rk-chavali/truegrain-python
+Project-URL: Engine, https://github.com/rk-chavali/truegrain
+Project-URL: Issues, https://github.com/rk-chavali/truegrain-python/issues
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agents,governance,mcp,metrics,ossie,semantic-layer
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Database :: Front-Ends
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: pandas>=1.5; extra == 'dev'
+Requires-Dist: pytest>=7; extra == 'dev'
+Requires-Dist: pyyaml>=6; extra == 'dev'
+Provides-Extra: pandas
+Requires-Dist: pandas>=1.5; extra == 'pandas'
+Description-Content-Type: text/markdown
+
+# truegrain (Python)
+
+The Python client for [truegrain](https://github.com/rk-chavali/truegrain):
+governed metrics for agents, notebooks and applications.
+
+There is no method that sends SQL, because there is no endpoint that accepts it.
+The only expressible request is a semantic one.
+
+```bash
+pip install truegrain            # no dependencies
+pip install truegrain[pandas]    # adds to_dataframe()
+```
+
+The client uses only the standard library. That is deliberate: this package goes
+into agent environments where a dependency conflict is a real cost, and thirteen
+endpoints do not justify dragging one in.
+
+## Use it
+
+```python
+import os
+from truegrain import Client, filters
+
+client = Client.from_env()          # SEMANTIC_URL, SEMANTIC_TOKEN
+
+for metric in client.metrics(search="revenue"):
+    print(metric.name, "-", metric.description)
+
+result = client.query(
+    metrics=["sales.order_revenue", "marketing.campaign_spend"],
+    dimensions=["sales.orders.order_date"],
+    grain="month",
+    filters=[filters.in_("sales.orders.status", "shipped", "delivered")],
+    order_by=[{"field": "order_date"}],
+)
+
+result.to_dataframe()
+```
+
+Those two metrics live in different namespaces and aggregate different facts.
+The engine computes each separately and joins them on the shared month, so both
+numbers are correct rather than one being inflated by the join.
+
+Every result carries the SQL that produced it and the exact version of the
+definitions used:
+
+```python
+frame = result.to_dataframe()
+frame.attrs["compiled_sql"]
+frame.attrs["model_version"]      # sha256:eebdad0d19bb
+```
+
+That is not a debug feature. It is how a disagreement about a number gets
+settled, which is why it survives into the frame rather than being dropped at
+the client boundary.
+
+## Refusals are answers
+
+The engine declines questions it cannot answer correctly, and says what to do
+instead. Catch `Refused` and branch on the retry class rather than on the text.
+
+```python
+from truegrain import Refused
+
+try:
+    client.query(metrics=["sales.order_revenue"],
+                 dimensions=["sales.products.category"])
+except Refused as refusal:
+    if refusal.should_modify():
+        print("try instead:", refusal.hint)
+    elif refusal.should_wait():
+        ...        # the same request may work shortly
+    elif refusal.is_final():
+        ...        # stop; say so rather than substituting another metric
+```
+
+That example refuses because an order contains several products, so revenue per
+category has no answer without an allocation rule. The hint names the metrics
+defined at the grain where the question *is* well defined:
+
+```
+fan_out_would_inflate: metric "order_revenue" aggregates SUM(...) over orders,
+but this query repeats orders rows
+  hint: ... Metrics defined at the order_lines grain answer this correctly:
+        line_revenue, units_sold.
+  retry: modify
+```
+
+The three classes matter most to an agent. Without them it either gives up on a
+typo or loops forever on a denial.
+
+| `retry` | Meaning |
+|---|---|
+| `modify` | Answerable, but not as written. Change the arguments. |
+| `later` | Nothing is wrong with the request. Something outside it failed. |
+| `never` | No version of this will succeed for you. Stop. |
+
+## Wiring into an agent framework
+
+Most frameworks accept a list of function schemas and call back with a name and
+arguments. `tools` produces that list and dispatches those calls, which covers
+LangChain, CrewAI, the OpenAI Agents SDK, Pydantic AI and anything hand-rolled
+without this library growing an adapter per framework.
+
+```python
+from truegrain import Client, tools
+
+client = Client.from_env()
+specs = tools.tool_specs()          # hand these to the framework
+
+# when the model calls back:
+result = tools.dispatch(client, name, arguments)
+```
+
+`dispatch` returns refusals rather than raising them, because a framework
+feeding the result back to a model wants the text and the retry class, not a
+traceback.
+
+If your client speaks the Model Context Protocol, skip this and point it at the
+engine's MCP server instead. Same four tools, same guarantees, no code.
+
+```bash
+claude mcp add truegrain -- /path/to/truegrain serve mcp
+```
+
+## Dry runs
+
+`compile` returns the SQL a request would produce without running it, which is
+useful before committing an agent to an expensive query.
+
+```python
+compiled = client.compile(metrics=["sales.order_revenue"],
+                          dimensions=["sales.customers.region"])
+print(compiled.compiled_sql)
+print(compiled.parts)      # >1 means facts were aggregated separately and joined
+```
+
+A dry run is still governed. A request you may not run returns a refusal and no
+SQL, and the inspection is recorded in the audit log as `compiled` rather than
+`allowed`. It shows you what a query would do; it is not a way around the gate.
+
+## Know what you are trusting
+
+```python
+health = client.health()
+health.governs_columns          # is column-level access control configured at all
+health.enforcement_notes        # plain-language list of what this deployment does NOT enforce
+```
+
+A deployment that enforces nothing says so here. Overstating a governance
+guarantee is worse than not offering one.
+
+## Errors
+
+| Exception | When |
+|---|---|
+| `Refused` | The engine understood and declined. Carries `code`, `reason`, `hint`, `retry`. |
+| `Unauthorized` | Credentials missing or not recognised. |
+| `TransportError` | The engine could not be reached, or answered with something unparseable. Never a statement about the request. |
+| `SemanticError` | Base class for all of the above. |
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest
+```
+
+`tests/test_covers_spec.py` checks this client against `api/openapi.yaml`: an
+operation added to the engine with no method here fails the suite. The client is
+hand-written rather than generated because eight endpoints do not justify a
+codegen toolchain, and that test is what pays for the choice.
+
+## Licence
+
+Apache 2.0.
+
+## How this stays in step with the engine
+
+The engine's OpenAPI contract is vendored at `spec/openapi.yaml`, pinned to an
+engine commit in `spec/PINNED_AT`.
+
+`tests/test_covers_spec.py` checks this client against it in both directions: an
+operation the engine exposes with no method here fails the build, and a method
+claiming an operation the spec does not define fails it too. A scheduled job
+compares the pin against the engine daily and opens a pull request when the
+contract moves, so a change arrives as a reviewable diff with the contract tests
+already run against it.
+
+The client is hand-written rather than generated. A generator produces a
+transport and a flat error type; the parts worth having are the ones it cannot
+produce: `Refused.should_modify()`, and `run()` submitting a job and polling it
+so no caller writes that loop.
+
+## Licence
+
+Apache 2.0, matching the engine.