Configuration records use immutable configuration identifiers and atomic reorder

Context

Configuration is shared by baselines, imports, integrations and interactive selection. Its identity needs to remain stable when its display name changes.

Decision

The cited configuration and ordering decisions remain authoritative. Creation uses a supplied configuration name or derives it from the display name. Database grammar and local uniqueness apply; subsequent renaming retains identity.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

Activity configuration already uses the atomic console order adapter. Task configuration currently uses separate saves, leaving a recorded implementation difference.