Records the canonical purpose, domains, package roles, owners, and source-of-truth boundaries for the guide, plugin, theme, and external implementation project.
Canonical roles
- MiRust.com: guide, documentation, research, evidence, and roadmap.
- MiRust theme: presentation and frontend behavior.
- MiRust Core: portable content types, metadata, starter content, and editorial controls.
- GGUPF.MiRust.com: separately governed implementation project identified by the owner.
Review triggers
Update the map when a domain, repository, package owner, release channel, or source-of-truth boundary changes.
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?