Skip to content
Venturi
Contact

06 / The decision record

Every decision keeps its evidence and history.

Observed, inferred, allocated, estimated, event-time, and current-state truth remain distinct. Corrections append new events rather than rewriting the record.

Mechanism . Describes how the product is designed to work. Architecture commitment . A required system behavior that still needs deployment evidence.
Inspect trust model Review adoption and cost intelligence

Question

How can an attribution decision remain explainable after evidence, ownership, or policy changes?

Mechanism

How the mechanism works

The immutable source history preserves original evidence and governed events. Relationship resolution produces a derived graph. Materialization produces an inspectable decision record and serving index. A correction appends a new event, then the derived state is rebuilt.

  1. 01Immutable source history

    Governed source events, versions, and provenance.

  2. 02Derived graph and index

    Rebuildable ownership relationships and bounded lookup.

  3. 03Corrections and overrides

    New events with reason, actor, time, and policy basis.

  4. 04Rebuild and auditability

    Re-materialize with the retained evidence and versioned logic.

Six truth domains

Observed . Directly present in a source record.

Directly present in a source recordSource event and connector provenance

Inferred . Derived from eligible evidence with uncertainty preserved.

Derived from eligible evidence with uncertainty preservedAttribution decision and model or rule version

Allocated . A governed split of shared cost, separate from ownership.

A governed split of shared costAllocation method and recipients

Estimated . Calculated from an explicit method when reconciled values are unavailable.

Calculated when reconciled values are unavailableNamed estimation method and time basis

Event-time . The state that applied when the governed event occurred.

The state that applied when the governed event occurredEffective-dated source history

Current-state . The latest known state at the time of inspection.

The latest known state at inspectionCurrent source snapshot

Annotated visual

Inspect the path and its unresolved states

Illustrative synthetic example

Timeline moment

Initial evidence

Mechanism . Describes how the product is designed to work.
Original evidence
Provider billing, service identity, deployment metadata, organization hierarchy
Winning candidate
No winner
Alternative candidates
Customer Operations Platform; Support Experience
Operational confidence
Not available
Output state
Unknown
Policy or model version
Policy v1 / no model decision
Event-time ownership
Unknown
Current-state ownership
Unknown
Correction reason
None
Action class
Observe only
Truth-domain labels Observed . Directly present in a source record. Event-time . The state that applied when the governed event occurred.
Illustrative synthetic example

Timeline moment

Attribution decision

Mechanism . Describes how the product is designed to work.
Original evidence
Provider billing, service identity, deployment metadata, organization hierarchy
Winning candidate
Customer Operations Platform
Alternative candidates
Support Experience retained as a close alternative
Operational confidence
0.68
Output state
Ambiguous
Policy or model version
Policy v1 / attribution model synthetic-v1
Event-time ownership
Customer Operations Platform
Current-state ownership
Customer Operations Platform
Correction reason
None
Action class
Human review required
Truth-domain labels Observed . Directly present in a source record. Inferred . Derived from eligible evidence with uncertainty preserved. Event-time . The state that applied when the governed event occurred.
Illustrative synthetic example

Timeline moment

Human correction

Mechanism . Describes how the product is designed to work.
Original evidence
Provider billing, service identity, deployment metadata, organization hierarchy
Winning candidate
Support Experience
Alternative candidates
Original candidate preserved in history
Operational confidence
0.68 at original decision
Output state
Bounded
Policy or model version
Correction policy v1
Event-time ownership
Support Experience
Current-state ownership
Support Experience
Correction reason
Deployment catalog omitted the event-time project transfer
Action class
Correction review completed
Truth-domain labels Observed . Directly present in a source record. Inferred . Derived from eligible evidence with uncertainty preserved. Event-time . The state that applied when the governed event occurred.
Illustrative synthetic example

Timeline moment

Re-materialized decision

Mechanism . Describes how the product is designed to work.
Original evidence
Provider billing, service identity, deployment metadata, organization hierarchy
Winning candidate
Support Experience
Alternative candidates
Customer Operations Platform retained in prior history
Operational confidence
0.95 cap
Output state
Deterministically resolved
Policy or model version
Policy v2 / deterministic relationship
Event-time ownership
Support Experience
Current-state ownership
Support Experience
Correction reason
Correction event applied during rebuild
Action class
Eligible for finance review
Truth-domain labels Observed . Directly present in a source record. Event-time . The state that applied when the governed event occurred.
Illustrative synthetic example

Timeline moment

Current-state view

Mechanism . Describes how the product is designed to work.
Original evidence
Provider billing, service identity, deployment metadata, organization hierarchy
Winning candidate
Customer Operations Platform
Alternative candidates
Event-time owner remains Support Experience
Operational confidence
0.95 cap
Output state
Deterministically resolved
Policy or model version
Organization view current at inspection
Event-time ownership
Support Experience
Current-state ownership
Customer Operations Platform
Correction reason
No rewrite of event-time ownership
Action class
Use the time basis required by the decision
Truth-domain labels Current-state . The latest known state at the time of inspection. Observed . Directly present in a source record.

In summary: initial evidence produces an ambiguous attribution, a governed human correction adds missing event-time ownership, the record is re-materialized, and a later current-state view shows a different current owner without rewriting the event-time owner.

Concrete example

Apply the mechanism to one synthetic workload

Illustrative synthetic example

A project transfer discovered after materialization

Original decision
Customer Operations Platform, ambiguous, 0.68 operational confidence
New evidence
Effective-dated project transfer to Support Experience
Correction
Append a correction event with reason and source provenance
Re-materialized decision
Support Experience, deterministically resolved, confidence capped at 0.95
Current-state view
Customer Operations Platform shown separately from event-time ownership
Action class
Eligible for finance review after correction review

Evidence and implementation boundary

What the current claim supports

The event history is authoritative. The graph and decision-time index are derived and rebuildable. Append-only history does not eliminate privacy obligations; erasure, tombstone, and crypto-erasure semantics require the applicable privacy treatment.

Allocation and ownership remain distinct fields. A fractional cost split can be recalculated without rewriting the owner path. Event-time and current-state views remain labeled so a reviewer can select the basis appropriate to the decision.

See the Privacy Policy and trust model for retention, erasure, and boundary treatment.

Known limitations

Unknown and unresolved states remain valid outcomes

  • 01A current-state organization view cannot replace event-time ownership when a historical decision requires the original context.
  • 02A human correction needs a reason, actor, time, and policy basis; it cannot silently mutate the prior event.
  • 03A rebuild can reproduce only the evidence, versions, and correction events retained under the applicable policy.

Decision enabled

Reconstruct why a decision was made, what changed, and which time and truth domain should govern the next action.

An inspectable record supports dispute resolution, finance review, model review, and policy review because each action can be tied to the evidence and version that existed at the decision point.