Commit 48098b6a authored by Dimitrios Gogos's avatar Dimitrios Gogos
Browse files

docs(decisions): accept the eleven implemented proposed ADRs 

ADR-0047, 0048, 0053, 0054, 0061 and 0063-0068 are implemented in the
component repos, so their status moves from proposed to accepted. Drops
ADR-0061's reference to an internal merge request.

Co-Authored-By: default avatarClaude Opus 5.5 <noreply@anthropic.com>
parent 335bf53a

decisions/0047-terminal-record-read-follows-camara-schema.md

+2 −2
Changes for decisions/0047-terminal-record-read-follows-camara-schema.md: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -4,12 +4,12 @@ title: "ADR-0047: Terminal-record read behaviour follows each family's own CAMAR 
description: "ADR-0034's rule that reads of a terminal record return 404 rests on CAMARA having no representation for a deleted resource. That holds for QoD's qosStatus enum and not for Traffic Influence, whose state enum documents 'deletion in progress' and 'deleted'. The rule is scoped to families whose vendored schema has no deleted representation."

tags: [adr]

timestamp: 2026-09-09T00:00:00Z

status: "proposed"

status: "accepted"

---



# ADR-0047: Terminal-record read behaviour follows each family's own CAMARA schema



**Status:** proposed

**Status:** accepted

**Date:** 2026-09-09

**Affects:** amends [ADR-0034](/decisions/0034-network-capability-delete-is-async.md), [oeg/interface-contract.md](/oeg/interface-contract.md), [srm/interface-contract.md](/srm/interface-contract.md) §E.1

decisions/0048-platform-roles.md

+2 −2
Changes for decisions/0048-platform-roles.md: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -4,12 +4,12 @@ title: "ADR-0048: Three platform roles, API products granted per user and client 
description: "Realm oop has exactly three realm roles. Every new user gets app-provider on registration but, in normal mode, calls only the API products granted to them: each CAMARA scope is issued only to holders of its product role. User administration runs through a dedicated Admin API client. Tenancy is the token's organization claim, else its subject. A development mode switches login off for local use."

tags: [adr, security, keycloak, portal, oeg]

timestamp: 2026-10-04T00:00:00Z

status: "proposed"

status: "accepted"

---



# ADR-0048: Three platform roles, API product grants, and tenancy



**Status:** proposed — decision 6's "`app_provider_id` is the token's `sub`" is amended by [ADR-0066](/decisions/0066-api-clients-through-keycloak-client-registration.md): the `app_provider_id` claim when present, else `sub`

**Status:** accepted — decision 6's "`app_provider_id` is the token's `sub`" is amended by [ADR-0066](/decisions/0066-api-clients-through-keycloak-client-registration.md): the `app_provider_id` claim when present, else `sub`

**Date:** 2026-10-04

**Affects:** [platform/architecture.md](/platform/architecture.md) §Security Architecture → Roles, [oeg/overview-and-architecture.md](/oeg/overview-and-architecture.md) (role and scope checks, F4), [oeg/interface-contract.md §9](/oeg/interface-contract.md#9-data-dictionary) (`tenant_id`, `app_provider_id`, `api_subscriptions`), [platform/glossary.md](/platform/glossary.md), [ADR-0006](/decisions/0006-oeg-db-schema-consolidation.md), [ADR-0035](/decisions/0035-qod-session-service-specification.md), portal backend `Role` enum, Helm `charts/keycloak` (realm `oop`)

decisions/0053-srm-fm-federated-lifecycle-handoff-over-the-databus.md

+2 −2
Changes for decisions/0053-srm-fm-federated-lifecycle-handoff-over-the-databus.md: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -4,12 +4,12 @@ title: "ADR-0053: SRM hands federated deploys and terminates to FM over the Data 
description: "SRM hands federated deploys and terminates to FM over the DataBus, and FM reports the outcome the same way"

tags: [adr]

timestamp: 2026-09-22T00:00:00Z

status: "proposed"

status: "accepted"

---



# ADR-0053: SRM hands federated deploys and terminates to FM over the DataBus, and FM reports the outcome the same way



**Status:** proposed (amended 2026-09-25: SRM keeps instance rows for partner targets, superseded on 2026-10-08; 2026-09-29: `partner_not_found`; 2026-10-08: order-local `federated_handoff` instead of partner inventory; 2026-10-15: SRM reads FM's instance before a federated terminate)

**Status:** accepted (amended 2026-09-25: SRM keeps instance rows for partner targets, superseded on 2026-10-08; 2026-09-29: `partner_not_found`; 2026-10-08: order-local `federated_handoff` instead of partner inventory; 2026-10-15: SRM reads FM's instance before a federated terminate)

**Date:** 2026-09-22

**Affects:** [fm/overview-and-architecture.md](/fm/overview-and-architecture.md) (open item G4, UC-FM-07), [fm/requirements-and-design.md](/fm/requirements-and-design.md) (the SRM→FM hand-off section §L.3a, FM's DataBus sections §K.2 and §M), [srm/interface-contract.md](/srm/interface-contract.md) (stream configuration §D, the federated hand-off flow §F.4a), [srm/persistence-model.md](/srm/persistence-model.md) (`service_order.federated_handoff`), [platform/architecture.md](/platform/architecture.md) (DataBus configuration)

**Amends:** ADR-0001 and ADR-0022, where they make SRM the only consumer of `OOP_TASKS`; ADR-0046, where it keeps the DataBus to `command.srm.*` / `event.srm.*`

decisions/0054-fm-receives-gsma-callbacks-through-one-router.md

+2 −2
Changes for decisions/0054-fm-receives-gsma-callbacks-through-one-router.md: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -4,12 +4,12 @@ title: "ADR-0054: FM receives every GSMA callback through one router under /oper 
description: "FM receives every GSMA callback through one router under /operatorplatform/federation/v1/callbacks/{kind}"

tags: [adr]

timestamp: 2026-09-22T00:00:00Z

status: "proposed"

status: "accepted"

---



# ADR-0054: FM receives every GSMA callback through one router under `/operatorplatform/federation/v1/callbacks/{kind}`



**Status:** proposed

**Status:** accepted

**Date:** 2026-09-22

**Affects:** [fm/requirements-and-design.md](/fm/requirements-and-design.md) (new §L.1a, callbacks FM receives), [fm/overview-and-architecture.md](/fm/overview-and-architecture.md) (partner authentication)

decisions/0061-use-short-execution-action-vocabulary.md

+2 −2
Changes for decisions/0061-use-short-execution-action-vocabulary.md: 2 added lines, 2 removed lines.
Original line number Diff line number Diff line
@@ -4,12 +4,12 @@ title: "ADR-0061: Use one short execution-action vocabulary at the SRM–TF-SDK 
description: "The five advertised actions and public execution methods share one vocabulary; SRM maps its business operations to it before placement."

tags: [adr, tf-sdk, srm]

timestamp: 2026-09-29T00:00:00Z

status: "proposed"

status: "accepted"

---



# ADR-0061: Use one short execution-action vocabulary at the SRM–TF-SDK boundary



**Status:** proposed in Architecture MR !5

**Status:** accepted

**Date:** 2026-09-29

**Affects:** [ADR-0027](/decisions/0027-tfsdk-generic-capability-adapter-interface.md), [ADR-0058](/decisions/0058-adapters-declare-their-own-executable-surface.md), [TF-SDK requirements](/tf-sdk/requirements-and-design.md), [SRM placement](/srm/interface-contract.md), SRM and TF-SDK implementations