Federated governance architecture
Federation, trust, wallets, audited evidence and AI governance with MistralMyGovernance registers MyFIWARE as an NGSI-LD provider, aggregates its credential into the federated catalog, and mediates the real EDC contract, HttpData-PULL transfer, EDR authorization, download, and audit flow for MyDataSpace and GoToDataSpace.
SIMPL plane
Loading
Health endpoint
-
Published version
-
Operational base path
/simpl
Danube / Compliance
Loading
Profile
-
Mode
-
Trust anchors
-
Trusted issuers
-
Document AI audit
Local
Engine
-
Reports issued
-
Decisions
-
Connected dataspaces
Live governance registryFunctional infrastructure, connectors, policies and contracts
Operational separation by dataspaceThis 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 federated assets... | ||||||
Audited transactions
Cross-view between traces, compliance, and evidence| Trace ID | Consumer | Provider | Event | Outcome | SIMPL / 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| Trace ID | Asset | Provider dataspace | Decision | Legal classification | Why this classification | Time |
|---|---|---|---|---|---|---|
| Loading document reports... | ||||||