munarium-matrix 1.0.0__tar.gz

munarium_matrix-1.0.0/.gitignore

@@ -0,0 +1,164 @@
+# Munarium — what this repository does not track.
+#
+# One section per component, because the reasons are specific and worth keeping.
+
+# ---------------------------------------------------------------- shared ---
+.DS_Store
+Thumbs.db
+*.swp
+*~
+.idea/
+.vscode/
+
+# Local agent guidance. Keep the two root copies identical and untracked.
+/AGENTS.md
+/CLAUDE.md
+
+# Build output and tool residue wherever a toolchain leaves it. None of these
+# names is a source directory in this tree (Rust `src/bin/` is not matched).
+**/target/
+**/__pycache__/
+**/*.py[cod]
+**/.venv/
+**/venv/
+**/*.egg-info/
+**/.pytest_cache/
+**/.mypy_cache/
+**/.ruff_cache/
+**/node_modules/
+**/.gradle/
+clients/*/build/
+clients/*/bin/
+clients/*/obj/
+clients/*/src/*/bin/
+clients/*/src/*/obj/
+clients/*/tests/*/bin/
+clients/*/tests/*/obj/
+
+
+# ----------------------------------------------------------- server/ ---
+server/target/
+server/.env
+server/*.local.toml
+server/deploy/terraform/**/.terraform/
+server/deploy/terraform/**/*.tfstate*
+server/deploy/terraform/**/*.tfplan
+# `*.tfplan` does NOT match an extensionless `terraform plan -out=tfplan`, and
+# a suffixed name (`tfplan.datastore`) matches neither. A plan file embeds the
+# FULL tfstate, generated passwords included, so every spelling is covered.
+server/deploy/terraform/**/tfplan*
+server/deploy/terraform/**/.terraform.lock.hcl
+server/deploy/terraform/**/*.tfvars
+!server/deploy/terraform/**/example.tfvars
+
+# Python residue from the tree's own stdlib tools — check_license.py,
+# tools/third_party_notices.py, contract/mmp/publish.py, docs/route-index.py.
+server/__pycache__/
+server/*.py[cod]
+server/.venv/
+server/venv/
+
+# Local run artifacts: a database dump, a saved SBOM, a captured gate log. The
+# notices file itself is COMMITTED; this is the scratch beside it.
+server/*.sbom.json
+server/*.cdx.json
+server/scratch/
+
+# Editors and operating systems. Committed editor settings would impose one
+# person's toolchain on every contributor; per-clone settings are theirs.
+server/.vscode/
+server/.idea/
+server/*.swp
+server/.DS_Store
+server/Thumbs.db
+
+# ----------------------------------------------------------- matrix/ ---
+matrix/target/
+matrix/*.tfstate
+matrix/*.tfstate.*
+matrix/.terraform/
+matrix/tfplan
+matrix/.mxtest-current.json
+# Conformance results files are committed (they are small and are the
+# evidence), never gitignored. Run transcripts under artifacts/ are not.
+matrix/artifacts/
+
+# Python residue from the tree's own stdlib tools — check_license.py,
+# scripts/third_party_notices.py, scripts/boundaries.py, scripts/doclint.py,
+# contract/publish.py.
+matrix/__pycache__/
+matrix/*.py[cod]
+matrix/.venv/
+matrix/venv/
+
+# Local run artifacts: a saved SBOM, a captured gate log. THIRD_PARTY_NOTICES.md
+# itself is COMMITTED; this is the scratch beside it.
+matrix/*.sbom.json
+matrix/*.cdx.json
+matrix/scratch/
+
+# Editors and operating systems. Committed editor settings would impose one
+# person's toolchain on every contributor; per-clone settings are theirs.
+matrix/.vscode/
+matrix/.idea/
+matrix/*.swp
+matrix/.DS_Store
+matrix/Thumbs.db
+
+# ----------------------------------------------------------- clients/ ---
+# The Munarium client libraries: several language trees, so the rules are the
+# union of what those toolchains leave behind.
+#
+# Each language directory keeps its own .gitignore for what only it produces
+# (dotnet/, java/, python/); this file is the cross-cutting set.
+
+# Rust: cargo build output. Cargo.lock IS committed — the conformance runner is
+# an application and its resolved set is part of what CI proves.
+clients/target/
+
+# Python: virtual environments, caches, build output. The generated protobuf
+# stubs under python/src/munarium_client/_proto/ are COMMITTED and drift-checked.
+clients/__pycache__/
+clients/*.py[cod]
+clients/.venv/
+clients/venv/
+clients/*.egg-info/
+clients/dist/
+clients/build/
+clients/.mypy_cache/
+clients/.ruff_cache/
+clients/.pytest_cache/
+
+# .NET and Java build output (also covered by dotnet/.gitignore and
+# java/.gitignore; kept here so a build from the repository root is clean).
+clients/bin/
+clients/obj/
+clients/*.user
+clients/.gradle/
+
+# Local run artifacts: a saved SBOM, a packed wheel or nupkg under test.
+# THIRD_PARTY_NOTICES.md itself is COMMITTED.
+clients/*.sbom.json
+clients/*.cdx.json
+clients/*.nupkg
+clients/*.whl
+clients/scratch/
+
+# Editors and operating systems. Committed editor settings would impose one
+# maintainer's toolchain on every contributor.
+clients/.vscode/
+clients/.idea/
+clients/*.swp
+clients/.DS_Store
+clients/Thumbs.db
+
+# The release-time copy of server/proto that cargo package needs inside the
+# crate; the normative protos stay at server/proto and this must never land.
+server/src/munarium-proto/proto/
+
+# ------------------------------------------------------------- docs/ ---
+# The lab example's local secrets and the files a run writes beside them.
+docs/lab/example/.env
+docs/lab/example/ingest-manifest.json
+docs/lab/example/results*.json
+docs/lab/example/ledger-results.json

munarium_matrix-1.0.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.

munarium_matrix-1.0.0/NOTICE

@@ -0,0 +1,15 @@
+Munarium client libraries
+Copyright (c) 2026 Ioka LLC
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+these files except in compliance with the License. A copy of the License is in
+the LICENSE file beside this notice.
+
+"Munarium" and "Ioka" are trademarks of Ioka LLC. The License grants no right
+to use them beyond what is needed to describe the origin of these files.
+
+These libraries speak to Munarium Server, a separate work licensed under its
+own terms; nothing here grants any right to it, to Munarium Matrix, or to any
+support from Ioka LLC.
+
+The MMP contract bundle under contract/ carries its own NOTICE.

munarium_matrix-1.0.0/PKG-INFO

@@ -0,0 +1,157 @@
+Metadata-Version: 2.5
+Name: munarium-matrix
+Version: 1.0.0
+Summary: Python client for Munarium Matrix, the structured-evidence plane
+Project-URL: Homepage, https://github.com/iokaio/munarium
+Project-URL: Repository, https://github.com/iokaio/munarium
+Project-URL: Changelog, https://github.com/iokaio/munarium/blob/main/clients/CHANGELOG.md
+Author: Ioka
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# munarium-matrix (Python)
+
+The Python client for **Munarium Matrix**, the structured-evidence plane. It
+speaks Matrix's REST API and it is deliberately small: Matrix's whole surface
+is *registering assets, running the three modes, and reading what happened*.
+
+Install from the repository root with Python 3.10+:
+
+```console
+python -m pip install ./clients/matrix-python
+```
+
+The source version is 1.0.0; a PyPI release was not available at the
+[publication check](../README.md#installation-and-publication).
+
+One runtime dependency, `httpx` — the same choice the server's Python client
+made, for the same reasons: one library for sync and async, a timeout that is
+not optional, and no transitive surprise.
+
+## Use
+
+```python
+from munarium_matrix import MatrixClient
+
+with MatrixClient("https://matrix.example", token="...", uid="ops@example.com") as mx:
+    print(mx.version().lockstep_ok)  # does Matrix agree with its server?
+
+    mx.apply(open("datasource.crm.yaml").read())
+    mx.apply(open("contract.pipeline.yaml").read())
+
+    outcome = mx.verify("open-pipeline-by-region")
+    if outcome.failed:
+        for q in outcome.questions:
+            if not q.ok:
+                print(q.question, q.failures)
+        raise SystemExit(3)  # the exit discipline `mxctl` uses
+```
+
+Async is the same surface:
+
+```python
+from munarium_matrix import AsyncMatrixClient
+
+async with AsyncMatrixClient("https://matrix.example", token="...") as mx:
+    await mx.sync("crm")
+```
+
+### Refusals are typed
+
+Matrix answers a refusal as RFC 9457 problem+json carrying a `refusal` object
+with the **class** and the **code** — the closed vocabulary the whole system
+rests on. They arrive as attributes, not prose:
+
+```python
+from munarium_matrix import MatrixError
+
+try:
+    mx.verify("open-pipeline-by-region")
+except MatrixError as e:
+    if e.retryable:  # unavailable | exhausted
+        wait = e.retry_after  # seconds, when the service said
+    elif e.code == "not_covered":  # the collection cannot answer it
+        ...
+```
+
+`retryable` is a property and not a guess: `unavailable` and `exhausted` are
+states of the world, and every other class is a statement about the request or
+the assets, where repeating it changes nothing. Retrying a `denied` is
+hammering a door that is locked on purpose.
+
+### Lockstep
+
+`version().lockstep_ok` is true only when the server reports `exact`. That is
+the one state in which an evidence id minted by this Matrix is certain to
+resolve on that server — which is what a citation like
+`[evidence/<id>#r0003]` depends on.
+
+## What this client deliberately does NOT do
+
+Three absences, each of them a design decision rather than a missing feature:
+
+* **No sealing.** A manifest is a statement about work the *sealer* did. An SDK
+  offering `seal_evidence` would invite an application to assert provenance it
+  cannot vouch for. Sealing is Matrix's own act; evidence is *read* through the
+  **server's** client, resolving `[evidence/<id>#<row>]`.
+* **No local validation.** `validate()` posts the YAML and returns Matrix's own
+  findings. A client carrying its own copy of the rules would drift from the
+  service that enforces them, and the drift would surface as an asset that
+  validates here and is refused there.
+* **No SQL.** Nothing on this surface takes a statement. Queries are
+  pre-declared contracts and views, executed by name.
+
+There is also no gRPC transport here. Matrix's gRPC plane serves `Execute`
+alone, and `Execute` is service-to-service — the munarium-server calls it, not
+an application. When that changes, this package grows a transport rather than a
+second client.
+
+## Surface
+
+| Area | Methods |
+| --- | --- |
+| meta | `version`, `healthz`, `healthdata` |
+| registry | `apply`, `validate`, `list_assets`, `get_yaml` |
+| sources | `introspect`, `probe`, `sync` |
+| contracts and views | `verify`, `verify_view` |
+| reconcile | `reconcile`, `promotion_status`, `gate_history`, `promote`, `demote`, `rollback` |
+| audit | `journal` |
+
+`verify_view` takes either a metric view or a native data view and tries the
+metric-view route first — the caller names the view, not the route it happens
+to live on. The fallback fires on a 404 **or** a `not_covered` 422, because a
+missing metric view loads through the runtime and comes back as the latter; a
+different 422, such as `metric_view_changed`, is a real answer about a view
+that exists and is not retried as something else.
+
+`validate` returns the service's own `valid` flag beside its findings, and not
+`not findings`: three codes are advisory, so a valid asset can carry them.
+
+`sync` and `reconcile` return a `JobAccepted`: Matrix queues them, so the call
+returns an id rather than an outcome. Poll `journal()` or the run route for the
+terminal state.
+
+## Versioning
+
+This package targets Matrix `1.0.0`. A version bump on the wire surface bumps
+them together.
+
+## Tests
+
+```bash
+pip install -e ".[dev]"
+pytest
+```
+
+The offline tier drives a stub transport and asserts the response *shapes* this
+client claims to understand, which is what catches a field rename. Setting
+`MUNARIUM_MATRIX_TEST_URL` adds a live round-trip against a real Matrix; with
+it unset that test **says it skipped**, because a skip that prints nothing is
+indistinguishable from a pass.

munarium_matrix-1.0.0/README.md

@@ -0,0 +1,139 @@
+# munarium-matrix (Python)
+
+The Python client for **Munarium Matrix**, the structured-evidence plane. It
+speaks Matrix's REST API and it is deliberately small: Matrix's whole surface
+is *registering assets, running the three modes, and reading what happened*.
+
+Install from the repository root with Python 3.10+:
+
+```console
+python -m pip install ./clients/matrix-python
+```
+
+The source version is 1.0.0; a PyPI release was not available at the
+[publication check](../README.md#installation-and-publication).
+
+One runtime dependency, `httpx` — the same choice the server's Python client
+made, for the same reasons: one library for sync and async, a timeout that is
+not optional, and no transitive surprise.
+
+## Use
+
+```python
+from munarium_matrix import MatrixClient
+
+with MatrixClient("https://matrix.example", token="...", uid="ops@example.com") as mx:
+    print(mx.version().lockstep_ok)  # does Matrix agree with its server?
+
+    mx.apply(open("datasource.crm.yaml").read())
+    mx.apply(open("contract.pipeline.yaml").read())
+
+    outcome = mx.verify("open-pipeline-by-region")
+    if outcome.failed:
+        for q in outcome.questions:
+            if not q.ok:
+                print(q.question, q.failures)
+        raise SystemExit(3)  # the exit discipline `mxctl` uses
+```
+
+Async is the same surface:
+
+```python
+from munarium_matrix import AsyncMatrixClient
+
+async with AsyncMatrixClient("https://matrix.example", token="...") as mx:
+    await mx.sync("crm")
+```
+
+### Refusals are typed
+
+Matrix answers a refusal as RFC 9457 problem+json carrying a `refusal` object
+with the **class** and the **code** — the closed vocabulary the whole system
+rests on. They arrive as attributes, not prose:
+
+```python
+from munarium_matrix import MatrixError
+
+try:
+    mx.verify("open-pipeline-by-region")
+except MatrixError as e:
+    if e.retryable:  # unavailable | exhausted
+        wait = e.retry_after  # seconds, when the service said
+    elif e.code == "not_covered":  # the collection cannot answer it
+        ...
+```
+
+`retryable` is a property and not a guess: `unavailable` and `exhausted` are
+states of the world, and every other class is a statement about the request or
+the assets, where repeating it changes nothing. Retrying a `denied` is
+hammering a door that is locked on purpose.
+
+### Lockstep
+
+`version().lockstep_ok` is true only when the server reports `exact`. That is
+the one state in which an evidence id minted by this Matrix is certain to
+resolve on that server — which is what a citation like
+`[evidence/<id>#r0003]` depends on.
+
+## What this client deliberately does NOT do
+
+Three absences, each of them a design decision rather than a missing feature:
+
+* **No sealing.** A manifest is a statement about work the *sealer* did. An SDK
+  offering `seal_evidence` would invite an application to assert provenance it
+  cannot vouch for. Sealing is Matrix's own act; evidence is *read* through the
+  **server's** client, resolving `[evidence/<id>#<row>]`.
+* **No local validation.** `validate()` posts the YAML and returns Matrix's own
+  findings. A client carrying its own copy of the rules would drift from the
+  service that enforces them, and the drift would surface as an asset that
+  validates here and is refused there.
+* **No SQL.** Nothing on this surface takes a statement. Queries are
+  pre-declared contracts and views, executed by name.
+
+There is also no gRPC transport here. Matrix's gRPC plane serves `Execute`
+alone, and `Execute` is service-to-service — the munarium-server calls it, not
+an application. When that changes, this package grows a transport rather than a
+second client.
+
+## Surface
+
+| Area | Methods |
+| --- | --- |
+| meta | `version`, `healthz`, `healthdata` |
+| registry | `apply`, `validate`, `list_assets`, `get_yaml` |
+| sources | `introspect`, `probe`, `sync` |
+| contracts and views | `verify`, `verify_view` |
+| reconcile | `reconcile`, `promotion_status`, `gate_history`, `promote`, `demote`, `rollback` |
+| audit | `journal` |
+
+`verify_view` takes either a metric view or a native data view and tries the
+metric-view route first — the caller names the view, not the route it happens
+to live on. The fallback fires on a 404 **or** a `not_covered` 422, because a
+missing metric view loads through the runtime and comes back as the latter; a
+different 422, such as `metric_view_changed`, is a real answer about a view
+that exists and is not retried as something else.
+
+`validate` returns the service's own `valid` flag beside its findings, and not
+`not findings`: three codes are advisory, so a valid asset can carry them.
+
+`sync` and `reconcile` return a `JobAccepted`: Matrix queues them, so the call
+returns an id rather than an outcome. Poll `journal()` or the run route for the
+terminal state.
+
+## Versioning
+
+This package targets Matrix `1.0.0`. A version bump on the wire surface bumps
+them together.
+
+## Tests
+
+```bash
+pip install -e ".[dev]"
+pytest
+```
+
+The offline tier drives a stub transport and asserts the response *shapes* this
+client claims to understand, which is what catches a field rename. Setting
+`MUNARIUM_MATRIX_TEST_URL` adds a live round-trip against a real Matrix; with
+it unset that test **says it skipped**, because a skip that prints nothing is
+indistinguishable from a pass.