Design Objective
To ensure transparency, traceability, and archiving requirements, the prototype needs to store data persistently and immutably. According to management, to date, this has only been done in centralized systems with classic backup redundancy.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/unchaining-social-crowdlending-do11design-knowledge/unchaining-social-crowdlending-do11.mdTo ensure transparency, traceability, and archiving requirements, the prototype needs to store data persistently and immutably. According to management, to date, this has only been done in centralized systems with classic backup redundancy.
This design objective is proposed by Unchaining Social Businesses - Blockchain as the Basic Technology of a Crowdlending Platform (Andre Schweizer, Vincent Schlatt, Nils Urbach, Gilbert Fridgen, 2017).
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.
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
2 of 2 concepts · 2 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-objective",
"title": "DO11 - Data persistency",
"description": "To ensure transparency, traceability, and archiving requirements, the prototype needs to store data persistently and immutably. According to management, to date, this has only been done in centralized systems with classic backup redundancy.",
"resource": "https://aisel.aisnet.org/icis2017/TransformingSociety/Presentations/8",
"source_paper": "Unchaining Social Businesses - Blockchain as the Basic Technology of a Crowdlending Platform",
"label": "DO11",
"tags": [
"unchaining-social-crowdlending",
"design-objective",
"social-business",
"crowdlending",
"fintech",
"platforms"
]
}