# Verification rules

Public sources only. No logins, no scraping that violates a site’s terms or `robots.txt`, and no private or leaked data. Never add an install without a source. If the evidence is weak, use `unconfirmed` rather than omitting the signal or overstating it. This ledger is not investment advice.

## Status bars

Each location-level record has exactly one current `status`. Announcement-level count claims belong in `data/announcements.json`, not here.

### unconfirmed

Use when a public signal exists but does not meet the bar for `announced`, `piloting`, `live`, or `removed`.

Typical cases: a single undated photo; a user social post that does not clearly name the site; a job posting that mentions a robot and a city but not a store; a maker page that claims “deployed with Brand X” and names no location.

`unconfirmed` is a first-class status, not a hidden queue. Confidence is usually `low`.

### announced

The location itself must be identified.

A first-party maker or operator source, or a tier-1/tier-2 news source, states a plan or commitment to install a named robot at that **named site**, and there is not yet evidence the unit is on site in a pilot or in service.

Chain-wide or count claims (“100 units,” “rollout across the brand”) are **not** location-level `announced` rows. Record them as announcements. Create an `announced` install only when the specific site is named.

A trade-show booth, lab demo, or “coming soon” teaser with no site name is not an install.

### piloting

A dated first-party source, or a dated tier-1/tier-2 press or local-news source, says the robot is on site at the named location in a test, pilot, limited trial, or “in a restaurant for testing,” and has not described it as regular production service.

One such source is enough if it is first-party or tier-1/tier-2 and names the site. Otherwise two independent public signals are required.

### live

All of the following:

1. The specific location is named (store, venue, or equivalent).
2. The robot product (or a clearly identified product family) is named or unambiguously pictured in context.
3. A dated source says the unit is in regular service, not only on display or in a trial.

Evidence options (either one):

- One dated first-party source (operator or maker newsroom, IR, or SEC filing) **or** one dated credible press / local-news source that names the location and states it is operating in service; or
- Two independent public signals that together name the location and show ongoing operation (for example local news plus a dated on-site photo; an earnings remark plus local TV). Two reprints of the same press release are not independent.

Trade-show, investor-day, and lab demonstrations are not `live` restaurant installs.

### removed

The site previously had a `piloting` or `live` (or, rarely, `announced`) record, and dated evidence shows the unit is no longer there.

Acceptable evidence: a first-party statement that the unit was removed or decommissioned; credible press to the same effect; or two independent recent on-site signals of absence plus the prior install record. A store closure is `removed` with a note that the site closed — not a claim that the robot “failed.”

Do **not** mark `removed` only because sources went quiet. Quiet sources trigger `needs_reverification` and leave status unchanged until there is positive evidence.

## Source tiers

| Tier | Types | What it can do |
|---|---|---|
| 1 | First-party operator or maker newsroom; official IR; SEC filing; on-the-record earnings remark posted on IR or EDGAR | Can establish any status if it names the needed facts and is dated |
| 2 | Established trade press, local news, national news, or a press wire quoting a named official | Same as tier 1 for location-level facts those outlets actually state |
| 3 | Official social accounts of the maker or operator | Can support `announced` or `piloting` when they name a site and date; alone they are not enough for `live` unless they are clearly an official newsroom equivalent (link the underlying post and archive it) |
| 4 | User social posts, reviews, job postings, unlabeled photos or videos | Leads and supporting signals only. A tier-4 item may be one of two independent signals; it cannot be the sole basis for `live` or `removed` |

Independence means different organizations, not a syndicated copy of the same release. A maker press release and a wire reprint of that release count as one signal.

## Staleness

- For `live` and `piloting`, if `last_confirmed` is older than **12 months**, set `needs_reverification=true`. Do not auto-change `status`.
- After a failed re-check (no confirming public signal found), leave the status in place, keep the flag, and note the attempt and date in `notes` or the weekly change log. A second annual miss still does not equal `removed`.
- For location-level `announced`, review if the stated target date is **6 months** past, or if **18 months** have passed with no target date and no on-site evidence. The record may stay `announced` or move to `unconfirmed`; do not invent a removal.
- For announcements (count claims), use the same 6-month-past-target / 18-month review. Possible announcement statuses: `active`, `revised`, `withdrawn`, `fulfilled`, `expired`. `expired` means the target window passed without support for fulfillment — not that the claim was false when made.

Proposed windows are also listed in `open-questions.md` and can be tightened after the first seed pass.

## Social posts, reviews, and job postings

- Official maker/operator accounts: treat as tier 3. Archive the post. Quote only the fact-bearing line.
- User posts and reviews: usable only if they are public, dated or date-inferable, and identify the venue. They are supporting evidence, not a standalone `live` source.
- Job postings (“robot technician,” a model name, a city or store): investigation leads. They may justify an `unconfirmed` row if they clearly refer to a robot already associated with a site; they do not by themselves make a site `live`.
- Do not use private groups, deleted posts that were not archived, or anything behind a login.

## Archiving

When a source is used to add a record or change a status, capture a public archive, preferably the [Wayback Machine](https://web.archive.org/) (`https://web.archive.org/save/{url}` or a save that produces a snapshot URL). Store that URL in `archive_url`.

If the archive fails, keep `url`, `accessed_date`, and a short `quote_excerpt`, set `archive_url` to null, and note the failure. Do not use an archive service that requires a login.

Re-archive if the live page changes in a way that affects the cited fact.

## Removals and conflicts

- Prefer first-party or press evidence of removal.
- If sources conflict (one says live, a later one says removed), record both, set status to the later well-sourced fact, lower `confidence` if the later source is weaker, and explain in `notes`.
- A maker “customer logo” page with no date and no site is not evidence that every logo still has a live unit.

## Confidence

- `high`: tier 1 or 2, dated, names site and product, and is not contradicted.
- `medium`: meets the status bar but is thinner (older, official social, or two weaker signals).
- `low`: `unconfirmed`, or a status that rests on the minimum bar and has unresolved questions.

## What counts as a robot

Robots that make, cook, serve or deliver food and drink inside a venue count. As of Nov 18, 2026 that includes every automated coffee kiosk (for example the Touch Coffee Smart Bar), not only kiosks with an arm. A kiosk follows the same rules as any other record: a public, dated source that names the place is needed for in use; a kiosk seen only in the company's own social post is `unconfirmed`. Sidewalk delivery, cleaning-only robots and factory lines stay out.

## Out of bounds

- No record without a public source.
- No credentials, email harvesting, or off-the-record tips used as the source of record. A tip is a lead; it becomes usable only when a public source is found.
- No ToS-violating scraping. Prefer official RSS and manual reading of public pages. Check `robots.txt` before any automated fetch.
- Paywalled articles: cite them only if a public headline/lede or archived public snapshot supports the fact, and look for a free corroborating source. Do not create accounts to bypass paywalls.
- Do not guess street addresses or precise coordinates. See `data/schema.md` for `geo_precision`.
