Use user terminology, including internal identifiers and compatibility migration #1840

Open
opened 2026-11-03 22:45:20 +00:00 by jason.woltje · 0 comments
Owner

Jason requests user rather than human terminology throughout the system, explicitly including internal identifiers (2026-11-03). Tracked as Vikunja #798. Lower priority than #797. Start with a Luna inventory; sequence code changes after the active Console/intake branches integrate. Cover UI/CLI copy, role instructions, internal symbols/files, transport and config/schema keys, event/message names, error codes, current examples and tests. Preserve owner-versus-granted-user authorization semantics. Use explicit validated migration/legacy-reader compatibility for persisted names, refuse ambiguous mixed keys, and never rewrite immutable run records, append-only logs or historical quotations. This is a naming migration, with no authority expansion or live-host migration authorized by task creation.

Jason requests user rather than human terminology throughout the system, explicitly including internal identifiers (2026-11-03). Tracked as Vikunja #798. Lower priority than #797. Start with a Luna inventory; sequence code changes after the active Console/intake branches integrate. Cover UI/CLI copy, role instructions, internal symbols/files, transport and config/schema keys, event/message names, error codes, current examples and tests. Preserve owner-versus-granted-user authorization semantics. Use explicit validated migration/legacy-reader compatibility for persisted names, refuse ambiguous mixed keys, and never rewrite immutable run records, append-only logs or historical quotations. This is a naming migration, with no authority expansion or live-host migration authorized by task creation.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1840