orbid-read-datasheetlisted

# Read a product datasheet (no Orbid) Read-only extract from **this file**. Marketing copy is not a spec. Certificates count only if this document lists them. ## Gate Need a product PDF/DOCX (or paste) in the chat. None → ask to attach. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not pull another vendor’s numbers from memory. If they also attached a tender / RFP, use **orbid-read-compare**. ## Iron law ``` ALL DATA MUST ORIGINATE FROM THE ATTACHED FILE. Allowed: Extract → cite page Forbidden: Prior knowledge → other vendors → “typical ICU ventilator” ``` Missing value → `NOT SPECIFIED` (optional gloss 未写明). Unreadable scan or garbled digits → `UNABLE TO READ`. Do not OCR-guess. ## Extract (cite page) Load `references/extract-contract.md` when extracting tables. 1. **Identity** — brand, model, variants in this PDF (one brochure often mixes SKUs — keep them separate). 2. **Intended use** — stated indications; ignore slogan lines. 3. **Numbered specs** — parameter, value, unit, condition (e.g. at 25 °C), page. Prefer tables over prose. Ranges stay ranges; do not pick the marketing max. 4. **Certificates on this document** — quote the exact string (e.g. “CE marked to MDD 93/42/EEC”). If it says “complies with ISO 13485” without a cert id, report that wording — do not invent a certificate number. 5. **What is missing** — warranty absent on a datasheet is normal → `NOT SPECIFIED` for this file, not a product failure. ## Adversarial cases Honesty fi