orbid-read-comparelisted

# Compare tender vs datasheet (no Orbid) Read-only overlay of **two user files**. Not Orbid `run_match`. No scores, no fill, no catalog UUID. ## Gate Need both: a tender and a product document in this chat. Only one file → extract that side, then ask for the other. Even if Orbid MCP is already connected, do not call Orbid MCP. Do not invent the missing side. ## Iron law ``` ALL DATA MUST ORIGINATE FROM THE ATTACHED FILES. Allowed: Extract → cite page or sheet on both sides Forbidden: Prior knowledge → catalog UUID → “typical ICU ventilator” ``` Missing → `NOT SPECIFIED`. Unreadable → `UNABLE TO READ`. ## Steps Load `references/overlay-contract.md` for the full overlay (this folder is self-contained; do not open a sibling skill file). 1. **Tender extract** — shall / must rows: value, unit, **mandatory** vs **preferred** (do not collapse). Buyer, lots, deadline, compliance clauses quoted. Cite page or sheet. 2. **Datasheet extract** — numbered specs: parameter, value, unit, condition, page. Keep SKUs separate. Certs only as printed. 3. Align on **parameter + unit**. Convert units only when both sides state them; otherwise verdict `unit unclear`. 4. For each row pick exactly one verdict: `meets` / `short` / `not in datasheet` / `not in tender` / `conflict` / `unit unclear` / `not evaluated`. Cite pages on both sides. **`not evaluated` ≠ `meets`.** 5. Regulatory lines: only if both documents mention the same scheme. “CE” on a brochure is not proof against “valid CE certi