Maps the solution and NMake-style project to Cargo and PowerShell commands without presenting Visual Studio as a separate build system.
Implementation evidence: this topic is grounded in the reviewed GGUF.MiRust.com source snapshot. It documents observed code and artifacts without claiming broad deployment, model quality, or production readiness.
Composition root
TinyRustLM.sln and the Visual Studio project wrap command-line operations. PowerShell scripts build, run, and test the Cargo workspace and local browser surface.
Authority
Cargo manifests, source, and lockfile remain the implementation authority. IDE files should not introduce hidden flags, alternate source lists, or untracked outputs.
Release check
CI should compare Visual Studio wrapper results with the documented Cargo commands and fail when artifact locations or profile selection diverge.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?