S02 · Reusable rules and shared-time engine

Current implementation: Reusable execution, real-time commitments, scoped state and explicit migrations exist and have regression coverage.

Outstanding acceptance: Broader effect coverage, production concurrency and whole-floor integration still require acceptance.

The four requirements below preserve the original release target. Their historic baseline is not used as a current completion score. This page does not mark the entire stream complete merely because related components are installed.

Reference

Requirement	Required deliverable	Acceptance standard
S02.01 · Generalize effect execution	Specify status families, conversion, targeting, control, triggers, action budgets, random streams and rounding, preserving baseline fixtures.	Independent tests resolve ordering, duplicate triggers, expiry, simultaneous deaths and resource conservation without unbounded recursion.
S02.02 · Extend authoritative activity plans	Implement permitted conditional plans, knowledge-limited inputs, consumable policies, stop rules, safe return and cancellation.	A plan cannot read future outcomes, reroll by refresh or cancellation, multiply player bodies, or consume uncommitted supplies.
S02.03 · Define world and instance scopes	Specify region stock, travel, encounter instances, shared campaign updates, historical events and per-player discovery.	Extra instances or Discord installations cannot duplicate scarce world claims; a shared result has one authoritative transition.
S02.04 · Version activities and migrations	Define save/schema migration, active-job compatibility, old items and safety overrides for disabled effects.	Existing inventories, contracts and activities migrate or terminate through documented accounting; version pinning cannot preserve a known exploit.