Design Requirement
Tamper-proof and automated data processing, for instance via smart contracts, to avoid the storage of erroneous data or its manipulation during information transfer.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/ambivalence-trust-loyalty-dr2design-knowledge/ambivalence-trust-loyalty-dr2.mdTamper-proof and automated data processing, for instance via smart contracts, to avoid the storage of erroneous data or its manipulation during information transfer.
This design requirement is proposed by From ambivalence to trust: Using blockchain in customer loyalty programs (Manuel Utz, Simon Johanning, Tamara Roth, Thomas Bruckner, Jens Strueker, 2023).
02
Concepts connected by incoming or outgoing native Markdown links.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
Derived heading context: Addresses
Derived heading context: Source paper
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
3 of 3 concepts · 5 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-requirement",
"title": "DR2 - Tamper-proof and automated data processing",
"description": "Tamper-proof and automated data processing, for instance via smart contracts, to avoid the storage of erroneous data or its manipulation during information transfer.",
"resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
"source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
"label": "DR2",
"tags": [
"ambivalence-trust-loyalty",
"design-requirement",
"energy",
"customer-loyalty",
"trust",
"green-electricity"
]
}