List only the entry points in the sidebar - The sidebar is navigation, not a second index: each system's main page and the pages that stand alone, in four groups - Each system's main page opens by linking its references and design, so every page stays two clicks from the sidebar; Home still lists all - Documentation standards states the rule
State how a design built in stages ships - Each built stage's decisions move off the design page onto the system's pages, so the page stays published only for what's left
Mark Codec design committed and the house style an index - The codec is built on main, and the page describes it as built; it points at the message reference and the audit page - The house style holds rules for writing pages, as its parent does, and Home already lists it as an index
Re-date Documentation standards after its client-identifier change
Allow the client's identifiers where it ships them in plain view A table or column name, or a value its tables or public add-on interface name, may be used where a verified declaration needs it. Interface and script text, names found only inside the executable, and whole name tables stay off. The example client fact is now one the audit has verified.
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.
List a generated set through its own index The message reference will run to an index and one page per area; Home and the sidebar list the index, which lists the rest.
Say which client facts the wiki states, and pause step 2 for the audit Documentation-standards gains Facts about the client: purpose, field meanings, units, ranges, value sets, table indexes and order are stated as facts; addresses, decompiled code, tool names and output, client strings and method stay off. Roadmap: stage 3 paused for an audit of every message against the client before more feature work, and why it comes before the core skeleton.
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.
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.