matrixscroll 0.6.0__tar.gz → 0.6.1__tar.gz

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/CHANGELOG.md

@@ -4,6 +4,14 @@ All notable changes to the Matrix Scroll Python SDK are documented here. The
 format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.1] - 2026-07-22
+
+### Documentation
+- **L2 Hardware prototype (2026-07-21)** — Pico 2 W / RP2350 + GMT130 ST7789
+  LCD/LED bring-up locked; SE050 M1 PoC remains bench-validated (not GA).
+  README compliance table, `docs/hardware-provider.md`, and roadmap updated.
+  Docs-only release; install pin `matrixscroll==0.6.1`.
+
 ## [0.6.0] - 2026-07-03
 
 MCP Trust Scanner — sign any MCP server's tool surface and detect rug-pulls offline.
@@ -237,6 +245,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.6.1]: https://github.com/SSX360/matrixscroll/releases/tag/v0.6.1
 [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

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: matrixscroll
-Version: 0.6.0
+Version: 0.6.1
 Summary: Signed provenance for agent-assisted Git commits with offline Ed25519 verification; optional ML-DSA/SLH-DSA software overlay (FIPS 204/205). USB/NFC/SE050 hardware remains Ed25519.
 Project-URL: Homepage, https://ssx360.com
 Project-URL: Documentation, https://ssx360.com/docs
@@ -15,7 +15,7 @@ Project-URL: Changelog, https://github.com/SSX360/matrixscroll/blob/main/CHANGEL
 Project-URL: Discussions, https://github.com/SSX360/matrixscroll/discussions
 Project-URL: Security, https://github.com/SSX360/matrixscroll/blob/main/SECURITY.md
 Project-URL: GitHub Action, https://github.com/SSX360/matrixscroll-verify-action
-Project-URL: PyPI Provenance, https://pypi.org/project/matrixscroll/0.6.0/
+Project-URL: PyPI Provenance, https://pypi.org/project/matrixscroll/0.6.1/
 Project-URL: Reference Device, https://ssx360.com/hardware
 Project-URL: Tests, https://github.com/SSX360/matrixscroll/tree/main/tests
 Project-URL: Public Roadmap, https://github.com/SSX360/matrixscroll/blob/main/docs/ROADMAP_2026-07.md
@@ -68,13 +68,18 @@ Description-Content-Type: text/markdown
 
 **146 tests** · Hypothesis-verified security properties · [Security properties](https://github.com/SSX360/matrixscroll/blob/main/docs/SECURITY_PROPERTIES.md) · [TLA+ formal models](formal/README.md)
 
-**Signed proof of who — or what — wrote every AI-assisted commit.** Matrix Scroll is an
-**open protocol for cryptographically signed, AI-assisted code provenance** — Ed25519 commit
-envelopes for Git (and universal action envelopes for CI, IaC, and migrations),
-verified offline in CLI, browser, and CI. Software emulated keys ship today; NXP SE050
-secure-element signing is in firmware validation with the same verifier contract.
+**Agent Authorization Authority — offline-verifiable proof for every machine action.** Matrix Scroll is an
+**open protocol for cryptographically signed agent authorization** — Ed25519 records for Git commits (L1),
+MCP tool surfaces (L2), and agent runs / NHI actions (L3), verified offline in CLI, browser, and CI.
+Software emulated keys ship today; NXP SE050 secure-element signing is a
+bench-validated PoC (Jul 2026) with the same verifier contract. The Pico 2 W /
+GMT130 display bring-up is a locked L2 Hardware prototype (Jul 2026) — not GA.
 
-**Hosted control plane:** identity, billing, audit ledger, and Scroll Gate live at
+*They receipt the model call. We receipt everything the machine does.*
+
+**Authorization ladder:** L1 Code (commits) · L2 Tools (MCP manifests) · L3 Actions (agent runs) · L4 Money (AP2 — demo) · L5 Silicon (2029+)
+
+**Hosted control plane:** identity, billing, authorization ledger, and Scroll Gate live at
 [ssx360.com](https://ssx360.com/). Enterprise teams evaluating protected-branch enforcement should
 [book a provenance pilot](https://ssx360.com/contact?intent=pilot) or visit
 [ssx360.com/enterprise](https://ssx360.com/enterprise).
@@ -109,23 +114,27 @@ Agents sign commits in-loop via the **provenance-only** MCP server:
 ```
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.0"
+pip install "matrixscroll[mcp]==0.6.1"
 matrixscroll-mcp   # stdio — register in Cursor / Claude Desktop / VS Code
 ```
 
 **MCP tools (provenance verbs only):** `create_envelope`, `sign_action`, `verify_envelope`,
 `verify_pr_range` (Scroll Gate), `publish_notes`, `status`, `audit_export`, `list_envelopes`,
-`connect_card` (SE050 hardware preview, roadmap).
+`connect_card` (SE050 hardware prototype — pilot evaluation; not GA).
 
 **MCP trust tools (manifest surface):** `scan_mcp_server`, `sign_mcp_manifest`, `verify_mcp_manifest`.
 
 ### MCP Trust Scanner — catch a rug-pull in 60 seconds
 
+![MCP rug-pull detection demo](examples/demo/mcp-rugpull-demo.gif)
+
+[Watch on asciinema](https://asciinema.org/a/rbCRkIcZnjNWmqZF) · cast file: [`examples/demo/mcp-rugpull-demo.cast`](examples/demo/mcp-rugpull-demo.cast)
+
 Sign the tool surface. Verify at install. Offline Ed25519 manifests for MCP rug-pull detection —
 zero cloud, zero signup, exit code 2 fails your CI.
 
 ```bash
-pip install matrixscroll
+pip install "matrixscroll==0.6.1"
 
 # 1. Scan a live MCP server (stdio) — fingerprints every tool: name, description, input schema
 matrixscroll mcp scan --connect stdio --server-command "npx -y some-mcp-server" \
@@ -154,6 +163,18 @@ FAIL  surface_drift — do not trust this server until you review the diff
 Offline mode works too — no server needed: `matrixscroll mcp scan --tools ./tools.json`
 accepts a plain JSON tool array or `{"tools": [...]}` (paste from any `tools/list` response).
 
+Gate it in CI — fail the build on unsigned or drifted manifests with the reusable workflow:
+
+```yaml
+jobs:
+  mcp-gate:
+    uses: SSX360/matrixscroll-verify-action/.github/workflows/mcp-manifest-gate.yml@main
+    with:
+      manifest: mcp/my-server.signed.json
+      baseline: mcp/my-server.baseline.json
+      matrixscroll_version: "0.6.1"
+```
+
 Full scripted demo: [`examples/demo/mcp-rugpull-demo.sh`](examples/demo/mcp-rugpull-demo.sh)  
 Golden artifact (this repo's own MCP server, signed): [`examples/mcp/matrixscroll-mcp.signed.json`](examples/mcp/matrixscroll-mcp.signed.json)  
 Schema (CC0): [`schemas/ssx360.mcp-manifest.v1.json`](schemas/ssx360.mcp-manifest.v1.json)  
@@ -163,7 +184,7 @@ Launch checklist: [`docs/SHOW-HN-MCP-TRUST-LAUNCH.md`](docs/SHOW-HN-MCP-TRUST-LA
 ## Also available — CLI & hooks
 
 ```bash
-pip install "matrixscroll==0.6.0"
+pip install "matrixscroll==0.6.1"
 matrixscroll hook-install
 export MATRIXSCROLL_ACTOR_TYPE=agent
 export MATRIXSCROLL_TOOL=agent-runner
@@ -211,11 +232,13 @@ that produced it.
 Keep GitHub Advanced Security, Semgrep, Snyk, branch protection, and artifact
 attestations. Matrix Scroll adds signed commit-time authorship proof before
 merge, and it keeps the same offline verification contract across the CLI,
-browser, CI, and the SE050 preview path.
+browser, CI, and the SE050 hardware prototype path.
 
 The reference SDK ships pure Ed25519 over canonical manifest bytes today. The
-SSX360 / NXP SE050 path is the compatible next trust layer and remains a
-preview path until device acceptance is complete.
+SSX360 / NXP SE050 path is the compatible next trust layer: M1 signing PoC and
+RP2350 + GMT130 display prototype are bench-validated; live SE050 on the
+display bring-up UF2 remains fail-closed until the NXP backend is restored.
+This is **prototype / pilot evaluation**, not a GA hardware product.
 
 ## RFC 8032 (Ed25519) alignment
 
@@ -227,13 +250,16 @@ canonical UTF-8 JSON bytes (see [`SPEC.md`](https://github.com/SSX360/matrixscro
 
 ## Honest limits
 
-- Shipping now: PyPI `matrixscroll==0.6.0`, Git post-commit hooks,
+- Shipping now: PyPI `matrixscroll==0.6.1`, Git post-commit hooks,
   `matrixscroll sign-action`, `matrixscroll scroll commit` (thin wrapper),
   `matrixscroll envelope-verify`, Scroll Gate PR verification (partial SLSA L1–2),
-  verifier, the GitHub Action, and a USB CDC host transport preview for the
-  SE050 rollout path. Emulated mode is the default evaluation path.
-- In progress: nRF52840 + SE050 firmware validation — secure-element signing remains preview until device acceptance gates pass; external Ed25519-capable
-  hardware key backends, and transparency-log integrations.
+  verifier, the GitHub Action, and a USB CDC host transport for the SE050
+  hardware prototype path. Emulated mode is the default evaluation path.
+- Prototype (bench): Pico 2 W / RP2350 + GMT130 ST7789 LCD/LED bring-up locked
+  (2026-07-21); NXP SE050 M1 signing PoC accepted (Jul 2026) on contractor
+  firmware — not GA; display bring-up UF2 keeps `pubkey`/`sign` fail-closed
+  until Plug & Trust restore. External Ed25519-capable hardware key backends
+  and transparency-log integrations remain roadmap.
 - Compliance language is evidence mapping (DORA, PCI DSS 4.0, Treasury FS-AI RMF, SSDF, EU AI Act Article 12 readiness, Five Eyes agentic-AI guidance), not certification or customer endorsement.
 - Illustrative deployment profiles are not endorsements or existing customer relationships.
 - Not: IAM, sandboxing, prompt filtering, or an agent runtime.
@@ -263,8 +289,9 @@ verify that proof offline in the CLI, browser, or CI before merge.
 Emulated mode ships today and keeps the signing key on disk with owner-only
 permissions so teams can evaluate the full workflow now. Hardware mode keeps
 the same verifier contract and commit envelope schema, but moves the private
-key into the SE050 secure element so the host cannot export it; that path
-remains preview-only until device acceptance is complete.
+key into the SE050 secure element so the host cannot export it. That path is
+a bench-validated L2 Hardware prototype (Pico 2 W + SE050 M1 PoC) available
+for pilot evaluation — not GA.
 
 ### How can I integrate Matrix Scroll into a CI/CD workflow?
 
@@ -277,7 +304,7 @@ alongside your existing scanners, branch protection, and build attestations.
 ## Quickstart (CLI)
 
 ```bash
-pip install "matrixscroll==0.6.0"
+pip install "matrixscroll==0.6.1"
 matrixscroll hook-install
 matrixscroll hook-status
 
@@ -306,7 +333,7 @@ See [`docs/quickstart-git.md`](docs/quickstart-git.md) and run
     head-ref: ${{ github.event.pull_request.head.sha }}
     base-ref: ${{ github.event.pull_request.base.sha }}
     source: notes
-    matrixscroll-version: "0.6.0"
+    matrixscroll-version: "0.6.1"
     require-mode: emulated
 ```
 
@@ -326,7 +353,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.0"
+    matrixscroll-version: "0.6.1"
     summary-output: provenance-summary.json
 ```
 
@@ -334,7 +361,7 @@ See [`docs/quickstart-git.md`](docs/quickstart-git.md) and
 [`examples/ci/protected-branch.yml`](examples/ci/protected-branch.yml).
 
 The `--require-mode`, `--trusted-keys`, and actor or delegation policy checks
-ship in the current release line; examples in this README pin `0.6.0`.
+ship in the current release line; examples in this README pin `0.6.1`.
 
 ## Security: Ed25519 via cryptography
 
@@ -368,12 +395,12 @@ when they preserve the same pure Ed25519 byte contract.
 - GitHub Action: <https://github.com/SSX360/matrixscroll-verify-action>
 - Agentic AI controls: [`docs/AGENTIC_AI_SECURITY.md`](https://github.com/SSX360/matrixscroll/blob/main/docs/AGENTIC_AI_SECURITY.md)
 - Site: <https://matrixscroll.com> · Control plane: <https://ssx360.com> · Enterprise: <https://ssx360.com/enterprise>
-- SE050 hardware preview: <https://ssx360.com/enterprise#roadmap> (in firmware validation)
+- SE050 hardware prototype: <https://ssx360.com/enterprise#roadmap> (bench-validated; not GA)
 
 ## Python API
 
 ```bash
-pip install "matrixscroll==0.6.0"
+pip install "matrixscroll==0.6.1"
 ```
 
 ```python
@@ -423,7 +450,7 @@ matrixscroll.sign_manifest(...)  /  post-commit hook
          v
 IdentityProvider          -->  Ed25519 signature
 (L1 emulated today,
- SSX360 / SE050 in firmware validation)
+ SSX360 / SE050 prototype — bench-validated)
          |
          v
 signed document  -->  matrixscroll.verify_manifest(...)
@@ -431,21 +458,23 @@ signed document  -->  matrixscroll.verify_manifest(...)
 ```
 
 Switch providers with `MATRIXSCROLL_MODE`. Hardware mode includes a USB CDC
-host transport preview and a mock path for CI; real SE050 signing still
-depends on device firmware validation. External-key backends stay out of the
-mainline until they can sign the same canonical bytes with Ed25519.
+host transport and a mock path for CI. The L2 Hardware prototype (Pico 2 W /
+GMT130 display + SE050 M1 PoC) is bench-validated; live SE050 signing on the
+display bring-up UF2 stays fail-closed until the NXP backend is restored.
+External-key backends stay out of the mainline until they can sign the same
+canonical bytes with Ed25519.
 
 For rollout order, start with `MATRIXSCROLL_MODE=emulated` for evaluation,
 layer in external Ed25519-capable signers only when they stay verifier
-compatible, and treat `hardware` as the SE050 preview path until device
-acceptance is complete.
+compatible, and treat `hardware` as the SE050 prototype path for pilot
+evaluation — not GA.
 
 ## Compliance levels
 
 | Level | Provider | Backed by | Status |
 | ----- | -------- | --------- | ------ |
 | **L1** Emulated | `EmulatedProvider` | Software key, file-backed (0600) | Shipping |
-| **L2** Hardware | `HardwareProvider` | NXP SE050 secure element (SSX360) | In progress |
+| **L2** Hardware | `HardwareProvider` | NXP SE050 + Pico 2 W / RP2350 + GMT130 (SSX360) | Prototype (bench) |
 | **L3** Attested | future | L2 + remote attestation | Roadmap |
 
 `status()` exposes the active level via the `mode` and `available` fields.
@@ -484,7 +513,7 @@ The MCP server exposes **provenance verbs** (`create_envelope`, `verify_envelope
 Install and register in Cursor / Claude Desktop / VS Code:
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.0"
+pip install "matrixscroll[mcp]==0.6.1"
 matrixscroll-mcp   # stdio
 ```
 

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/README.md

@@ -10,13 +10,18 @@
 
 **146 tests** · Hypothesis-verified security properties · [Security properties](https://github.com/SSX360/matrixscroll/blob/main/docs/SECURITY_PROPERTIES.md) · [TLA+ formal models](formal/README.md)
 
-**Signed proof of who — or what — wrote every AI-assisted commit.** Matrix Scroll is an
-**open protocol for cryptographically signed, AI-assisted code provenance** — Ed25519 commit
-envelopes for Git (and universal action envelopes for CI, IaC, and migrations),
-verified offline in CLI, browser, and CI. Software emulated keys ship today; NXP SE050
-secure-element signing is in firmware validation with the same verifier contract.
+**Agent Authorization Authority — offline-verifiable proof for every machine action.** Matrix Scroll is an
+**open protocol for cryptographically signed agent authorization** — Ed25519 records for Git commits (L1),
+MCP tool surfaces (L2), and agent runs / NHI actions (L3), verified offline in CLI, browser, and CI.
+Software emulated keys ship today; NXP SE050 secure-element signing is a
+bench-validated PoC (Jul 2026) with the same verifier contract. The Pico 2 W /
+GMT130 display bring-up is a locked L2 Hardware prototype (Jul 2026) — not GA.
 
-**Hosted control plane:** identity, billing, audit ledger, and Scroll Gate live at
+*They receipt the model call. We receipt everything the machine does.*
+
+**Authorization ladder:** L1 Code (commits) · L2 Tools (MCP manifests) · L3 Actions (agent runs) · L4 Money (AP2 — demo) · L5 Silicon (2029+)
+
+**Hosted control plane:** identity, billing, authorization ledger, and Scroll Gate live at
 [ssx360.com](https://ssx360.com/). Enterprise teams evaluating protected-branch enforcement should
 [book a provenance pilot](https://ssx360.com/contact?intent=pilot) or visit
 [ssx360.com/enterprise](https://ssx360.com/enterprise).
@@ -51,23 +56,27 @@ Agents sign commits in-loop via the **provenance-only** MCP server:
 ```
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.0"
+pip install "matrixscroll[mcp]==0.6.1"
 matrixscroll-mcp   # stdio — register in Cursor / Claude Desktop / VS Code
 ```
 
 **MCP tools (provenance verbs only):** `create_envelope`, `sign_action`, `verify_envelope`,
 `verify_pr_range` (Scroll Gate), `publish_notes`, `status`, `audit_export`, `list_envelopes`,
-`connect_card` (SE050 hardware preview, roadmap).
+`connect_card` (SE050 hardware prototype — pilot evaluation; not GA).
 
 **MCP trust tools (manifest surface):** `scan_mcp_server`, `sign_mcp_manifest`, `verify_mcp_manifest`.
 
 ### MCP Trust Scanner — catch a rug-pull in 60 seconds
 
+![MCP rug-pull detection demo](examples/demo/mcp-rugpull-demo.gif)
+
+[Watch on asciinema](https://asciinema.org/a/rbCRkIcZnjNWmqZF) · cast file: [`examples/demo/mcp-rugpull-demo.cast`](examples/demo/mcp-rugpull-demo.cast)
+
 Sign the tool surface. Verify at install. Offline Ed25519 manifests for MCP rug-pull detection —
 zero cloud, zero signup, exit code 2 fails your CI.
 
 ```bash
-pip install matrixscroll
+pip install "matrixscroll==0.6.1"
 
 # 1. Scan a live MCP server (stdio) — fingerprints every tool: name, description, input schema
 matrixscroll mcp scan --connect stdio --server-command "npx -y some-mcp-server" \
@@ -96,6 +105,18 @@ FAIL  surface_drift — do not trust this server until you review the diff
 Offline mode works too — no server needed: `matrixscroll mcp scan --tools ./tools.json`
 accepts a plain JSON tool array or `{"tools": [...]}` (paste from any `tools/list` response).
 
+Gate it in CI — fail the build on unsigned or drifted manifests with the reusable workflow:
+
+```yaml
+jobs:
+  mcp-gate:
+    uses: SSX360/matrixscroll-verify-action/.github/workflows/mcp-manifest-gate.yml@main
+    with:
+      manifest: mcp/my-server.signed.json
+      baseline: mcp/my-server.baseline.json
+      matrixscroll_version: "0.6.1"
+```
+
 Full scripted demo: [`examples/demo/mcp-rugpull-demo.sh`](examples/demo/mcp-rugpull-demo.sh)  
 Golden artifact (this repo's own MCP server, signed): [`examples/mcp/matrixscroll-mcp.signed.json`](examples/mcp/matrixscroll-mcp.signed.json)  
 Schema (CC0): [`schemas/ssx360.mcp-manifest.v1.json`](schemas/ssx360.mcp-manifest.v1.json)  
@@ -105,7 +126,7 @@ Launch checklist: [`docs/SHOW-HN-MCP-TRUST-LAUNCH.md`](docs/SHOW-HN-MCP-TRUST-LA
 ## Also available — CLI & hooks
 
 ```bash
-pip install "matrixscroll==0.6.0"
+pip install "matrixscroll==0.6.1"
 matrixscroll hook-install
 export MATRIXSCROLL_ACTOR_TYPE=agent
 export MATRIXSCROLL_TOOL=agent-runner
@@ -153,11 +174,13 @@ that produced it.
 Keep GitHub Advanced Security, Semgrep, Snyk, branch protection, and artifact
 attestations. Matrix Scroll adds signed commit-time authorship proof before
 merge, and it keeps the same offline verification contract across the CLI,
-browser, CI, and the SE050 preview path.
+browser, CI, and the SE050 hardware prototype path.
 
 The reference SDK ships pure Ed25519 over canonical manifest bytes today. The
-SSX360 / NXP SE050 path is the compatible next trust layer and remains a
-preview path until device acceptance is complete.
+SSX360 / NXP SE050 path is the compatible next trust layer: M1 signing PoC and
+RP2350 + GMT130 display prototype are bench-validated; live SE050 on the
+display bring-up UF2 remains fail-closed until the NXP backend is restored.
+This is **prototype / pilot evaluation**, not a GA hardware product.
 
 ## RFC 8032 (Ed25519) alignment
 
@@ -169,13 +192,16 @@ canonical UTF-8 JSON bytes (see [`SPEC.md`](https://github.com/SSX360/matrixscro
 
 ## Honest limits
 
-- Shipping now: PyPI `matrixscroll==0.6.0`, Git post-commit hooks,
+- Shipping now: PyPI `matrixscroll==0.6.1`, Git post-commit hooks,
   `matrixscroll sign-action`, `matrixscroll scroll commit` (thin wrapper),
   `matrixscroll envelope-verify`, Scroll Gate PR verification (partial SLSA L1–2),
-  verifier, the GitHub Action, and a USB CDC host transport preview for the
-  SE050 rollout path. Emulated mode is the default evaluation path.
-- In progress: nRF52840 + SE050 firmware validation — secure-element signing remains preview until device acceptance gates pass; external Ed25519-capable
-  hardware key backends, and transparency-log integrations.
+  verifier, the GitHub Action, and a USB CDC host transport for the SE050
+  hardware prototype path. Emulated mode is the default evaluation path.
+- Prototype (bench): Pico 2 W / RP2350 + GMT130 ST7789 LCD/LED bring-up locked
+  (2026-07-21); NXP SE050 M1 signing PoC accepted (Jul 2026) on contractor
+  firmware — not GA; display bring-up UF2 keeps `pubkey`/`sign` fail-closed
+  until Plug & Trust restore. External Ed25519-capable hardware key backends
+  and transparency-log integrations remain roadmap.
 - Compliance language is evidence mapping (DORA, PCI DSS 4.0, Treasury FS-AI RMF, SSDF, EU AI Act Article 12 readiness, Five Eyes agentic-AI guidance), not certification or customer endorsement.
 - Illustrative deployment profiles are not endorsements or existing customer relationships.
 - Not: IAM, sandboxing, prompt filtering, or an agent runtime.
@@ -205,8 +231,9 @@ verify that proof offline in the CLI, browser, or CI before merge.
 Emulated mode ships today and keeps the signing key on disk with owner-only
 permissions so teams can evaluate the full workflow now. Hardware mode keeps
 the same verifier contract and commit envelope schema, but moves the private
-key into the SE050 secure element so the host cannot export it; that path
-remains preview-only until device acceptance is complete.
+key into the SE050 secure element so the host cannot export it. That path is
+a bench-validated L2 Hardware prototype (Pico 2 W + SE050 M1 PoC) available
+for pilot evaluation — not GA.
 
 ### How can I integrate Matrix Scroll into a CI/CD workflow?
 
@@ -219,7 +246,7 @@ alongside your existing scanners, branch protection, and build attestations.
 ## Quickstart (CLI)
 
 ```bash
-pip install "matrixscroll==0.6.0"
+pip install "matrixscroll==0.6.1"
 matrixscroll hook-install
 matrixscroll hook-status
 
@@ -248,7 +275,7 @@ See [`docs/quickstart-git.md`](docs/quickstart-git.md) and run
     head-ref: ${{ github.event.pull_request.head.sha }}
     base-ref: ${{ github.event.pull_request.base.sha }}
     source: notes
-    matrixscroll-version: "0.6.0"
+    matrixscroll-version: "0.6.1"
     require-mode: emulated
 ```
 
@@ -268,7 +295,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.0"
+    matrixscroll-version: "0.6.1"
     summary-output: provenance-summary.json
 ```
 
@@ -276,7 +303,7 @@ See [`docs/quickstart-git.md`](docs/quickstart-git.md) and
 [`examples/ci/protected-branch.yml`](examples/ci/protected-branch.yml).
 
 The `--require-mode`, `--trusted-keys`, and actor or delegation policy checks
-ship in the current release line; examples in this README pin `0.6.0`.
+ship in the current release line; examples in this README pin `0.6.1`.
 
 ## Security: Ed25519 via cryptography
 
@@ -310,12 +337,12 @@ when they preserve the same pure Ed25519 byte contract.
 - GitHub Action: <https://github.com/SSX360/matrixscroll-verify-action>
 - Agentic AI controls: [`docs/AGENTIC_AI_SECURITY.md`](https://github.com/SSX360/matrixscroll/blob/main/docs/AGENTIC_AI_SECURITY.md)
 - Site: <https://matrixscroll.com> · Control plane: <https://ssx360.com> · Enterprise: <https://ssx360.com/enterprise>
-- SE050 hardware preview: <https://ssx360.com/enterprise#roadmap> (in firmware validation)
+- SE050 hardware prototype: <https://ssx360.com/enterprise#roadmap> (bench-validated; not GA)
 
 ## Python API
 
 ```bash
-pip install "matrixscroll==0.6.0"
+pip install "matrixscroll==0.6.1"
 ```
 
 ```python
@@ -365,7 +392,7 @@ matrixscroll.sign_manifest(...)  /  post-commit hook
          v
 IdentityProvider          -->  Ed25519 signature
 (L1 emulated today,
- SSX360 / SE050 in firmware validation)
+ SSX360 / SE050 prototype — bench-validated)
          |
          v
 signed document  -->  matrixscroll.verify_manifest(...)
@@ -373,21 +400,23 @@ signed document  -->  matrixscroll.verify_manifest(...)
 ```
 
 Switch providers with `MATRIXSCROLL_MODE`. Hardware mode includes a USB CDC
-host transport preview and a mock path for CI; real SE050 signing still
-depends on device firmware validation. External-key backends stay out of the
-mainline until they can sign the same canonical bytes with Ed25519.
+host transport and a mock path for CI. The L2 Hardware prototype (Pico 2 W /
+GMT130 display + SE050 M1 PoC) is bench-validated; live SE050 signing on the
+display bring-up UF2 stays fail-closed until the NXP backend is restored.
+External-key backends stay out of the mainline until they can sign the same
+canonical bytes with Ed25519.
 
 For rollout order, start with `MATRIXSCROLL_MODE=emulated` for evaluation,
 layer in external Ed25519-capable signers only when they stay verifier
-compatible, and treat `hardware` as the SE050 preview path until device
-acceptance is complete.
+compatible, and treat `hardware` as the SE050 prototype path for pilot
+evaluation — not GA.
 
 ## Compliance levels
 
 | Level | Provider | Backed by | Status |
 | ----- | -------- | --------- | ------ |
 | **L1** Emulated | `EmulatedProvider` | Software key, file-backed (0600) | Shipping |
-| **L2** Hardware | `HardwareProvider` | NXP SE050 secure element (SSX360) | In progress |
+| **L2** Hardware | `HardwareProvider` | NXP SE050 + Pico 2 W / RP2350 + GMT130 (SSX360) | Prototype (bench) |
 | **L3** Attested | future | L2 + remote attestation | Roadmap |
 
 `status()` exposes the active level via the `mode` and `available` fields.
@@ -426,7 +455,7 @@ The MCP server exposes **provenance verbs** (`create_envelope`, `verify_envelope
 Install and register in Cursor / Claude Desktop / VS Code:
 
 ```bash
-pip install "matrixscroll[mcp]==0.6.0"
+pip install "matrixscroll[mcp]==0.6.1"
 matrixscroll-mcp   # stdio
 ```
 

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/docs/ADOPTER_KIT.md

@@ -11,7 +11,7 @@ who want to trial Matrix Scroll without changing their core workflow.
 
 ## 15-minute pilot
 
-1. Install `matrixscroll==0.6.0` in one repo.
+1. Install `matrixscroll==0.6.1` in one repo.
 2. Run `matrixscroll hook-install`.
 3. Make one agent-assisted commit and verify it locally.
 4. Publish notes with `matrixscroll envelope-publish-notes`.
@@ -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.0"
+          matrixscroll-version: "0.6.1"
           require-mode: emulated
 ```
 
@@ -64,7 +64,7 @@ jobs:
 ## Clean-machine proof status
 
 Recorded on `2026-06-21` against the pinned public flow:
-`pip install "matrixscroll==0.6.0"` -> `matrixscroll hook-install` ->
+`pip install "matrixscroll==0.6.1"` -> `matrixscroll hook-install` ->
 `matrixscroll hook-status` -> first agent-assisted commit ->
 `matrixscroll envelope-verify`.
 

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/docs/COMMIT_TIME_VS_ARTIFACT_TIME.md

@@ -19,7 +19,7 @@ These answers are different, and mature teams usually want both.
 | Main unit | Commit envelope | Package, container, or predicate |
 | Actor / tool in record | Yes | Usually no |
 | Offline verify | Yes | Varies by workflow |
-| Hardware path | In progress | External to the standard flow |
+| Hardware path | Prototype (bench) | External to the standard flow; not GA |
 
 ## Where Matrix Scroll fits
 

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/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.0"` and `MATRIXSCROLL_PQC=ml-dsa-65`.
+Enable: `pip install "matrixscroll[pqc]==0.6.1"` and `MATRIXSCROLL_PQC=ml-dsa-65`.
 
 ## POC 2 audit answers
 

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/docs/DOCTRINE.md

@@ -20,7 +20,7 @@ The buyer is a security or platform team, but the user who decides if we win is
 
 ### 3. Every claim must be falsifiable — in marketing, in code, in README.
 
-The Honest Limits section is the brand. Emulated signing is called emulated. Hardware in firmware validation is not "hardware-backed signing." Illustrative deployment profiles carry their disclaimer. "Aligned to SSDF / EU AI Act," never "certified" until a third party says so. The site, the PyPI page, the action README, and the sales deck must say the identical thing — the buyer we want is trained to find the gap, and finding one costs us the category. Unfalsifiable copy ("100% of AI writes") is a bug; file it and fix it like one.
+The Honest Limits section is the brand. Emulated signing is called emulated. Hardware prototype (bench) is not "hardware-backed signing ships today" and is never GA until productized. Illustrative deployment profiles carry their disclaimer. "Aligned to SSDF / EU AI Act," never "certified" until a third party says so. The site, the PyPI page, the action README, and the sales deck must say the identical thing — the buyer we want is trained to find the gap, and finding one costs us the category. Unfalsifiable copy ("100% of AI writes") is a bug; file it and fix it like one.
 
 ### 4. Dogfood the provenance or don't ship it.
 
@@ -35,7 +35,7 @@ The market's live pain: unattributed machine-speed writes are breaking platforms
 - **Evidence Pack** as the flagship artifact. Signed, versioned, downloadable, self-verifying, mapped field-by-field to the frameworks we name. Optimize its legibility before optimizing anything else.
 - **Verification everywhere git goes.** CI gate hardening, server-side enforcement for self-hosters, offline verify, browser verify. Verification speed, determinism, and zero-false-positive behavior are the performance metrics that matter.
 - **Forge-agnostic integrations** as first-class citizens: the same install, the same gate, the same export on GitHub, GitLab, and Forgejo/Gitea. Treat every integration doc as a landing page.
-- **Hardware as device-bound identity** — activation, custody, revocation, offboarding. One clear story. The secure-element signing path graduates from preview only when firmware validation passes, and not one sentence sooner.
+- **Hardware as device-bound identity** — activation, custody, revocation, offboarding. One clear story. The secure-element signing path is a bench-validated prototype for pilot evaluation; it graduates to GA only when productized, and not one sentence sooner.
 - **Crawlability and machine-readability** of everything public. Specs, docs, llms.txt, sitemaps, plain-markdown paths. When a buyer's AI assistant is asked "what is Matrix Scroll," our own text must be the answer.
 
 ## Hold — maintained, not grown

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/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.0"
+pip install "matrixscroll==0.6.1"
 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.0"
+    matrixscroll-version: "0.6.1"
     require-mode: emulated
 ```
 

{matrixscroll-0.6.0 → matrixscroll-0.6.1}/docs/POC2_AUDIT.md

@@ -42,7 +42,7 @@
 | ------- | --- | ------------- |
 | SSX360 | https://ssx360.com | Vercel production |
 | Matrix Scroll | https://matrixscroll.com | Vercel production |
-| PyPI | https://pypi.org/project/matrixscroll/0.6.0/ | v0.6.0 (ssx360 CLIs on PyPI) |
+| PyPI | https://pypi.org/project/matrixscroll/0.6.1/ | v0.6.0 (ssx360 CLIs on PyPI) |
 
 ## 7. Reviewer artifacts