## Begin of the deletion <img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/923080/content">

##

##End of the deletion Summary

Begin of the insertionPersistenceEnd of the insertion Begin of the deletion Introduce the persistenceEnd of the deletion layer for the description assistant: a model for admin-managed Begin of the deletion
End of the deletion text-transform Begin of the insertion
actionsEnd of the insertion Begin of the deletion actions,End of the deletion plus Begin of the insertionseeded defaults. Defaults are plain seeds — created once on fresh
installations, never touched afterwards (same semantics as statuses/types).End of the insertion Begin of the deletion seeding of the default action set with upgrade-safe semantics.
End of the deletion No UI, no Begin of the insertionAPI.

ImplementedEnd of the insertion Begin of the deletion APIEnd of the deletion in Begin of the insertionPR: https://github.com/opf/openproject/pull/24847End of the insertion Begin of the deletion this work package.End of the deletion

## Acceptance criteria

Begin of the insertionModel `AI::TextTransformAction` (table `ai_text_transform_actions`)End of the insertion Begin of the deletion * A model (working name: `Ai::TextTransformAction`, naming open) existsEnd of the deletion with: Begin of the insertion

-End of the insertion Begin of the deletion

* `builtin_key` (string, nullable, unique) — set for seeded actions, `NULL` for custom ones

* End of the deletion `label` (string, required) Begin of the insertion
-End of the insertion Begin of the deletion

* End of the deletion `prompt` Begin of the insertion(text, required)
- `usage_scope` (string enum,End of the insertion Begin of the deletion (text) — **nullable**: for builtin actions, `NULL` means &quot;use the shippedEnd of the deletion default Begin of the insertion`everywhere`): `everywhere` | `all_work_package_types` | `specific_work_package_types` — single-select; future scopes (comments, wikis, long text custom fields) are new enum values, no migration needed
-End of the insertion Begin of the deletion text&quot;; a resolver method returns the effective prompt (stored text, or the shipped default looked up by `builtin_key`)

* End of the deletion `active` (boolean, default Begin of the insertiontrue)
-End of the insertion Begin of the deletion `true`)

* End of the deletion `position` Begin of the insertion(integer, acts_as_list)
- `injects_type_template`End of the insertion Begin of the deletion (integer) — list order in the dropdown/admin list

* `model` (string, nullable) — optional LLM model override; `NULL` = default from LLM settings

* type restriction: `applies_to_all_types`End of the deletion (boolean, default Begin of the insertionfalse) — type description template is injected at execution time

Type restriction viaEnd of the insertion Begin of the deletion `true`) plus aEnd of the deletion join Begin of the insertionmodel `AI::TextTransformActionType`End of the insertion Begin of the deletion table to `types` for restricted actionsEnd of the deletion (pattern: Begin of the insertion`project_types`),
targeting types — variantsEnd of the insertion Begin of the deletion custom fields ↔ types)

* Validations: label presence; prompt presence for custom actions (builtin actions may be `NULL`); temperature/model valuesEnd of the deletion are Begin of the insertionincluded automatically at runtime. Types required iff
`specific_work_package_types`.

End of the insertion Begin of the deletion not validated against the LLM connection (loose coupling).

* An `available_for_type?(type)` query method encapsulates: `active` AND type restriction AND, for the `sort_into_template` builtin, &quot;type has a non-blank default description&quot;.

* End of the deletion Seeder Begin of the insertion`BasicData::AiTextTransformActionSeeder` (`ModelSeeder`)End of the insertion creates Begin of the insertion`fix_grammar`,
End of the insertion Begin of the deletion the builtin actions (`fix_grammar`,End of the deletion `make_concise`, `translate`, Begin of the insertion`sort_into_template` (onlyEnd of the insertion Begin of the deletion `sort_into_template`) with `prompt: NULL`, translatable labels and stable positions.

* Upgrade semantics verified by specs:

* Re-runningEnd of the deletion the Begin of the insertionlatterEnd of the insertion Begin of the deletion seeder on an existing installation creates missing builtins and never

touches existing rows (user edits, ordering, active flags survive).

* A builtinEnd of the deletion with Begin of the insertiontemplate injection).
Labels translatable (`t_` mechanism), prompts untranslated. SeedingEnd of the insertion Begin of the deletion `prompt: NULL` resolves to the _current_ shipped default after an upgrade.

* Deleting a builtin rowEnd of the deletion is Begin of the insertiona no-op once any
record exists (verified by specs); seededEnd of the insertion Begin of the deletion not possible via model API (builtins are deactivated instead); customEnd of the deletion actions Begin of the insertionare ordinary records — editable and
deletable. PromptEnd of the insertion Begin of the deletion can be destroyed.

* Shipped default promptEnd of the deletion texts live in Begin of the insertion`app/seeders/common.yml` (singleEnd of the insertion Begin of the deletion a dedicated, reviewable location (e.g. YAML under the seeder or a `Prompts` module) — singleEnd of the deletion source of truth Begin of the insertionfor
AI-97); texts are working drafts, finalization is AI-97.

End of the insertion Begin of the deletion also used by the evals alignment task.


End of the deletion ## Technical notes

Begin of the insertion- `builtin_key` / NULL-promptEnd of the insertion Begin of the deletion * Follow `BasicData::ModelSeeder` conventions where possible, but note its `applicable?` skips seeding entirely once records exist — this seeder must instead upsert missing builtins (idempotent per `builtin_key`).

* Translatable labels via the `t_`\-prefix mechanism (`Source::Translate`, crowdin pipeline).

* The `NULL`\-promptEnd of the deletion resolution Begin of the insertion/ upgrade upserts deliberately dropped: existing installations don't receive new or changed defaults on upgrade (accepted).
-End of the insertion Begin of the deletion replaces any digest/&quot;customized\_at&quot; bookkeeping — keep it simple.

* Type restriction join table only consulted when `applies_to_all_types` is `false`.

* End of the deletion No Begin of the insertionper-action model overrideEnd of the insertion Begin of the deletion `enabled` global toggle hereEnd of the deletion — Begin of the insertionLLM model is configured elsewhere (AI-3).
- Availability logic is not part ofEnd of the insertion the Begin of the insertionmodel: template existence depends on the project's active type variant, so resolutionEnd of the insertion Begin of the deletion feature toggleEnd of the deletion belongs to Begin of the insertionAI-100.
- Zeitwerk inflection `"ai" => "AI"` added (matchesEnd of the insertion the Begin of the insertionexisting AS acronym).

End of the insertion Begin of the deletion admin UI/settings work package.


End of the deletion ## Out of scope

Begin of the deletion * End of the deletion Admin UI Begin of the insertion(AI-98) · transformEnd of the insertion Begin of the deletion (separate work package)

* Prompt assembly/resolution against LLM requests (transformEnd of the deletion API Begin of the insertion(AI-100) · per-projectEnd of the insertion Begin of the deletion work package)

* Per-projectEnd of the deletion scoping Begin of the insertion· upgrade-refreshEnd of the insertion of Begin of the insertionshipped defaults
End of the insertion Begin of the deletion actionsEnd of the deletion