sigrix-runtime 0.1.0__tar.gz

sigrix_runtime-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/

sigrix_runtime-0.1.0/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+All notable changes to this project are recorded here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the versioning is
+described in `VERSIONING.md`.
+
+## [Unreleased]
+
+## [0.1.0] - 2026-09-26
+
+First release as a package of its own. The same code has shipped inside every
+Sigrix bundle before this; nothing it answers has changed.
+
+### Added
+
+- `sigrix_runtime.postern`: a Postern 0.1 runner at Level 3. `describe`,
+  `status`, `run` and `stream` on loopback; the entitlement check of the
+  specification's §5 with its cache and grace period; the verified bundle
+  pull; the version check of §8.
+- `--mcp`: an MCP server's tools served as one agent, `describe` from
+  `tools/list` and each run a `tools/call`.
+- The execution layer a bundle's `main.py` and the server share, and the
+  `crewai` extra it needs to run a CrewAI crew.
+- `sigrix-runtime`, a console script for the same entry point as
+  `python -m sigrix_runtime.postern`.
+- Type information (`py.typed`), checked under `mypy --strict`.

sigrix_runtime-0.1.0/LICENSE

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

sigrix_runtime-0.1.0/NOTICE

@@ -0,0 +1,10 @@
+sigrix-runtime
+Copyright 2026 Sigrix
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+Trademarks. "Sigrix" and the Sigrix logo are trademarks of Sigrix. The Apache
+License does not grant permission to use them. The name of this repository and
+package identifies the marketplace whose bundles this runner serves; it does
+not imply endorsement of a derivative work. A fork or a derived runner must not
+present itself as Sigrix or as published by Sigrix.

sigrix_runtime-0.1.0/PKG-INFO

@@ -0,0 +1,173 @@
+Metadata-Version: 2.5
+Name: sigrix-runtime
+Version: 0.1.0
+Summary: The Postern runner inside every Sigrix bundle: serves one agent's describe, run, stream and status on loopback, checks the buyer's entitlement, and serves an MCP server's tools over the same four verbs.
+Project-URL: Homepage, https://github.com/sigrix-io/sigrix-runtime
+Project-URL: Source, https://github.com/sigrix-io/sigrix-runtime
+Project-URL: Issues, https://github.com/sigrix-io/sigrix-runtime/issues
+Project-URL: Changelog, https://github.com/sigrix-io/sigrix-runtime/blob/main/CHANGELOG.md
+Project-URL: Specification, https://github.com/sigrix-io/postern
+Author: Sigrix
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agents,crewai,entitlement,mcp,postern,runner
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Internet :: WWW/HTTP :: HTTP Servers
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Provides-Extra: crewai
+Requires-Dist: crewai-tools<2,>=1.15.20; extra == 'crewai'
+Requires-Dist: crewai<2,>=1.15.20; extra == 'crewai'
+Requires-Dist: python-dotenv<2,>=1.2.2; extra == 'crewai'
+Requires-Dist: pyyaml>=6.0; extra == 'crewai'
+Provides-Extra: dev
+Requires-Dist: mypy==2.3.1; extra == 'dev'
+Requires-Dist: postern-conformance==0.1.2; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: pyyaml>=6.0; extra == 'dev'
+Requires-Dist: ruff==0.16.8; extra == 'dev'
+Requires-Dist: types-pyyaml>=6.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# sigrix-runtime
+
+The [Postern](https://github.com/sigrix-io/postern) runner inside every bundle
+[Sigrix](https://sigrix.io) delivers. It serves one agent on your own machine
+over Postern's four verbs, checks that you are entitled to run it, and runs it
+with the keys in your own environment.
+
+This is the code that already ships in every Sigrix bundle, published here so it
+can be read, tested and depended on. A bundle carries its own copy, so running
+one needs nothing installed from here:
+
+```console
+$ cd my-bundle
+$ python -m sigrix_runtime.postern
+```
+
+then point a client at `http://127.0.0.1:8787/postern/v0/describe`. Install it
+to serve an MCP server's tools (below), or to build on it:
+
+```console
+$ pip install sigrix-runtime
+```
+
+Python 3.11 or newer. The server is standard library only.
+
+## What it serves
+
+| Verb | Route | Answers |
+|---|---|---|
+| `describe` | `GET /postern/v0/describe` | what the agent takes and returns, which credentials it needs, which tools cost money |
+| `status` | `GET /postern/v0/status` | whether it is ready, and whether you may still run it |
+| `run` | `POST /postern/v0/run` | the result |
+| `stream` | `POST /postern/v0/stream` | the run as it goes, as server-sent events |
+
+It meets [Level 3](https://github.com/sigrix-io/postern/blob/main/SPEC.md#3-conformance)
+of the specification: all four verbs, the entitlement check of §5 and the version
+check of §8. CI holds it to that with
+[`postern-conformance`](https://pypi.org/project/postern-conformance/), run against
+the runner itself rather than a stand-in.
+
+One case falls short, and is said rather than hidden. An MCP server with
+several tools is served as one agent whose `tool` input picks among them, and
+`describe` has no way to declare a tool's own inputs required only when that
+tool is chosen, so a request that satisfies `describe` can still be refused with
+`bad_request` naming the missing input. Served with one tool, which is what CI
+checks, the runner is conformant.
+
+## What it does at start
+
+    resolve the token → check the entitlement → pull the bundle → verify its digest → serve
+
+A bundle already unzipped skips the middle two steps, because there is nothing
+to fetch. The container image, `sigrix/runner`, runs this same module as its
+entrypoint, so the two cannot drift.
+
+The entitlement is checked with the distributor at start and again once the
+answer is older than the bound the distributor declared. A distributor that
+cannot be reached is not a refusal: a held answer lasts through the grace period
+the distributor declared, a restart does not start a new one, and past it the
+runner answers `unavailable`, which invites a retry. A refusal it has been given
+keeps refusing, reachable or not.
+
+## Configuration
+
+Read from the process environment first and from the bundle's `.env` second, so
+a container can export them and a buyer can fill in the `.env` their bundle came
+with. An exported value always wins.
+
+| Variable | Meaning |
+|---|---|
+| `SIGRIX_TOKEN` | a runner token for this listing |
+| `POSTERN_AGENT_ID` | which listing the bundle is, as `{seller}/{listing-id}` |
+| `POSTERN_DISTRIBUTOR` | the distributor's base URL; `https://sigrix.io` if unset |
+| `POSTERN_INBOUND_TOKEN` | when set, every request must carry it as a bearer token |
+
+The listing can also be named as the one positional argument, which beats both:
+`python -m sigrix_runtime.postern acme/my-crew`.
+
+| Option | Default |
+|---|---|
+| `--bundle PATH` | the current directory |
+| `--host HOST`, `--port PORT` | `127.0.0.1`, `8787` |
+| `--allow-origin ORIGIN` | none: a browser page may not call the runner until you allow its origin |
+| `--max-run-seconds N` | no limit (`POSTERN_MAX_RUN_SECONDS`) |
+| `--max-concurrent-runs N` | 1 (`POSTERN_MAX_CONCURRENT_RUNS`) |
+| `--no-pull` | pulling on; an empty folder is then an error rather than a download (`POSTERN_PULL=0`) |
+| `--max-bundle-bytes N` | 64 MiB (`POSTERN_MAX_BUNDLE_BYTES`) |
+| `--mcp` | serve an MCP server's tools instead of a bundle (below) |
+| `--quiet` | log warnings and errors only |
+
+Provider keys are none of the runner's business. The run reads them from the
+bundle's `.env`, the runner reads only the names above out of that file, and
+there is nowhere in the protocol for a key to travel. The runner's own settings
+are removed from the environment of everything it runs.
+
+**Exit codes**, because a container's is the only thing an operator sees when it
+does not stay up: `0` interrupted after serving; `2` not configured; `3` refused,
+by the distributor or by the checks on the bundle it served; `4` no usable
+answer, or the bundle could not be written, which is worth a retry.
+
+## Serving an MCP server's tools
+
+```console
+$ sigrix-runtime --mcp -- python my_server.py
+```
+
+`--mcp` starts an MCP server over stdio and serves its tools as one agent:
+`describe` comes from the server's `tools/list`, and a `run` is a `tools/call`,
+with the same bounds and cancellation as a crew's run. Nothing is pulled.
+
+## Running a CrewAI bundle
+
+A crew bundle runs through the execution layer, which needs CrewAI. A bundle's
+own `requirements.txt` pins the exact versions it ships with; outside one, the
+`crewai` extra installs a supported range:
+
+```console
+$ pip install "sigrix-runtime[crewai]"
+```
+
+## Layout
+
+- `sigrix_runtime.postern`: the server, the entitlement check, the verified
+  pull, the version check and the MCP mode. Standard library only.
+- `sigrix_runtime.execution`, `loader`, `workforce`, `sandbox`, `configuration`,
+  `quiet`, `runner_env`: the one run path a bundle's `main.py` and the server
+  share, and what it needs to build and run a crew.
+
+## Versioning and licence
+
+Semantic versioning, pre-1.0; `VERSIONING.md` says what may change and how a
+release is made. Licensed under Apache-2.0; `NOTICE` covers the Sigrix name and
+logo, which the licence does not grant.

sigrix_runtime-0.1.0/README.md

@@ -0,0 +1,133 @@
+# sigrix-runtime
+
+The [Postern](https://github.com/sigrix-io/postern) runner inside every bundle
+[Sigrix](https://sigrix.io) delivers. It serves one agent on your own machine
+over Postern's four verbs, checks that you are entitled to run it, and runs it
+with the keys in your own environment.
+
+This is the code that already ships in every Sigrix bundle, published here so it
+can be read, tested and depended on. A bundle carries its own copy, so running
+one needs nothing installed from here:
+
+```console
+$ cd my-bundle
+$ python -m sigrix_runtime.postern
+```
+
+then point a client at `http://127.0.0.1:8787/postern/v0/describe`. Install it
+to serve an MCP server's tools (below), or to build on it:
+
+```console
+$ pip install sigrix-runtime
+```
+
+Python 3.11 or newer. The server is standard library only.
+
+## What it serves
+
+| Verb | Route | Answers |
+|---|---|---|
+| `describe` | `GET /postern/v0/describe` | what the agent takes and returns, which credentials it needs, which tools cost money |
+| `status` | `GET /postern/v0/status` | whether it is ready, and whether you may still run it |
+| `run` | `POST /postern/v0/run` | the result |
+| `stream` | `POST /postern/v0/stream` | the run as it goes, as server-sent events |
+
+It meets [Level 3](https://github.com/sigrix-io/postern/blob/main/SPEC.md#3-conformance)
+of the specification: all four verbs, the entitlement check of §5 and the version
+check of §8. CI holds it to that with
+[`postern-conformance`](https://pypi.org/project/postern-conformance/), run against
+the runner itself rather than a stand-in.
+
+One case falls short, and is said rather than hidden. An MCP server with
+several tools is served as one agent whose `tool` input picks among them, and
+`describe` has no way to declare a tool's own inputs required only when that
+tool is chosen, so a request that satisfies `describe` can still be refused with
+`bad_request` naming the missing input. Served with one tool, which is what CI
+checks, the runner is conformant.
+
+## What it does at start
+
+    resolve the token → check the entitlement → pull the bundle → verify its digest → serve
+
+A bundle already unzipped skips the middle two steps, because there is nothing
+to fetch. The container image, `sigrix/runner`, runs this same module as its
+entrypoint, so the two cannot drift.
+
+The entitlement is checked with the distributor at start and again once the
+answer is older than the bound the distributor declared. A distributor that
+cannot be reached is not a refusal: a held answer lasts through the grace period
+the distributor declared, a restart does not start a new one, and past it the
+runner answers `unavailable`, which invites a retry. A refusal it has been given
+keeps refusing, reachable or not.
+
+## Configuration
+
+Read from the process environment first and from the bundle's `.env` second, so
+a container can export them and a buyer can fill in the `.env` their bundle came
+with. An exported value always wins.
+
+| Variable | Meaning |
+|---|---|
+| `SIGRIX_TOKEN` | a runner token for this listing |
+| `POSTERN_AGENT_ID` | which listing the bundle is, as `{seller}/{listing-id}` |
+| `POSTERN_DISTRIBUTOR` | the distributor's base URL; `https://sigrix.io` if unset |
+| `POSTERN_INBOUND_TOKEN` | when set, every request must carry it as a bearer token |
+
+The listing can also be named as the one positional argument, which beats both:
+`python -m sigrix_runtime.postern acme/my-crew`.
+
+| Option | Default |
+|---|---|
+| `--bundle PATH` | the current directory |
+| `--host HOST`, `--port PORT` | `127.0.0.1`, `8787` |
+| `--allow-origin ORIGIN` | none: a browser page may not call the runner until you allow its origin |
+| `--max-run-seconds N` | no limit (`POSTERN_MAX_RUN_SECONDS`) |
+| `--max-concurrent-runs N` | 1 (`POSTERN_MAX_CONCURRENT_RUNS`) |
+| `--no-pull` | pulling on; an empty folder is then an error rather than a download (`POSTERN_PULL=0`) |
+| `--max-bundle-bytes N` | 64 MiB (`POSTERN_MAX_BUNDLE_BYTES`) |
+| `--mcp` | serve an MCP server's tools instead of a bundle (below) |
+| `--quiet` | log warnings and errors only |
+
+Provider keys are none of the runner's business. The run reads them from the
+bundle's `.env`, the runner reads only the names above out of that file, and
+there is nowhere in the protocol for a key to travel. The runner's own settings
+are removed from the environment of everything it runs.
+
+**Exit codes**, because a container's is the only thing an operator sees when it
+does not stay up: `0` interrupted after serving; `2` not configured; `3` refused,
+by the distributor or by the checks on the bundle it served; `4` no usable
+answer, or the bundle could not be written, which is worth a retry.
+
+## Serving an MCP server's tools
+
+```console
+$ sigrix-runtime --mcp -- python my_server.py
+```
+
+`--mcp` starts an MCP server over stdio and serves its tools as one agent:
+`describe` comes from the server's `tools/list`, and a `run` is a `tools/call`,
+with the same bounds and cancellation as a crew's run. Nothing is pulled.
+
+## Running a CrewAI bundle
+
+A crew bundle runs through the execution layer, which needs CrewAI. A bundle's
+own `requirements.txt` pins the exact versions it ships with; outside one, the
+`crewai` extra installs a supported range:
+
+```console
+$ pip install "sigrix-runtime[crewai]"
+```
+
+## Layout
+
+- `sigrix_runtime.postern`: the server, the entitlement check, the verified
+  pull, the version check and the MCP mode. Standard library only.
+- `sigrix_runtime.execution`, `loader`, `workforce`, `sandbox`, `configuration`,
+  `quiet`, `runner_env`: the one run path a bundle's `main.py` and the server
+  share, and what it needs to build and run a crew.
+
+## Versioning and licence
+
+Semantic versioning, pre-1.0; `VERSIONING.md` says what may change and how a
+release is made. Licensed under Apache-2.0; `NOTICE` covers the Sigrix name and
+logo, which the licence does not grant.