Re-verify the repository layout at bootstrap f129108 - The generator now reports NTC001 to NTC013, and the suite is 208 tests.
Describe the converter as built on the codec design - Name the tool, its patterns, when a type converts, how it rewrites in place, and its report. - Generalize the 64-bit enum case to any member written wider than its type.
Record nested messages, the NTC003 warning and NTC013 on the codec design - Let a message sit inside another layout unless it holds an aligned blob. - Make NTC003 a suppressible warning for enum sentinels, and add NTC013 for a case its selector can't carry.
Record why converted models keep their old methods until stage 3
Add the legacy snapshot to the repository layout and suppressions - Describe the temporary copy of the old models the conversion is proven against. - List its suppressions with their reasons, and re-badge both pages to bootstrap f04e5ee.
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.
Fold the stage 1 review's generator changes into the codec design - Widen NTC004, NTC009 and NTC012 to what the generator now catches. - Say a type built on a failing type emits nothing, and that messages may derive from messages.
Add the conversion's plan for its awkward cases - Record the scope (927 messages, 326 nested types, STS out) and how 64-bit enum defaults, the dispatch factories, the bit array and guid types, and unregistered models convert. - Close the open question on how many enums the old code writes at 64 bits.
Add the codec's first-stage runs to its verification status - Cite run 38690623961, 196 of 196, and the planted-bug runs that show the tests catch mistakes.
Spell out what each codec diagnostic catches - Give each of NTC001 to NTC012 its exact conditions, as the generator checks them. - Note that NTC006 is an error under our build, and that a type with an error gets no code.
Mark the codec's first stage as built - Name the facts table's path and say its check is proven on test messages for now.
List the generator's twelve diagnostics on the codec design - Replace the seven planned ids with NTC001 to NTC012 as the generator reports them. - Note the test that holds a generated Write to zero allocations.
Settle signedness, unions and unnamed opcodes on the codec design - Record SInt as two's complement, sign-extended on read, with signed range checks. - Record that a union with no arm for selector 0 fails the facts check for its opcode. - Record that unnamed opcodes are counted and reported, not failed. - Add the three stages the codec is built in.
Record the codec decisions the first two tasks settled - Name the message attribute WireMessage, as the code does. - Move overwide values and reads past the body to settled: both throw CodecException. - Say the codec lives in its own hot-path project, with ref struct readers and writers.
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
Add the code standard, workflow, tests guide and repository layout - Explain the code standard's choices and why the build holds them. - Explain the branches, the dispatch-only test workflow and its guard rails. - Add a guide to running the tests locally and in CI, and a reference to every project, test and root file.
Add the server core design and the roadmap - Record the approved design: owners by routing tag, declared messages, persistence, authority, content, the console and verification, with what was rejected and why. - Set out the six build steps, milestone one's messages, and where step 1 stands.
Carry over the documentation standards and house style - Adapt the status ladder and the ref badge to what's built on bootstrap and main. - Switch the wiki's commit format to the repository's: imperative headline, blank line.
Initial Home page