assets workspace agendas

This commit is contained in:
2026-03-24 13:42:40 +00:00
parent 8b0de17859
commit fcfe732eac
4 changed files with 135 additions and 10 deletions
@@ -2,7 +2,7 @@
## Status
Open
Closed
## Purpose
@@ -62,13 +62,39 @@ Prefer Option A.
Recommended baseline:
- asset list or registry-aware browser on the left,
- a custom visual `Asset Tree` / `Asset Navigator` on the left,
- asset details in the main panel,
- diagnostics and action surfaces attached to the selected asset,
- broader activity/progress outside the asset details body when possible.
The Assets workspace must remain asset-first, but it must not hide physical organization.
Baseline path and structure rules:
- the primary navigation unit is the managed asset, not the raw file;
- the left navigation surface should not be a generic file tree; it should be an asset-aware tree that teaches the packer model;
- asset root path must remain visible for the selected asset;
- the asset list may be grouped by path or parent folder to preserve project structure awareness;
- the selected asset view should include a location section for asset root and relocational actions;
- the selected asset view should include an inputs/preview section that exposes internal files and folders as part of the asset;
- filesystem structure is supporting context, not the primary identity model.
Baseline visual navigation rules:
- the Assets workspace should use a custom `Asset Tree` / `Asset Navigator` component rather than a plain `TreeView` clone;
- asset nodes should carry strong visual semantics such as icons, badges, and state styling;
- the navigator should clearly surface managed/orphan state, preload intent, diagnostics presence, and broad asset family where available;
- grouping nodes may reflect path structure, but asset nodes remain the primary navigable unit;
- optional expansion of an asset into internal inputs is allowed as supporting inspection, not as a replacement for asset-first navigation.
This exists so the Assets workspace teaches the packer model while still letting users understand and organize the project's directory layout.
## Expected Follow-up
- an information architecture decision,
- a workspace spec,
- a PR/plan for the first concrete `AssetsWorkspace`.
## Resolution
Closed by [`../decisions/004-asset-workspace-information-architecture-decision.md`](../decisions/004-asset-workspace-information-architecture-decision.md).
+8 -7
View File
@@ -6,19 +6,20 @@ This directory contains active Studio discussion agendas.
The initial Studio UI planning wave is:
1. [`01.1. Asset Workspace Information Architecture Agenda.md`](./01.1.%20Asset%20Workspace%20Information%20Architecture%20Agenda.md)
2. [`01.2. Asset List, Filters, and Selection Model Agenda.md`](./01.2.%20Asset%20List,%20Filters,%20and%20Selection%20Model%20Agenda.md)
3. [`01.3. Asset Details, Diagnostics, and Action Surface Agenda.md`](./01.3.%20Asset%20Details,%20Diagnostics,%20and%20Action%20Surface%20Agenda.md)
4. [`01.4. Background Events, Progress, and Activity Feed Agenda.md`](./01.4.%20Background%20Events,%20Progress,%20and%20Activity%20Feed%20Agenda.md)
5. [`01.5. Preview, Confirm, and Apply Mutation Flows Agenda.md`](./01.5.%20Preview,%20Confirm,%20and%20Apply%20Mutation%20Flows%20Agenda.md)
1. [`01.2. Asset List, Filters, and Selection Model Agenda.md`](./01.2.%20Asset%20List,%20Filters,%20and%20Selection%20Model%20Agenda.md)
2. [`01.3. Asset Details, Diagnostics, and Action Surface Agenda.md`](./01.3.%20Asset%20Details,%20Diagnostics,%20and%20Action%20Surface%20Agenda.md)
3. [`01.4. Background Events, Progress, and Activity Feed Agenda.md`](./01.4.%20Background%20Events,%20Progress,%20and%20Activity%20Feed%20Agenda.md)
4. [`01.5. Preview, Confirm, and Apply Mutation Flows Agenda.md`](./01.5.%20Preview,%20Confirm,%20and%20Apply%20Mutation%20Flows%20Agenda.md)
Recommended discussion order:
`01.1 -> 01.2 -> 01.3 -> 01.4 -> 01.5`
`01.2 -> 01.3 -> 01.4 -> 01.5`
The shell, UI foundations, and components admission baselines were already consolidated into [`../specs/`](../specs/) and [`../learn/`](../learn/).
The remaining order closes the asset workspace structure first, and only after that the detailed interaction flows.
The asset workspace information architecture baseline is already closed in [`../decisions/004-asset-workspace-information-architecture-decision.md`](../decisions/004-asset-workspace-information-architecture-decision.md).
The remaining order closes the detailed interaction model on top of that structure.
## Purpose