Source snapshot bcc79fcc · Declared package version 0.1.0. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
Portable signal declarations and evidence envelopes shared by observability and billing.
Import defineSignal, SignalSpecModel and signal types from @lssm-tech/lib.observability-spec/signal-spec. Import evidence models and validateEvidenceRecord from /evidence-record. The root exports both complete families.
Signal identifiers stay canonical and locale-free. Evidence keeps raw tenant identifiers, numeric quantities and the original cost evidence fields. Validation and rejection messages are unchanged. Existing Observability and ContractSpec compatibility leaves forward to these same objects.
OpenTelemetry instrumentation, database signal defaults and persistence remain in their runtime owners.
Commands: bun run test, bun run typecheck, bun run lint:check, bun run build. This candidate requires task-bound adoption and clean declaration/consumer qualification before integration.
The /analytics/semantic-spec entry owns locale-free metric and dimension identifiers with localized labels and aliases. These are type-only declarations; executable audit and time-window SchemaModel declarations remain in Observability runtime.
Declared capabilities.
Portable signal declarations and evidence envelopes
Complete existing schema instances, inferred fields and deterministic validation shared by billing and observability.
Use it to
Declare locale-free signals and validate raw-tenant signal evidence without importing observability runtime.
Choose another boundary when
Observation, OpenTelemetry instrumentation, database persistence, provider adapters or populated database signal defaults are needed.
These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.