Split the host, command layer and harness the same way - Host lifecycle, Command layer dispatcher, Harness server and Harness scenarios carry the facts, checked against bootstrap c3409ba - Each system page keeps the shape, how its parts hook together, and why, with the rejected ideas for what's built - Each design page keeps only what isn't built: the maps' start and stop order, roles and front ends, stepped maps and world scenarios
Add the generated opcode table and commands pages, bootstrap efc697d - Gateway-opcode-table and Command-layer-commands, generated from the opcode table and the server's command list - Command layer's hand-kept table and Gateway's opcode paragraph point at them; Home, the sidebar and Running a server link both - Regenerate the message pages at efc697d; 742 of 742 in run 39092971388
Document step 3's first stage as built, at bootstrap e8da4aa The real client logs in through our own server and creates a character. Host, Gateway, Owners, Persistence, Command layer and Harness each get an explanation page checked against the merged code, and Running a server is the guide to running it. The six design pages say their first stage is built and stay the direction for the rest. Repository layout, Running the tests, Roadmap, Client protocol and Server core design catch up; Home groups pages by area now the wiki is past twenty. Counts from run 39083384598: 718 tests in 13 applications.
Move step 3's first systems onto design pages of their own Step 3's first stage is approved and being built, so the host, gateway, owners, persistence, command layer and harness get their own design pages, moved off Server core design with their knobs and rejected ideas, and filled in from the stage's plan. The map scheduler and timer wheel stay until the map side is planned. Home, the sidebar and Roadmap's step 3 point at them.