# Follow-up Spec Map

Verification level: derived from existing implementation using Spec 368 recommendations, Spec 369 deferrals, and the user-provided Spec 370 draft.

## Explicitly Deferred From Spec 370

| Follow-up | Why Deferred | Suggested Boundary |
|---|---|---|
| Backup Set View decision-first productization | Restore-critical runtime UI change; should consume contract after docs are reviewed. | Existing Backup Set view only, no restore engine changes. |
| OperationRun View metadata/proof separation polish | OperationRun surfaces were recently changed by Specs 358-367; avoid immediate broad reopening. | Run detail hierarchy only, reuse OperationRun UX contract. |
| Customer/Auditor Surface Safety Pass | Customer-facing surfaces need careful browser and text review. | Customer Review Workspace, Environment Review, Review Pack, Stored Report, Evidence Snapshot reachability. |
| Diagnostic Surface Separation | Needs fixture/auth work for Required Permissions/System/Evidence Snapshot. | Diagnostics pages and access paths only. |
| Provider Connections readiness productization | Runtime configuration surface change near credentials and permissions. | Provider readiness summary and action hierarchy only. |
| Target mock/example per archetype | Spec 368 Candidate A named this as useful, but Spec 370 v1 is limited to source-evidence-backed review rules and avoids creating target imagery. | Later design/spec package only, after the IA contract is accepted. |
| UI Bloat Regression Guard v1 | Automation could be brittle before the contract is proven by consumers. | One bounded guard after another UI spec consumes this contract. |
| Docs/product publication | May create duplicate source of truth too early. | Publish only after review or second consuming spec proves stable location is needed. |

## Out-of-Scope Runtime Pages

- Baseline Profile View
- Backup Set View
- OperationRun View
- Restore Run View
- Restore Create Wizard
- Operations Hub
- Environment Dashboard
- Customer Review Workspace
- Provider Connections
- Environment Diagnostics
- Required Permissions
- Evidence Snapshot
- System panel

## Promotion Rule

A follow-up may be promoted when it has:

- source evidence;
- a bounded surface list;
- no hidden adjacent page refactors;
- RBAC and isolation impact stated;
- destructive/high-impact action safety preserved;
- test lane and browser/manual smoke need stated.