swt3-ai 0.6.6 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +26 -18
  3. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 719cc19c6202c043713079ad509eb09a4c729393ecf7488e35c6b122660e241c
4
- data.tar.gz: 388ee4b8e7ca9810490d186066840808a088d2766546f57c2651a3d40f4fc61f
3
+ metadata.gz: f796446c334f2e8d057bd6f0233a8c06e7e69fb4c1dfddc4fcc113922b1fecea
4
+ data.tar.gz: 6d4e9d4dddc88968b5eccc5727a9ea23e3229558737b1fa5aa24669294cb6166
5
5
  SHA512:
6
- metadata.gz: 94f83a0f5ce92842abfd3bb615a412527828bff511e8179ee5bb6416cd8b6758470aae7820e9ec6274d97ed5803cbf2b599680f9ad301e0549e4f966b55093c4
7
- data.tar.gz: 1475c12c91eb99198fef45ce8da074349d55a8d1f426a3b43c58b06da6ce7f4a8d10e200702f6555eb7285f5c40736c8988c2879e5f0f840f2c8e8d8db8c2438
6
+ metadata.gz: 915aa33a2e78e682c0a671f3740368b708e3c35a8f9793f9ce5c491d8e92f5117849b7e9edc27df6e979e9d449630519629594b920daf8e65c43981c2e0454a8
7
+ data.tar.gz: ac360e61a803cc6f32d539d6ede8de83a89be6180a720face17a04490a1df2f506764d5b53b4bb4dd95a497357592879d2a8d1cbbcb26ee384182fa530f6ed4f
data/README.md CHANGED
@@ -11,37 +11,45 @@ Built for platform engineers who need to bolt compliance witnessing onto product
11
11
 
12
12
  EU AI Act GPAI transparency obligations enforced since **August 2, 2026**. High-risk enforcement follows **December 2, 2027**. This SDK gives you the cryptographic primitives for both.
13
13
 
14
- ## What's New in v0.6.6
15
-
16
- Supply chain accountability. Four new procedures, a CI/CD gate action, and OTel GenAI conventions across the ecosystem. Every improvement flows through to Ruby because fingerprints are identical across all 10 languages.
14
+ ## What's New in v0.7.1
17
15
 
18
- ### 4 New Procedures
16
+ MCP security is under fire. OWASP published the MCP Top 10 in 2026 -- 30-82% of MCP servers are vulnerable to tool poisoning, insufficient authentication, and shadow server proliferation. v0.7.1 adds three new procedures (AI-MCP.2, AI-MCP.3, AI-MCP.4) that close the remaining OWASP gaps. SWT3 is now the first protocol to cover all 10 OWASP MCP risks with cryptographic evidence. Every new anchor type verifies with the existing `Swt3Ai::Fingerprint.mint_fingerprint` method -- no gem update required.
19
17
 
20
- **AI-PROV.1 (Model Provenance Chain):** Records model lineage -- base model, training pipeline, fine-tuning ancestry. The G7 Hiroshima AI SBOM framework requires provenance documentation. A `parent_model_fingerprint` parameter on model weight/adapter/quantization methods links derivative models to their ancestors. Provenance anchors verify with `mint_fingerprint` like any other anchor.
18
+ **Why this matters for Ruby:** Rails dashboards displaying compliance posture and Sidekiq workers processing witness data will encounter the new MCP security anchors (tool integrity, server auth, server discovery) as your Python and TypeScript pipelines adopt them. The anchors are structurally identical to inference anchors -- same `mint_fingerprint` verification, same `WitnessPayload` structure. Your Ruby reporting layer can surface MCP security findings (schema drift detected, unauthenticated server, shadow server) without any gem changes.
21
19
 
22
- **AI-DEL.2 (Delegation Boundary):** Records what an agent is NOT permitted to do -- blocked tools, restricted scopes, escalation triggers. EU AI Act Art. 14 requires documented AI system limitations. Where AI-DEL.1 tracks permissions, AI-DEL.2 tracks constraints.
20
+ ### 3 New Procedures
23
21
 
24
- **AI-DENSITY.1 (Anchor Density):** Records the ratio of witnessed events to total events over a time window. Catches the slow coverage drift from 100% to 2% that nobody notices until the audit. A DensityEnforcer class in Python and TypeScript auto-fires density anchors when coverage drops.
22
+ - **AI-MCP.2** (Tool Integrity Attestation): Detects tool schema drift between connect and invoke. OWASP MCP-03.
23
+ - **AI-MCP.3** (Server Auth Attestation): Records auth method and verification. No auth = FAIL = IA-9 finding. OWASP MCP-07.
24
+ - **AI-MCP.4** (Server Discovery Attestation): Shadow server detection via allowlist check. OWASP MCP-09.
25
25
 
26
- **AI-MCP.1 (MCP Security Posture):** Evaluates 8 security properties of an MCP server connection. Records checks passed vs. total -- never which specific checks failed. NSA and CISA flagged 200,000+ vulnerable MCP deployments in 2026. This creates evidence that security was evaluated at connection time without becoming an attack map.
26
+ ### Updated Coverage
27
27
 
28
- **Why it matters for Ruby:** All four procedures produce anchors with the same fingerprint formula. Your Ruby code can verify any of these new anchor types with the existing `Swt3Ai::Fingerprint.mint_fingerprint` method -- no gem update required for verification. Your Rails dashboards and Sidekiq workers can process provenance and density anchors from the Python pipeline without any changes. When your Ruby monitoring layer ingests anchor data, the new procedure types are just more rows with the same verifiable fingerprint structure.
28
+ - 275 procedures across 77 namespaces (was 266/75)
29
+ - 63 MCP tools (was 59)
30
+ - 10 SDK languages with byte-identical output
31
+ - 77 framework crosswalks, 250 compliance guides
32
+ - ~2,950 tests passing across 5 languages
29
33
 
30
- ### GitHub Action
34
+ ## What's New in v0.7.0
31
35
 
32
- `tenova-labs/swt3-gate-action@v1` evaluates `.swt3-gate.yml` in CI/CD. Fails the build when coverage drops. Works with any language -- the gate checks anchors on the server, not the SDK in your repo. Your Gemfile-driven CI pipeline can enforce compliance gates without installing any additional gems.
36
+ AI does not run in a vacuum. It authenticates with service accounts, runs on hardware with supply chains, and consumes enough electricity to reshape power grids. v0.7.0 extends SWT3 down the full AI infrastructure stack with 22 new procedures across three families: credential governance (NHI), hardware supply chains (HBOM/DPP), and energy management (ADR). Every new anchor type verifies with the existing `Swt3Ai::Fingerprint.mint_fingerprint` method -- no gem update required.
33
37
 
34
- ### OTel GenAI Conventions (Python + TypeScript)
38
+ **Why this matters for Ruby:** Rails dashboards and Sidekiq workers are where AI data flows through enterprise systems. These new procedure families mean your Ruby monitoring layer can process credential rotation anchors, hardware inventory attestations, and demand response settlements alongside inference anchors -- same verifiable fingerprint structure, same verification call, new evidence categories. When your Python team witnesses service account rotation and your Ruby dashboard displays it, the fingerprint math is identical.
35
39
 
36
- The OpenTelemetry exporters now emit `gen_ai.system`, `gen_ai.request.model`, and token usage attributes following the OTel GenAI semantic conventions. If your Ruby service consumes OTel spans from the Python or TypeScript witness pipeline, these new attributes appear automatically.
40
+ ### 22 New Procedures
37
41
 
38
- ### Updated Coverage
42
+ **NHI (6):** Credential scope, lifecycle, privilege changes, rotation, delegation, revocation. **HBOM/DPP (10):** Hardware inventory, component lifecycle, thermal monitoring, water, PUE, supply chain provenance, battery health, charge cycles, degradation, end-of-life. **ADR (6):** Demand response events, baseline, curtailment, settlement, carbon credits, grid signals.
39
43
 
40
- - 118 procedures across 64 namespaces (+AI-PROV.1, AI-DEL.2, AI-DENSITY.1, AI-MCP.1)
41
- - 37 MCP tools (+witness_delegation_boundary, witness_anchor_density, witness_mcp_security, witness_model_provenance)
44
+ - 266 procedures across 75 namespaces (was 118/64)
45
+ - 59 MCP tools (was 37)
42
46
  - 10 SDK languages with byte-identical output
43
- - 36 framework crosswalks, 222 compliance guides
44
- - 2,825 tests passing across 5 languages
47
+ - 36 framework crosswalks, 237 compliance guides
48
+ - ~2,950 tests passing across 5 languages
49
+
50
+ ## What's New in v0.6.6
51
+
52
+ Supply chain accountability. Four new procedures, a CI/CD gate action, and OTel GenAI conventions across the ecosystem. Every improvement flows through to Ruby because fingerprints are identical across all 10 languages.
45
53
 
46
54
  ## What's New in v0.6.5
47
55
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: swt3-ai
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.6.6
4
+ version: 0.7.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - TeNova Labs
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2026-08-25 00:00:00.000000000 Z
11
+ date: 2026-09-08 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: Mint, verify, and sign SWT3 witness anchors for AI compliance. EU AI
14
14
  Act, NIST AI RMF, CMMC, SR 11-7. Cross-language parity with Python and TypeScript
@@ -52,6 +52,6 @@ requirements: []
52
52
  rubygems_version: 3.4.20
53
53
  signing_key:
54
54
  specification_version: 4
55
- summary: 'SWT3 AI Witness SDK: cryptographic attestation for AI inference. 118 procedures,
56
- 64 namespaces, 10 languages, 18 profiles, 21 integrations.'
55
+ summary: 'SWT3 AI Witness SDK: cryptographic attestation for AI inference and infrastructure
56
+ governance. 275 procedures, 9 namespaces, 10 languages, 77 frameworks.'
57
57
  test_files: []