Design Objective
The artifact should be built on an infrastructure capable of scaling with growing transaction volumes and users.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/procurement-is-trilemma-do4design-knowledge/procurement-is-trilemma-do4.mdThe artifact should be built on an infrastructure capable of scaling with growing transaction volumes and users.
This design objective is proposed by Designing a blockchain-based information system for procurement processes - Balancing decentralization, scalability, and security while maintaining privacy (Valeriya Arnold, Tobias Guggenberger, Jan Stramm, Nils Urbach, 2026).
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: Design knowledge
Derived heading context: Addresses
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-objective",
"title": "DO4 - Infrastructure that scales with volume and users",
"description": "The artifact should be built on an infrastructure capable of scaling with growing transaction volumes and users.",
"resource": "https://doi.org/10.1016/j.is.2026.102723",
"source_paper": "Designing a blockchain-based information system for procurement processes - Balancing decentralization, scalability, and security while maintaining privacy",
"label": "DO4",
"tags": [
"procurement-is-trilemma",
"design-objective",
"procurement",
"blockchain-trilemma",
"privacy",
"zero-knowledge"
]
}