Design Requirement
Deliver all information for the setup process, should the electricity supplier deem it necessary or desirable that customers set up the system without the support of a technician.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/ambivalence-trust-loyalty-dr6design-knowledge/ambivalence-trust-loyalty-dr6.mdDeliver all information for the setup process, should the electricity supplier deem it necessary or desirable that customers set up the system without the support of a technician.
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": "DR6 - Deliver all information for setup process",
"description": "Deliver all information for the setup process, should the electricity supplier deem it necessary or desirable that customers set up the system without the support of a technician.",
"resource": "https://doi.org/10.1016/j.ijinfomgt.2022.102496",
"source_paper": "From ambivalence to trust: Using blockchain in customer loyalty programs",
"label": "DR6",
"tags": [
"ambivalence-trust-loyalty",
"design-requirement",
"energy",
"customer-loyalty",
"trust",
"green-electricity"
]
}