What is changing.
Why it matters.

The public site used to carry one job: explain the premise and collect playtest interest. It now also needs to answer what the game expects from players and what players should expect from the service.

The new field guide documents the playable systems without turning the website into a second rules authority. Community Standards establish the line between hard competitive play and abuse. The independent status surface checks both the public website and playable game.

A public forum is deliberately absent. The first community venue should open with an active cohort and real moderation coverage, not an empty category list.

A second holding should solve a real dependency rather than act as another copy of the first. Woodland, highland, and riverland seats create different production strengths, construction pressures, and defensive problems.

Goods do not teleport between them. House roads, Caravan Yard capacity, travel time, and available stores determine whether one holding can support another. Army marches also consume grain. That makes expansion useful, but it creates something worth scouting, raiding, and defending.

The goal is a legible loop: steward the holding, establish another for a reason, connect it, and decide what must remain protected when the House reaches farther than it can comfortably hold.

Confirmed orders continue when a tab closes. Refresh restores authoritative state. Resource rates, warnings, costs, and campaign previews remain available across the supported layouts.

Sessions support quick check-ins and longer planning. No routine production, construction, recruitment, convoy, or campaign timer requires an open browser tab. The current interface adapts its Courtyard, War Room, and Scribe views for smaller screens.

This constraint is useful. It forces every visual ambition to answer a simple question: does it strengthen the persistent world without making ordinary browser play slower, less reliable, or less fair?