docs: align research doc Tier 4 with OEM Reference Design rename - #16
Merged
Conversation
The Tier 4 heading in docs/research/hardware-drivers-and-migration.md still used the old semantics where "Reference" is the top OEM tier, conflicting with the authoritative SupportTier ladder in crates/andromeda-hardware/src/model.rs (blocked < community < reference < supported < certified), where `reference` is the second-lowest, virtual-only evidence tier. PR #11 already renamed the top "Tier 4 Reference" to "OEM Reference Design" in the product plan §6.2 and architecture doc §3.2 but left this research doc untouched (out of that PR's scope). Rename the heading and add a clarifying note that OEM Reference Design is a product-line milestone, NOT the SupportTier `reference` value. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
docs/research/hardware-drivers-and-migration.md§5 的 Tier 4 — Reference 仍沿用旧语义，把「Reference」当作最高的 OEM 整机层。这与权威定义crates/andromeda-hardware/src/model.rs中的SupportTier阶梯冲突——那里blocked < community < reference < supported < certified，reference实为次低级、只有虚拟（L0–L2）证据的档位。PR #11 已在
docs/product-development-plan.md§6.2 和docs/os-landscape-and-andromeda-architecture.md§3.2 完成同名修正，但未覆盖该研究文档（超出其 scope）。本 PR 补齐这一处一致性。改动
### Tier 4 — Reference→### Tier 4 — OEM Reference Design（顶层硬件产品线）SupportTier枚举取值；给出权威阶梯来源与完整阶梯，说明代码里的reference反而是次低级虚拟证据档。范围最小化：
Phase H4：OEM Reference与结尾 "OEM Reference Hardware" 已带OEM前缀、无旧语义歧义，且不属于 Tier 4 定义段落，保持原样。1 文件，+3/-1，纯文档。
🤖 Generated with Claude Code