libraryPackage manifestv0.1.0

lib.observability-spec

Pure signal declarations, cost evidence models and deterministic validation shared by observability and billing.

@lssm-tech/lib.observability-spec
Source, release and verification context

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.

Package source ↗ Manifest ↗
serverwebnodebunbrowser
EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGElib.observability-specplatform

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

3 declarationsSELECT TO INSPECT

Observability Spec

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.

@lssm-tech/lib.observability-spec/signal-specSignalSpec, SignalSpecModel, defineSignal

@lssm-tech/lib.observability-spec/evidence-recordEvidenceRecord, EvidenceRecordModel, validateEvidenceRecord

Imports and export paths.

4 entries

These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.

4 imports

Dependencies and related packages.

Runtime dependencies 3
zod
catalog:
Development dependencies 3
@types/bun
catalog:types

Package scripts.

Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.

buildcontractspec-bun-build build
build:bundlecontractspec-bun-build transpile
build:typescontractspec-bun-build types
prebuildcontractspec-bun-build prebuild
testbun test
typechecktsgo --noEmit
lint:checknode ../../../../scripts/biome.cjs check .
Your view

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Your context

The different parts of you

Choose a starting point

A useful mix of context, visuals and gentle guidance.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Reading comfort

Choose your language

Interface language changes text only. Markets, prices and workflows keep their own settings.

Translation coverage

Original source

Navigation151
Graph616
Categories378
Portfolio833
Examples2,035
Source preview1,542

More translations will be added as content is reviewed.

This preference is saved on this browser.

Search the website

Useful starting points

No results. Try a shorter phrase, an operation name or another search area.

A LITTLE ROOM TO EXPLORE

Find something to explore.

Open a closer look on this page, try a different perspective, or follow the detail into its own page.

How previews and controls work
01

Look before you leave

Hover a link or focus it with Tab to see a preview. Clicking the original link or pressing Enter always opens its destination.

02

Stay with the context

Move into the preview to explore its sections. Use Alt + ↓ from a focused link to enter it with the keyboard. Escape closes it.

03

Open the possibilities

Disclosure rows, perspective choices and highlighted controls reveal more. Your view changes reading comfort and the context you explore.

A separate button for a closer look

Show small preview buttons beside links where there is room. Tap the eye to inspect, or tap the link to go straight there. This choice stays in this tab.

No browsing history is collected. Reduced motion follows your device and Your view.