internal/

Package admin serves OpticTrace's control-plane HTTP surface, deliberately on a separate listener from proxied traffic so it can be firewalled independently:

Package applog governs application log lines on the way into the store.

Package config defines the optic.yaml schema, its loader, and validation.

Package engine compiles an optic.yaml Config into an immutable, allocation- light rule engine evaluated on every request.

Package export is OpticTrace's pluggable output layer: every governed telemetry record (post-restriction, post-redaction — exporters can never see raw sensitive data) fans out to the exporters declared under telemetry.exporters in optic.yaml.

Package metrics exposes OpticTrace telemetry to Prometheus.

Package mock turns an OpenAPI spec into a running, STATEFUL mock server:

Package proxy provides OpticTrace's interception layer in two flavors that share one code path:

Package replay re-issues captured traffic against a target service.

Package review turns everything OpticTrace knows into one pull-request comment.

Package ruletest runs assertions about optic.yaml against the real rule engine, with no server and no network.

Package scaffold turns an OpenAPI or Swagger document into a starting optic.yaml.

Package scan is OpticTrace's safety net.

Package spans governs inner spans on the way into the store.

Package spec bridges static API contracts and runtime reality:

Package store persists governed telemetry records (what optic.yaml allowed through) and answers the dashboard's query/analytics needs.

Package suggest proposes governance rules for traffic that has none.

Package telcap holds the two mechanics every per-request telemetry stream needs: a memory-bounded per-key counter, and a truncation that respects UTF-8.

Package tracectx handles W3C Trace Context — the header that lets records from several services be recognised as one request.