Quality requirements

This section specifies quality scenarios that make the quality goals from section 1 concrete and testable.

Quality scenarios

Quality goal	Scenario	Expected outcome
Data sovereignty	In a consent-enabled scenario, a data owner revokes consent for a study via the CMA. The consumer subsequently attempts to negotiate a new contract for that study.	The contract hook rejects the AGREED transition. The negotiation terminates without reaching FINALIZED.
Interoperability	A third-party connector that is compliant with the IDSA Dataspace Protocol initiates a contract negotiation with a RUN-DSP provider instance.	The negotiation completes to FINALIZED following the standard DSP state machine without modification to RUN-DSP.
Scalability	100 concurrent contract negotiations are active on a single RUN-DSP instance, each progressing independently.	No negotiation experiences a timeout beyond normal DSP roundtrip latency. The connector processes all transitions without queuing.
Security and compliance	A participant presents a DPoP token whose signature was produced with a key that is not declared in their DID document.	Signature-Auth-Handler rejects the request. RUN-DSP does not process it. No dataset metadata or transfer URL is returned.