OpenTelemetry GenAI · pinned development revision 67dff024
Supported only within its exact published binding and proof ceiling.
Tracevity CLI 0.5.0 · Distribution preview
Tracevity turns supported local trace evidence into deterministic Reconstruction Reports, then compares those outcomes across a release or migration. Your trace never has to leave your machine.
Install
This build does not claim that a public package exists. Installation commands and the PyPI link remain hidden until the exact qualified distribution is available from the public provider.
Synthetic quickstart
The static bundle contains only Tracevity-generated OTLP fixtures, manifests, requirements, and an unchanged Gate suite. It never sends data to this website.
1 · List and inspect one exact execution
tracevity traces list --manifest inspect/manifest.json
tracevity inspect \
--manifest inspect/manifest.json \
--requirements inspect/requirements.json \
--out reconstruction-report.json2 · Gate an unchanged synthetic release
tracevity gate \
--suite gate/tracevity-gate.json \
--out tracevity-gate-report.jsonUnzip into an empty directory and run the commands from that directory. A synthetic passing Gate case proves installation and deterministic command behavior—not certification or production completeness.
Supported surface
The operational input is OTLP trace protobuf. Logs and metrics are recognized as unsupported. Declaring a compatible dialect does not prove which producer emitted the artifact.
Supported only within its exact published binding and proof ceiling.
Supported only within its exact published binding and proof ceiling.
Supported only within its exact published binding and proof ceiling.
Supported only within its exact published binding and proof ceiling.
Read the Inspector evidence boundary and the exact compatibility mappings before interpreting a report.
Local privacy boundary
Inspect, trace discovery, and Gate make no network request, call no model, create no account, and use no runtime database. There is no update check, crash report, hidden cache, or upload path.
Trace values are parsed as data, never executed or followed as URLs. Reports minimize prompt, output, argument, result, and local-path values. Only the output path you select is written.
The website uses separately bounded coarse analytics only when configured and when DNT/GPC permits. Session replay is always disabled. The CLI contains no analytics code.
Gate exit contract
| Exit | Meaning |
|---|---|
0 | The suite passes under its named reconstruction policy. |
2 | A required reconstruction regression blocks the change. |
3 | A required case is indeterminate or incomparable and needs attention. |
4 | The input, policy, or baseline is invalid. |
5 | The selected representation is unsupported. |
70 | An internal or prohibited-network failure occurred. |
Semantic limits
Tool success is not external settlement. Agent identity is not initiating-principal evidence. Valid OTLP is not sufficient reconstruction. A Gate pass says only that the named required outcomes did not regress for the exact supplied inputs and policy.
Feedback and correctionsReport a bounded documentation issue or CLI bug in the public Tracevity feedback repository. Never post production traces, credentials, customer data, prompts, outputs, or logs. Use private vulnerability reporting for sensitive security findings.