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
KAT is supported: flip Getting-Started, Features and Roadmap, and close the tracker
Both widths verified on the real install with stored golden baselines. The
Roadmap entry is DONE, the wiki status wording no longer says a first
verification is pending, and the tracker's task table is closed out. Records
that it took five bugs, including the expert-fusion ordering that no byte-level
check could see.
agent
committed
Sep 13, 2026
State KAT-Coder's verification status where a user reads it
KAT-Coder-V2.5-Dev: prep landed, conversion pending
The new family member is a Qwen3.6-35B-A3B fine-tune, so it is the same code
path this runtime already serves. The tracker records what was checked against
the checkpoint before any download (31,333 tensors, none outside the converter's
namespaces, no vision tower despite the declared vision_config, the plan's
tensor split and the ~20 GB 4-bit output), what has landed (converter, installer
and launcher rows, profile rows, display name), and what remains (conversion,
installs, the app's two fingerprints which need the converted snapshot to
exist, and verification).
Two deviations from the checkpoint's own recommendations are stated rather than
hidden: presence_penalty 1.5 is not implemented by this runtime (it supports
0.0 only), and preserve_thinking has no equivalent here. The roadmap entry
gains a status line and its own open questions are answered -- the mrope block
is present and identical to AgentWorld's, and the checkpoint carries no vision
tensors.
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 Qwen3.8-Flash-Next, per-family tuning, and the new model ids
The wiki was last updated before three shipped changes, so it described a
runtime that no longer exists.
- Qwen3.8-Flash-Next 125B-A6B appeared only in the changelog. It is now in
Home, Features and System Design, including the install size, which is
about 161 GB and dominated by a 95 GB hashed n-gram table, and the point
that it runs on 24 GiB because the experts are streamed.
- NVMAI was described throughout as a "Qwen3.5-MoE 35B-A3B" runtime. There
are three families now, and Qwen3.8-Flash-Next does not share the tensor
contract the other two do.
- Model ids gained the routed-expert width (`_4-Bit`, `_8-Bit`). Every
example in the server guide and FAQ still showed the bare id, which the
server no longer accepts.
- ANE prefill was documented as experimental and opt-in; it is the default,
and falls back to the GPU when a model has no sidecar.
- The expert-cache budget was documented as a flat 8 GiB deriving 128 or 64
slots. It is per family now, with a clamp to half of physical memory, and
speculative expert prefetch was not documented at all.
The dated v4.1 and v4.6 benchmark sections are left as they are: they record
what was measured at the time, and their 8 GiB budget note was accurate for
those runs. Only the claim that ANE "stays off by default", which a reader
would take as current, is corrected there. Current numbers follow in a
separate commit once the re-measurement finishes.
Audit the wiki: current v4.6 state, remove engineering history records
- Move the v4.2/v4.3 experiment qualification record out of the wiki
(now docs/v4.2-experiments.md in the source repository) and drop its
navigation entries; the wiki keeps user-facing documentation only.
- Trim Benchmarks to current, decision-relevant results: v4.6, its v4.1
baseline, the MTP and coding/tooling qualifications behind the shipped
defaults, and fast-alias latency. Remove superseded 6-bit-era tables,
the stale prompt-length record, and the historical M5 reference.
- Bring Features and System Design to v4.6 (tiled Top-K sampling, opt-in
ANE prefill) and remove release-tag phrasing from runtime descriptions.
- Remove the empty Unreleased changelog section, the legacy 6-bit row in
Getting Started, and a duplicated server snippet.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Document NVMAI 4.1 release
agent
committed
Aug 21, 2026
Document NVMAI 4.0 defaults and qualification
Document binary thinking controls
Document Ornith as the default baseline
Document Ornith native MTP support and benchmarks
Document compressed KV cache and YaRN contexts
docs: add Ornith 1.5 user guide
docs: refocus wiki on core user workflows
docs: update launchers and release history through 3.9
features: move the Features and What NVMAI added sections from the README into a wiki page