BS-JD-211 - Content workspace and import authoring refactor #59

New Issue

Closed

opened 2026-07-13 16:50:43 -04:00 by Rbanh · 3 comments

Rbanh commented

2026-07-13 16:50:43 -04:00

Owner

Copy Link

Goal

Make Blacksite's Content Browser a user-organized project file manager and make imported static/skinned models first-class assets with editable, stable material defaults.

Product contract

Assets may live in any user-chosen folder beneath the project assets/ content root; folder names do not define asset type.
Import targets the current or explicit project folder and never silently sorts sources into visible type directories.
Imported model slots may keep source fallback, map to an existing project Material/Instance, extract an editable Material, or intentionally select the project/engine default.
Material precedence is: runtime MaterialPropertyBlock -> scene/prefab assignment -> model-asset default -> imported source -> project default -> built-in DefaultGrid.
Missing layers inherit downward; configured but broken authored references render the fallback with diagnostics.
Move, rename, reimport, validation, packaging, and headless processing preserve stable identity and never silently overwrite authored Materials.
Absolute linked assets outside the project are out of scope pending a separate portability/VFS decision.

Existing foundation

Reuse the shared Material Library (#16), exact material drops (#18), renderer slot/material foundation (#51), deterministic fingerprints (#56), and transactional FBX dependency handling (#58). Do not introduce a second catalog, material type, or renderer path.

Work breakdown

#60 Project content and derived-artifact contract
#62 Path-agnostic asset catalog, loading, validation, and packaging
#66 Built-in Default Grid fallback material
#20 Content Browser file operations and reference-safe moves
#61 Destination-first transactional asset import
#64 Static and skinned model-asset material slot mappings
#63 Editable imported-material extraction and per-slot import policy
#17 PBR texture-set auto-detection
#19 Live asset watcher and refresh
#21 Headless asset processing command
#53 Runtime material property blocks and promote-to-instance
#67 Editor asset dirty state and explicit save transactions
#68 Modular Editor UI Architecture and Debt Ratchet
#65 M2 migration and acceptance signoff

Exit condition

A representative project can organize arbitrary folders, import static and skeletal models in place, extract and assign editable Materials, use project/engine fallbacks, place and override models, apply/promote a property block, move the folder, reimport, save/reopen, validate, and package without losing UUIDs, slot mappings, scene overrides, thumbnails, authored Material edits, or visibility. Cancel/failure paths restore the exact prior state. Every issue assigned to M2 is closed before the milestone closes.

Source plan

.cursor/plans/content_workspace_and_import_authoring_2026-07-13.plan.md

## Goal Make Blacksite's Content Browser a user-organized project file manager and make imported static/skinned models first-class assets with editable, stable material defaults. ## Product contract - Assets may live in any user-chosen folder beneath the project `assets/` content root; folder names do not define asset type. - Import targets the current or explicit project folder and never silently sorts sources into visible type directories. - Imported model slots may keep source fallback, map to an existing project Material/Instance, extract an editable Material, or intentionally select the project/engine default. - Material precedence is: runtime MaterialPropertyBlock -> scene/prefab assignment -> model-asset default -> imported source -> project default -> built-in DefaultGrid. - Missing layers inherit downward; configured but broken authored references render the fallback with diagnostics. - Move, rename, reimport, validation, packaging, and headless processing preserve stable identity and never silently overwrite authored Materials. - Absolute linked assets outside the project are out of scope pending a separate portability/VFS decision. ## Existing foundation Reuse the shared Material Library (#16), exact material drops (#18), renderer slot/material foundation (#51), deterministic fingerprints (#56), and transactional FBX dependency handling (#58). Do not introduce a second catalog, material type, or renderer path. ## Work breakdown - [x] #60 Project content and derived-artifact contract - [x] #62 Path-agnostic asset catalog, loading, validation, and packaging - [x] #66 Built-in Default Grid fallback material - [x] #20 Content Browser file operations and reference-safe moves - [x] #61 Destination-first transactional asset import - [x] #64 Static and skinned model-asset material slot mappings - [x] #63 Editable imported-material extraction and per-slot import policy - [x] #17 PBR texture-set auto-detection - [x] #19 Live asset watcher and refresh - [x] #21 Headless asset processing command - [x] #53 Runtime material property blocks and promote-to-instance - [x] #67 Editor asset dirty state and explicit save transactions - [x] #68 Modular Editor UI Architecture and Debt Ratchet - [x] #65 M2 migration and acceptance signoff ## Exit condition A representative project can organize arbitrary folders, import static and skeletal models in place, extract and assign editable Materials, use project/engine fallbacks, place and override models, apply/promote a property block, move the folder, reimport, save/reopen, validate, and package without losing UUIDs, slot mappings, scene overrides, thumbnails, authored Material edits, or visibility. Cancel/failure paths restore the exact prior state. Every issue assigned to M2 is closed before the milestone closes. ## Source plan `.cursor/plans/content_workspace_and_import_authoring_2026-07-13.plan.md`