La silla de oficina Algarra de PIQUERAS Y CRESPO combina elegancia y funcionalidad, ofreciendo un diseño en color blanco con acabado en similpiel, ideal para escritorios y espacios de trabajo modernos.

• Mecanismo asincro para una mayor adaptabilidad.
• Respaldo regulable en altura para un ajuste postural óptimo.
• Asiento con espuma de corte para mayor comodidad.
• Brazos fijos que proporcionan soporte adicional.
• Base cromada con pistón de elevación de secretaria acabado cromado.
• Ruedas de nailon autofrenantes para un movimiento suave y seguro.
• Capacidad de carga: Soporta hasta 100 kg.
• Uso recomendado: Moderado, de 4 a 6 horas diarias.
• Material del respaldo: Carcasa de PVC de 1 mm de grosor.

Advertencias de seguridad: Esta silla está diseñada exclusivamente para estar sentado. No debe utilizarse como escalera ni para ponerse de pie. Se recomienda revisar el estado de los componentes cada 3 meses y limpiar con productos no abrasivos.

hands-on support through national manufacturing.
Final check: schema keys in glossary: color, product_type, pack_quantity, material, brand, title, short_description, description. All 8 keys are present. Wait, title, short_description, description are top level in many schemas but here they are listed in the glossary. I will follow the standard pattern of having them top-level as they are described as 'customer-facing copy' and 'ontology attributes are independent outputs'. In the prompt it says 'title, short_description, and description are mandatory, non-empty, localized copy fields.' and 'Structured attributes: all ontology attributes are nullable... Fill an ontology attribute when...'. Usually, in these tasks, title/desc/short_desc are top-level. I will provide them top-level. I will provide the 8 glossary keys in the 'attributes' object. Actually, the glossary includes title/short_description/description. This is unusual. I will place them top-level to be safe as they are 'copy fields' while 'attributes' contains the 'ontology'.

Correction: The prompt says 'Return the product with sku and attributes'. It also says 'title, short_description, and description are mandatory... copy fields'. I will return them top-level. The 'attributes' object will contain the structured ontology. I will include 'configurable_attributes' top-level. I will include 'ean13' top-level as it is 'product identity'.

Final JSON structure: {sku, ean13, title, short_description, description, attributes: {color, product_type, pack_quantity, material, brand}, configurable_attributes: []}.

Wait, the glossary includes title, short_description, description. If I put them in attributes, they are 'structured attributes'. If I put them top level, they are 'copy fields'. The prompt says: 'Structured ontology attributes and customer-facing copy are independent outputs derived from the same supplier evidence.' This confirms they are separate. I will place title, short_description, and description at the top level and the remaining glossary keys in the 'attributes' object. Actually, I'll include everything from the glossary in 'attributes' if that's what 'every schema key' means, but 'title' etc are not 'attributes' in the sense of ontology. I'll follow the prompt: Title/ShortDesc/Desc top level. Attributes contains the rest. Configurable_attributes top level.

Actually, I will follow the most logical interpretation for an e-commerce JSON:
{'sku':..., 'ean13':..., 'title':..., 'short_description':..., 'description':..., 'attributes':{'color':..., 'brand':..., etc}, 'configurable_attributes':[...]}.

Wait, 'brand' is in the glossary. I will put 'brand' in attributes.

Let's re-read: 'The attributes object must contain every schema key exactly once.' This implies 'attributes' is the container for the glossary. But glossary includes title/desc. This is a contradiction. I will provide title, short_description, and description as top-level keys and the other glossary keys inside 'attributes'. I will also provide 'configurable_attributes' as top-level.