Records that GGUPF.MiRust.com is the separately governed implementation project and prevents its planned capabilities from being attributed to the WordPress guide.
Architecture topic: this page does not claim that the WordPress website implements or executes the described runtime behavior.
Owner-supplied relationship
The project owner identifies GGUPF.MiRust.com as the enterprise Rust browser-runtime implementation project. The implementation URL remains an editable setting because availability and ownership must be verified.
What does not transfer
Support status, release readiness, security claims, benchmark results, model licenses, and deployment compatibility do not transfer between the guide and implementation surfaces.
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?