ContractSpec docs

OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

SignalSpec — observability/cost/usage signal declarations

Canonical, locale-free declaration layer for metric/trace/cost/usage signals.

field.key.label
SignalSpec — observability/cost/usage signal declarations
field.version.label
field.type.label
field.title.label
SignalSpec — observability/cost/usage signal declarations
field.description.label

Canonical, locale-free declaration layer for metric/trace/cost/usage signals.

field.tags.label
observability,signals,cost,usage,i18n
field.owners.label
field.stability.label
public

The typed declaration layer for all observability/cost/usage signals. One spine, two consumers: observability (metric/trace) and billing (cost/usage).

•

Declared as the `SignalSpecModel` `SchemaModel`; `SignalSpec` is its

Zod-inferred TS shape.

•

`id` and `dimensions` are stable machine strings — never localized, never

locale-suffixed (enforced by `i18n/no-localized-machine-contracts` and by `defineSignal` validation).

•

`dimensions` reuse canonical semantic dimension ids from the analytics layer.

•

`costModelVersion` and `redactionPolicyRef` are optional refs consumed by the

billing/evidence pipeline.

Use `defineSignal(spec)` to construct a validated `SignalSpec`.