feat: derive capable opportunity helpers
This commit is contained in:
@@ -731,13 +731,18 @@ Completed:
|
||||
player tree-harvest resolutions use real economy history; interested-party
|
||||
death and one-day staleness close the need cleanly. The compact UI explains
|
||||
the blocked action without reusing the pantry's hunger cue.
|
||||
28. Explainable capable helper: an open food or wood need now names one
|
||||
deterministic informed and trusted villager plus the ordinary gather or
|
||||
deposit action and real inventory/resource route that makes them capable.
|
||||
The result is re-derived after restore and does not assign work or alter the
|
||||
simulation.
|
||||
|
||||
Next:
|
||||
|
||||
1. Add the first read-only capable-helper query for an open need. Expose one
|
||||
deterministic viable villager and the real knowledge, relationship, action,
|
||||
inventory, and resource facts behind that result before allowing it to
|
||||
affect autonomous selection, as sequenced in `LEARNING_ROADMAP.md`.
|
||||
1. Let the currently derived helper consume the query through ordinary
|
||||
autonomous action selection, after urgent self-care and schedule precedence.
|
||||
Re-query instead of persisting assignment, and keep acceptance/rewards out
|
||||
of scope, as sequenced in `LEARNING_ROADMAP.md`.
|
||||
|
||||
Do not start with GIS data, a full city, a large asset pack, or more NPC
|
||||
mechanics. The next proof is a beautiful stage for the systems that already
|
||||
|
||||
Reference in New Issue
Block a user