sigrank-standard (Python)
Portable five-metric core for AI operator token-processing efficiency. Conforms to the TTEOP v0.1-draft specification.
Note: The PyPI distribution name remains
sigrank-standardfor backward compatibility with existing installs. The canonical protocol name is TTEOP (Token Telemetry Evaluation Operator Protocol). Seeteps/TEP-0001.md.
Install
pip install sigrank-standard
Usage
Compute metrics
from sigrank_standard import compute_metrics, build_record
# Four token pillars: input, output, cache_write, cache_read
result = compute_metrics(
input_tokens=1_251_211,
output_tokens=11_296_121,
cache_write=128_196_310,
cache_read=2_555_179_769,
)
print(result["metrics"])
# {'yield': 18436.98, 'leverage': 2042.2, 'velocity': 9.028, 'output_fraction': 0.9003, 'log_leverage': 3.31}
Build a full record
from sigrank_standard import build_record
import json
record = build_record(
input_tokens=1_251_211,
output_tokens=11_296_121,
cache_write=128_196_310,
cache_read=2_555_179_769,
provider="anthropic",
model="claude-sonnet-4",
tool="claude-code",
)
print(json.dumps(record, indent=2))
Run conformance suite
sigrank-conformance
# or
python -m sigrank_standard
Metrics
| Metric | Formula | Description |
|---|---|---|
| Yield (Υ) | (cache_read * output) / input^2 |
Token cascade efficiency |
| Leverage | cache_read / input |
Context reuse |
| Velocity | output / input |
Output amplification |
| output_fraction | output / (input + output) |
Output share of total tokens |
| log_leverage | log10(cache_read / input) |
Log-scaled context reuse |
Legacy aliases (deprecated): SNR → output_fraction, 10xDEV → log_leverage.
Null semantics
- When a denominator is zero, the metric is
None(not 0 or Infinity) - When
cache_readisNone, Yield, Leverage, and log_leverage areNone - When
cache_writeisNone, log_leverage isNone
Spec
TTEOP v0.1-draft (Token Telemetry Evaluation Operator Protocol). See signalaf.com/standard.
License
Apache-2.0
Metadata
Release files for sigrank-standard 0.1.5
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 |
|---|---|---|---|---|
| sigrank_standard-0.1.5.tar.gz | 10.1 kB | Without provenance | Details for sigrank_standard-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sigrank_standard-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for sigrank_standard-0.1.5-py3-none-any.whl |
Total release size: 18.2 kB
Release files / sigrank_standard-0.1.5.tar.gz
| Download URL | sigrank_standard-0.1.5.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4260da25f90ae0072b03de7a424b29fad9344ab58b7cd8aa3ce5b554bb25b133
|
|
BLAKE2b-256 checksum How to use checksums |
85ba2e7c1524c7cf30262f5c94869cbdd7082ef274cbcbe2e95c0342161dd486
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / sigrank_standard-0.1.5-py3-none-any.whl
| Download URL | sigrank_standard-0.1.5-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd398d27122388352ca1d550ea1fe66ac4e16a328281f46d2c10e0272acce70f
|
|
BLAKE2b-256 checksum How to use checksums |
7ca3f00235ff2c4e9900f14e4b224f886802c85518c938854522a3c7f15e65f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for sigrank-standard 0.1.5
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.