Skip to content

Consent flow

Planned

The consent flow described here is planned but not yet implemented. The current r-squared demo runs without data owner consent. This page documents the intended design.

Intended flow

In scenarios where data owner consent is required before a transfer can proceed, the Consent Management App (CMA) acts as the gating mechanism.

sequenceDiagram
    participant DO as Data Owner
    participant CMA as Consent Management App
    participant RUN as RUN-DSP (consumer)
    participant CS as Reference Contract Service

    DO->>CMA: Reviews pending access request
    DO->>CMA: Grants consent for data set
    CMA->>CS: Records consent decision
    RUN->>CS: Contract hook — check consent state
    CS-->>RUN: Consent granted — proceed
    RUN->>RUN: Contract negotiation continues to AGREED

Consent is intended to be scoped per data set. Once a data owner grants consent for a data set, all transfers within that data set can proceed without requiring individual approval for each one.

Enforcement point

The Reference Contract Service hook in RUN-DSP is the enforcement point. When a contract negotiation reaches the AGREED state, the contract service checks whether the data owner has granted consent. If not, the negotiation transitions to TERMINATED.