Skip to main content

Transaction Details Ledger

The DSM includes a general-purpose transaction details ledger for recording quantitative transactions — such as reputation scores, payment tracking, or reviews. This ledger exists independently of the approval workflow and is designed for tracking cumulative or scored data rather than state-change events.

What gets recorded​

Each ledger entry stores:

  • Source — the user or entity initiating the transaction
  • Target — the user or entity receiving the transaction
  • Subject — what the transaction relates to (for example, a review category or transaction type)
  • Amount — a numeric value (score, payment amount, count, etc.)
  • Description — a human-readable summary of the transaction

Uniqueness constraint​

The ledger enforces a uniqueness constraint across the combination of source, target, and subject. This prevents duplicate entries and ensures data integrity — for example, two review scores from the same source cannot exist for the same target and subject.

Use cases​

  • Reputation scoring — tracking trust scores awarded by other users
  • Payment records — recording monetary transactions or adjustments
  • Review tracking — storing quality or satisfaction ratings
  • Audit records — maintaining a ledger of quantitative actions

Visibility and access​

Transaction ledger records inherit visibility rules from their associated entities. Generally, parties involved in a transaction can view the ledger entry, and administrative users with appropriate permissions can access the full ledger.