Commit 1cb4c77f authored by Dimitrios Gogos's avatar Dimitrios Gogos
Browse files

docs(decisions): state the ADR rules in the index and note the unused 0052 

The index pointed readers at the record-decision skill, which is not
part of the published repo; it now states the numbering, change and
status rules itself. ADR-0052 was skipped when that record became
ADR-0053, so the list says so instead of leaving a silent gap.

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

decisions/index.md

+5 −2
Changes for decisions/index.md: 5 added lines, 2 removed lines.
Original line number Diff line number Diff line 
# Decisions



Numbered, immutable Architecture Decision Records. Specs state only the current rule;

the reasoning lives here. Never renumber; supersede instead (see the record-decision skill).

Numbered Architecture Decision Records. Specs state only the current rule; the reasoning

lives here. Numbers are permanent: a record is never renumbered and a number is never reused.

To change a decision, record a new ADR that supersedes or amends it, and name the new ADR in

the older record's status line. Status is `proposed`, `accepted`, or `superseded by ADR-NNNN`.



* [ADR-0001](0001-srm-command-event-subject-scheme.md) - SRM DataBus contract: command.srm.* / event.srm.* with versioned envelope and per-command schemas

* [ADR-0002](0002-no-stored-capacity.md) - SRM holds no stored capacity or reservations
@@ -54,6 +56,7 @@ the reasoning lives here. Never renumber; supersede instead (see the record-deci 
* [ADR-0049](0049-data-lab-standalone-profile-shared-ingress-and-iam.md) - Data Lab is a standalone compose profile behind the platform Nginx and Keycloak (realm `dataspace`); no DataBus/SRM/OEG coupling in the catalogue release

* [ADR-0050](0050-oeg-federation-lifecycle-proxy-errors-are-gsma-problem-json.md) - OEG's federation-lifecycle proxy endpoints (§N.7, ADR-0046) return OPG.04 `application/problem+json` `ProblemDetails` for every error - FM's errors relayed unchanged, OEG's own 400/401/403/502/503 from a fixed template; ADR-0030's `ErrorInfo` rule is scoped to OEG's CAMARA northbound surface

* [ADR-0051](0051-oeg-fronts-federation-lifecycle-ewbi-byte-for-byte.md) - OEG fronts eight GSMA federation-lifecycle operations on its own platform namespace, `/platform/v1/federation/partners/{partnerOpId}/federations/...`, scoped by a registered `partnerOpId` (create/read/update/delete federation, fed-context-id lookup, zone list/subscribe/details/unsubscribe), forwarding the raw GSMA request/response byte-for-byte to FM including the query string, pinned to GSMA OPG.04 v6.0 / artifact v1.4.0; operator-triggered outbound only, separated from inbound EWBI at the ingress; also proxies partner registration (`POST`/`GET`/`PATCH` `/platform/v1/federation/partners[/{partnerOpId}]` onto FM's L.2, amended 2026-09-24) our own federation identity (`GET /platform/v1/federation/identity`, amended 2026-10-13), and agreements with the zones they can offer (`/platform/v1/federation/agreements[/{agreementId}]`, `/platform/v1/federation/local-zones`, amended 2026-10-15); keeps ADR-0046's sync-HTTP/stateless/no-DataBus transport and ADR-0050's error model (amends this ADR's own first version, which used the bare canonical OPG.04 paths and lost the partner addressing GSMA gets for free from the URL)

* ADR-0052 - not used; the number was skipped when that record became ADR-0053

* [ADR-0053](0053-srm-fm-federated-lifecycle-handoff-over-the-databus.md) - SRM hands federated deploys and terminates to FM as `command.fm.service.deploy` / `.terminate` on `OOP_TASKS`, and FM reports the outcome as `event.fm.operation.completed` on `OOP_EVENTS`; zone lookups stay synchronous HTTP reads. `completion_basis` separates a confirmed deploy from a terminate the partner only accepted. SRM writes a `service_order` and tracks pending partner targets in order-local `federated_handoff` (no partner zone/instance inventory); `payload_snapshot` stays frozen command audit; completes the order from FM's answer. FM waits 30 minutes by default for a deploy callback. Amends ADR-0001/0022 (FM consumes `command.fm.>`) and ADR-0046's DataBus scope; resolves G4

* [ADR-0054](0054-fm-receives-gsma-callbacks-through-one-router.md) - FM receives every OPG.04 callback on `/operatorplatform/federation/v1/callbacks/{kind}`: one router that checks the `fed-mgmt-notif` scope and that `federationContextId` is an outbound context of the calling partner, then a per-kind idempotent handler. `onPartnerStatusEvent` first; `FM_PARTNER_STATUS_LINK` moves to `/callbacks/partner-status`. The `federation` realm gets `fed-mgmt-notif` as an optional scope on partner clients

* [ADR-0055](0055-topology-discovery-is-a-separate-adapter-interface.md) - topology discovery is a separate TopologyDiscoveryAdapter interface, not optional methods on CapabilityExecutionAdapter (amends ADR-0027)