DEENESPTFRRUARHIKOZHNL

class ara::diag::DiagSovdErrorDomain

[SWS_DM_01809] Upstream: RS_AP_00119

class DiagSovdErrorDomain final :                public ara::core::ErrorDomain {...};

Error domain for errors originating from SOVD.

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Forwarding-Header#include "ara/diag/diag_fwd.h"
Scopenamespace ara::diag
Basisklasse(n)ara::core::ErrorDomain
Unique IDAs per ara::diag::DiagSovdErrorDomain in [SWS_CORE_90023]

User GuideAI-GENERATED

Defines the error domain for identification, text translation, and exception handling of errors from SOVD.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: c5b4c66a9279 Provenance Open questions (2)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

Defines the error domain for identification, text translation, and exception handling of errors from SOVD.

The class ara::diag::DiagSovdErrorDomain encapsulates the standardized error domain for SOVD-specific diagnostic errors within the AUTOSAR Adaptive Platform ([SWS_DM_01809]). Via its thread-safe member functions, it enables the reliable translation of numeric error codes into text messages as well as the controlled throwing of suitable C++ exception types ([SWS_DM_01814]). If C++ exceptions are disabled in the compiler toolchain, the method for throwing exceptions conformantly does not participate in overload resolution.

Context

The class ara::diag::DiagSovdErrorDomain maps the specific error domain for error conditions resulting from the SOVD (Service-Oriented Vehicle Diagnostics) subsystem ([SWS_DM_01809], AUTOSAR_AP_SWS_Diagnostics §8.51.3 “Class: DiagSovdErrorDomain”). As a final specialization of the base infrastructure class ara::core::ErrorDomain, it seamlessly integrates error codes and associated exception handling of the SOVD context into the unified error model of the AUTOSAR Adaptive Platform ([SWS_DM_01809]).

For standardized identification, the member function Name() provides the short name (ApApplicationErrorDomain.SN) of the error domain according to [SWS_CORE_90023] ([SWS_DM_01813], AUTOSAR_AP_SWS_Diagnostics §8.51.3 “Class: DiagSovdErrorDomain”). In addition, the class defines two central type aliases for its namespace: Errc acts as an alias for the underlying enumeration DiagSovdErrc ([SWS_DM_01810], AUTOSAR_AP_SWS_Diagnostics §8.51.3.1.1 “Type Alias: Errc”) and Exception represents the corresponding base exception class DiagSovdException ([SWS_DM_01811], AUTOSAR_AP_SWS_Diagnostics §8.51.3.1.2 “Type Alias: Exception”). Access to the domain in practice is mostly accomplished via the free function ara::diag::GetDiagSovdErrorDomain ([SWS_DM_01816], AUTOSAR_AP_SWS_Diagnostics §8.51.2.1.1 “GetDiagSovdErrorDomain”).

Lifecycle

Instantiation of ara::diag::DiagSovdErrorDomain is performed via the parameterless default constructor constexpr DiagSovdErrorDomain() noexcept ([SWS_DM_01812], AUTOSAR_AP_SWS_Diagnostics §8.51.3.2.1.1 “Default Constructor”). Thanks to the specification as constexpr and noexcept, creation is guaranteed to be exception-safe and can already occur at compile time or during static initialization. Interpretation: Providing the constexpr constructor likely allows the platform to maintain a long-lived singleton instance referenced via GetDiagSovdErrorDomain ([SWS_DM_01816]). Question Q-777076a993f1202d (open)

With respect to concurrency, all member functions of the class are explicitly declared as thread-safe (\"thread-safe\"). This applies to the constructor ([SWS_DM_01812]) as well as to the read operations Name() ([SWS_DM_01813]) and Message() ([SWS_DM_01814]) and to throwing exceptions via ThrowAsException() ([SWS_DM_01815]). Multiple threads can thus operate on the same domain instance in parallel and without external synchronization mechanisms.

Usage Path

The regular sequence for using ara::diag::DiagSovdErrorDomain is divided into the following steps:

Typical interaction for error resolution and exception handlingApplicationara::diag::GetDiagSovdErrorDomainara::diag::DiagSovdErrorDomainGetDiagSovdErrorDomain()const ara::core::ErrorDomain&Message(errorCode)const char* (Fehlertext)optC++ exceptions enabled and error escalation requiredThrowAsException(errorCode)throw DiagSovdException

Sequence diagram: Typical interaction sequence for resolving error descriptions and optionally throwing exceptions via the error domain. Sources: [SWS_DM_01814], [SWS_DM_01815], [SWS_DM_01816].

Error Scenarios

In the context of error handling, the interface of ara::diag::DiagSovdErrorDomain exhibits specific behavioral characteristics:

  • Guaranteed text return: The method Message is declared as noexcept and is fully exception-safe (\"exception safe\") ([SWS_DM_01814]). It never fails and always returns a valid, non-empty character string ([SWS_DM_01814]).
  • Targeted exception throwing: The method ThrowAsException is intended to throw exceptions and is therefore provided with noexcept(false) as well as the classification \"not exception safe\" ([SWS_DM_01815]). Depending on the passed ara::core::ErrorCode, it throws the corresponding exception of type Exception (DiagSovdException) ([SWS_DM_01811], [SWS_DM_01815]).
  • Disabled C++ exceptions: According to [SWS_CORE_10304], ThrowAsException does not participate in overload resolution if C++ exceptions are disabled in the compiler toolchain ([SWS_DM_01815]). In such environments, the function is not available, and errors must mandatorily be evaluated via error codes.

This guide is based exclusively on the specification requirements of the AUTOSAR module diag (Release R25-11).

Member map

Constructors and destructor

1

Type aliases

2

Class diagram

Hohle Dreieckspfeile = Vererbung (zeigt zur Basisklasse); Klicken öffnet die jeweilige Klassenseite.

G nara__diag__DiagSovdErrorDomain991 DiagSovdErrorDomain + DiagSovdErrorDomain() + Message() + Name() + ThrowAsException() nara__core__ErrorDomain335 ErrorDomain nara__diag__DiagSovdErrorDomain991->nara__core__ErrorDomain335

Detail view

Select an entry in the outline.

Constructors and destructor

Default constructor.

constexpr DiagSovdErrorDomain () noexcept;

Methods

Message function

Translate an error code value into a text message.

const char * Message (ara::core::ErrorDomain::CodeType errorCode) const noexcept override;
Name function

Return the "shortname" ApApplicationErrorDomain.SN of this error domain.

const char * Name () const noexcept override;

Throw the exception type corresponding to the given ErrorCode. As per [SWS_CORE_10304], this function does not participate in overload resolution when C++ exceptions are disabled in the compiler toolchain.

void ThrowAsException (const ara::core::ErrorCode &errorCode) const noexcept(false) override;

Type aliases

Errc type alias

Alias for the error code value enumeration.

using Errc = DiagSovdErrc;
Exception type alias

Alias for the exception base class.

Method documentation

function DiagSovdErrorDomain [SWS_DM_01812] Upstream: RS_AP_00119

constexpr DiagSovdErrorDomain () noexcept;

Default constructor.

AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: e054a1afabf9 Provenance Open questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

use

The default constructor initializes an instance of the error domain ara::diag::DiagSovdErrorDomain [SWS_DM_01812] in accordance with AUTOSAR_AP_SWS_Diagnostics §8.51.3.2.1.1 “Default Constructor”. The function is declared as constexpr as well as noexcept and requires the inclusion of the header #include "ara/diag/diag_sovd_error_domain.h" [SWS_DM_01812].

Interaction and Call Context

In typical application scenarios, direct manual instantiation via this constructor should rarely be required, since the functional interface ara::diag::GetDiagSovdErrorDomain() already provides a reference to the global instance of the error domain [SWS_DM_01816]. Question Q-8c4b22173b01dce7 (open)

The class DiagSovdErrorDomain defines the error domain for SOVD and provides essential types and functions:

Error Handling and Concurrency

As a parameterless noexcept function, the constructor does not throw any exceptions. According to the specification, the call is exception-safe ("exception safe") and concurrently thread-safe ("thread-safe") [SWS_DM_01812]. No specific preconditions or error codes are defined for the constructor.

This text was generated by an AI and serves as documentation supplement.

Implementer's Guide to follow (complexity I2)

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Scopeclass ara::diag::DiagSovdErrorDomain
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01812
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01812@rel:R25-11#0ace1d49
Content hash
0ace1d49
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01812
Status: valid/unmigrated Version: rel:R25-11#9902f400 Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01812@rel:R25-11#9902f400
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#0ace1d492026-09-30
  • R23-11rel:R23-11#c4e261b62026-10-14
  • R24-11rel:R24-11#17b155a72026-10-14
  • R25-11rel:R25-11#9902f4002026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

function Message [SWS_DM_01814] Upstream: RS_AP_00119

const char * Message (ara::core::ErrorDomain::CodeType errorCode) const noexcept override;

Translate an error code value into a text message.

AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 83c49eafd3e0 Provenance Open questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

The member function Message of class ara::diag::DiagSovdErrorDomain serves to synchronously translate a numeric error code into a readable text message [SWS_DM_01814] (evidenced in AUTOSAR_AP_SWS_Diagnostics p. 69). It is provided via the header file ara/diag/diag_sovd_error_domain.h in namespace ara::diag.

The following specification characteristics apply to the call and runtime behavior:

  • Usage and semantics: As an input parameter, errorCode of type ara::core::ErrorDomain::CodeType is passed. The function synchronously returns a pointer to a constant character string (const char *) that contains the textual error description. The specification bindingly guarantees that this return value is never nullptr [SWS_DM_01814].
  • Error handling and robustness: The interface is qualified with noexcept and defined as exception safe (exception safe) [SWS_DM_01814]. No C++ exceptions are thrown. Interpretation: When passing an undefined or unknown error code, the implementation is likely to return a standardized informational message in order to fulfill the guarantee against null pointers. Question Q-c115f3da24bde8bd (open)
  • Concurrency: The method is declared as a const operation and explicitly specified as thread-safe (thread-safe) [SWS_DM_01814]. It does not modify internal states, is subject to no sequencing constraints, and can be called in parallel from multiple threads without external locks or synchronization mechanisms.
  • Interplay in Diagnostic Management: The method provides the standardized text translation for the SOVD error domain. It follows the uniform architecture pattern of the Adaptive Platform and corresponds in signature and behavior to the Message implementations of related diagnostic error domains such as DiagErrorDomain [SWS_DM_00522], DiagUdsNrcErrorDomain [SWS_DM_00534], DiagOfferErrorDomain [SWS_DM_00994], and DiagReportingErrorDomain [SWS_DM_01001].

This usage note was generated automatically based on the specification.

Implementer's Guide to follow (complexity I1)

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Scopeclass ara::diag::DiagSovdErrorDomain
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Parameter (in)

ParameterBeschreibung
errorCodethe error code value

Rückgabewert

TypBeschreibung
const char *the text message, never nullptr

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01814
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01814@rel:R25-11#82b505e5
Content hash
82b505e5
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01814
Status: valid/unmigrated Version: rel:R25-11#ffbd0e80 Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01814@rel:R25-11#ffbd0e80
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#82b505e52026-09-30
  • R23-11rel:R23-11#f2dfd27e2026-10-14
  • R24-11rel:R24-11#ffbd0e802026-10-14
  • R25-11rel:R25-11#ffbd0e802026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

function Name [SWS_DM_01813] Upstream: RS_AP_00119

const char * Name () const noexcept override;

Return the "shortname" ApApplicationErrorDomain.SN of this error domain.

AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: f69f6a515368 Provenance Open questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

use

The method Name of class ara::diag::DiagSovdErrorDomain returns the short name (ApApplicationErrorDomain.SN) of the SOVD error domain synchronously as a C string (const char*) ([SWS_DM_01813]; AUTOSAR_AP_SWS_Diagnostics §7 “Diagnostics”). The function expects no parameters and is provided via header ara/diag/diag_sovd_error_domain.h ([SWS_DM_01813]). Interpretation: The returned pointer is likely to point to an immutable, statically stored character string that remains valid throughout the entire runtime. Question Q-b7b74a09ea645e46 (open)

Error Handling and Concurrency

The function is declared as noexcept and considered exception safe (exception safe) ([SWS_DM_01813]). It reports no error codes and generates neither DET nor DEM entries. Regarding concurrency, the method is specified as thread-safe (thread-safe) ([SWS_DM_01813]). It thus possesses reentrant properties and can be called from arbitrary threads without external synchronization mechanisms.

Interaction

The interface follows the uniform name querying pattern for error domains in adaptive diagnostics. Corresponding implementations can be found in ara::diag::DiagErrorDomain ([SWS_DM_00521]), ara::diag::DiagUdsNrcErrorDomain ([SWS_DM_00533]), ara::diag::DiagOfferErrorDomain ([SWS_DM_00993]), and ara::diag::DiagReportingErrorDomain ([SWS_DM_01000]). It typically serves for logging and identifying error domains in the SOVD context.

This usage note was generated automatically and is based on the AUTOSAR Adaptive Platform R25-11 specification.

Implementer's Guide to follow (complexity I1)

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Scopeclass ara::diag::DiagSovdErrorDomain
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Rückgabewert

TypBeschreibung
const char *As per ara::diag::DiagSovdErrorDomain in [SWS_CORE_ 90023]

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01813
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01813@rel:R25-11#75e08407
Content hash
75e08407
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01813
Status: valid/unmigrated Version: rel:R25-11#677ee3b1 Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01813@rel:R25-11#677ee3b1
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#75e084072026-09-30
  • R23-11rel:R23-11#91f360a72026-10-14
  • R24-11rel:R24-11#1d9d4d622026-10-14
  • R25-11rel:R25-11#677ee3b12026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

function ThrowAsException [SWS_DM_01815] Upstream: RS_AP_00119

void ThrowAsException (const ara::core::ErrorCode &errorCode) const noexcept(false) override;

Throw the exception type corresponding to the given ErrorCode. As per [SWS_CORE_10304], this function does not participate in overload resolution when C++ exceptions are disabled in the compiler toolchain.

AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: e5c7c7c60bd3 Provenance Open questions (1)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

use

The method ThrowAsException of class ara::diag::DiagSovdErrorDomain ([SWS_DM_01815], declared in header ara/diag/diag_sovd_error_domain.h; see AUTOSAR_AP_SWS_Diagnostics §8.51.3.2.2.3 “ThrowAsException”) serves to convert an error code synchronously into the assigned C++ exception type. It accepts the input parameter errorCode of type const ara::core::ErrorCode & and has no return value (void). When called, it throws the exception corresponding to the error code according to the signature with noexcept(false).

Error Handling and Boundary Conditions

The specification classifies the method as “not exception safe” ([SWS_DM_01815]). Interpretation: This classification is likely justified by the fact that throwing an exception intentionally leaves regular control flow. Question Q-23924e13760f4186 (open) A key constraint concerns the compiler toolchain: According to [SWS_CORE_10304], ThrowAsException does not participate in overload resolution if C++ exceptions are disabled in the compiler.

Concurrency and Interaction

The function is classified as thread-safe (thread-safe) ([SWS_DM_01815]) and allows concurrent calls. The behavior follows the standardized scheme for diagnostic error domains in module DM. Analogous definitions apply to ara::diag::DiagErrorDomain ([SWS_DM_00523], see AUTOSAR_AP_SWS_Diagnostics §8.11.3.2.2.3 “ThrowAsException”), ara::diag::DiagOfferErrorDomain ([SWS_DM_00995], see AUTOSAR_AP_SWS_Diagnostics §8.11.5.2.2.3 “ThrowAsException”), ara::diag::DiagReportingErrorDomain ([SWS_DM_01002], see AUTOSAR_AP_SWS_Diagnostics §8.11.7.2.2.3 “ThrowAsException”), and ara::diag::DiagUdsNrcErrorDomain ([SWS_DM_00535], see AUTOSAR_AP_SWS_Diagnostics §8.12.3.2.2.3 “ThrowAsException”).

This usage note was generated automatically based on the AUTOSAR Release R25-11 specification.

Implementer's Guide to follow (complexity I2)

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Scopeclass ara::diag::DiagSovdErrorDomain
Exception-Sicherheitnot exception safe
Thread-Sicherheitthread-safe

Parameter (in)

ParameterBeschreibung
errorCodethe ErrorCode instance

Rückgabewert

TypBeschreibung
None

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01815
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01815@rel:R25-11#2fdaf071
Content hash
2fdaf071
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01815
Status: valid/unmigrated Version: rel:R25-11#975d8ee0 Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01815@rel:R25-11#975d8ee0
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#2fdaf0712026-09-30
  • R23-11rel:R23-11#1a45209e2026-10-14
  • R24-11rel:R24-11#57b430f42026-10-14
  • R25-11rel:R25-11#975d8ee02026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

Type alias documentation

type alias Errc [SWS_DM_01810] Upstream: RS_AP_00119

using Errc = DiagSovdErrc;

Alias for the error code value enumeration.

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Scopeclass ara::diag::DiagSovdErrorDomain
SymbolErrc

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01810
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01810@rel:R25-11#b173fbe8
Content hash
b173fbe8
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01810
Status: valid/unmigrated Version: rel:R25-11#8846b3aa Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01810@rel:R25-11#8846b3aa
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#b173fbe82026-09-30
  • R23-11rel:R23-11#8846b3aa2026-10-14
  • R24-11rel:R24-11#8846b3aa2026-10-14
  • R25-11rel:R25-11#8846b3aa2026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill

type alias Exception [SWS_DM_01811] Upstream: RS_AP_00119

using Exception = DiagSovdException;

Alias for the exception base class.

Header-Datei#include "ara/diag/diag_sovd_error_domain.h"
Scopeclass ara::diag::DiagSovdErrorDomain
SymbolException

Request a governed re-review of this record. The record is not changed immediately.

Record
AUTOSAR/AP/record/SWS_DM_01811
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_DM_01811@rel:R25-11#1c571c47
Content hash
1c571c47
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_Diagnostics.pdf#nameddest=SWS_DM_01811
Status: valid/unmigrated Version: rel:R25-11#afe352e2 Versionshistorie & Revisions (1 transition, 4 revision)
Current State
valid/unmigrated
Reason
mechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record
Campaign
2026-08-13-status-backfill
Active Version
AUTOSAR/AP/record/SWS_DM_01811@rel:R25-11#afe352e2
Point-in-Time History:
Recorded Revisions (4):
  • R25-11rel:R25-11#1c571c472026-09-30
  • R23-11rel:R23-11#afe352e22026-10-14
  • R24-11rel:R24-11#afe352e22026-10-14
  • R25-11rel:R25-11#afe352e22026-10-14 active
DateActorTransitionReason / RationaleCampaign
2026-08-13toolnone → valid/unmigratedmechanically backfilled by migriere_status_backfill.py -- no per-field curation history exists yet for this record2026-08-13-status-backfill