Merge branch 'feat/datalab' into 'develop'

| **Link graph** | Cross-references in the body use bundle-absolute paths (e.g. `/srm/persistence-model.md`). Companion lists at the top of each doc form the navigable graph. |

| **Records** | [decisions/](decisions/) holds numbered ADRs (reasoning); [external-specs/](external-specs/) holds vendored API snapshots with commit pinning. |

Release 2 specs are pinned at `version: "2.0"` in frontmatter until the next release cut ([ADR-0021](decisions/0021-pinned-release-version-2-0.md)).

## How to use this bundle

**Implementing a component**

1. Read [platform/architecture.md](platform/architecture.md) for the end-to-end mental model.

2. Open the component folder ([oeg/](oeg/), [srm/](srm/), [fm/](fm/), [tf-sdk/](tf-sdk/), [portal/](portal/)) via its `index.md`.

2. Open the component folder ([oeg/](oeg/), [srm/](srm/), [fm/](fm/), [tf-sdk/](tf-sdk/), [data-lab/](data-lab/), [portal/](portal/)) via its `index.md`.

3. Follow architecture → interface contract → persistence model → flow walk-throughs in that order.

4. When a spec cites an ADR, read the decision record for the rationale behind the rule.

- **Search by metadata** — filter documents by `component`, `type`, `tags`, or `version` in frontmatter.

- **Traverse the graph** — follow bundle-absolute links and companion lists to pull related specs into context (IDE, doc site, or agent).

- **Validate release pinning** — run `scripts/check-spec-versions.sh` to confirm all in-scope specs remain at version `2.0`.

## Layout

| [fm/](fm/) | Federation Manager — cross-operator EWBI federation |

| [tf-sdk/](tf-sdk/) | Transformation Function SDK — vendor adapters inside SRM |

| [portal/](portal/) | Portal — developer portal and admin console |

| [data-lab/](data-lab/) | Data Lab — dataspace metadata catalogue |

| [decisions/](decisions/) | Architecture Decision Records |

| [external-specs/](external-specs/) | Vendored third-party API definitions |

| [archive/](archive/) | Superseded working documents |

# Data Lab (DL)

Released catalogue specification (`version: "0.1.0"`, [ADR-0071](/decisions/0071-data-lab-own-version-outside-release-pin.md)).

Four-part spec; read in order. Requirement status is in Requirements & Design §H.1;

open questions in Overview §F; implementation gaps in Implementation & Delivery §T.

* [Overview & Architecture](overview-and-architecture.md) - what the Data Lab is, scope and ownership, who sees what, terms, features, boundaries, assumptions, open questions

* [Requirements & Design](requirements-and-design.md) - requirements, components and interfaces, access control, flows, metadata model, lifecycle, errors

* [Implementation & Delivery](implementation-and-delivery.md) - code layout, configuration, deployment, observability, testing, known gaps, later releases, common changes

* [Interface Contract](interface-contract.md) - Data Lab API details, the dataset record, piveau API usage, worked examples

Normative metadata reference: [6G-DALI Metadata Application Profile (vendored snapshot)](/external-specs/6gdali-metadata-application-profile/VERSION.md) - DCAT-AP 3.0 + `dali:` testbed context + PROV-O + DQV, with layered SHACL shapes and the `dali:` ontology (ADR-0026, ADR-0070)