jackin-telemetry

The schema authority and governed instrumentation facade keep jackin❯ telemetry consistent across processes.

What this crate owns

The closed OpenTelemetry extension registry and generated Rust constants.
Bounded semantic values and correlation-id minting.
Privacy-safe typed error capture for arbitrary Result error types.

Architecture tier and allowed dependencies

T0; no workspace dependencies. Ecosystem dependencies are limited to OpenTelemetry semantic conventions and UUID generation.

Structure

Module	Owns	Tests
`lib.rs`	Crate root and re-exports	—
`schema.rs` · `schema/`	Generated attributes, events, spans, and bounded values	`tests.rs`
`event.rs` · `error.rs` · `operation.rs` · `metric.rs`	Bounded governed signal facade	`disabled_alloc.rs`
`spawn.rs` · `propagation.rs`	Async ownership and W3C propagation	module tests
`benches/`	Disabled-path benchmark and reviewed 5% cross-workload baseline	`cargo xtask telemetry-bench`

Public API

Import schema names and bounded values through jackin_telemetry::schema.

At a fallible operation's semantic owner, ResultTelemetryExt records any Err as one typed event without formatting it and returns the result unchanged. The operation guard separately completes failed span status with the same type.

How to verify

cargo nextest run -p jackin-telemetry --locked

The scheduled performance lane runs the calibration benchmark and four product Criterion targets, then cargo xtask telemetry-bench --capture. The comparator normalizes every workload median by the same-run telemetry_calibration median, so uniform runner-speed changes do not masquerade as product regressions. Refresh the reviewed baseline only from one complete, inspected run with reference machine/toolchain data; a normalized regression above 5% fails.