Toronto Public Library procurement (own site)

Part of #103. Blocked on #103's keyspace and terms-of-use decisions.

## What exists

Toronto Public Library posts RFQs, RFPs, REIs and tender calls under **Doing Business with the Library** — `https://www.torontopubliclibrary.ca/about-the-library/business-with-the-library/` — with a published purchasing policy at `https://www.torontopubliclibrary.ca/terms-of-use/library-policies/purchasing-policy.jsp`.

## Why this one is different from the rest of #103

**It appears to publish on its own website rather than a commercial platform.** That makes it the cheapest of the set to archive and the one least likely to raise the terms-of-use question in #103 — but also the one that needs bespoke parsing rather than an adapter, since there is no platform to share.

Our spine currently contains **1** solicitation matching "Library", and that is a mention inside a City call, not TPL procurement.

## First step

Fetch the Doing Business page and establish what it actually lists: current opportunities only, or closed and awarded too? If it is current-only, this is an **archive-at-scrape-time** source with no backfill — the same shape as Ariba open postings (spec §2.5.3), and its value depends entirely on running regularly from now on. That changes the priority: a source that cannot be backfilled is worth starting sooner, not later.

## Sources

- https://www.torontopubliclibrary.ca/about-the-library/business-with-the-library/
- https://www.torontopubliclibrary.ca/terms-of-use/library-policies/purchasing-policy.jsp

Start by fetching the Toronto Public Library Doing Business page and compare its listed opportunities with the purchasing policy page. Read issue #103 and spec §2.5.3 for the keyspace, terms-of-use decisions, and archive-at-scrape-time model. Done means establishing whether current, closed, or awarded notices are listed and documenting the source shape and bespoke parsing scope.

Written by the indexing model from the issue text.