snapshot: preserve totp account security baseline

PRODUCTIZATION_ROADMAP.md

@@ -16,6 +16,7 @@ Current branch roles:
 3. Start as single-tenant configurable, not full multi-tenant.
 4. Make branding and document identity admin-managed, not code-managed.
 5. Add new business apps only after the core platform layer is standardized.
+6. Prefer inline editing for lightweight profile and configuration data, but keep explicit forms for sensitive or high-risk settings.
 
 ## Product Layers
 
@@ -213,3 +214,35 @@ This is the first productization slice because it gives:
 - keep migrations backward-compatible
 - update both wiki and developer handbook for every architecture change
 - snapshot at the end of each major phase
+
+## Shared UI Pattern: Inline Editing
+
+Use inline editing as a platform pattern where it improves speed without weakening clarity or safety.
+
+Good candidates:
+
+- user profile and contact data
+- company config sections
+- branding text and non-sensitive metadata
+- low-risk app-registry metadata
+
+Do not use it by default for:
+
+- credentials and secrets
+- integrations with side effects
+- destructive actions
+- multi-step workflow forms
+- settings that need heavy validation or confirmation
+
+Preferred implementation style:
+
+- section-level inline editing
+- explicit `Bearbeiten`, `Speichern`, `Abbrechen`
+- no noisy per-field autosave
+- clear view mode and edit mode separation
+
+Reason:
+
+- keeps Workdock faster and more product-grade
+- avoids large admin-style forms for simple edits
+- still preserves reliable validation and safer change boundaries