matrixscroll 0.6.4__tar.gz → 0.7.0__tar.gz

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/.gitignore

@@ -18,6 +18,7 @@ htmlcov/
 .tox/
 .mypy_cache/
 .ruff_cache/
+onboarding-smoke-summary*.json
 
 # Virtual envs
 .venv/

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/CHANGELOG.md

@@ -6,6 +6,59 @@ this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [0.7.0] - 2026-08-11
+
+Fail-closed verification, package completeness, and public positioning. No
+wire-format change.
+
+### Added
+- Range verification results now report agent-scope details and the formal model
+  includes the default-path invariant `Inv_EmptyRangeFailsClosed`.
+- Added `schemas/ssx360.evidence-pack.v1.json` for the document written by the
+  evidence-pack exporter.
+- Added a hardware-signed SE050 acceptance vector with CLI and CI verification.
+- You can explicitly set the composite action's `allow-empty-range` input. It
+  remains disabled by default and cannot satisfy a signature-mode requirement.
+
+### Changed
+- Empty commit ranges now return `ok: false` by default. CLI and Python callers
+  that intentionally accept an empty range must opt in explicitly. MCP callers
+  use the same explicit opt-in and fail closed by default.
+- Documentation now describes the shipped 14-tool MCP server and completed USB
+  signer directly, without retired pricing tiers or level-based product gates.
+- Development, documentation, and GitHub Action dependencies were refreshed.
+- Public package metadata now describes signed machine-action records instead
+  of leading with AI terminology. Exact schema terms such as `actor_type: agent`
+  remain unchanged.
+
+### Fixed
+- **The verify action could hand a caller a blank `ok` when the verifier
+  crashed.** It now writes all eight outputs on every path, masks captured
+  verifier output in the job summary, and distinguishes tool failures from
+  legitimate verification failures. Parser and action-step tests cover crashes,
+  silent output, malformed JSON, and signature failures.
+- Unhandled CLI exceptions now return structured JSON with exit status 1 instead
+  of leaking a traceback into automation output.
+- Evidence-pack annotations no longer mutate signed hosted response bodies.
+- JSON schemas now ship in wheels and MCP schema resources resolve the installed
+  copies.
+- The MCP extra now requires the verified 1.28+ SDK line; earlier 1.x releases
+  cannot register the server's annotated tools, and MCP 2.0 removed the
+  `mcp.server.fastmcp` API entirely.
+- You receive an explicit rejection when a hosted MCP Git range is empty, before
+  any API call. Non-empty ranges send the resolved commit SHAs.
+- Hosted CLI checks now write `--summary-output` on successful and empty-range
+  responses, matching local checks.
+- Local evidence-pack documents without a `bundle` now fail schema validation,
+  and CI verifies all eight schemas from an isolated wheel installation.
+
+### Removed
+- **Breaking:** removed `matrixscroll claim`, `matrixscroll identity`, the
+  `--identity` verification flag, and their private paid-enrollment client. The
+  retired service no longer issues identity certificates; device identity
+  remains the local Ed25519 key pair reported by `matrixscroll status`.
+- Removed the retired platform-pricing and signup guide.
+
 ## [0.6.4] - 2026-08-11
 
 Documentation and release metadata. No wire-format change.
@@ -334,6 +387,7 @@ Initial public release. Extracted from the SSX360 reference implementation.
 - Device id format: `MS-XXXX-XXXX` (SHA-256 of the raw public key, first 8 hex
   chars, uppercase).
 
+[0.7.0]: https://github.com/SSX360/matrixscroll/releases/tag/v0.7.0
 [0.6.4]: https://github.com/SSX360/matrixscroll/releases/tag/v0.6.4
 [0.6.3]: https://github.com/SSX360/matrixscroll/releases/tag/v0.6.3
 [0.6.2]: https://github.com/SSX360/matrixscroll/releases/tag/v0.6.2
@@ -341,6 +395,12 @@ Initial public release. Extracted from the SSX360 reference implementation.
 [0.6.0]: https://github.com/SSX360/matrixscroll/releases/tag/v0.6.0
 [0.5.1]: https://github.com/SSX360/matrixscroll/releases/tag/v0.5.1
 [0.5.0]: https://github.com/SSX360/matrixscroll/releases/tag/v0.5.0
+[0.4.2]: https://github.com/SSX360/matrixscroll/releases/tag/v0.4.2
+[0.4.1]: https://github.com/SSX360/matrixscroll/releases/tag/v0.4.1
+[0.3.0]: https://github.com/SSX360/matrixscroll/releases/tag/v0.3.0
+[0.2.6]: https://github.com/SSX360/matrixscroll/releases/tag/v0.2.6
+[0.2.5]: https://github.com/SSX360/matrixscroll/releases/tag/v0.2.5
+[0.2.4]: https://github.com/SSX360/matrixscroll/releases/tag/v0.2.4
 [0.2.2]: https://github.com/SSX360/matrixscroll/releases/tag/v0.2.2
 [0.2.1]: https://github.com/SSX360/matrixscroll/releases/tag/v0.2.1
 [0.2.0]: https://github.com/SSX360/matrixscroll/releases/tag/v0.2.0

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.5
 Name: matrixscroll
-Version: 0.6.4
-Summary: MCP server for signed AI-agent provenance with offline tool-surface checks and SSX360 USB signer support.
+Version: 0.7.0
+Summary: MCP server for signed machine-action records, offline tool-surface checks, and SSX360 USB signer support.
 Project-URL: Homepage, https://matrixscroll.com
 Project-URL: Documentation, https://matrixscroll.com/docs/
 Project-URL: Specification, https://matrixscroll.com/spec/
@@ -21,7 +21,7 @@ Project-URL: Maintainer, https://ssx360.com/about
 Author-email: SSX360 <security@matrixscroll.com>
 License-Expression: Apache-2.0
 License-File: LICENSE
-Keywords: ai,ed25519,fips-204,fips-205,matrixscroll,ml-dsa,post-quantum,provenance,root-of-trust,secure-element,signing,slh-dsa,ssx360,supply-chain
+Keywords: authorization,ed25519,fips-204,fips-205,machine-action,matrixscroll,ml-dsa,post-quantum,provenance,root-of-trust,secure-element,signing,slh-dsa,ssx360,supply-chain
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: Information Technology
@@ -39,32 +39,34 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Requires-Dist: cryptography>=43.0
 Provides-Extra: dev
-Requires-Dist: build>=1.0; extra == 'dev'
-Requires-Dist: hypothesis>=6.100; extra == 'dev'
-Requires-Dist: pytest-cov>=4.1; extra == 'dev'
-Requires-Dist: pytest>=7.4; extra == 'dev'
+Requires-Dist: build>=1.5.0; extra == 'dev'
+Requires-Dist: hypothesis>=6.165.2; extra == 'dev'
+Requires-Dist: jsonschema>=4.23.0; extra == 'dev'
+Requires-Dist: pytest-cov>=7.1.0; extra == 'dev'
+Requires-Dist: pytest>=9.1.1; extra == 'dev'
+Requires-Dist: pyyaml>=6.0.3; extra == 'dev'
 Provides-Extra: git
 Provides-Extra: hardware
 Requires-Dist: pyserial>=3.5; extra == 'hardware'
 Provides-Extra: mcp
-Requires-Dist: mcp<2.0.0,>=1.0.0; extra == 'mcp'
+Requires-Dist: mcp<2.0.0,>=1.28.0; extra == 'mcp'
 Provides-Extra: pqc
-Requires-Dist: liboqs-python>=0.12.0; extra == 'pqc'
+Requires-Dist: liboqs-python>=0.16.0; extra == 'pqc'
 Provides-Extra: tpm
 Provides-Extra: yubikey
-Requires-Dist: python-pkcs11>=0.7; extra == 'yubikey'
+Requires-Dist: python-pkcs11>=0.9.5; extra == 'yubikey'
 Description-Content-Type: text/markdown
 
 # Matrix Scroll
 
-Model Context Protocol server for signed agent provenance and offline MCP tool-surface verification.
+Model Context Protocol server for signed machine-action records and offline tool-surface verification.
 
 [![ci-unit](https://github.com/SSX360/matrixscroll/actions/workflows/ci-unit.yml/badge.svg)](https://github.com/SSX360/matrixscroll/actions/workflows/ci-unit.yml)
 [![PyPI](https://img.shields.io/pypi/v/matrixscroll)](https://pypi.org/project/matrixscroll/)
 [![Python](https://img.shields.io/pypi/pyversions/matrixscroll)](https://pypi.org/project/matrixscroll/)
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue)](https://github.com/SSX360/matrixscroll/blob/main/LICENSE)
 
-An MCP server can change its tool descriptions or input schemas after you install it. A Git commit can also name an agent without carrying proof of what signed the record. Matrix Scroll addresses both gaps with Ed25519-signed evidence that you can verify offline.
+An MCP server can change its tool descriptions or input schemas after installation. A Git commit can also declare an actor or tool without carrying a signed authorization record. Matrix Scroll addresses both gaps with Ed25519-signed evidence that reviewers can verify offline.
 
 The `matrixscroll-mcp` stdio server exposes 14 tools for commit envelopes, action records, pull-request checks, Git notes, MCP surface manifests, agent traces, and the SSX360 USB signer. Local signing and verification need no cloud account.
 
@@ -88,7 +90,7 @@ Matrix Scroll is an open protocol. The Python SDK is Apache-2.0 software, and th
 Install the current release from PyPI:
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.4"
+pip install "matrixscroll[mcp]==0.7.0"
 ```
 
 Register the stdio server in your MCP client:
@@ -116,7 +118,7 @@ After your client connects, call `status`. The server reports the local identity
 
 ## MCP tools
 
-The `0.6.4` server exposes these tools:
+The `0.7.0` server exposes these tools:
 
 | Tool | What it does | Network or write behavior |
 | --- | --- | --- |
@@ -142,7 +144,7 @@ An API key is optional. Local signing, offline verification, MCP manifest checks
 Matrix Scroll records an MCP server's tool names, descriptions, and input schemas in a signed manifest. Re-scan the server after an update and compare it with the install-time baseline.
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.4"
+pip install "matrixscroll[mcp]==0.7.0"
 
 matrixscroll mcp scan \
   --connect stdio \
@@ -179,7 +181,7 @@ matrixscroll mcp scan --tools tools.json --output manifest.json --pretty
 Install the hardware and MCP extras:
 
 ```bash
-pip install "matrixscroll[mcp,hardware]==0.6.4"
+pip install "matrixscroll[mcp,hardware]==0.7.0"
 ```
 
 Set the hardware provider and USB CDC port before starting the MCP server.
@@ -243,7 +245,7 @@ The host receives the public key and signature. The private key stays inside the
 The Python package includes a CLI and Git hooks for workflows that do not use MCP.
 
 ```bash
-pip install "matrixscroll==0.6.4"
+pip install "matrixscroll==0.7.0"
 matrixscroll hook-install
 
 export MATRIXSCROLL_ACTOR_TYPE=agent
@@ -266,7 +268,7 @@ matrixscroll verify release.signed.json
 
 <!-- vale ai-tells.ShipOveruse = NO -->
 
-- Shipping now: PyPI `matrixscroll==0.6.4` installs the 14-tool stdio MCP server and Git hooks. The release also includes the MCP Trust Scanner, offline verification, and USB CDC integration for the SSX360 signer.
+- Shipping now: PyPI `matrixscroll==0.7.0` installs the 14-tool stdio MCP server and Git hooks. The release also includes the MCP Trust Scanner, offline verification, and USB CDC integration for the SSX360 signer.
 - Hardware availability: SSX360 produces the USB signer and supplies it after a direct inquiry. PyPI distributes the host software only.
 - Hosted tools: `list_envelopes` and the hosted modes of `verify_pr_range` and `audit_export` require `SSX360_API_KEY` and a deployed SSX360 API. Local alternatives remain available without a key.
 - Post-quantum overlay: the optional `matrixscroll[pqc]` extra provides ML-DSA and SLH-DSA through liboqs. This module has no CMVP validation. liboqs states that applications should not rely on it to protect sensitive data in production.
@@ -279,11 +281,11 @@ matrixscroll verify release.signed.json
 
 GitHub Actions publishes each Matrix Scroll release through PyPI Trusted Publishing. PyPI records a PEP 740 attestation for the wheel and source distribution.
 
-Ask PyPI for the `0.6.4` wheel provenance:
+Ask PyPI for the `0.7.0` wheel provenance:
 
 ```bash
 curl -H "Accept: application/vnd.pypi.integrity.v1+json" \
-  https://pypi.org/integrity/matrixscroll/0.6.4/matrixscroll-0.6.4-py3-none-any.whl/provenance
+  https://pypi.org/integrity/matrixscroll/0.7.0/matrixscroll-0.7.0-py3-none-any.whl/provenance
 ```
 
 The response names the GitHub publisher:

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/README.md

@@ -1,13 +1,13 @@
 # Matrix Scroll
 
-Model Context Protocol server for signed agent provenance and offline MCP tool-surface verification.
+Model Context Protocol server for signed machine-action records and offline tool-surface verification.
 
 [![ci-unit](https://github.com/SSX360/matrixscroll/actions/workflows/ci-unit.yml/badge.svg)](https://github.com/SSX360/matrixscroll/actions/workflows/ci-unit.yml)
 [![PyPI](https://img.shields.io/pypi/v/matrixscroll)](https://pypi.org/project/matrixscroll/)
 [![Python](https://img.shields.io/pypi/pyversions/matrixscroll)](https://pypi.org/project/matrixscroll/)
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue)](https://github.com/SSX360/matrixscroll/blob/main/LICENSE)
 
-An MCP server can change its tool descriptions or input schemas after you install it. A Git commit can also name an agent without carrying proof of what signed the record. Matrix Scroll addresses both gaps with Ed25519-signed evidence that you can verify offline.
+An MCP server can change its tool descriptions or input schemas after installation. A Git commit can also declare an actor or tool without carrying a signed authorization record. Matrix Scroll addresses both gaps with Ed25519-signed evidence that reviewers can verify offline.
 
 The `matrixscroll-mcp` stdio server exposes 14 tools for commit envelopes, action records, pull-request checks, Git notes, MCP surface manifests, agent traces, and the SSX360 USB signer. Local signing and verification need no cloud account.
 
@@ -31,7 +31,7 @@ Matrix Scroll is an open protocol. The Python SDK is Apache-2.0 software, and th
 Install the current release from PyPI:
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.4"
+pip install "matrixscroll[mcp]==0.7.0"
 ```
 
 Register the stdio server in your MCP client:
@@ -59,7 +59,7 @@ After your client connects, call `status`. The server reports the local identity
 
 ## MCP tools
 
-The `0.6.4` server exposes these tools:
+The `0.7.0` server exposes these tools:
 
 | Tool | What it does | Network or write behavior |
 | --- | --- | --- |
@@ -85,7 +85,7 @@ An API key is optional. Local signing, offline verification, MCP manifest checks
 Matrix Scroll records an MCP server's tool names, descriptions, and input schemas in a signed manifest. Re-scan the server after an update and compare it with the install-time baseline.
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.4"
+pip install "matrixscroll[mcp]==0.7.0"
 
 matrixscroll mcp scan \
   --connect stdio \
@@ -122,7 +122,7 @@ matrixscroll mcp scan --tools tools.json --output manifest.json --pretty
 Install the hardware and MCP extras:
 
 ```bash
-pip install "matrixscroll[mcp,hardware]==0.6.4"
+pip install "matrixscroll[mcp,hardware]==0.7.0"
 ```
 
 Set the hardware provider and USB CDC port before starting the MCP server.
@@ -186,7 +186,7 @@ The host receives the public key and signature. The private key stays inside the
 The Python package includes a CLI and Git hooks for workflows that do not use MCP.
 
 ```bash
-pip install "matrixscroll==0.6.4"
+pip install "matrixscroll==0.7.0"
 matrixscroll hook-install
 
 export MATRIXSCROLL_ACTOR_TYPE=agent
@@ -209,7 +209,7 @@ matrixscroll verify release.signed.json
 
 <!-- vale ai-tells.ShipOveruse = NO -->
 
-- Shipping now: PyPI `matrixscroll==0.6.4` installs the 14-tool stdio MCP server and Git hooks. The release also includes the MCP Trust Scanner, offline verification, and USB CDC integration for the SSX360 signer.
+- Shipping now: PyPI `matrixscroll==0.7.0` installs the 14-tool stdio MCP server and Git hooks. The release also includes the MCP Trust Scanner, offline verification, and USB CDC integration for the SSX360 signer.
 - Hardware availability: SSX360 produces the USB signer and supplies it after a direct inquiry. PyPI distributes the host software only.
 - Hosted tools: `list_envelopes` and the hosted modes of `verify_pr_range` and `audit_export` require `SSX360_API_KEY` and a deployed SSX360 API. Local alternatives remain available without a key.
 - Post-quantum overlay: the optional `matrixscroll[pqc]` extra provides ML-DSA and SLH-DSA through liboqs. This module has no CMVP validation. liboqs states that applications should not rely on it to protect sensitive data in production.
@@ -222,11 +222,11 @@ matrixscroll verify release.signed.json
 
 GitHub Actions publishes each Matrix Scroll release through PyPI Trusted Publishing. PyPI records a PEP 740 attestation for the wheel and source distribution.
 
-Ask PyPI for the `0.6.4` wheel provenance:
+Ask PyPI for the `0.7.0` wheel provenance:
 
 ```bash
 curl -H "Accept: application/vnd.pypi.integrity.v1+json" \
-  https://pypi.org/integrity/matrixscroll/0.6.4/matrixscroll-0.6.4-py3-none-any.whl/provenance
+  https://pypi.org/integrity/matrixscroll/0.7.0/matrixscroll-0.7.0-py3-none-any.whl/provenance
 ```
 
 The response names the GitHub publisher:

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/SECURITY.md

@@ -40,8 +40,9 @@ Out of scope:
 
 | Version | Status |
 | ------- | ------ |
-| 0.6.x   | Active development. Security fixes are released as patch versions. The published release is 0.6.4. |
-| 0.5.x and earlier | Legacy. Upgrade to 0.6.x for the post-quantum overlay and the in-repo verify action. |
+| 0.7.x | Active development. Security fixes are released as patch versions. The published release is 0.7.0. |
+| 0.6.x | Maintenance through 2026-11-09 under the 90-day previous-minor policy. |
+| 0.5.x and earlier | Legacy. Upgrade to 0.7.x for the current MCP server, USB signer host path, and in-repo verify action. |
 
 Pre-1.0 there is no extended support window. Pin to a known-good version
 in production until 1.0.

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/SPEC.md

@@ -14,8 +14,8 @@ Two schema identifiers are stamped into every artifact:
   `status`, the on-disk key store).
 - `matrixscroll.signature.v1` — the signature block attached to manifests.
 - `matrixscroll.commit_envelope.v1` — Git commit provenance document (see §10).
-- `matrixscroll.release_manifest.v1` and evidence-pack schemas — release and
-  audit artifacts (see §10).
+- Release and audit artifacts (see §10): `matrixscroll.release_manifest.v1`,
+  `matrixscroll.evidence_pack.v1`, and `ssx360.evidence-pack.v1`.
 
 A breaking change to canonical encoding, signature layout, device id
 derivation, or algorithm choice **must** bump the relevant version. Minor
@@ -192,10 +192,27 @@ Conformance vector: [`vectors/valid_commit_envelope.json`](vectors/valid_commit_
 Signed release metadata (version, tag, artifact list). JSON Schema:
 [`schemas/release-manifest.v1.json`](schemas/release-manifest.v1.json).
 
-### 10.3 Evidence pack
-
-Signed audit or agent-scope evidence. JSON Schema:
-[`schemas/evidence-pack.v1.json`](schemas/evidence-pack.v1.json).
+### 10.3 Evidence packs
+
+`matrixscroll.evidence_pack.v1` and `ssx360.evidence-pack.v1` both carry the
+"evidence pack" name. They are separate documents with separate schemas, and
+neither validates against the other.
+
+`matrixscroll.evidence_pack.v1` is the protocol document: a `subject` plus an
+`artifacts` list, holding audit or agent-scope evidence. JSON Schema:
+[`schemas/evidence-pack.v1.json`](schemas/evidence-pack.v1.json). No command in
+the Python reference SDK writes one yet. The schema is published so other
+implementers can agree on the shape ahead of that.
+
+`ssx360.evidence-pack.v1` is what `ssx360 ledger export` and
+`ssx360-ledger --export` write. It is an index over a bundle of signed commit
+envelopes, annotated with a framework mapping. The wrapper carries no
+`signature` block and makes no claim about itself. The trust is in the
+envelopes it points at, and each one verifies on its own. When the hosted
+export returns a body that does carry a signature, that body is nested verbatim
+under `evidence_pack` so its canonical bytes are the ones the signer covered.
+JSON Schema:
+[`schemas/ssx360.evidence-pack.v1.json`](schemas/ssx360.evidence-pack.v1.json).
 
 ## 11. Post-quantum overlay (v1.1 extension)
 

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/docs/ADOPTER_KIT.md

@@ -6,14 +6,14 @@ who want to trial Matrix Scroll without changing their core workflow.
 ## Best first-fit teams
 
 - OSS repos with active PR review and at least one protected branch
-- platform or DevSecOps teams evaluating agent-assisted coding controls
+- platform or DevSecOps teams evaluating machine-action controls
 - teams that already use GitHub Actions and can add one verification job
 
 ## 15-minute pilot
 
-1. Install `matrixscroll==0.6.4` in one repo.
+1. Install `matrixscroll==0.7.0` in one repo.
 2. Run `matrixscroll hook-install`.
-3. Make one agent-assisted commit and verify it locally.
+3. Make one commit with a declared actor and tool, then verify it locally.
 4. Publish notes with `matrixscroll envelope-publish-notes`.
 5. Add `SSX360/matrixscroll/.github/actions/verify@action-v1` to PR CI.
 
@@ -38,7 +38,7 @@ jobs:
           head-ref: ${{ github.event.pull_request.head.sha }}
           base-ref: ${{ github.event.pull_request.base.sha }}
           source: notes
-          matrixscroll-version: "0.6.4"
+          matrixscroll-version: "0.7.0"
           require-mode: emulated
 ```
 
@@ -65,7 +65,7 @@ jobs:
 
 Recorded on `2026-06-21` against the pinned public flow:
 `pip install matrixscroll` -> `matrixscroll hook-install` ->
-`matrixscroll hook-status` -> first agent-assisted commit ->
+`matrixscroll hook-status` -> first signed commit ->
 `matrixscroll envelope-verify`.
 
 The pin that run used is not named here. It moved with every release since, and

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/docs/COMMIT_TIME_VS_ARTIFACT_TIME.md

@@ -38,7 +38,7 @@ Use artifact-layer tools when you need:
 
 ## How to use them together
 
-1. Sign agent-assisted commits with Matrix Scroll.
+1. Sign commit-time authorization records with Matrix Scroll.
 2. Verify commit ranges in PRs with `SSX360/matrixscroll/.github/actions/verify@action-v1`.
 3. Keep Sigstore, GitHub attestations, or SLSA on the release path.
 

matrixscroll-0.7.0/docs/COMPARISON.md

@@ -0,0 +1,47 @@
+# Where Matrix Scroll fits
+
+Matrix Scroll signs a declared authorization record at commit or action time.
+It complements, rather than replaces, identity systems, source-control policy,
+build provenance, artifact signing, and runtime security controls.
+
+## Control boundaries
+
+| Control area | Primary question | Matrix Scroll role |
+| --- | --- | --- |
+| Identity and access management | Who may access or change a system? | Consumes trusted-key and authorization policy; does not issue access |
+| Source-control policy | Which changes may merge? | Supplies a signed record and range-verification result for policy checks |
+| Build provenance | What process produced an artifact? | Supplies optional source-history evidence; does not attest the build |
+| Artifact signing | Which key signed a release or image? | Separate control; Matrix Scroll records can be referenced by the release process |
+| Runtime security | What code or process is executing now? | Outside protocol scope |
+| Compliance assessment | Which evidence supports a control review? | Exports signed records and verification results for scoped review |
+
+## Commit-time and artifact-time evidence
+
+Matrix Scroll binds an envelope to a Git commit before or around push. Build
+provenance and artifact-signing systems operate later, after CI has produced an
+artifact. A complete software supply-chain review may use both:
+
+1. Matrix Scroll records the declared actor class, tool, scope, and commit SHA.
+2. Scroll Gate checks the selected commit range against key and policy inputs.
+3. CI produces build provenance and signs the resulting artifact.
+4. Reviewers compare the source-history and artifact evidence as separate
+   control records.
+
+## Signer choices
+
+The file-backed provider is included for local use, tests, and CI. The completed
+SSX360 USB signer keeps the Ed25519 private key inside an NXP SE050 secure
+element and is supplied through [SSX360 contact](https://ssx360.com/contact).
+Both paths produce the same public envelope format.
+
+## Limits
+
+- A valid envelope proves integrity and key possession, not authorization to
+  use the key.
+- Scroll Gate does not replace branch protection or reviewer approval.
+- Matrix Scroll does not establish a SLSA level or certify compliance.
+- Hardware custody, trusted-key registration, revocation, and offboarding are
+  deployment responsibilities.
+
+For protocol details, read [`SPEC.md`](../SPEC.md). For an implementation path,
+start with [`FIVE_MINUTES.md`](FIVE_MINUTES.md).

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/docs/CRYPTO_ROADMAP.md

@@ -46,7 +46,7 @@ Post-sunset    Ed25519-only envelopes rejected when org policy mandates PQC
 | FIPS 204 | ML-DSA (Dilithium) | Primary PQC signature | `ml-dsa-44/65/87` via liboqs |
 | FIPS 205 | SLH-DSA (SPHINCS+) | Hash-based backup | `slh-dsa-sha2-128s/f` |
 
-Enable: `pip install "matrixscroll[pqc]==0.6.4"` and `MATRIXSCROLL_PQC=ml-dsa-65`.
+Enable: `pip install "matrixscroll[pqc]==0.7.0"` and `MATRIXSCROLL_PQC=ml-dsa-65`.
 
 ## POC 2 audit answers
 

matrixscroll-0.7.0/docs/DOCTRINE.md

@@ -0,0 +1,56 @@
+# Publishing doctrine: SSX360 and Matrix Scroll
+
+This document defines the public claims and technical boundaries shared by the
+Matrix Scroll package, matrixscroll.com, PyPI, GitHub, and SSX360.
+
+## The thesis
+
+Software changes code, infrastructure, and business records at machine speed.
+Matrix Scroll signs a declared authorization record for those actions and lets
+reviewers verify the record offline. SSX360 maintains the protocol, produces the
+USB signer, and delivers scoped cybersecurity services.
+
+## Rules
+
+### 1. Describe evidence, not trust
+
+Matrix Scroll verifies that signed bytes match and correspond to a key. It does
+not establish who was authorized to use that key. Trusted-key policy, access
+control, key custody, revocation, and review remain deployment responsibilities.
+
+### 2. Keep the protocol portable
+
+The envelope format, schemas, conformance vectors, and verifier must work
+without a Matrix Scroll account. Integrations may target GitHub, GitLab,
+Forgejo, Gitea, or other systems, but the wire format must not depend on one
+platform.
+
+### 3. Make every claim checkable
+
+Software signing is described as software signing. The completed SSX360 USB
+signer is described as an RP2350 and NXP SE050 device supplied through direct
+contact. PyPI distributes the host software, not the physical device. Compliance
+references are evidence mappings, not certifications.
+
+### 4. Apply the same controls to releases
+
+Release examples use explicit version pins. PyPI artifacts are built from the
+tagged repository state and published through Trusted Publishing with
+attestations. The changelog, support policy, action defaults, site, and package
+metadata must identify the same current release.
+
+### 5. Separate open software from commercial delivery
+
+Matrix Scroll remains Apache-2.0 software with CC0 specification text and
+vectors. SSX360 earns revenue from cybersecurity products and scoped services,
+including the physical USB signer and compliance-aligned assessment work.
+
+## Publication check
+
+Before publishing, confirm that:
+
+1. The capability exists in the referenced release or deployed service.
+2. The evidence and limitations appear beside the claim.
+3. Version numbers and install commands agree across every public surface.
+4. Hardware availability distinguishes host software from physical units.
+5. Standards references do not imply certification or third-party validation.

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/docs/FIVE_MINUTES.md

@@ -12,7 +12,7 @@ five-minute path from `pip install` to a verifiable commit envelope.
 ## 1. Install the SDK
 
 ```bash
-pip install "matrixscroll==0.6.4"
+pip install "matrixscroll==0.7.0"
 matrixscroll hook-install
 matrixscroll hook-status
 ```
@@ -61,7 +61,7 @@ git push origin refs/notes/matrixscroll
     head-ref: ${{ github.event.pull_request.head.sha }}
     base-ref: ${{ github.event.pull_request.base.sha }}
     source: notes
-    matrixscroll-version: "0.6.4"
+    matrixscroll-version: "0.7.0"
     require-mode: emulated
 ```
 

matrixscroll-0.7.0/docs/POC2_AUDIT.md

@@ -0,0 +1,52 @@
+# Matrix Scroll release evidence
+
+This checklist records the public evidence for Matrix Scroll 0.7.0. It is a
+release-readiness record, not a third-party audit or certification.
+
+## Release surfaces
+
+| Surface | Current reference |
+| --- | --- |
+| Python package | `matrixscroll==0.7.0` |
+| MCP server | `matrixscroll-mcp`, 14 tools |
+| GitHub Action | `SSX360/matrixscroll/.github/actions/verify@action-v1` |
+| Browser verifier | <https://matrixscroll.com/verify/> |
+| MCP surface scanner | <https://matrixscroll.com/scan/> |
+| Protocol source | [`SPEC.md`](../SPEC.md) and [`schemas/`](../schemas/) |
+
+## Verification behavior
+
+- Ed25519 signatures are checked over deterministic canonical JSON bytes.
+- Invalid signatures, unsupported schemas, malformed records, and empty commit
+  ranges fail closed by default.
+- Range checks can read local envelopes, Git notes, or exported bundles without
+  a hosted account.
+- The wheel includes the public schemas used by the MCP resources and evidence
+  exporter.
+
+## Hardware path
+
+- SSX360 produces the RP2350 and NXP SE050 USB signer.
+- The SE050 creates and retains the non-exportable Ed25519 private key.
+- USB CDC host support ships in `matrixscroll[hardware]==0.7.0`.
+- Physical units are supplied by SSX360 through direct contact. PyPI distributes
+  the host software only.
+
+## Release chain
+
+- GitHub Actions builds the wheel and source distribution from the release
+  repository state.
+- PyPI Trusted Publishing supplies provenance attestations for both artifacts.
+- `python scripts/release-readiness.py` checks package, README, and registry
+  version consistency before publication.
+- `python -m twine check --strict dist/*` validates the built metadata.
+
+## Limits
+
+- A valid signature proves integrity and key possession, not authorization to
+  use the key.
+- The optional ML-DSA and SLH-DSA overlay uses liboqs and has no CMVP validation.
+- Matrix Scroll does not replace IAM, sandboxing, build attestations, or review
+  policy.
+- Compliance references map available evidence to control questions; they do
+  not claim certification.

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/docs/ROADMAP_2026-07.md

@@ -6,7 +6,7 @@ Matrix Scroll stabilizes the verifier contract before adding new signing provide
 
 ## Current release
 
-- PyPI release: `matrixscroll==0.6.4`
+- PyPI release: `matrixscroll==0.7.0`
 - MCP transport: stdio through `matrixscroll-mcp`
 - Public trust contract: Ed25519 over canonical manifest bytes
 - Software provider: file-backed key under `MATRIXSCROLL_HOME`
@@ -31,7 +31,7 @@ Matrix Scroll stabilizes the verifier contract before adding new signing provide
 - Commit-envelope schema
 - CLI exit codes
 - Offline verification behavior
-- MCP tool names for the `0.6.x` release line
+- MCP tool names for the `0.7.x` release line
 
 ## Release rule
 

{matrixscroll-0.6.4 → matrixscroll-0.7.0}/docs/SECURITY_PROPERTIES.md

@@ -1,6 +1,6 @@
 # Matrix Scroll security properties
 
-Machine-checkable guarantees for the reference SDK (v0.6.4). Properties marked
+Machine-checkable guarantees for the reference SDK (v0.7.0). Properties marked
 **verified** have Hypothesis property tests in `tests/test_security_properties.py`.
 **Formal TLA+ models** in [`formal/tla/`](../formal/tla/) are checked by TLC in
 [`.github/workflows/formal-verify.yml`](../.github/workflows/formal-verify.yml).

matrixscroll-0.7.0/docs/SLSA_SOURCE_TRACK_MAPPING.md

@@ -0,0 +1,26 @@
+# SLSA source evidence context
+
+SLSA applies requirements to software supply-chain provenance. Matrix Scroll
+adds signed commit-time records that can support a reviewer examining source
+history, but the protocol does not establish or certify a SLSA level.
+
+## Evidence Matrix Scroll can provide
+
+| Review question | Matrix Scroll evidence | Deployment dependency |
+| --- | --- | --- |
+| Which commit was assessed? | Commit SHA bound into a signed envelope | Git repository history |
+| Which actor class and tool were declared? | `provenance.actor_type` and `provenance.tool` | Accurate declaration by the signer |
+| Was the record altered? | Ed25519 signature over canonical bytes | Trusted public-key policy |
+| Did every selected commit carry a valid record? | Scroll Gate range result | Correct base and head refs |
+| Was protected review enforced? | External branch and review evidence | Forge configuration and organization policy |
+| What artifact did CI build? | Not provided by Matrix Scroll | Build provenance such as SLSA or Sigstore |
+
+## Use in an assessment
+
+Treat Matrix Scroll envelopes and range results as source-history evidence. Pair
+them with branch-protection records, reviewer approvals, build attestations, and
+artifact signatures where those controls are in scope.
+
+Use language such as "provides signed commit-time evidence for SLSA review."
+Do not claim a SLSA level, SLSA certification, or complete build provenance from
+Matrix Scroll alone.