Skip to content

Rulvar API reference


Rulvar API reference / @rulvar/rulvar / PinnedPricingSegment

Interface: PinnedPricingSegment

Defined in: packages/core/dist/index.d.ts

One pin's coverage (RV611): the run-settle that recorded it, the seq range it settled FIRST, and exactly the version and rows it pinned. The whole array is the per-segment provenance a single last-pin version used to hide: an invoice folded over a rotation can now say every table version that priced it, with the boundary seqs.

Properties

PropertyTypeDescriptionDefined in
fromSeqnumberThe first seq this pin covers: the previous pin's settle seq, 0 for the first pin. Rows with fromSeq <= seq < settleSeq price under this pin in the seq-aware fold.packages/core/dist/index.d.ts
pricingVersion?stringThe PriceTable version THIS settle pinned; absent for caps-only rows.packages/core/dist/index.d.ts
ratesVerifiedAt?{ newest: string; oldest: string; }The freshness range of THIS pin's dated rows (RV3703): the oldest and newest ratesVerifiedAt among rows carrying a parsable one, the machine-readable age of the table that priced the segment. Absent when no row is dated: freshness is then unattested, never guessed.packages/core/dist/index.d.ts
ratesVerifiedAt.neweststring-packages/core/dist/index.d.ts
ratesVerifiedAt.oldeststring-packages/core/dist/index.d.ts
rowsAppliedPricingRow[]The applied rows THIS settle pinned.packages/core/dist/index.d.ts
rowsHashstringsha256 over the canonical JSON of THIS pin's rows (RV3703): the version string is a label the table author chose, and the third experiment's arc found a price defect that a label cannot expose; the hash is the content. Two tables sharing a version string but disagreeing on rates are distinguishable, and two folds of one journal always derive the same hex. Computed at read time from the pinned bytes: the journal is unchanged and every existing pin gains it.packages/core/dist/index.d.ts
settleSeqnumberThe pinning run-settle's own seq (the exclusive upper bound).packages/core/dist/index.d.ts