Gaia-X Danube Public surfaces
Go to MyDataSpace
MyGovernance Governance fabric MyGovernance

MyGovernance

Unified audit console for transactions and Gaia-X Danube compliance

Operational console to supervise the governed data space, MyDataSpace, its evidence, audit traces, and the Gaia-X Danube compliance of its participants, verified against the clearing house.

Global status
Loading
Compliance
-
Last refresh
-

Governance architecture

Trust, wallets, audited evidence and AI governance with Mistral

MyGovernance governs a single data space, MyDataSpace: it receives and keeps its audited evidence, verifies the Gaia-X Danube compliance of its participants against the gxdch.mygovernance.es clearing house, audits documents and offers the stateless Mistral routes. There is no federation with other data spaces.

Registered dataspaces - -
Audited traces - -
Transactions in pass - -
Signature coverage - -

Danube / Compliance

Loading
Profile -
Mode -
Clearing house -
Compliant participants -
Trust anchors -
Trusted issuers -

Document AI audit

Local
Engine -
Reports issued -
Decisions -

Gaia-X Danube: participant compliance

Loading

Local Gaia-X Danube clearing house (gxdch.mygovernance.es), not recognised by Gaia-X AISBL; registration number verified by MyDataSpace.

For each participant of the data space its gx:LabelCredential is read from MyDataSpace's public Gaia-X endpoints and verified here against the clearing house did:web:gxdch.mygovernance.es:compliance:v2: signature with the key in its did.json, x5u chain carrying that same key, issuer, type, covered credentials and validity.

Participant Connector Registration number Gaia-X Danube Level Valid until Reason Credentials
Loading participants...

Assessment as JSON · MyDataSpace Gaia-X participants · Clearing house DID · Danube dispatcher

Connected dataspaces

Live governance registry

Functional infrastructure, connectors, policies and contracts

Operational separation by dataspace

This view separates the functional base of each dataspace: identity, deployed connectors, published capabilities, and the operational policy and contract layer used to govern exchanges.

Data assets, sharing model and transfer channel

What is shared, how it is negotiated, and through which delivery path
Asset Provider dataspace What is shared Policy / licence Contract How it is shared Through what
Loading assets...

Audited transactions

Cross-view between traces, compliance, and evidence
Trace ID Consumer Provider Event Outcome Registry Danube / Compliance Signature Time
Loading transactions...

Document audit reports

Local analysis inspired by GDPR, Data Governance Act, Data Act, Omnibus law and governed reuse

Legal legend

  • open-public-sector-reuse
    Open reuse with enhanced traceability
  • controlled-governed-reuse
    Governed reuse with contractual conditions
  • restricted-personal-data-review
    Legal review for possible personal data
  • restricted-sensitive-data-review
    Enhanced review for sensitive or special-category data
  • missing-legal-basis-review
    Review for insufficient legal basis or licence
Trace ID Asset Provider dataspace Decision Legal classification Why this classification Time
Loading document reports...

Metaregistry and trust

Consolidated issuer and anchor view

Trust Anchors

    Trusted Issuers

      Metaregistry

      Loading...

      Public surfaces

      Every plane by its own door, and what has none

      MyGovernance has no sign-in of its own: auth.mygovernance.es does not exist, and that is not an oversight. This domain is the governance plane, not a participant; anybody who needs to sign in does so at MyDataSpace, which is the one with connectors, a catalogue and a user console.