Falling-Metal-Interactive/Blacksite
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

BS-JD-214 - Path-agnostic asset catalog, loading, validation, and packaging #62

New Issue
Closed
opened 2026-07-13 16:51:55 -04:00 by Rbanh · 1 comment
Rbanh commented 2026-07-13 16:51:55 -04:00
Owner
Copy Link

Summary

Make asset type and stable identity independent of conventional folder names across editor, runtime, validation, and packaging.

Scope

  • Replace directory-name classification for Materials, Material Instances, shaders, post effects, profiles, levels, and prefabs with registry/document-schema-aware typing.
  • Resolve current paths through AssetId before cached path hints in editor and hydration consumers.
  • Share catalog rules with project validation, build manifests, live watcher #19, and headless processing #21.
  • Protect and consistently exclude editor-managed derived/cache/trash paths.
  • Migrate existing registry records and authored references without UUID churn or semantically unnecessary rewrites.

Acceptance criteria

  • A Material/Instance, shader schema, prefab, level, model, texture, or audio asset retains its type after moving to any normal folder under assets/.
  • Static/skinned hydration, thumbnails, Locate/Browse, validation, and packaging resolve the moved asset by stable ID.
  • Ambiguous or invalid authored RON documents show diagnostics rather than being guessed as levels.
  • Existing projects migrate deterministically with stable UUIDs and byte-preserving no-op refreshes.
  • Editor and headless catalog/validation results are identical.
  • Managed artifacts never appear as user assets or package inputs unless explicitly required.

Tests/docs

Arbitrary-folder fixtures for every authored/imported kind, move/restart/PIE/package tests, and clean-worktree validation.

Dependencies

Child of #59; depends on storage contract #60.

## Summary Make asset type and stable identity independent of conventional folder names across editor, runtime, validation, and packaging. ## Scope - Replace directory-name classification for Materials, Material Instances, shaders, post effects, profiles, levels, and prefabs with registry/document-schema-aware typing. - Resolve current paths through `AssetId` before cached path hints in editor and hydration consumers. - Share catalog rules with project validation, build manifests, live watcher #19, and headless processing #21. - Protect and consistently exclude editor-managed derived/cache/trash paths. - Migrate existing registry records and authored references without UUID churn or semantically unnecessary rewrites. ## Acceptance criteria - [ ] A Material/Instance, shader schema, prefab, level, model, texture, or audio asset retains its type after moving to any normal folder under `assets/`. - [ ] Static/skinned hydration, thumbnails, Locate/Browse, validation, and packaging resolve the moved asset by stable ID. - [ ] Ambiguous or invalid authored RON documents show diagnostics rather than being guessed as levels. - [ ] Existing projects migrate deterministically with stable UUIDs and byte-preserving no-op refreshes. - [ ] Editor and headless catalog/validation results are identical. - [ ] Managed artifacts never appear as user assets or package inputs unless explicitly required. ## Tests/docs Arbitrary-folder fixtures for every authored/imported kind, move/restart/PIE/package tests, and clean-worktree validation. ## Dependencies Child of #59; depends on storage contract #60.
Rbanh added this to the M2 - Content workspace and asset pipeline milestone 2026-07-13 16:51:55 -04:00
Rbanh commented 2026-07-17 23:46:59 -04:00
Author
Owner
Copy Link

Closed against M2 candidate cf6eaba

Registry v3, stable IDs, folder-independent classification, managed-directory exclusion, runtime catalog v2, texture/model import settings, project defaults, migrations, incremental publication, and package catalog validation are implemented and deterministic.

Consolidated code, deterministic, native, and package evidence: M2 evaluation record. Candidate gates passed in full and the commit is published on codex/m2-content-workspace.

## Closed against M2 candidate `cf6eaba` Registry v3, stable IDs, folder-independent classification, managed-directory exclusion, runtime catalog v2, texture/model import settings, project defaults, migrations, incremental publication, and package catalog validation are implemented and deterministic. Consolidated code, deterministic, native, and package evidence: [M2 evaluation record](https://git.spacetrainclubhouse.com/Falling-Metal-Interactive/Blacksite/src/commit/cf6eaba53473d2825d0109f5a18f44794af5bd48/docs/editor/evaluations/content-workspace-m2/README.md). Candidate gates passed in full and the commit is published on `codex/m2-content-workspace`.
Rbanh closed this issue 2026-07-17 23:47:06 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
area:animation

Skeletal animation import, preview, graph/state authoring, and runtime integration.

  
area:assets

Asset browser, material browser, thumbnails, import, processing, and asset watcher.

  
area:audio

Audio source/listener authoring, buses, spatial preview, and runtime integration.

  
area:brushes

Brush geometry, CSG, face editing, UVs, and brush diagnostics.

  
area:build-release

Build profiles, packaging, content validation, release gates, and distribution diagnostics.

  
area:extensions

Static extension API, extension scaffolds, dylib exploration.

  
area:governance

Policy, attribution, planning, and production process.

  
area:hierarchy

Outliner hierarchy, parenting, grouping, prefab structure, ordering, and selection workflows.

  
area:inspector

Inspector, component metadata, component editing UX.

  
area:navigation

Navigation mesh authoring, baking, diagnostics, and AI path preview.

  
area:operators

Editor operator/action framework, undo, commit/cancel semantics.

  
area:physics

Physics placement, colliders, rigid bodies, diagnostics, and overlays.

  
area:project-ux

Project launcher, profiles, templates, or first-run project workflow.

  
area:quality

Regression packs, tests, performance budgets, profiler, first-hour UX.

  
area:rendering

Static and skinned renderers, material slots, shaders, ray tracing, and render-path integration.

  
area:runtime

BRP, remote inspector, PIE, game preview, runtime integration.

  
area:scene-io

Scene document, save/load, schema, migration, or reference repair.

  
area:terrain

Terrain authoring, terrain sculpting, heightmaps, and terrain materials.

  
area:viewport

Viewport interaction, selection, shortcuts, camera, overlays, and controls.

  
priority:P0

Must-have prerequisite or milestone-critical item.

  
priority:P1

Important production feature after P0 work is stable.

  
priority:P2

Useful follow-up or polish item.

  
priority:P3

Exploratory or later spike.

  
roadmap:jackdaw

Jackdaw-inspired Blacksite editor roadmap item.

  
roadmap:production

Blacksite production-readiness roadmap item beyond the Jackdaw-inspired foundation.

  
type:architecture

Architecture, internal framework, or hard-to-reverse technical decision.

  
type:docs

Documentation, policy, samples, or issue-board structure.

  
type:epic

Tracking epic that groups related milestone work.

  
type:feature

User-visible feature or capability.

No Label
area:animation
area:assets
area:audio
area:brushes
area:build-release
area:extensions
area:governance
area:hierarchy
area:inspector
area:navigation
area:operators
area:physics
area:project-ux
area:quality
area:rendering
area:runtime
area:scene-io
area:terrain
area:viewport
priority:P0
priority:P1
priority:P2
priority:P3
roadmap:jackdaw
roadmap:production
type:architecture
type:docs
type:epic
type:feature
Milestone
Clear milestone
No items
No Milestone
M2 - Content workspace and asset pipeline
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Falling-Metal-Interactive/Blacksite#62
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?