Design the map side from the approved Stage 2a plan
- Map scheduler design and Timer wheel design, moved out of Server
core design with the plan's rulings
- Owners design gains the map owners, the hand back and the second
login; Gateway design locks tagged routing
- Harness design gains stepped maps and the world scenarios
- The handling gate by verified members (decided 2026-10-18) on Message
audit design, Gateway design and Roadmap
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
Point the wiki at main, now that main has the work
main was fast-forwarded to bootstrap at 3bdebd6, so every ref badge, the
reference pages and the README and CONTRIBUTING links now name main.
Roadmap says each step is done on main and one run-time check is still
owed; Branches and workflow says what main now holds. Gateway and Running a
server cover the debug-level message log. Counts from run 39087772844:
724 tests in 13 applications.
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.
Document world entry at bootstrap 7c68ecc
Six world-entry messages verified to their fields: the reference pages
regenerated, Client protocol follows the conversation to the end of the
loading screen, and Roadmap's milestone one table takes their names and the
client's WorldReady. Counts from run 38972717843: 273 tests, 46 read to
fields, 1,073 unverified. Repository layout carries the reference tool's two
new tests.
Publish the generated message reference at bootstrap 58cb3ba
Messages and a page per area, generated by Tools/NexusTomorrow.ProtocolReference
at 58cb3ba: 1,119 messages on 40 pages. Home, the sidebar, Client protocol,
Codec design and Message audit design link it. Repository layout gains the
Tools folder, the generator and its tests; the counts move to 271 tests in six
applications. Code pages re-verified against 58cb3ba, run 38964363277.
Record the build reorder: step 2 closed, the audit alongside step 3
The codec's third stage closed after its review at c6b56e9, and the core skeleton starts on the messages already verified rather than after the whole audit, so the project can stop depending on the old server; milestone one's messages are checked first and the rest alongside the build. Roadmap marks step 2 done and step 3's pregame stage planned and waiting on review; the audit page records decision 2's change with its reason; Codec-design closes stage 3.
Add Client protocol, the pregame conversation as far as it's verified
An explanation page for how the 16042 client talks to a server: its three connections, the envelopes and keys, the greeting's build and protocol checks, and the pregame conversation from logging in through character select, realm select and transfers to entering the world, named by the verified declarations. Sign-on is labelled as carried over from the old code. Linked from Home, the sidebar, Roadmap and the audit page.
Add the message audit's design
A published design page for checking every message against the client before more feature work: the five rungs, the Verified attribute and its shrinking-list test, the use gate at dispatch, neutral names, the full-layout tree check, feature areas, the generated protocol reference, and the order of the work. Linked from Home, the sidebar, Codec-design, Roadmap and the systems table.
Set the documentation format for building out the core
Documentation-standards gains a system's page set (design, explanation hub, references, guides), generated reference for the code's registries, a Where the code lives table on every page with a ref badge and none on index pages, a path-based re-verify check, Home by area past twenty pages, and the three kinds of reader. Server-core-design gains the systems table that points at each system's current page. House style names messages with their opcode beside them. Home drops its ref badge; Running-the-tests, Codec-design and Roadmap gain their code tables.
Bring the core design up to one world, the gateway and public hosting
Server-core-design takes the new names (message queue, gateway, write-behind queue, AOI, conflation, handoff, TCC), one world with no layering, routing by an opcode table with priorities, rate limits and kill switches, the realm as modules, pooled and dedicated map threads, tick and update interval per instance type, sleeping cells, AOI tiers, the gateway's login exchange, the hardened client ports, the two unsent-bytes limits, the write-behind sequencer and load workers, the private pack, the portal's recovery and source link, and a Hosting section. Roadmap drops public hosting from out of scope and states one world and public hosting as goals.
Bring the wiki up to the codec's first stage at bootstrap 4bb1920
- Add the codec, its generator, their tests, the hot-path files and packages to the repository layout, with 206 tests.
- Describe the hot-path tier as built: the switch, the ban list, the rules it raises, and where analysers stop.
- Run the format check after the build everywhere, since it loads the generator.
- Record the review's union selector and aligned blob rules, and move step 2 to stage 1 of 3.
Bring the pages up to the enforced build at bootstrap 490ed16
- Explain build enforcement, the pinned analysis level and every suppression with its reason.
- List the commit message, em dash and format checks CI runs before the build, with fixes.
- Use the renamed identifiers: ServerPathInitialize, HousingNeighborhoodInfoEntry.
- Point the roadmap at run 38682391315, seven of seven on SDK 10.0.402.
Add the codec design and link it from the core design and roadmap
- Record the declaration format, the generator's diagnostics, the client-facts table, the converter and the equivalence-first rule, at discussion until step 2's plan is agreed.
- List what's still open: overwide values, signed fields, unnamed opcodes, and the opcode errata.
Turn the home page into the index and add the sidebar