Repository navigation
Releases
TACET 0.3.0 — PNX profile, first PyPI release
TACET 0.3.0 — PNX: Proof of Non-Exfiltration
First release available from PyPI via Trusted Publishing:
pip install crovia-tacet-operator "crovia-seal @ git+https://github.com/croviatrust/crovia-seal#subdirectory=reference/python"
tacet-operator verify <proof>.seal.jsonNew
- PNX profile
crovia.pnx.v1(tacet/PNX.md,tacet/egress.py): an egress witness fingerprints an agent's outbound bytes (salted 32-byte k-grams, winnowing window 16) into the TACET sparse Merkle map and signs a run sheet; the operator proves per protected asset non-inclusion (or inclusion) against the run root; verification is offline and recomputes everything when the assets are supplied. Any shared substring of 47 bytes or more is always detected; shorter assets are reported aspartial/undetectableand never counted as clean. 7 new tests. GROWTH.md: thesis, build order, public/paid boundary.
Changed
- Packages published to PyPI as
crovia-tacetandcrovia-tacet-operator(one GitHub environment per project). - Conformance vectors regenerated for 0.3.0 (47 Python cases, 20 Node cases, unchanged semantics).
Wire format of epoch sheets, snapshots, silence proofs and Seal wrapping is unchanged from 0.2.0.
TACET 0.2.0 — Bitcoin anchors, verifiable without a node
New: SPEC §8.6, anchor verification without a Bitcoin node
Until now the OpenTimestamps step needed the ots client and a local Bitcoin node (ots verify refuses to finish without one), so nearly every verifier saw the anchors as unchecked — or, if the client was installed, as failed.
Both TACET verifiers now do the check themselves:
tacet.ots(reference, standard library only) parses a detached.ots, replays the operation tree from the file digest, and collects everyBitcoinBlockHeaderAttestation: the 32-byte message at that leaf is the block's merkle root. The proof verifies ifffile_digest == SHA-256(sheet_hash bytes)and the merkle root atclosed.block_heightmatches the block header from a header source the verifier chooses (a node, a headers file, or by default a public explorer).site/registry/seal/verify/ots-verify.jsis the same logic in plain JS on WebCrypto; with network checks on, the browser verifier fetches each.otsand matches it to the block header from mempool.space / blockstream.info (both CORS-enabled).ots_checkis now tri-state:True/False/None. Unchecked (no header source reachable) is a warning that names the height and expected merkle root, never a failure.
Conformance
- New static vector
ots_001_live_anchors.json: the real.otsproofs of TACET epochs 0–2, confirmed in Bitcoin blocks 967736 and 967740, with sheet hashes, file digests and merkle roots — checkable against any node or explorer. Positive cases plus wrong sheet hash, wrong height, truncated proof, and no header source. - 47 Python cases, 20 browser cases, both green in CI.
Also
tacet-operator verifyno longer needsopentimestamps-client.- Operator: anchors refreshed every 2 h; featured proofs re-issued as soon as a sheet closes.
$ tacet-operator verify Qwen__Qwen3-32B.seal.json
"ok": true, "strength_verified": 2, "silence_days": "0.12",
"anchors": ["block 967736 merkle root a27c668a… matches the proof", …, "block 967740 merkle root a41b0f50… matches the proof"],
"warnings": []
TACET 0.1.2
Changed
silence_daysis truncated, never rounded (SPEC §9).floor(silence_seconds*100/86400)/100, rendered with exactly two decimals, integer arithmetic only. The Python reference and the in-browser verifier now produce the same string byte-for-byte and compare it with==(previously the browser tolerated ±0.005 and could display0.13where the reference said0.12).- Operator:
refresh-anchorsre-issues the featured proofs as soon as a sheet closes in Bitcoin, so published silence figures follow anchoring within the refresh cadence instead of the daily job. - Release workflow: the PyPI publish job is skipped (not failed) until Trusted Publishing is configured.
Conformance
- 34 reference cases, 10 browser-verifier cases; vectors regenerated (
tacet.version= 0.1.2).
Verify a live proof
pip install -e tacet/reference/python -e tacet/operator
curl -sO https://croviatrust.com/registry/data/tacet/proofs/Qwen__Qwen3-32B.seal.json
tacet-operator verify Qwen__Qwen3-32B.seal.json
or in the browser: https://croviatrust.com/registry/seal/verify/?url=https://croviatrust.com/registry/data/tacet/proofs/Qwen__Qwen3-32B.seal.json
TACET 0.1.1 — verify in the browser
TACET 0.1.1
Second verifier. A TACET proof can now be verified in the browser with nothing installed: /registry/seal/verify/?url=<proof>. site/registry/seal/verify/tacet-verify.js (plain JS on WebCrypto, <300 lines) re-does SPEC §8.5 independently of the Python reference: seal binding, sheet signatures and hash chain, the empty slot under every depth-256 root, observer signatures and RFC 6962 inclusion of each negative snapshot, silence recomputation under the monotonicity rule, witness quorum, plus opt-in network checks (drand round bytes, published trust root). The OpenTimestamps step remains command-line only. Both verifiers run against the same vectors in CI (tacet/conformance/run_conformance_js.cjs).
Conformance.
- Fixture drand rounds are now the real rounds for the fixture epochs on chain
8990e7a9…; a verifier that enforces §8.5 step 2 accepts the vectors. (0.1.0 vectors used placeholder rounds and would be rejected by such a verifier.) - New
wrapped_002_invalid.json: six invalid proofs under a valid outer Seal. A verifier that stops at the Seal signature accepts them; a conformant one must reject every case. Runner: 34 cases.
Spec. §7.3: a predicate MUST state what it does not recognise; the reference predicate 1.0.0 is English-only, stated in the spec, on the TACET page and in #3.
Operator. publish writes shields.io endpoint badges under /registry/data/tacet/badges/ (epochs, models, negative, latest) — live figures for READMEs, defined by CANON §4.
Repository. SECURITY.md states TACET's claims and non-goals; issue forms for verifier failures, predicate proposals and witnesses; roadmap issues #2–#6.
Wire compatibility: unchanged. Sheets, snapshots and proofs from 0.1.0 verify under 0.1.1; generator.version in new seals reads 0.1.1.
TACET v0.1.0 — verifiable silence, live
First production release of TACET — verifiable silence for AI training disclosure.
The live log started at 2026-09-19T18:00:00Z (epoch 0) on croviatrust.com: https://croviatrust.com/registry/tacet/
What is in this release
tacet/SPEC.mdv0.1-draft (CC0): sparse Merkle map, epoch sheets with drand/Bitcoin temporal sandwich, surface snapshots and public predicates, silence proofs at three strength levels, the monotonicity rule, Seal wrapping, commit-then-reveal for providers.tacet/reference/python(Apache-2.0): reference implementation, 28 unit tests.tacet/conformance: deterministic vectors and a 28-case runner to port to other languages.tacet/operator: the production operator —run-epoch,refresh-anchors,publish,prove,verify— with the first public predicatecrovia.pred.hf-card-training-data1.0.0 and real-card vectors.CANON.md/canon/canon.json: single source of truth for every Crovia surface;tools/audit_surfaces.pyaudits the live site against it.
Verify a live proof
pip install -e countersign/tacet/reference/python -e crovia-seal/reference/python -e countersign/tacet/operator
curl -sO https://croviatrust.com/registry/data/tacet/proofs/mistralai__Mistral-7B-v0.1.seal.json
tacet-operator verify mistralai__Mistral-7B-v0.1.seal.jsonKnown limits
- Proofs are level 2 (surface-silence). Level 3 needs independent witnesses — open an issue to run one.
- One predicate, one surface family (Hugging Face model cards).
- Silence figures are 0.00 until the first epochs are confirmed in Bitcoin; that is the monotonicity rule working as intended.