synapsek-claims 0.1.0__tar.gz

synapsek_claims-0.1.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.

synapsek_claims-0.1.0/MANIFEST.in

@@ -0,0 +1,8 @@
+include LICENSE
+include README.md
+include RELEASE-CHECKLIST.md
+include examples/trusted-issuer.pub
+recursive-include docs *.md
+recursive-include tests *.py
+recursive-include examples *.json *.md *.jsonl *.py *.txt
+recursive-exclude examples *.pt

synapsek_claims-0.1.0/PKG-INFO

@@ -0,0 +1,158 @@
+Metadata-Version: 2.4
+Name: synapsek-claims
+Version: 0.1.0
+Summary: SVC — Synapsek Verified Claims: neutral, cryptographic verification of measured claims about AI artifacts and pipelines
+Author: Synapsek Labs
+License: Apache-2.0
+Keywords: ai,attestation,verification,reproducibility,llm,supply-chain
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography>=41
+Provides-Extra: test
+Requires-Dist: pytest>=7; extra == "test"
+Dynamic: license-file
+
+# synapsek-claims (svc)
+
+**Verified claims for AI artifacts.** A framework-agnostic, cryptographically
+verifiable layer that signs *measured quality claims* about any AI artifact or
+pipeline — and lets a buyer **re-derive them with one command**.
+
+You have seen vendor-reported benchmark numbers. You may have re-run one and
+found it did not come out the same. `svc` is the missing referee:
+
+- the issuer signs a claim document: measured values, the exact evidence
+  traces, the exact artifacts and code used, the pinned environment;
+- the buyer runs **one command** that (1) checks the signature against a
+  trusted key, (2) re-hashes every pinned file, (3) re-checks every evidence
+  trace (sha256 + Merkle), (4) **recomputes every claimed number from the
+  evidence**, optionally **re-executes the pinned evaluation**, and (5)
+  re-derives every pass/fail status from the documented thresholds.
+
+If the issuer claimed more than the numbers support, verification **fails**.
+That last property — anti-overclaiming by construction — is what makes this
+different from a signed eval dashboard.
+
+```
+$ svc verify claim.json --trusted-pubkey issuer.pub --base-dir . --rerun
+=== SVC VERIFY synapsek.claim/knowledge-encoder-dedup/v3b-seed1 ===
+  [PASS] L1 authenticity: valid
+  [PASS] L2 integrity: 10 files match
+  [PASS] L3 evidence: 2 traces match
+  [PASS] L4 soundness: 1/1 values recomputed
+  [PASS] L4b rerun: 1 claims re-executed
+  [PASS] L5 claims: statuses + recommendations re-derived
+  claim dedup_spearman: value=0.4172424238214698 recomputed=0.4172424238214698 status=proven [OK]
+RESULT: PASS — all layers verified; claims re-derived
+```
+
+## What a claim is
+
+A claim is a JSON document:
+
+- **subject** — what is being claimed about: files (hashed) + evidence traces
+  (hashed + Merkle-rooted);
+- **pinned** — the environment, dataset, and config the measurement used;
+- **claims** — each has a metric, a measured `value`, a documented
+  `threshold`, a `status` (`proven` / `not_proven`), and a `derivation`
+  (a rule that tells the buyer how to recompute the value from the evidence);
+- **recommendation** — which labels are recommended (only the proven ones may
+  be) and which are explicitly not;
+- **disclosures** — honest limitations;
+- **signature** — Ed25519 over the canonical form of everything above.
+
+Derivation rules are a tiny grammar, **no arbitrary code in rules**:
+
+| rule | meaning |
+|---|---|
+| `field:<name>\|mean` / `field:<name>\|last` | aggregate a field over an evidence trace |
+| `file:<path>#<field>` | read a field from a pinned JSON file |
+| `script:<path>#<id>` | run `python3 <path>` in the claim dir; read `id` from its final JSON stdout |
+| `attested:<json.path>` | read a value from a pinned attestation document |
+
+`script:` is the only rule that executes code — it is the issuer's pinned
+evaluation script, fully visible to the buyer, and it only runs if the buyer
+passes `--rerun` (or explicitly accepts it). The buyer reads the script before
+it can ever run.
+
+## Quickstart
+
+```bash
+pip install synapsek-claims        # or: pip install -e .
+
+# buyer side
+svc verify examples/pipeline-dedup/claim.json \
+    --trusted-pubkey examples/trusted-issuer.pub \
+    --base-dir examples/pipeline-dedup \
+    --rerun                          # also re-execute the pinned eval (CPU)
+
+# issuer side
+svc keygen --out-dir ./keys         # new attestation authority
+svc attest skeleton.json --key keys/issuer_ed25519 --base-dir ./claimdir
+svc registry add registry/registry.json --claim claimdir/claim.json --issuer-id me
+```
+
+Exit code 0 = PASS, 1 = FAIL. `--json` gives a machine-readable report.
+
+## The two working examples
+
+Both are real, measured, and verify PASS as shipped:
+
+1. **`examples/pipeline-dedup`** — a knowledge encoder (2-layer transformer +
+   Perceiver resampler, K=128 latents). Claims Spearman 0.4172 between latent
+   similarity and token Jaccard over a pinned 100-doc holdout (4950 pairs,
+   full pair-level evidence trace). `--rerun` re-executes the pinned eval on
+   CPU and reproduces the value **bit-exactly**.
+2. **`examples/cartridge-v11`** — the Synapsek knowledge cartridge v1.1,
+   wrapped through the same pipeline as its full attestation. 13 claims: the
+   4 v0 gist dimensions recorded as **not_proven** (below pre-registered bars —
+   an honest claim is allowed to say "no"), and 9 QA-fidelity numbers
+   re-derived from the pinned per-item traces, including cross-family results
+   (a 7B model decoding latents produced by a small encoder).
+
+## What this is NOT
+
+- **Not a model-signing tool.** OpenSSF/Sigstore-style integrity signing is a
+  commodity and a good one; `svc` is complementary. It signs *quality claims*
+  and proves they re-derive, not just that the bytes did not change.
+- **Not a benchmarking service.** We pin *your* evaluation. `svc` cannot make
+  a bad number look good, and it is structurally hostile to one.
+- **Not a quality certifier.** A `proven` claim means: this measured value is
+  reproducible from the pinned evidence at/above the documented threshold.
+  The threshold is the issuer's documented commitment, and the buyer is free
+  to think it is low.
+
+## Security model
+
+- Ed25519 over deterministic canonical bytes (sorted keys, compact JSON).
+- Only the **public** key ships with claims; the private key stays with the
+  issuer. Buyers verify against a trusted public key held out-of-band;
+  `issuer.public_key` must equal the trusted key (no rogue self-issuance).
+- The registry is a trust anchor: claim id → issuer key → claim hash.
+- Every layer is independently checkable; the report says which layer failed
+  and why.
+
+## Tests
+
+```bash
+python3 -m pytest tests/ -q     # 16 tests: roundtrip, tamper L1/L2/L3/L4b/L5, registry
+```
+
+## Layout
+
+```
+src/svc/            canonical, crypto, schema, rules, rerun, claim, verify, registry, cli
+tests/              16-test suite
+examples/pipeline-dedup/   real claim, rerunnable on CPU (artifact/encoder.pt is a release asset)
+examples/cartridge-v11/    real claim wrapping the v1.1 attestation + QA traces
+docs/DESIGN.md      schema, threat model, design decisions
+RELEASE-CHECKLIST.md  10-minute publish handoff
+```
+
+## License
+
+Apache-2.0. See LICENSE.

synapsek_claims-0.1.0/README.md

@@ -0,0 +1,140 @@
+# synapsek-claims (svc)
+
+**Verified claims for AI artifacts.** A framework-agnostic, cryptographically
+verifiable layer that signs *measured quality claims* about any AI artifact or
+pipeline — and lets a buyer **re-derive them with one command**.
+
+You have seen vendor-reported benchmark numbers. You may have re-run one and
+found it did not come out the same. `svc` is the missing referee:
+
+- the issuer signs a claim document: measured values, the exact evidence
+  traces, the exact artifacts and code used, the pinned environment;
+- the buyer runs **one command** that (1) checks the signature against a
+  trusted key, (2) re-hashes every pinned file, (3) re-checks every evidence
+  trace (sha256 + Merkle), (4) **recomputes every claimed number from the
+  evidence**, optionally **re-executes the pinned evaluation**, and (5)
+  re-derives every pass/fail status from the documented thresholds.
+
+If the issuer claimed more than the numbers support, verification **fails**.
+That last property — anti-overclaiming by construction — is what makes this
+different from a signed eval dashboard.
+
+```
+$ svc verify claim.json --trusted-pubkey issuer.pub --base-dir . --rerun
+=== SVC VERIFY synapsek.claim/knowledge-encoder-dedup/v3b-seed1 ===
+  [PASS] L1 authenticity: valid
+  [PASS] L2 integrity: 10 files match
+  [PASS] L3 evidence: 2 traces match
+  [PASS] L4 soundness: 1/1 values recomputed
+  [PASS] L4b rerun: 1 claims re-executed
+  [PASS] L5 claims: statuses + recommendations re-derived
+  claim dedup_spearman: value=0.4172424238214698 recomputed=0.4172424238214698 status=proven [OK]
+RESULT: PASS — all layers verified; claims re-derived
+```
+
+## What a claim is
+
+A claim is a JSON document:
+
+- **subject** — what is being claimed about: files (hashed) + evidence traces
+  (hashed + Merkle-rooted);
+- **pinned** — the environment, dataset, and config the measurement used;
+- **claims** — each has a metric, a measured `value`, a documented
+  `threshold`, a `status` (`proven` / `not_proven`), and a `derivation`
+  (a rule that tells the buyer how to recompute the value from the evidence);
+- **recommendation** — which labels are recommended (only the proven ones may
+  be) and which are explicitly not;
+- **disclosures** — honest limitations;
+- **signature** — Ed25519 over the canonical form of everything above.
+
+Derivation rules are a tiny grammar, **no arbitrary code in rules**:
+
+| rule | meaning |
+|---|---|
+| `field:<name>\|mean` / `field:<name>\|last` | aggregate a field over an evidence trace |
+| `file:<path>#<field>` | read a field from a pinned JSON file |
+| `script:<path>#<id>` | run `python3 <path>` in the claim dir; read `id` from its final JSON stdout |
+| `attested:<json.path>` | read a value from a pinned attestation document |
+
+`script:` is the only rule that executes code — it is the issuer's pinned
+evaluation script, fully visible to the buyer, and it only runs if the buyer
+passes `--rerun` (or explicitly accepts it). The buyer reads the script before
+it can ever run.
+
+## Quickstart
+
+```bash
+pip install synapsek-claims        # or: pip install -e .
+
+# buyer side
+svc verify examples/pipeline-dedup/claim.json \
+    --trusted-pubkey examples/trusted-issuer.pub \
+    --base-dir examples/pipeline-dedup \
+    --rerun                          # also re-execute the pinned eval (CPU)
+
+# issuer side
+svc keygen --out-dir ./keys         # new attestation authority
+svc attest skeleton.json --key keys/issuer_ed25519 --base-dir ./claimdir
+svc registry add registry/registry.json --claim claimdir/claim.json --issuer-id me
+```
+
+Exit code 0 = PASS, 1 = FAIL. `--json` gives a machine-readable report.
+
+## The two working examples
+
+Both are real, measured, and verify PASS as shipped:
+
+1. **`examples/pipeline-dedup`** — a knowledge encoder (2-layer transformer +
+   Perceiver resampler, K=128 latents). Claims Spearman 0.4172 between latent
+   similarity and token Jaccard over a pinned 100-doc holdout (4950 pairs,
+   full pair-level evidence trace). `--rerun` re-executes the pinned eval on
+   CPU and reproduces the value **bit-exactly**.
+2. **`examples/cartridge-v11`** — the Synapsek knowledge cartridge v1.1,
+   wrapped through the same pipeline as its full attestation. 13 claims: the
+   4 v0 gist dimensions recorded as **not_proven** (below pre-registered bars —
+   an honest claim is allowed to say "no"), and 9 QA-fidelity numbers
+   re-derived from the pinned per-item traces, including cross-family results
+   (a 7B model decoding latents produced by a small encoder).
+
+## What this is NOT
+
+- **Not a model-signing tool.** OpenSSF/Sigstore-style integrity signing is a
+  commodity and a good one; `svc` is complementary. It signs *quality claims*
+  and proves they re-derive, not just that the bytes did not change.
+- **Not a benchmarking service.** We pin *your* evaluation. `svc` cannot make
+  a bad number look good, and it is structurally hostile to one.
+- **Not a quality certifier.** A `proven` claim means: this measured value is
+  reproducible from the pinned evidence at/above the documented threshold.
+  The threshold is the issuer's documented commitment, and the buyer is free
+  to think it is low.
+
+## Security model
+
+- Ed25519 over deterministic canonical bytes (sorted keys, compact JSON).
+- Only the **public** key ships with claims; the private key stays with the
+  issuer. Buyers verify against a trusted public key held out-of-band;
+  `issuer.public_key` must equal the trusted key (no rogue self-issuance).
+- The registry is a trust anchor: claim id → issuer key → claim hash.
+- Every layer is independently checkable; the report says which layer failed
+  and why.
+
+## Tests
+
+```bash
+python3 -m pytest tests/ -q     # 16 tests: roundtrip, tamper L1/L2/L3/L4b/L5, registry
+```
+
+## Layout
+
+```
+src/svc/            canonical, crypto, schema, rules, rerun, claim, verify, registry, cli
+tests/              16-test suite
+examples/pipeline-dedup/   real claim, rerunnable on CPU (artifact/encoder.pt is a release asset)
+examples/cartridge-v11/    real claim wrapping the v1.1 attestation + QA traces
+docs/DESIGN.md      schema, threat model, design decisions
+RELEASE-CHECKLIST.md  10-minute publish handoff
+```
+
+## License
+
+Apache-2.0. See LICENSE.

synapsek_claims-0.1.0/RELEASE-CHECKLIST.md

@@ -0,0 +1,65 @@
+# Release checklist — synapsek-claims v0.1.0
+
+Prepared 2026-10-17. All build/verify steps below were already executed on
+Cherry; the remaining ~10 minutes are YOUR calls (org, account, publish).
+
+## Already done (on Cherry, /root/synapsek-verified-claims)
+
+- [x] package builds: `pip install -e .` clean, `python3 -m compileall` clean
+- [x] 16/16 tests pass (roundtrip, tamper L1/L2/L3/L4b/L5, registry, canonical)
+- [x] example 1 sealed + verified PASS (incl. bit-exact CPU rerun) + tamper-tested
+- [x] example 2 sealed + verified PASS (13 claims: 4 not_proven + 9 proven) + tamper-tested
+- [x] both claims registered in registry/registry.json under issuer
+      synapsek.compiler/v1 (public key MHYuRK-KEKtx3w-MQYnEJ7oiHWWJsJfP0WzNwn_Fi1M)
+- [x] leak scan: no private key material anywhere in the tree (public key only)
+
+## Your steps (~10 min)
+
+1. **Review** (2 min): open `examples/*/claim.json` and the two
+   `svc verify ... --rerun` outputs above. The claim text is the public face
+   of the project — read the disclosures.
+2. **GitHub** (3 min): create the org/repo `synapsek/synapsek-verified-claims`
+   (public). From the tree:
+   ```
+   cd /root/synapsek-verified-claims
+   git init -b main && git add -A && git commit -m "synapsek-claims v0.1.0"
+   git remote add origin git@github.com:synapsek/synapsek-verified-claims.git
+   git push -u origin main
+   git tag v0.1.0 && git push origin v0.1.0
+   ```
+   (`.gitignore` already excludes the 160MB `encoder.pt`, Python cache,
+   `.svc_*` rerun logs.)
+3. **Release asset** (2 min): GitHub → repo → Releases → `v0.1.0` → attach
+   `examples/pipeline-dedup/artifact/encoder.pt` (160MB). Fresh clones get a
+   README pointer; verify of example 1 needs that asset placed back into
+   `artifact/encoder.pt`.
+4. **PyPI** (3 min): create the account/owner (suggested: user `synapsek` or
+   `synapsek-claims`; project is `synapsek-claims`, already named in
+   pyproject). Then:
+   ```
+   pip install build twine
+   python -m build            # -> dist/synapsek_claims-0.1.0.*
+   twine upload dist/*
+   ```
+   Verify: `pip install synapsek-claims --dry-run` from a clean venv, or
+   `pip download synapsek-claims`.
+5. **Key ceremony (optional but recommended)**: publish the trusted issuer
+   public key + the exact `svc verify` commands as a repo page or
+   `TRUST.md`, so buyers know which key to trust and how to get it out-of-band
+   (this file itself is that artifact: `examples/trusted-issuer.pub`).
+6. **Announce** (1 min): one-paragraph blurb — "verified claims for AI
+   artifacts; one command re-derives the numbers" + the two example links.
+
+## Non-goals for v0.1.0 (do not promise in the announcement)
+
+- No public registry *service* yet (the registry is a portable JSON file;
+  endpoint comes later).
+- No GPU/CPU cross-device tolerance guarantees (example 1's rerun is
+  CPU-bit-exact on the pinned env; other envs may need a documented tolerance).
+- No agent-execution attestation yet (roadmap, v0.2+).
+
+## Rollback
+
+Unpublish is one `twine`/GitHub action per surface; the tag is the anchor.
+Nothing here touches the RunPod pod, the compiler key, or any model weights
+beyond the one example artifact.

synapsek_claims-0.1.0/docs/DESIGN.md

@@ -0,0 +1,98 @@
+# SVC design notes (schema v0.1)
+
+## Threat model
+
+Attacker/defect goals, and the layer that stops each:
+
+| threat | stopped by |
+|---|---|
+| claim document edited after signing (value, status, threshold) | L1 (signature) |
+| issuer swap (rogue key self-attesting) | L1 (`issuer.public_key` must equal trusted key) |
+| artifact/weights/code replaced in the claim dir | L2 (per-file sha256) |
+| evidence trace edited, reordered, truncated | L3 (file sha256 + item count + Merkle root) |
+| claimed value not actually supported by the evidence | L4 (value recomputed from evidence by the derivation rule) |
+| claimed value not actually reproducible by re-executing the pinned eval | L4b (`--rerun`) |
+| status overstated vs value+threshold | L5 (status re-derived) |
+| recommendation includes a not-proven label / omits a not-proven label | L5 (recommendation set re-derived) |
+| claim circulated that was never registered | `--registry` hash match |
+
+What the layers do **not** stop: a buyer running a `script:` rule whose
+contents they did not read; an evaluation script that measures something
+different from what the metric name implies (mitigation: the script is pinned,
+visible, and small by convention); a threshold chosen to be trivially low
+(mitigation: it is disclosed and the buyer judges it).
+
+## Canonical form
+
+`canonical_bytes(obj) = json.dumps(obj, sort_keys=True, separators=(",", ":"),
+ensure_ascii=False).encode("utf-8")`. The signature covers everything except
+the `signature` field itself. Same byte format as the Synapsek v1.1
+attestation engine — an SVC claim and a v1.1 attestation over the same JSON
+object share canonical bytes, so the ecosystems interoperate.
+
+## Evidence model
+
+Evidence is JSONL (one JSON object per line; a single-line JSON file is a
+valid 1-item trace). Each trace carries `sha256` (whole file), `n_items`, and
+`merkle_root` (order-sensitive: leaf = sha256(canonical(item)), odd nodes
+duplicated). Per-item traces (e.g. one row per doc pair, or one row per QA
+item) give the buyer auditable granularity; the Merkle root makes even a
+single swapped row visible.
+
+## Claim lifecycle
+
+1. **measure** — issuer runs the pinned eval on the pinned dataset/artifacts;
+   the eval writes evidence traces (per-item rows) and prints the summary.
+2. **seal** — `svc attest` fills every file hash, trace hash, Merkle root and
+   item count from disk, re-derives every claim `status` from `value` +
+   `threshold` (the skeleton's status is overwritten — the issuer cannot
+   hand-pick), hashes the config, and signs.
+3. **register** — `svc registry add` stores claim id → issuer key → claim
+   hash. The registry file is plain JSON and portable (same shape as the v11
+   attestation registry).
+4. **verify** — `svc verify` (buyer). With `--registry`, the claim document is
+   first matched against the registry entry, then the 5 layers run. With
+   `--rerun`, pinned eval commands are re-executed and their outputs compared
+   within the claim's tolerance.
+
+## Rule grammar (deliberately tiny)
+
+No code evaluation inside rules. Four forms (see README table). `script:`
+runs `python3 <path>` with cwd = claim dir and a timeout; its **final stdout
+line must be one JSON object** and the named field must be numeric. This
+keeps the recompute path auditable: the buyer sees exactly which file runs,
+with which cwd, and what field is compared.
+
+## Recommendation semantics
+
+- `recommended_for` must **exactly** equal the sorted set of labels of
+  proven claims (over-recommending fails, under-recommending fails);
+- `not_recommended_for` must be a **superset** of the labels of not-proven
+  claims (extra entries allowed — use them for honest scope limits).
+
+This is the anti-overclaiming core: a vendor cannot ship a claim whose
+numbers fail its own thresholds while still marketing the label.
+
+## Scale honesty
+
+Values and thresholds live in whatever scale the derivation rule produces.
+If the evidence is 0-1 and the claim value is percent-based (or vice versa),
+L4 fails — a good failure, because scale confusion is exactly how vendor
+numbers get misread. Claim `unit` fields document the scale.
+
+## Relationship to the v1.1 attestation
+
+The cartridge attestation signs the whole cartridge qualification
+(provenance, fidelity, 24 evidence traces). An SVC claim about the same
+cartridge *wraps* it: the attestation document is a pinned file (role
+`attestation`), `attested:` rules re-derive values from it, and QA-fidelity
+claims re-derive directly from the same per-item traces. Chain of trust:
+SVC claim → (hash) → v1.1 attestation → (hash) → weights.
+
+## v0.2 ideas (not shipped)
+
+- public registry endpoint + claim URI scheme
+- verifiable agent-execution records (tool calls, approvals, audit log
+  entries as evidence traces)
+- batch verify (many claims, one report)
+- tolerance policies for GPU/CPU drift