Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/dissonance-dialogue-recall-dp4

Producer label: DP4
Source paper: From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/dissonance-dialogue-recall-dp4.md

design-principledissonance-dialogue-recallerp-integrationrecall-communicationtokenizationtraceability

Design principle DP4: Interoperability across EVM-supported applications

Provide interoperability between EVM-supported software applications using recall tracing across organizational borders.

Source paper

This design principle 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).

Addresses

Design requirement DR4: Interoperability with permissionless blockchain

Implemented by

02

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

6 Design Features

design-knowledge/dissonance-dialogue-recall-df1

DF1 - Customer wallet notification for recall states

Customers log in with an Ethereum wallet and receive notifications about recall states of products they own.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2

design-knowledge/dissonance-dialogue-recall-df3

DF3 - Recall tracing and product-state extension of the token

A standard token interface that traces recalls and extends the product state as the token moves between organizations and customers.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2

design-knowledge/dissonance-dialogue-recall-df4

DF4 - Interorganizational BC-based data storage

Inter-organizational blockchain-based data storage shared between manufacturers and customers.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2

design-knowledge/dissonance-dialogue-recall-df5

DF5 - Customer product-defect announcement

A feature allowing customers to announce product defects and voluntarily report their health state.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2

design-knowledge/dissonance-dialogue-recall-df6

DF6 - Manufacturer product-defect announcement

A feature allowing manufacturers to announce a defective product, initiating a forward recall that notifies all customers holding the token.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2

design-knowledge/dissonance-dialogue-recall-df7

DF7 - Manufacturer recall-state management

A feature by which manufacturers set and manage recall states (e.g., 'Checked NOT OK') for affected products.

design-featuredissonance-dialogue-recallerp-integrationrecall-communication+2

1 Design Requirement

design-knowledge/dissonance-dialogue-recall-dr4

DR4 - Interoperability with permissionless blockchain

The system should allow interoperability between enterprise systems and permissionless blockchain.

design-requirementdissonance-dialogue-recallerp-integrationrecall-communication+2

1 Paper

papers/dissonance-dialogue-recall

From Dissonance to Dialogue: A Token-Based Approach to Bridge the Gap Between Manufacturers and Customers

The paper presents a token-based recall-communication system integrating ERP and blockchain, developing six design principles (and supporting design features) that improve recall coordination, traceability and co-value creation between manufacturers and customers.

blockchaindesign-science-researchdissonance-dialogue-recallerp-integration+3

03

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

8

Incoming backlinks

7

04

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

9 of 9 concepts · 29 directed relationships

Concept types

05

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-principle",
  "title": "DP4 - Interoperability across EVM-supported applications",
  "description": "Provide interoperability between EVM-supported software applications using recall tracing across organizational borders.",
  "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": "DP4",
  "tags": [
    "dissonance-dialogue-recall",
    "design-principle",
    "recall-communication",
    "erp-integration",
    "traceability",
    "tokenization"
  ]
}