Defines MiRust.com as the guide and evidence surface while separately governing implementation projects such as GGUF.MiRust.com.
Guide responsibilities
MiRust.com owns terminology, framework explanations, source-aware model profiles, benchmark methodology, editorial statuses, and cross-project evidence links.
Implementation responsibilities
An implementation project owns source code, executable artifacts, dependencies, tests, runtime security, deployment, model files, and measured performance. The owner currently identifies GGUF.MiRust.com as that separate project.
Cross-project rule
Link exact versions and evidence. Never infer implementation support from guide prose or guide maturity from an unreviewed prototype.
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?