mkbundle 0.2.0__tar.gz

mkbundle-0.2.0/.gitignore

@@ -0,0 +1,43 @@
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+*.egg-info/
+dist/
+build/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.coverage
+htmlcov/
+
+# Node (web/)
+node_modules/
+.next/
+.turbo/
+
+# Local config and secrets — never tracked
+.env
+.env.*
+!.env.example
+deploy/.local/
+deploy/secrets/
+# Database dumps written by the pg-backup sidecar on the host
+deploy/backups/
+*.pem
+*.key
+!**/*.pub.key
+# age identities generated for laptop bring-up
+*.age
+
+# Runtime state
+.mklang-platform/
+*.db
+*.sqlite3
+run-artifacts/
+
+# Editors / OS
+.DS_Store
+.idea/
+.vscode/

mkbundle-0.2.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 Gianluca
+
+   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.

mkbundle-0.2.0/PKG-INFO

@@ -0,0 +1,9 @@
+Metadata-Version: 2.4
+Name: mkbundle
+Version: 0.2.0
+Summary: Build, validate and sign bundles (ADR 0008)
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: <3.14,>=3.11
+Requires-Dist: mkp-contracts>=0.2.0
+Requires-Dist: pyyaml>=6.0

mkbundle-0.2.0/README.md

@@ -0,0 +1,157 @@
+# mkbundle — bundle build and validation
+
+The gate between authoring and everything downstream. A bundle that fails here never
+becomes a deployment candidate ([ADR 0008](../../docs/adr/0008-bundles-and-pull-based-deployment.md)).
+
+```
+mkbundle validate <path>...          a workflow, connector manifest, or bundle manifest
+mkbundle build <src> -o <out>        validate a source tree and archive it
+mkbundle inspect <archive>           the manifest and digest of a built bundle
+mkbundle verify <archive>            its signature, and its files against the manifest
+```
+
+`--format json` on any of them, for CI.
+
+## A bundle source tree
+
+```
+src/
+  bundle.yaml          project, pinned connector versions, requires
+  workflows/*.yaml     one workflow definition each
+  machines/*.mkl       the machines those workflows commission
+  assets/**            templates, prompts, fixtures
+```
+
+`bundle.yaml` declares **intent**: project, `lock.connectors`, `requires`, and optional
+`source` provenance. Everything the build **observes** — the file inventory, their
+digests, the mklang and spec versions actually used, the build time — is an output, and
+declaring one is an error rather than an override. A declared version can disagree with
+what actually validated the bundle; an observed one cannot.
+
+## Identity
+
+A bundle's identity is the sha256 of its canonicalized manifest. Three fields are
+outside that canonical form:
+
+| Field       | Why                                                                                     |
+| ----------- | --------------------------------------------------------------------------------------- |
+| `created`   | A build timestamp. Inside the digest, identical content would get two identities        |
+| `source`    | `bundle.schema.json` calls it informational: "identity is the content digest, not this" |
+| `signature` | Cannot be inside the bytes it signs                                                     |
+
+That is what makes promote-by-digest real: building the same tree twice gives the same
+digest, so "nothing is rebuilt between dev and production" is checkable rather than
+asserted. The signature (F4) covers exactly these canonical bytes, so there is one
+canonical form and not two.
+
+The archive is a deterministic `tar.gz` — sorted entries, zeroed mtimes and ownership,
+no filename in the gzip header — so identical content also produces identical bytes.
+
+## Rules
+
+Schema validation is the shape. These are the rules, and they are build-time because
+each is answerable from the bundle alone (`schema/README.md`):
+
+| Rule                         | What it catches                                          |
+| ---------------------------- | -------------------------------------------------------- |
+| `missing-idempotency-key`    | An `effect: write` action with no key — see below        |
+| `machine-missing`            | An mklang step pointing outside the bundle               |
+| `machine-check`              | A machine `mklang check` rejects                         |
+| `spec-mismatch`              | Machines targeting different language spec versions      |
+| `undeclared-connection`      | A connection used but not in `requires`                  |
+| `undeclared-secret`          | A secretRef used but not in `requires`                   |
+| `unknown-connector`          | A connector not pinned in `lock.connectors`              |
+| `connector-version-mismatch` | A pin that disagrees with the catalog                    |
+| `unknown-action`             | An action the connector manifest does not have           |
+| `duplicate-step-id`          | Two steps sharing an id within a workflow                |
+| `wait-declares-both`         | A `wait` with both `duration` and `until_event`          |
+| `wait-declares-nothing`      | A `wait` with neither, so nothing says what it waits for |
+| `machine-gate-unresolvable`  | A machine gating on a hook the platform cannot answer    |
+| `duplicate-workflow-name`    | Two workflows sharing a name within the bundle           |
+| `schema`                     | A document that does not match its contract              |
+
+`missing-idempotency-key` is the one that matters most. Durable execution is
+at-least-once for external effects ([ADR 0009](../../docs/adr/0009-durable-execution-engine.md)
+Amendment 1), so the idempotency key is the mechanism that makes an effect happen once.
+A write step without one is not untidy — it is a duplicate email waiting for the first
+crash, an ordinary retry, or a second runner.
+
+`machine-gate-unresolvable` is the newest and the one that reaches furthest outside this
+tool. A gate in a `.mkl` may carry `hook: <name>`, mklang resolves that name against a
+registry the host supplies, and a name it cannot resolve **halts the run when the gate is
+reached** — not at load, not at the first state, but when that gate is reached, which may be
+one model call later and only for some inputs. What a gate may name is
+[ADR 0011](../../docs/adr/0011-gates-are-data.md): a closed declarative vocabulary, defined in
+`mkp_contracts.gates` so that this tool and the runner cannot disagree. A gate cannot name a
+Python predicate, because ADR 0003 runs machines in the runner process _because_ "there is no
+customer code in a `.mkl`, only data", and a bundle carrying code for its gates would take
+that reason away.
+
+The two `wait-*` rules are newer and exist for a narrower reason (`D1`). The schema declares
+`duration`, `until_event` and `deadline` as three independent optional fields, so all four
+combinations of the first two validate — including the two nothing can execute. One sleeps
+for a fixed time and the other holds until something arrives; a step carrying both is a
+document whose author meant one of them, and a builder that picked would be deciding what a
+workflow does. The interpreter refuses the same two shapes, because a bundle built before
+these rules existed is still loadable.
+
+The rules needing **tenant** state are deploy-time and deliberately absent: budgets
+against a tenant's constraints, connections against a target environment. A builder has
+no tenant.
+
+Three rules need a connector catalog (`--connectors`, defaulting to `connectors/` when
+it holds manifests). Without one they cannot run, and the build says so on stderr rather
+than reporting a clean pass over checks it never made.
+
+## Signing
+
+```
+minisign -G -W -s build.key -p build.pub
+mkbundle build src -o out/ --sign-key build.key --public-key build.pub
+mkbundle verify out/acme-support-4529b6a34b4e.tar.gz --public-key build.pub
+```
+
+The signature covers exactly the canonical manifest bytes, and `signature` is outside
+that form — so a bundle's digest is the same before and after it is signed. Signing
+adds provenance to an identity; it does not create a new one.
+
+`signature.value` holds the whole `.minisig` file, base64-encoded, so it round-trips to
+bytes minisign verifies as-is. `signature.key_id` is minisign's key id, **not** the
+public key: a verifier looks that id up in a trust store it already holds. Taking the
+key from the artifact it authenticates would prove only that the artifact signed itself.
+
+`mkbundle verify` also re-hashes every file against the digest the manifest records. A
+signature over a manifest is worth exactly the file digests inside it.
+
+Build keys must be unencrypted (`-W`) — minisign prompts on a terminal otherwise, which
+a build does not have. Treat one as a credential: the whole point is that a runner can
+tell our bundles from anyone else's. `verify-at-load` is the runner's job (C3); this
+command exists so the tool can prove its own output rather than assert it.
+
+## Install
+
+Python 3.11 to 3.13. `mklang` and `minisign` are not Python dependencies — they must be
+on PATH, and the tool says so when they are not.
+
+```bash
+pipx install mkbundle
+mkbundle --version
+```
+
+Versions before `0.2.0` were never on an index: they are wheels on a `cli-v*` release of
+a private repository, fetched with `gh release download --repo gianlucamazza/mklang-platform`.
+
+## Development
+
+```
+uv sync
+uv run pytest
+uv run --with ruff ruff check .
+```
+
+`mklang` must be on PATH: the build shells out to `mklang check` rather than
+reimplementing it, and reads `lock.mklang` off `mklang --version`.
+
+Fixtures live in `tests/fixtures/`. The negative cases are the valid bundle with exactly
+one thing changed, built in `conftest.py`, so each test shows its own delta instead of
+hiding it in a near-duplicate directory.

mkbundle-0.2.0/pyproject.toml

@@ -0,0 +1,68 @@
+[project]
+name = "mkbundle"
+version = "0.2.0"
+description = "Build, validate and sign bundles (ADR 0008)"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11,<3.14"
+# `pyyaml` comes with `mkp-contracts` and is declared anyway: `rules.py` imports it to read
+# a machine's gates (`C21`), and a direct import that relies on somebody else's dependency
+# is one that breaks when that somebody stops needing it.
+dependencies = ["mkp-contracts>=0.2.0", "pyyaml>=6.0"]
+
+[project.scripts]
+mkbundle = "mkbundle.cli:main"
+
+[dependency-groups]
+dev = ["pytest>=8.0", "types-PyYAML"]
+
+[tool.uv.sources]
+mkp-contracts = { path = "../../packages/mkp-contracts", editable = true }
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/mkbundle"]
+
+[tool.ruff]
+line-length = 100
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "SIM", "RUF", "S"]
+
+[tool.ruff.lint.per-file-ignores]
+# Production exemptions with their reason, declared once (project rule: no inline
+# noqa). The toolchain and signing modules shell out to `mklang` and `minisign` by
+# name from PATH with fixed argv and no shell — that the version reported is the one
+# PATH serves is the point (S603, S607).
+"src/mkbundle/toolchain.py" = ["S603", "S607"]
+"src/mkbundle/signing.py" = ["S603", "S607"]
+# `S` reads production code. In a test the same rules are noise with a cost: a test that
+# asserts is doing its job (S101), a fixture's fake credential is a literal on purpose
+# (S105-S107), and a query built to set up a fixture is not a query an attacker reaches
+# (S608), and a suite that shells out to the real `minisign`, `age` or `mklang` rather
+# than skipping is this repository's rule and not an oversight (S603, S607). Ignored by
+# path rather than by line, because there would be one line per test.
+"tests/**" = ["S101", "S105", "S106", "S107", "S603", "S607", "S608"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.mypy]
+# Same settings as `mklang` and `packages/mkp-contracts` — see the note there on why
+# `warn_unused_ignores` is the one that earns its place first. Scope matches mklang too:
+# what ships. Extending it over the test suites is a separate, larger piece of work.
+files = ["src"]
+python_version = "3.11"
+check_untyped_defs = true
+disallow_incomplete_defs = true
+strict_equality = true
+no_implicit_reexport = true
+warn_redundant_casts = true
+warn_unused_ignores = true
+
+[tool.pyright]
+typeCheckingMode = "basic"
+exclude = [".venv"]

mkbundle-0.2.0/src/mkbundle/__init__.py

@@ -0,0 +1,12 @@
+"""mkbundle — build and validate the artifacts this platform deploys.
+
+Bundles are immutable, content-addressed and signed (ADR 0008). A bundle that
+fails validation never becomes a deployment candidate, so this tool is the gate
+between authoring and everything downstream.
+
+Named for what it makes rather than for the platform: `mkp` is the platform, and
+that name belongs to its roles, its settings and its services rather than to one of
+its tools.
+"""
+
+__version__ = "0.1.0"