# Asset Details, Diagnostics, and Action Surface Agenda

## Status

Open

## Purpose

Define what the selected asset view shows and which actions are directly available there.

## Domain Owner

`docs/studio`

## Current Code Context

The packer service model already expects:

- structured diagnostics,
- preview/apply mutation flows,
- operations such as `register_asset`, `adopt_asset`, `forget_asset`, `remove_asset`, `doctor`, and `build`.

The selected asset view should therefore be designed around explicit state and explicit actions.

## Core Questions

1. What summary information is always visible for the selected asset?
2. Which diagnostics belong inline versus in a separate panel?
3. Which actions should be primary, secondary, or hidden behind confirmation?
4. How should managed and orphan assets differ visually?
5. How should runtime-facing information such as preload and output format appear?

## Recommendation

Baseline direction:

- a summary card for identity and state,
- explicit diagnostics panel,
- explicit action group,
- clear differentiation between safe actions and sensitive mutations,
- no hidden automatic repair behavior.

## Expected Follow-up

- a decision on asset details composition,
- a spec for diagnostics and actions in the workspace,
- a plan for Studio service integration in the asset details view.