↗Review Records16 Oct
Pulse X 2: Why the Version Stays in the Record
Small differences in model naming can change which document a claim belongs to.
SOURCE ANALYSIS / NOT SCOREDReview Records
A model-by-model look at the documentation. These records distinguish brand statements from measurements we have not made.
6 recordsNEWEST FIRST / INDEX 2026
↗
↗Review Records16 Oct
Alibarbar Swirl: What an Image Can—and Cannot—Establish
Design presentation is a useful starting point. Physical inspection answers a different set of questions.
SOURCE ANALYSIS / NOT SCORED
↗Review Records16 Oct
Foger Bit 35K: Begin with a Separate Model File
Keep the Bit record distinct from the Switch Pro family before interpreting a specification.
SOURCE ANALYSIS / NOT SCORED
↗Review Records16 Oct
Geek Bar Pulse: A Record of What Is Documented
Follow the full model name, the original source and the limits of a published specification.
SOURCE ANALYSIS / NOT SCORED
↗Review Records16 Oct
Alibarbar Ingot 9000: The Source File
A focused documentation record for the Ingot name, its source context and the evidence still needed.
SOURCE ANALYSIS / NOT SCORED
↗Review Records16 Oct
Foger Switch Pro: Read the Components, Not Just the Name
A device, a pod and a charging component need separate records. Here is how the documentation fits together.
SOURCE ANALYSIS / NOT SCORED