MiRust and GGUPF: documentation versus implementation

A clear project boundary prevents research pages, WordPress releases, and external runtime prototypes from inheriting one another’s support claims.

MiRust.com is the project guide and public documentation surface. The project owner identifies GGUPF.MiRust.com as the separate enterprise Rust browser-runtime implementation project.

Why the split matters

A guide can define architecture, evidence requirements, terminology, and research questions without shipping a runtime. An implementation can test those ideas without automatically changing the guide’s maturity labels.

Independent versions

The WordPress theme, companion plugin, starter-content schema, and GGUPF implementation must retain independent versions and changelogs. Coordinated release notes should name each exact version.

Benchmark routing

Any result published on MiRust must identify the exact implementation revision, model, backend, hardware, method, raw data, date, and limitations.