ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/docs/ui-ux-enterprise-audit/page-reports/ui-013-environment-backup-sets.md
ahmido 8713b35da5 feat(ui): implement core operator view surfaces productization for backup sets (#442) 
Applied the decision-first global surface IA contract to BackupSet views. Includes decision summary header, usability status, and separation of technical metadata.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #442
2026-06-11 07:38:33 +00:00

2.9 KiB
Raw Permalink Blame History

UI-013 Environment Backup Sets

Field Value
Route /admin/workspaces/{workspace}/environments/{environment}/backup-sets
Source BackupSetResource
Area / scope Backup / restore / environment
Archetype Backup / Restore
Design depth Strategic Surface
Repo truth repo-verified route; Spec 371 browser verified
Screenshot ../../../specs/371-core-operator-view-surfaces-productization/artifacts/screenshots/spec371-backup-set-productization-01-backup-sets-list.png
Detail screenshot ../../../specs/371-core-operator-view-surfaces-productization/artifacts/screenshots/spec371-backup-set-productization-02-backup-set-detail.png
Mobile screenshot ../../../specs/371-core-operator-view-surfaces-productization/artifacts/screenshots/spec371-backup-set-productization-03-backup-set-detail-mobile.png
Browser status Spec 371 smoke passed with seeded owner/manager capability, healthy/degraded backup sets, included item, and linked operation.

First Five Seconds

Spec 371 verifies the Backup Sets list/detail with a capability-backed fixture. The list now leads with restore-point decision, item count, and degradation guidance. The detail now answers whether the backup is usable before lifecycle, operation, or raw metadata.

Productization Review

  • Decision-first: implemented for list rows and detail decision zone.
  • Evidence-first: included backup items are primary detail content below the decision.
  • Context: environment-bound route.
  • Customer/auditor safety: high when used as restore proof; Spec 371 avoids restore-safety claims beyond repo truth.
  • Diagnostics: operation evidence and technical/lifecycle metadata remain available but secondary/collapsed.

Information Inventory

Default content shows backup set identity, restore-point decision, captured item count, degraded/blocking state when present, included item evidence, operation traceability, and secondary lifecycle/technical details.

Dangerous Actions

Create backup, archive/delete, and restore-adjacent flows are high impact and require confirmation, authorization, audit, and OperationRun continuity. Spec 371 did not add a restore-from-backup action/link and preserved existing action handlers.

Scores

Spec 371 did not rerun the full Spec 368 numeric scorecard. Browser smoke evidence now verifies the target list/detail hierarchy, JavaScript health, screenshots, and mobile width check.

Top Issues

  1. Backup Set create and additional partial/failure workflow states still need separate target coverage.
  2. Restore Runs remain a separate high-risk backup/restore surface.
  3. Manual review should verify production-like data density beyond the bounded smoke fixture.

Target Direction

Spec 371 provides seeded browser proof for list/detail. Keep future backup/restore work focused on create flows, restore execution history, and richer backup failure states.