<aside> 💡 Submit a Knowledge Request (KR)
Knowledge Request Protocol MVP
</aside>
A Knowledge Request is the data structure that describes the unit of value containing the knowledge that is requested by a requester, produced by a subDAO, approved and delivered to the requester as a final product.
This section described the high-level structure of KR and how it evolves from a market order through the process of production to the final delivery.
Every KR should have at least the following properties:
Public data reference (e.g. URI)
Private (encrypted) data references (e.g. URIs) for all kinds of off-chain data that is a part of the KR, such as:Details provided by the requester;Documents attached by the requester;Knowledge provided by the assigned DAO Member;
Case-specific parameters, such as:Min count of approvals needed for the KR to pass the review stage.
KR files (stored off-chain and likely encrypted) would potentially contain sensitive patient data, so the access to them should be managed with caution and precision.
For this purpose it is proposed to associate all the addresses involved with a particular KR at the protocol level, and — combined with the role-based authorization — use this information as a gateway to any private data used in the application layer.
The same rules as above apply to KR mutation.
Any external transaction mutating the KR state must have a protocol-level guard logic checking the authorization level of the corresponding address.
The protocol must manage the lifecycle of the KR, ensuring proper transitions between its state based on the internal and external changes (effectively implementing a state machine).
Lifecycle Stages