BagCheck compares the three recorded measurements in the best physical orientation. It does not invent a missing axis label or assume that unknown protrusions are included.
Source
Where these details came from
Last checked
Unknown
Evidence
Residual-wave worker a-04 derived this from the retained first-party cabinmax.com feed object; the coordinator re-sliced every cited span from the capture bytes and re-ran the maintained parser, so each populated value is the parser's own derivation. Fields not located are null with an explicit field disposition. Worker verdict CREATE_SUPPORTED. Own product object (Shopify products.json node, id 15677180707190, exactly matching productNodeRanges) publishes the exterior envelope as its own FAQ answer 'this bag measures 40×30×20 cm' (parsed [[40,30,20]]) and the capacity 'It holds 24 Litres' ([24]); the sole variant SKU is 5060505766967 and the own prose 'The Kobe is a precision-engineered travel backpack' establishes a standalone carried under-seat backpack. Own body also carries a SECOND triple 'maximum 55x40x20cm' which the own text frames as Ryanair's PAID larger carry-on ('if you require a larger carry on bag or suitcase ... you will have to pay extra') — explicitly NOT this product, so not the envelope. Weight (800 g / 0.8 kg) has no empty/unladen/unpacked/tare basis, so emptyWeightKg stays null; publishedAxisOrder stays null (unlabelled triple). Nullable, non-blocking. Not in the accepted 1,713 manifest, not among the 20 reserved cabin-max IDs.