Start M0 editor workflow polish
This commit is contained in:
1 parent
3e053a81ab
commit
19c4d017dc
8 files changed
+236
-40
No files matched your search
@@ -0,0 +1,49 @@
|
||||
Status: Accepted
|
||||
|
||||
Context
|
||||
=======
|
||||
|
||||
Blacksite is evolving from a game-specific editor scaffold into a reusable
|
||||
Bevy editor sandbox for future game work. The Jackdaw editor provides useful
|
||||
public reference material for editor workflows such as brush geometry, material
|
||||
browser organization, terrain tools, physics placement, project launchers, and
|
||||
extension boundaries.
|
||||
|
||||
The roadmap should use those references as product and workflow inspiration
|
||||
without accidentally turning Blacksite into a fork, importing code without
|
||||
attribution, or overriding Blacksite's existing authoring/hydration model.
|
||||
|
||||
Decision
|
||||
========
|
||||
|
||||
Treat Jackdaw as an inspiration source, not as an architecture or format
|
||||
authority. Blacksite keeps its current foundations: Bevy DynamicScene RON,
|
||||
schema stamping and migration, authoring-only validation, hydration into runtime
|
||||
components, in-process PIE, and the unified viewport.
|
||||
|
||||
Each Jackdaw-inspired ticket must identify whether the work is:
|
||||
|
||||
- Design-inspired: adapted from public behavior, screenshots, docs, or workflow
|
||||
descriptions.
|
||||
- API-inspired: adapted from public API shape or concepts without copied code.
|
||||
- Code-derived: containing copied or closely translated source code.
|
||||
|
||||
Code-derived work requires a source URL, upstream commit or release reference,
|
||||
compatible license confirmation, and preserved file-level notices when required
|
||||
by the source license. Prefer clean-room implementation for geometry, terrain,
|
||||
operators, and extension APIs because Blacksite's scene and runtime ownership
|
||||
model differs from Jackdaw's.
|
||||
|
||||
Consequences
|
||||
============
|
||||
|
||||
The Jackdaw roadmap can be used for planning and prioritization while keeping
|
||||
Blacksite's architecture coherent and auditable.
|
||||
|
||||
M0-M5 planning details live in `.cursor/plans/` until implemented. Durable
|
||||
decisions move into `docs/adr/` or `docs/editor/`; user-visible workflows move
|
||||
into the root README. The Gitea issue tracker is the production task board, but
|
||||
docs remain the long-term source for accepted policy and architecture.
|
||||
|
||||
Reviewers should reject Jackdaw-inspired changes that do not declare their
|
||||
inspiration level or that copy source without license and source attribution.
|
||||
Reference in new issue
Block a user