docs: mark action separation phase complete
This commit is contained in:
@@ -65,10 +65,10 @@ the prototype. They do not yet own:
|
||||
- completion effects;
|
||||
- interruption and failure policy;
|
||||
- reservation strategy;
|
||||
- target resolution implementation;
|
||||
- detailed target-selection policy beyond current resource/activity/free
|
||||
metadata;
|
||||
- presentation hints beyond target type.
|
||||
|
||||
Those concerns move during the next architecture phase, which separates action
|
||||
selection, execution, target resolution, and visual travel. Keeping this first
|
||||
definition contract small avoids encoding the existing manager's mixed
|
||||
responsibilities as permanent data architecture.
|
||||
Selection, execution, target resolution, and visual travel are now separate
|
||||
responsibilities. The remaining concerns should move into definitions only
|
||||
when the action-system implementations prove a stable, reusable contract.
|
||||
|
||||
Reference in New Issue
Block a user