Survival needs

Ask which needs exist and whether they are cosmetic, advisory, gating, attritional, fail-state, hybrid, or existing.

Contract

Publish:

• stable needs_policy_id and revision
• meter/state IDs and ranges
• declared timebase and pause/suspend policy
• threshold/effect policy for each state
• source/sink transaction identity where resources are consumed
• persistence behavior and UI/accessibility signals

Ownership

This skill owns need-state progression and threshold events. rest-site, inventory/economy, health/damage, weather and durability remain separate owners and consume those events through explicit mappings.

Rules