Wiki audit: correct 12 pages against the code, and retire a command that cannot run
Every page was read against the 5.7 tree. Three systemic causes account for most of
what the audit found.
**Docs described tuning that is no longer shipped.** FAQ and Runtime-Controls quoted
the family fallback and pre-repair arms, while the defaults are the per-install
`ModelProfile.table`: the 35B rows are 10 GiB/160 slots at 4-bit and 12 GiB/96 at
8-bit with prefetch on, and Qwen3.8 is 12 GiB/96 at 4-bit and 9.5 GiB/40 at 8-bit
with prefetch off. Also corrected: Home's Swift floor (6.3 -> 6.4) and its 35B disk
range; Getting-Started's dense sizes, and its claim that a pipe sets up the browser
window (that prompt needs a terminal); Features' missing 8-bit Qwen3.8, its three
clients where there are five, and "binary thinking" where Qwen3.8 has four levels.
**Version labels had drifted.** Benchmarks' "v4.7" section is 5.0's work — there is
no v4.7 tag — and it claimed a v4.6 baseline for Qwen3.8, which did not exist then.
Its three percentages were withdrawn rather than re-guessed: their baselines cannot
be re-derived from anything in the repository.
**The LAN Manager's remote-access recipe was impossible.** The harness refuses
`--host 0.0.0.0`, and a specific address fails the webserver plugin's schema
(`expected "127.0.0.1" | "0.0.0.0"`), so the profile does not load. Verified by
trying both on a throwaway DSH_HOME. The page, the plugin README and the plugin's
own boot log all told operators to do it; all three now say what is true, and the
boot log no longer advertises addresses nothing is listening on.
Also: Cookbook's launcher keys, OpenAI-Compatible-Server's `-fast` listing and its
per-surface reasoning field, System-Design's ANE default, MTP numbers and interface
list, TinyTitan-Plugin's `--web` owner and its session-title overclaim, the LAN
fence's IPv6 ranges and its missing config keys, an unquoted receipt error, and a
duplicated sentence.
Verified after: links, anchors and the sidebar clean; every cited path still
resolves; both plugin suites pass; all six lint gates green.
Remove the Mac app: the product is the engine and its server
The app, the out-of-process decode service it drove, and their library and test
targets are gone from the repository. The wiki followed them: the Interfaces
rows, the app preference block, the app-only control rows and the iOS roadmap
item all described a front end TinyTitan no longer has and will not carry. A
second front end is a second surface to build, keep in step with every engine
feature, and support, so the Roadmap now says a GUI or mobile front end is out
of scope rather than deferred, and the tracker's issue-#5 items are closed
instead of left open for a future session to pick up.
Where a page told the reader to do something in the app it now gives the real
equivalent: the launcher's --model keys and --bits, the served id from
/v1/models, and the OpenAI (http://127.0.0.1:8080/v1) and Anthropic Messages
(http://127.0.0.1:8080) endpoints. Every process guard is now exactly
'TinyTitanServer|TinyTitanCLI|TinyTitanPackageTests|swiftpm-testing-helper|mlx_lm|mlx-lm'.
Getting Started also gained the one-command install it never mentioned
(tools/install_tinytitan.sh, which leaves ~/.local/bin/tinytitan), since the
installer and the server launcher are now the whole product surface.
Changelog.md is untouched: it is the chronological record of what shipped, and
entries describing the app were true when they were written.
The wiki is TinyTitan
Every page except the Changelog is renamed by the same rule the checkout used
(`NVMAI_` -> `TINYTITAN_`, `NVMAI` -> `TinyTitan`, `nvmai` -> `tinytitan`), and
the wiki's own `assets/wordmark.svg` is fixed the way the repository's was: the
name was split across two coloured spans, so it read `NVM` + `AI` and had to
become `Tiny` + `Titan`, with the canvas widened from 132 to 176 so the longer
name is not clipped.
The Changelog keeps its entries as they shipped -- they are the record of
releases made under the old name -- and gains one line at the top saying the
project was renamed on 2026-09-14, so the page is not a mystery. Its release
links still resolve: GitHub redirects a renamed repository.
Home now leads with the project's brand image
(`assets/tinytitan-hero.png`), the same artwork the README leads with, and the
tracker gains the closed row.
agent
committed
Sep 14, 2026
The developer role is served, and the clients live in one list
Two closures from the same session:
- The server guide's Chat Completions section says a `developer` message is
served as the system turn it stands for, and the DeepSeek Harness recipe's
`supportsDeveloperRole: false` is marked optional rather than required.
- The benchmarking guide documents the three rounds and where the client list
comes from: `NVMAI_CLIENTS` in tools/nvmai_models.sh, read by both the launcher
and the coder harness, with four coder clients and Zed as the editor client
that can only be wired and checked.
The tracker records both, with the measurements: three tests shown failing
without the role mapping, the golden gate byte-identical on a dense and an MoE
install, and Claude Code's first measured coder case (exit 0, 92.3 s, quality
pass) after installing it.
Head every page with the NVMAI wordmark
The wiki carried no visual identity at all, so the README and the wiki did
not look like the same project. Every content page and the sidebar now open
with the same two-colour wordmark the README slogan uses -- NVM in cyan, AI
in orange.
One file serves both themes here. The slogan needs a light and a dark
variant because its body text is neutral, but the wordmark is entirely
brand colours and both carry enough contrast on #ffffff and #0d1117, which
was checked against each before committing.
Deliberately not applied to the hundreds of inline "NVMAI" mentions in
prose: GitHub cannot colour inline text, so each one would have to become
an image, which would break text selection, search and screen readers for
no gain.
Document NVMAI 4.0 defaults and qualification
Document Ornith tooling matrix benchmark
Document binary thinking controls
Document Ornith concise tool qualification
Document benchmark production profile
Document Ornith as the default baseline
Document unified sampling defaults
Document Ornith native MTP support and benchmarks
docs: refocus wiki on core user workflows
docs: update launchers and release history through 3.9
docs: use nvmai/ as the model directory convention
rename model dirs to qwen3.6_35B_A3B_{4,6,8}Bit and update all references
Migrate project documentation into structured Wiki