Documentation intelligence
Source-linked system profiles separate vendor and standard documentation from Tracevity interpretation. Unknowns and not-documented findings remain explicit.
About Tracevity
The independent reconstruction layer
Tracevity maps what agent platforms, runtimes, frameworks, standards, formats, and observability systems record—and what those records still cannot establish.
Why it exists
Organizations already have traces. They need to know what can be reconstructed.
Debugging, incident review, delegated-authority analysis, portability, and privacy each need different evidence. Tracevity makes those requirements explicit without inventing a universal score or treating telemetry quantity as reconstruction quality.
Trace Map → compatibility → Inspect → Gate
Three evidence layers, one reconstruction system
Tracevity carries forward 15 published documentation profiles across 12 capability families, then adds exact bounded compatibility exercises and local deterministic reconstruction and release-gating tools. Each layer keeps its own evidence boundary.
Bounded tested evidence
Exact compatibility fixtures show what selected pinned representations preserve, normalize, lose, or leave dependent on external evidence. They do not certify an implementation or whole product.
Local reconstruction and Gate
Inspect evaluates a supported artifact against named requirements. Correlated Evidence can close bounded external gaps. Gate catches requirement-level evidence regressions across releases and migrations—all without hosted ingestion.
| Tracevity is | Tracevity is not |
|---|---|
| Evidence semantics and reconstruction intelligence | A hosted telemetry ingestion service |
| Use-case-specific requirements | A single score or vendor ranking |
| Explicit unknowns and limitations | A claim to hidden reasoning or latent motive |
| Exact, use-case-bound reconstruction conclusions | Certification or whole-product tested conformance |
Public release transparency
Current product: Tracevity v0.5 public beta
CLI version 0.5.0 · OTLP trace protobuf · four exact supported dialect declarations · evidence and compatibility observations dated on their source pages.
| CLI distribution | Not asserted by this build |
|---|---|
| Supported declarations | OpenTelemetry GenAI, OpenInference, MLflow native, MLflow GenAI-transformed |
| Proof ceiling | Named local inputs and requirements only; no producer-identity proof, hidden reasoning, arbitrary-system certification, or complete-capture assumption. |
Read the methodology and evidence dates, the CLI guide, and the corrections channel.
Explore the work
Begin with the local CLI or a reconstruction use case.
Every useful conclusion starts by naming what must be established and checking which artifacts can support it.