tibet-conformance-vectors
Canonical conformance vectors and IETF drafts for the TIBET continuity ecosystem.
This package ships the reference inputs that external evaluators and implementers need to validate any tibet-* implementation against the documented spec, without requiring access to the Humotica internal monorepo.
Why it exists
Independent peer-reviewers (= Red Specter Security Research, RS-2026-001) flagged that the previous evaluation kit pointed at an internal monorepo path:
FIXTURE_BASE=$REPO_ROOT/sandbox/ai/codex/continuityd-test-packages/
which is not reachable from a fresh PyPI install on a clean Kali host. This package fixes that distribution gap. Conformance vectors and IETF drafts now ship together as a public, citable artifact.
What's inside
Conformance vectors (data/v1.jsonl)
Reference vectors for the five intake categories the TIBET stack distinguishes:
| Vector ID | Category | Scope |
|---|---|---|
trusted-001 |
trusted | transport-canonical |
triage-001 |
triage | transport-canonical |
reseal-001 |
reseal | transport-canonical |
quarantine-001 |
quarantine | transport-canonical |
reject-001 |
reject | transport-canonical |
Each vector carries:
vector_id,category,scope,vector_versionfilename(= semantic surface manifest fields)content_base64(= raw bytes that should produce the expected disposition)expected_audit(= the audit record an implementation MUST emit)
IETF drafts (drafts/)
draft-vandemeent-tibet-causal-time-00.txt— Causal Time Substratedraft-vandemeent-tibet-semantic-surface-manifest-00.txt— SSM routing layer
Both submitted to the IETF datatracker; this package keeps a stable local copy aligned with each vector revision.
Eval kit examples (examples/)
Runnable scripts that demonstrate how to validate an implementation:
python -m tibet_conformance_vectors.check /path/to/audit.jsonl
Install
pip install tibet-conformance-vectors
Programmatic use
from tibet_conformance_vectors import load_vectors, get_vector
# Load all vectors from the bundled v1 set
vectors = load_vectors("v1")
# Or pull a single vector by id
trusted = get_vector("trusted-001", version="v1")
print(trusted["expected_audit"]["disposition_hint"])
# → 'trusted-candidate'
How to validate an implementation
Given an implementation (= tibet-continuityd or any compatible daemon) and its audit JSONL output:
from tibet_conformance_vectors import check_audit
ok, report = check_audit(
audit_path="/var/log/tibet/continuityd-audit.jsonl",
vector_version="v1",
)
if ok:
print("PASS — all 5 vectors match expected disposition + causal chain")
else:
for failure in report.failures:
print(failure)
Versioning policy
Vectors are versioned independently from any implementation. A vector
version (e.g. v1) is immutable once published. New vectors get a
new version directory (v2/, v3/) so that historical conformance
claims remain reproducible.
If a vector turns out to be wrong, it gets marked deprecated in
metadata but the byte content stays unchanged.
Related packages
tibet-continuityd— reference daemon implementationtibet-drop— TBZ pack/verify primitivestibet-phantom— Identity-Bound Continuity Container
License
MIT — Humotica + Root AI + Codex (2026)
Enterprise
For private hub hosting, SLA support, custom integrations, or compliance guidance:
| Enterprise | enterprise@humotica.com |
| Support | support@humotica.com |
| Security | security@humotica.com |
Credits
Designed by Jasper van de Meent. Built by Jasper and Root AI as part of HumoticaOS.
Stack-positie: Groep conformance · Bootstrap = OSAPI-handshake naar tibet + jis (fail → snaft-rule + tibet-pol-rapport) · See STACK.md · See demo/golden-path/ for the spine end-to-end.
Metadata
Release files for tibet-conformance-vectors 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tibet_conformance_vectors-0.2.2.tar.gz | 30.9 kB | Without provenance | Details for tibet_conformance_vectors-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tibet_conformance_vectors-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for tibet_conformance_vectors-0.2.2-py3-none-any.whl |
Total release size: 67.7 kB
Release files / tibet_conformance_vectors-0.2.2.tar.gz
| Download URL | tibet_conformance_vectors-0.2.2.tar.gz |
|---|---|
| Size | 30.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25d4b293ce8ad7da6b311e9acd9e4da2dbcfa19bd0b28e747bd81a8b27f77c77
|
|
BLAKE2b-256 checksum How to use checksums |
065b875e069c9a2098173f19fe80169492328a91ece907bb4879b2ffa0615e78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / tibet_conformance_vectors-0.2.2-py3-none-any.whl
| Download URL | tibet_conformance_vectors-0.2.2-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b846273ae7c3d4e92c7dc324b7d5e335aa92c19e07c5576e4e152ce9bfb62abc
|
|
BLAKE2b-256 checksum How to use checksums |
63be3e2a24f0a0ee31d9331e2314da3463bff4f06fa51450381faf4ca3a5ccb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for tibet-conformance-vectors 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.