DEENESPTFRRUARHIKOZHNL

namespace ara::exec

User GuideAI-GENERATED

Controls the process lifecycle, monitors execution states, and coordinates state transitions of function groups.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 03a628bdc05e Provenance Open questions (2)
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

Controls the process lifecycle, monitors execution states, and coordinates state transitions of function groups.

The namespace provides interfaces for process management and the control of function groups on the AUTOSAR Adaptive Platform. Processes use the client to report their execution state kRunning to Execution Management after successful initialization [SWS_EM_02000]. State Management requests transitions of function groups via interfaces, while impermissible state changes or communication errors are captured via standardized error codes [SWS_EM_02281]. Strict adherence to the transition order is mandatory.

Context

The namespace ara::exec provides the interfaces of Execution Management on the AUTOSAR Adaptive Platform. The module is responsible for starting, controlling, and monitoring processes as well as coordinating higher-level system and function group states. Central actors include application processes, State Management, and Execution Management itself. Processes use class ExecutionClient to report their internal runtime state to Execution Management. State Management in turn uses the interface StateClient to request state changes between function groups (FunctionGroup and FunctionGroupState). For error events at function group level, the type alias ExecutionError is used [SWS_EM_02541], which can be transported via ExecutionErrorEvent.

Lifecycle

The execution lifecycle of a process is controlled by Execution Management [SWS_EM_02000]. After scheduling, a newly started process is initially in an implicit state Initializing in which no application program code has been executed yet. Execution Management assumes that this initialization state lasts until the process actively reports state ExecutionState::kRunning via its ExecutionClient [SWS_EM_02000]. The enumeration ExecutionState is strictly restricted to those states that can be reported by processes to Execution Management and therefore contains exclusively the state kRunning [SWS_EM_02000]. If Execution Management requests termination, the process transitions to phase Terminating, which concludes with the final termination of the process [SWS_EM_02000].

prozess_lebenszyklus Initializing Initializing Running Running Initializing->Running Meldung kRunning Terminating Terminating Running->Terminating Terminierungsanforderung Terminiert Terminiert Terminating->Terminiert Process terminated

State diagram: Lifecycle of a process from the perspective of Execution Management with implicit states and reporting of kRunning. Sources: [SWS_EM_02000]

Usage Path

A typical usage flow is divided into the following phases:

  • After system startup, the process is created by Execution Management and performs its internal initialization [SWS_EM_02000].
  • As soon as initialization has been successfully completed, the process reports the state ExecutionState::kRunning to Execution Management via an instance of ExecutionClient [SWS_EM_02000].
  • Execution Management acknowledges this transition; however, if kRunning is reported when the process is already in the running state, this is rejected as an invalid transition ExecErrc::kInvalidTransition [SWS_EM_02281].
  • During further operation, State Management requests coordinated state transitions for function groups via StateClient as required.
State reporting of a process to Execution ManagementProcessExecutionClientExecution ManagementUse Case: Startup and state reportingProzessinitialisierung abgeschlossenZustandsmeldung kRunningMeldung an Execution ManagementaltSuccessful transitionState transition appliedErfolg (void)Fehlerfall (z. B. kInvalidTransition)Fehler aufgetretenReturn ExecErrc::kInvalidTransition

Sequence diagram: Call sequence during state reporting via ExecutionClient and handling of erroneous transitions. Sources: [SWS_EM_02000], [SWS_EM_02281]

Error Scenarios

Error situations are mapped in namespace ara::exec via the enumeration type ExecErrc and the error domain ExecErrorDomain [SWS_EM_02281]. A reference to the global domain object is returned by the thread- and exception-safe function GetExecErrorDomain() [SWS_EM_02290]. Concrete error objects of type ara::core::ErrorCode are created via the helper function MakeErrorCode() by passing the error code and vendor-specific context data [SWS_EM_02291]; class ExecException is also available for exception handling.

Specified error causes include, among others, [SWS_EM_02281]:

  • ExecErrc::kNoCommunication: Signals communication errors between client and Execution Management or between State Management and Execution Management. At system level, such a state would likely require entering an unrecoverable state [SWS_EM_02281]. Question Q-ad08207b6a16c6f9 (open)
  • ExecErrc::kInvalidTransition: Invalid transition, for example when a process repeatedly reports kRunning [SWS_EM_02281].
  • ExecErrc::kOperationFailed: An operation fails, for instance when a function group transition cannot be completed because kRunning was not reported in time [SWS_EM_02281].
  • ExecErrc::kOperationCanceled: A state transition of a function group was canceled by a newer request [SWS_EM_02281].
  • ExecErrc::kIntegrityOrAuthenticityCheckFailed: The integrity or authenticity check of a process to be started fails [SWS_EM_02281].
  • ExecErrc::kUnexpectedTermination: Abnormal termination during a transition [SWS_EM_02281].
  • ExecErrc::kInvalidMetaModelIdentifier as well as ExecErrc::kInvalidArgument: Impermissible metamodel identifiers or invalid parameter values [SWS_EM_02281].

This guide is based on the AUTOSAR Adaptive R25-11 specification for the Execution Management module (ara::exec).

Topic map

KI-gestützte Gruppierung auf Basis der Records und Spezifikationsauszüge; keine Gliederung aus der AUTOSAR-Spezifikation.

Class diagram

Abgerundete Rahmen = Namespace- bzw. Klassen-Scopes; hohle Dreieckspfeile = Vererbung (zeigt zur Basisklasse); graue Boxen = namespace-fremde bzw. externe Basisklassen. Klicken öffnet die jeweilige Klassen- bzw. cppreference-Seite.

G cluster_ns ara::exec nara__exec__ExecErrorDomain ExecErrorDomain next_ara__core__ErrorDomain ara::core::ErrorDomain nara__exec__ExecErrorDomain->next_ara__core__ErrorDomain nara__exec__ExecException ExecException next_ara__core__Exception ara::core::Exception nara__exec__ExecException->next_ara__core__Exception nara__exec__ExecutionClient ExecutionClient nara__exec__ExecutionErrorEvent «struct» ExecutionErrorEvent nara__exec__FunctionGroup FunctionGroup nara__exec__FunctionGroupState FunctionGroupState nara__exec__StateClient StateClient

Detail view

Select an entry in the outline.

Fehlerbehandlung

Defines a class representing the Execution Management error domain.

inherits from ara::core::ErrorDomain

Defines a class for exceptions to be thrown by the Execution Management.

inherits from ara::core::Exception

Returns a reference to the global ExecErrorDomain object.

const ara::core::ErrorDomain & GetExecErrorDomain () noexcept;
MakeErrorCode function

Creates an instance of ErrorCode.

ExecErrc enumeration

Defines an enumeration class for the Execution Management error codes.

enum class ExecErrc : ara::core::ErrorDomain::CodeType {...};

Ausführungsfehler

Represents an execution error event which happens in a Function Group.

ExecutionError type alias

Represents the execution error.

using ExecutionError = std::uint32_t;

Funktionsgruppen

Class representing Function Group defined in meta-model (ARXML)

Class representing Function Group State defined in meta-model (ARXML)

ara::exec::StateClient is an interface of Execution Management that is used by State Management to request transitions between Function Grou

Prozesszustand

The ara::exec::ExecutionClient API provides the functionality for a Process to report its Execution State to the Execution Management.

ExecutionState enumeration

Defines the internal states of a Process. Scoped enumeration of uint32_t. Please note that ara::exec::ExecutionState includes only states reportable by the Process to Execution Management and therefore does not include enumerations e.g. the "Initializing" state mentioned in Figure 7.2 and Figure 7.12, which are an implied states for Execution Management. The Initializing state starts when Process is first scheduled (so no code executed yet) and ends when kRunning is reported ([SWS_EM_01004]). The Terminating state starts when termination is requested by Execution Management and ends when the Process terminates ([SWS_EM_01404]). For the reasons mentioned, Execution Management assumes that Process is in initializing state until kRunning will be reported by it.

enum class ExecutionState : std::uint32_t {...};

Enumerations

enumeration ExecErrc [SWS_EM_02281] Upstream: RS_AP_00130, RS_AP_00122, RS_AP_00127, RS_AP_00154, RS_AP_00125, RS_AP_00142, RS_AP_00129, RS_AP_00149

enum class ExecErrc :            ara::core::ErrorDomain::CodeType {...};

Defines an enumeration class for the Execution Management error codes.

Header-Datei#include "ara/exec/exec_error_domain.h"
Forwarding-Header#include "ara/exec/exec_fwd.h"
Scopenamespace ara::exec
SymbolExecErrc
Basistypara::core::ErrorDomain::CodeType

Werte

EnumeratorBeschreibung
kNoCommunication=3 Communication error occurred, e.g. request cannot be send or result cannot be retrieved
kInvalidMetaModelIdentifier=4 Wrong meta model identifier passed to a function
kOperationCanceled=5 Transition to the requested Function Group state was canceled by a newer request
kOperationFailed=6 Requested operation could not be performed, e.g. Function Group state transition cannot be finished because kRunning was not reported on time
kInvalidTransition=9 Invalid transition (e.g. Process attempted to report kRunning, when it was already in a Running Process State)
kIntegrityOrAuthenticityCheckFailed= 14 Integrity or authenticity check for a Process to be spawned in the requested Function Group state failed
kUnexpectedTermination= 15 Abnormal Termination during a Function Group State transition occurred
kInvalidArgument= 16 Passed argument doesn’t appear to be valid.
Hinweise: If a kNoCommunication occurs at Execution Management or State Management level (or communication between both), the system may need to enter an Unrecoverable State. The internal mechanisms can detect this issue in the moment that a communication attempt occurs. This is not the case for applications that are using the interface of the ara::exec:: ExecutionClient or ara::exec::StateClient - they eventually get a communication error in the moment of the API use, i.e. possibly after the actual error occurrence. However, this is not problematic as the recovery options are limited from a client side viewpoint.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: d5c66509eff5 Provenance
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

The enumeration ExecErrc [SWS_EM_02281] defines error codes for Execution Management in namespace ara::exec based on underlying type ara::core::ErrorDomain::CodeType. It is used together with MakeErrorCode [SWS_EM_02291] for encapsulation in ara::core::ErrorCode and passed to callers synchronously via ara::core::Result or asynchronously using ara::core::Future.

The enumerators cover different error states [SWS_EM_02281]:

  • kNoCommunication indicates communication errors when sending requests or retrieving results [SWS_EM_02281]. If this occurs between Execution Management and State Management, the system can enter an unrecoverable state [SWS_EM_02281]. Clients such as ExecutionClient or StateClient only notice this during the next method call, with client-side recovery options being limited [SWS_EM_02281].
  • kOperationCanceled and kOperationFailed occur during state transitions of function groups [SWS_EM_02281], for example during SetState [SWS_EM_02278] or when a machine startup transition is canceled [SWS_EM_02279].
  • kInvalidTransition indicates invalid process transitions, for example when a process repeatedly reports kRunning [SWS_EM_02281], relevant for ReportExecutionState [SWS_EM_02003].
  • kIntegrityOrAuthenticityCheckFailed, kUnexpectedTermination, kInvalidMetaModelIdentifier, and kInvalidArgument handle errors during integrity checks, abnormal process terminations during function group state transitions, or invalid function parameters [SWS_EM_02281].

Callers evaluate these error codes to determine whether state transitions completed successfully, were preempted by subsequent requests, or were blocked by configuration errors [SWS_EM_02281].

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

Implementer's Guide to follow (complexity I1)

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

Record
AUTOSAR/AP/record/SWS_EM_02281
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_EM_02281@rel:R25-11#24bf4c2a
Content hash
24bf4c2a
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_ExecutionManagement.pdf#nameddest=SWS_EM_02281
Status: valid/unmigrated Version: rel:R25-11#402d3486 Versionshistorie & Revisions (1 transition, 8 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_EM_02281@rel:R25-11#402d3486
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#24bf4c2a2026-09-30
  • R19-11rel:R19-11#e465fc4b2026-10-14
  • R20-11rel:R20-11#e55946a82026-10-14
  • R21-11rel:R21-11#dfccc8ea2026-10-14
  • R22-11rel:R22-11#b421a5762026-10-14
  • R23-11rel:R23-11#11de95902026-10-14
  • R24-11rel:R24-11#f58eddc22026-10-14
  • R25-11rel:R25-11#402d34862026-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

enumeration ExecutionState [SWS_EM_02000] Upstream: RS_EM_00103, RS_AP_00125, RS_AP_00143, RS_AP_00129

enum class ExecutionState :              std::uint32_t {...};

Defines the internal states of a Process. Scoped enumeration of uint32_t. Please note that ara::exec::ExecutionState includes only states reportable by the Process to Execution Management and therefore does not include enumerations e.g. the "Initializing" state mentioned in Figure 7.2 and Figure 7.12, which are an implied states for Execution Management. The Initializing state starts when Process is first scheduled (so no code executed yet) and ends when kRunning is reported ([SWS_EM_01004]). The Terminating state starts when termination is requested by Execution Management and ends when the Process terminates ([SWS_EM_01404]). For the reasons mentioned, Execution Management assumes that Process is in initializing state until kRunning will be reported by it.

Header-Datei#include "ara/exec/execution_client.h"
Forwarding-Header#include "ara/exec/exec_fwd.h"
Scopenamespace ara::exec
SymbolExecutionState
Basistypstd::uint32_t

Werte

EnumeratorBeschreibung
kRunning=0 After a Process has been started by Execution Management, it reports ExecutionState kRunning.
AI-GENERATED unreviewed Model: gemini-3.8-flash-medium · Effort: medium · Temperature: not controllable · Prompt: 92ab45854562 Provenance
translated from the German guidegemini-3.8-flash-low · 2026-10-13 · German original

The typed enumeration ara::exec::ExecutionState [SWS_EM_02000] defines the internal states of a process that it can actively report to Execution Management. It is based on the underlying type std::uint32_t and is provided in namespace ara::exec via header file ara/exec/execution_client.h or the forwarding header ara/exec/exec_fwd.h.

For processes, the specification defines the reportable enumerator:

  • kRunning = 0: This state is reported by a process after it has been started by Execution Management [SWS_EM_02000].

The enumeration contains only states that can be actively reported. It therefore does not include implicit states of Execution Management such as Initializing or Terminating [SWS_EM_02000]. The initialization phase begins with the first scheduling of the process and ends when kRunning is reported [SWS_EM_01004]; until this report, Execution Management assumes that the process is initializing. The termination phase begins with the termination request and ends when the process is stopped [SWS_EM_01404].

The state is reported via the interface ara::exec::ExecutionClient::ReportExecutionState [SWS_EM_02003]. This method takes the current ExecutionState as a parameter, is declared as noexcept, and is both thread-safe and exception-safe. It returns a ara::core::Result<void> that confirms success or, in the error case, encapsulates an error code [SWS_EM_02003].

This usage note was generated by an AI based on the specification AUTOSAR Adaptive R25-11.

Implementer's Guide to follow (complexity I1)

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

Record
AUTOSAR/AP/record/SWS_EM_02000
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_EM_02000@rel:R25-11#a8ba80b5
Content hash
a8ba80b5
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_ExecutionManagement.pdf#nameddest=SWS_EM_02000
Status: valid/unmigrated Version: rel:R25-11#c62757d2 Versionshistorie & Revisions (1 transition, 8 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_EM_02000@rel:R25-11#c62757d2
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#a8ba80b52026-09-30
  • R19-11rel:R19-11#88b56faf2026-10-14
  • R20-11rel:R20-11#8e0737ad2026-10-14
  • R21-11rel:R21-11#658c6ef72026-10-14
  • R22-11rel:R22-11#658c6ef72026-10-14
  • R23-11rel:R23-11#81d91b0f2026-10-14
  • R24-11rel:R24-11#2e1e59b22026-10-14
  • R25-11rel:R25-11#c62757d22026-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 aliases

type alias ExecutionError [SWS_EM_02541] Upstream: RS_EM_00101, RS_AP_00122, RS_AP_00154

using ExecutionError = std::uint32_t;

Represents the execution error.

Header-Datei#include "ara/exec/execution_error_event.h"
Scopenamespace ara::exec
SymbolExecutionError

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

Record
AUTOSAR/AP/record/SWS_EM_02541
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_EM_02541@rel:R25-11#7aa66e05
Content hash
7aa66e05
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_ExecutionManagement.pdf#nameddest=SWS_EM_02541
Status: valid/unmigrated Version: rel:R25-11#ec889983 Versionshistorie & Revisions (1 transition, 7 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_EM_02541@rel:R25-11#ec889983
Point-in-Time History:
Recorded Revisions (7):
  • R25-11rel:R25-11#7aa66e052026-09-30
  • R20-11rel:R20-11#15d29ee52026-10-14
  • R21-11rel:R21-11#15d29ee52026-10-14
  • R22-11rel:R22-11#269b4a962026-10-14
  • R23-11rel:R23-11#ec8899832026-10-14
  • R24-11rel:R24-11#506e98662026-10-14
  • R25-11rel:R25-11#ec8899832026-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

Documentation of free functions

function GetExecErrorDomain [SWS_EM_02290] Upstream: RS_AP_00120, RS_AP_00130, RS_AP_00154, RS_AP_00159

const ara::core::ErrorDomain & GetExecErrorDomain () noexcept;

Returns a reference to the global ExecErrorDomain object.

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

use

The function GetExecErrorDomain in namespace ara::exec is included via the header file ara/exec/exec_error_domain.h [SWS_EM_02290]. It takes no input parameters and synchronously returns a const reference of type const ara::core::ErrorDomain & to the global ExecErrorDomain object [SWS_EM_02290]. The function typically serves to identify error domains during error handling in the context of Execution Management or to compare them with ara::core::ErrorCode instances.

Error Handling and Exception Safety

The function is declared with the specifier noexcept and defined as exception safe [SWS_EM_02290]. Since it merely returns an existing object reference, it throws no exceptions, reports no error codes, and requires no error checking upon call [SWS_EM_02290].

Concurrency and Interaction

According to the specification, the function is designated as thread-safe [SWS_EM_02290]. It may be called concurrently from arbitrary threads without external synchronization. The function is related to requirements [RS_AP_00120], [RS_AP_00130], [RS_AP_00154], and [RS_AP_00159]. The returned global singleton object is expected to remain valid and unchanged across the entire application lifetime. Question Q-060bbe6d5156346c (open)

This text was generated by an AI system based on the specification.

Header-Datei#include "ara/exec/exec_error_domain.h"
Scopenamespace ara::exec
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Rückgabewert

TypBeschreibung
const ara::core::ErrorDomain &Return a reference to the global ExecErrorDomain object.

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

Record
AUTOSAR/AP/record/SWS_EM_02290
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_EM_02290@rel:R25-11#fea7e7fe
Content hash
fea7e7fe
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_ExecutionManagement.pdf#nameddest=SWS_EM_02290
Status: valid/unmigrated Version: rel:R25-11#b2fe447e Versionshistorie & Revisions (1 transition, 8 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_EM_02290@rel:R25-11#b2fe447e
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#fea7e7fe2026-09-30
  • R19-11rel:R19-11#33d8bf8c2026-10-14
  • R20-11rel:R20-11#202753092026-10-14
  • R21-11rel:R21-11#202753092026-10-14
  • R22-11rel:R22-11#27b9334a2026-10-14
  • R23-11rel:R23-11#27d8586b2026-10-14
  • R24-11rel:R24-11#9c6228c12026-10-14
  • R25-11rel:R25-11#b2fe447e2026-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 MakeErrorCode [SWS_EM_02291] Upstream: RS_AP_00120, RS_AP_00121, RS_AP_00130, RS_AP_00154, RS_AP_00159

ara::core::ErrorCode MakeErrorCode (ara::exec::ExecErrc code, ara::core::ErrorDomain::SupportDataType data) noexcept;

Creates an instance of ErrorCode.

Header-Datei#include "ara/exec/exec_error_domain.h"
Scopenamespace ara::exec
Exception-Sicherheitexception safe
Thread-Sicherheitthread-safe

Parameter (in)

ParameterBeschreibung
codeError code number.
dataVendor defined data associated with the error.

Rückgabewert

TypBeschreibung
ara::core::ErrorCodeAn ErrorCode object.

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

Record
AUTOSAR/AP/record/SWS_EM_02291
Status
valid/unmigrated
Version
AUTOSAR/AP/record/SWS_EM_02291@rel:R25-11#edcfc523
Content hash
edcfc523
Source
https://www.autosar.org/fileadmin/standards/R25-11/AP/AUTOSAR_AP_SWS_ExecutionManagement.pdf#nameddest=SWS_EM_02291
Status: valid/unmigrated Version: rel:R25-11#0c8635c0 Versionshistorie & Revisions (1 transition, 8 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_EM_02291@rel:R25-11#0c8635c0
Point-in-Time History:
Recorded Revisions (8):
  • R25-11rel:R25-11#edcfc5232026-09-30
  • R19-11rel:R19-11#14c66c032026-10-14
  • R20-11rel:R20-11#2da017f22026-10-14
  • R21-11rel:R21-11#2da017f22026-10-14
  • R22-11rel:R22-11#65c1e3672026-10-14
  • R23-11rel:R23-11#71cba68d2026-10-14
  • R24-11rel:R24-11#0f447dbc2026-10-14
  • R25-11rel:R25-11#0c8635c02026-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