Frozen at capture
The record holds the value, definition, source, and timestamp as they were when the decision was made. The vendor UI stays live. The record does not.
Loading
Evidence Providers
The number, the definition, the source — frozen at the moment the decision was made.
Your semantic layer, your fleet telemetry, your governed sources — attached to the Decision Record and preserved exactly as they were used. Not a link that may have changed since.
What it is
Not intelligence. Not execution. Evidence.
An Evidence Provider supplies one thing: what was true, from a governed source, at the moment it informed the decision — frozen into a snapshot the Decision Record carries forever. Semantic evidence (Snowflake, Looker) and operational evidence (Samsara) are the two archetypes.
Three properties
What makes this different from linking to a dashboard.
Qualification inherited
How governed the definition is, how attestable its provenance, how fresh the reading — from the source's own mapping. Never asserted by the loop.
Conformance verifiable
The provider contract and conformance suite are open. An auditor can check that every evidence source in a decision conformed to the contract.
Semantic authority
Boss Loops doesn't care who authored the definition.
dbt, LookML, Snowflake Semantic Views, Cube, AtScale — tomorrow, maybe SAP BW or Microsoft Fabric. Different authoring surfaces, one role: the semantic authority your business already answers to. The provider contract is authority-agnostic. What it demands of a definition is the same four things everywhere:
Owned
A named team answers for the definition. On the record, the authority is attributed — Finance owns available budget, not “the warehouse.”
Versioned
The definition version is a fact of the snapshot, not a guess. The record pins the exact version the decision used.
Tested
The source's own checks passed at capture — and the result travels with the evidence, not with a wiki page.
Trusted
Certified and governed are inherited from the source's own mapping — never asserted by whoever built the loop.
Here is why that matters more than it sounds. Six months from now, the definition will change — definitions always do. Most systems then show you today's value under today's meaning and call it history. A Decision Record preserves the exact semantic definition that existed when the decision was made:
Decision Record · evidence row
Frozen at decision time- Evidence
- Available Budget
- Value
- $410,000
- Semantic authority
- Finance
- Semantic source
- dbt
- Model
- finance.department_budget_position
- Definition version
- v2.3
- Source tests at capture
- Passed
- Last refreshed
- 18 minutes ago
P: system-attestedD: governedF: fresh
The definition moves on
Finance ships v3.0 of available budget — committed spend is reclassified, and today's number answers a different question.
The record still answers with v2.3 — the meaning the decision was actually made under.
Decision used definition · v2.3
The record doesn't just capture what was known. It captures how it was understood — the meaning of the data at decision time.
Today
Three providers, one contract.
- Preview
Looker
Certified metric definitions travel with the decision. The Alpine invoice record carries vendor spend vs. a 12-month band as a preview snapshot — definition, value, and qualification frozen on the record.
- Planned
Snowflake
Governed semantic views — the definition layer many finance and ops teams already run — attached at capture with qualification inherited.
- Planned
Samsara
Operational readings from fleet and field at decision time. The reading that opened the loop is the reading on the record.
Governed sources
Looker
Certified BI metric
Snowflake
Governed semantic view
Samsara
Operational reading
Frozen at capture
- · the value
- · the source's own definition
- · provenance
- · freshness
content-hashed · immutable
Decision Record
Looker · frozen at decision time
Vendor spend within 12-month band
P: system-attestedD: certifiedF: fresh
The vendor UI stays live. The record does not change.
For finance and ops leaders
Attach your semantic layer to your first decision.
Pick a decision where the answer to "which number, as of when?" matters. We wire the provider and show you the record.
Design a pilot →