Skip to content

Normalize performance claims against hardware-readiness and QEMU-only evidence #5

Open
Open
Normalize performance claims against hardware-readiness and QEMU-only evidence#5
Labels
area: hardware-readinessIntel/x86_64/hardware readiness and platform ports.needs: validationNeeds validation evidence or gate run.priority: P1-highHigh-priority work for the current roadmap.risk: performance-claimRisk of unsupported performance or benchmark claims.type: docsDocumentation, contracts, or roadmap work.
Milestone
Phase 5 — Hardware Readiness and Ports

Description

@Pummelchen
Pummelchen
opened on Jul 9, 2026

Summary

Normalize performance wording so QEMU correctness evidence is not presented as hardware performance proof.

Problem / objective

README/wiki/tracker performance language should be reconciled with HARDWARE-READINESS.md and release-candidate contracts, which treat QEMU output as correctness evidence only.

Acceptance criteria

  • Audit README, local docs, wiki copies, tracker, and hardware-readiness docs for performance claims.
  • Mark unverified numbers as targets or remove unsupported claims.
  • Keep hardware performance claims blocked until measured hardware baselines exist.

Validation

  • docs-only
  • manual-review

Relevant files

  • README.md
  • HARDWARE-READINESS.md
  • PROJECT-TRACKER.md
  • wiki/Qwen3.6-INT6-Support.md
  • contracts/qemu-rc-v1.json

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: hardware-readinessIntel/x86_64/hardware readiness and platform ports.needs: validationNeeds validation evidence or gate run.priority: P1-highHigh-priority work for the current roadmap.risk: performance-claimRisk of unsupported performance or benchmark claims.type: docsDocumentation, contracts, or roadmap work.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions