Physical spec-sheet keys describing a concrete object's hardware. They belong
on a thing (a concrete named object) and must NEVER bleed onto a broad
domain / standard / person / project entity — the policy-example
parroting bug, where a broad DOMAIN article inherited a hardware spec key.
Grounding the infobox in the entity's own kind blocks the leak deterministically.
Physical spec-sheet keys describing a concrete object's hardware. They belong on a
thing(a concrete named object) and must NEVER bleed onto a broaddomain/standard/person/projectentity — the policy-example parroting bug, where a broad DOMAIN article inherited a hardware spec key. Grounding the infobox in the entity's own kind blocks the leak deterministically.