Design Requirement
The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/dissonance-dialogue-recall-dr1design-knowledge/dissonance-dialogue-recall-dr1.mdThe enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.
This design requirement is proposed by From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers (Norman Pytel, Christian Ziegler, Axel Winkelmann, 2024).
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: Design knowledge
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": "DR1 - Straightforward ERP mapping with essential on-chain data",
"description": "The enterprise systems should be mapped straightforwardly, and only essential recall-communication data must be stored in the blockchain.",
"resource": "https://doi.org/10.1145/3639058",
"source_paper": "From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers",
"label": "DR1",
"tags": [
"dissonance-dialogue-recall",
"design-requirement",
"recall-communication",
"erp-integration",
"traceability",
"tokenization"
]
}