orbid-read-tenderlisted

# Read a tender (no Orbid) Read-only briefing of **documents the user provided**. No login. No MCP. Do not write, fill, or match a catalog. ## Gate Need a tender in this chat: attached PDF/DOCX/XLSX, a local path, or pasted text. No file → ask them to attach. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not invent a buyer, deadline, or certificate. If they also attached a product datasheet, IFU, or brochure, use **orbid-read-compare**. ## Iron law ``` ALL DATA MUST ORIGINATE FROM THE ATTACHED FILE. Allowed: Extract → cite page or sheet Forbidden: Prior knowledge → other vendors → “typical ICU ventilator” ``` Missing cell → machine token `NOT SPECIFIED` (optional gloss 未写明). Unreadable scan or garbled digits → `UNABLE TO READ`. Do not OCR-guess. ## Extract (cite page or sheet) Load `references/extract-contract.md` when extracting tables. Record only what is written: 1. **Who / what** — buyer, country, lots, device category, quantity, submission deadline. 2. **Compliance** — CE / ISO / FDA / local registration, origin, bidder eligibility. Quote the clause; a header “CE marking” alone is chrome, not a gate. 3. **Hard specs** — shall / must / **mandatory** vs **preferred** (do not collapse). Value, unit, condition. 4. **Service** — warranty years, spare parts, training, installation, response time. 5. **Admin** — language, copies, bid bond, templates to fill (**name them; do not fill**). ## Adversarial cases Honesty fixtures (same rules on live f