S01 · Release contract and player journey

Current implementation: The public status matrix and player/testing guides now make implemented, verified and remaining scope inspectable.

Outstanding acceptance: A frozen full-floor contract, three complete career journeys and calibrated attention budgets remain open.

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
S01.01 · Freeze the Floor 1 contract	List the exact player-facing systems, tier endpoints, launch content IDs, recurring features and supported interfaces. Distinguish future-floor lore from installed actions.	Every advertised Floor 1 feature has an owner, executable deliverable, acceptance evidence and dependency; nothing is silently dropped to make a smaller alpha look complete.
S01.02 · Build three complete career journeys	Specify frontier-raider, professional-main and solo-generalist routes, including newcomer, established and post-clear versions.	Each route reaches meaningful Floor 1 completion without mandatory mastery of all professions or participation in unrelated career loops.
S01.03 · Define attention and progression budgets	Separate deliberate active play, elapsed production, coordination and idle waiting. Use the 250-active-hour example as a hypothesis.	Activity time is not double-counted; AFK and queue time do not manufacture the active-hour claim; the resulting goals have changing capabilities rather than an hours-played gate.
S01.04 · Create the readiness and status matrix	Use intended, implemented, tested, active and documented states independently. Define zero-placeholder checks by feature.	A description, catalogue row, agent contract or passing reference test cannot mark a gameplay system complete.