# Known-object test, TOI-5812.02

> Drafted by `python -m cygnus.campaign report` from the runner's outputs; reviewed 2026-09-25.
> The escalation and reviewer notes below were added by hand; every other number is the runner's.

## Escalation (2026-09-25)

**Repeat candidate — unverified lead.** The calibrated screen found a second, transit-like dip in
sector 82 at BJD 2460549.45, ΔT = 13.358 d after the catalogued transit, with a matching depth and a
similar duration. `docs/AGENT_RUNBOOK.md` makes a repeat candidate an escalation: the evidence level is
**not** raised here, and a reviewer should decide the follow-up. The hand tests done so far are in
*Reviewer notes*; difference-image centroids, an eclipsing-binary check and the TOI/ExoFOP record are
still open.

- Campaign spec: `campaigns/toi-5812-02.yaml`
- Parent queue: `tess-mono-01`
- Ledger runs: calibrate_screen #579, fetch_products #578, known_signal_recovery #580, period_aliases #582, prior_art #583, residual_screen #581
- Runner finished (UTC): 2026-09-25T11:08:29Z

## Bottom line

The calibrated screen **recovered the catalogued transit** of TOI-5812.02 (BJD 2460536.0834: recovered, depth 4669 ± 97 ppm (catalogue 5553 ppm)).
Outside the catalogued epoch the screen left 61 threshold entries forming **11 distinct event(s)**, **6 persistent** (SAP and PDCSAP, two or more baselines). None is vetted; see *Screen events*.
**Repeat candidate (unverified lead):** a persistent event at BJD 2460549.4561 matches the catalogued transit's depth (6326 vs 4669 ppm), 13.358 d later; 1 of 13 period aliases remain. See *Repeat candidates*.

This is a pipeline check on a known object, not a discovery claim. Two transits allow only the listed period aliases; they do not fix the period.


## Reviewer notes (2026-09-25, supersede pass)

**Superceded by the multi-archive runner:** re-run through `python -m cygnus.multi` on 2026-09-25, steps fetch_products, calibrate_screen, known_signal_recovery, residual_screen, period_aliases, prior_art (ledger fetch_products #1603, calibrate_screen #1604, known_signal_recovery #1605, residual_screen #1606, period_aliases #1607, prior_art #1608). Same retrieved products, same science outputs: entries, depths, k-star calibration and aliases match the production-runner results recorded here; the multi runner additionally records a screen-suitability census and a red-noise systematics model per light curve. The record is regenerated by the multi runner; nothing in the review changes.

## Reviewer notes (2026-09-25)

**Evidence level: Unverified lead** (a probable second transit of TOI-5812.02). Tests done by hand on the
sector 82 event, using the same SPOC PDCSAP/SAP light curve and 2-d running-median residuals already on disk:

| Test | Result | State |
|---|---|---|
| Quality flags and gaps | all cadences within ±0.15 d of the event have QUALITY = 0; largest gap 2.0 min | passed |
| SAP vs PDCSAP | 20-min binned profiles agree to ~100 ppm across the dip; centre ≈ −7.0 ppt in both | passed |
| Shape vs the catalogued transit | catalogued: flat bottom ≈ −5.5 ppt, width below −2 ppt ≈ 5.0 h; repeat event: flat bottom ≈ −6.5 to −7.8 ppt, width below −2 ppt ≈ 5.0 h | passed (similar) |
| Flux-weighted centroid (MOM_CENTR1/2) | after removing the slow sector drift, event residual +0.0022 / −0.0036 px against excursion scatter 0.0090 / 0.0040 px | passed (no anomaly at this precision) |
| Difference-image centroids / nearby-star blend | not done | not tested |
| Eclipsing-binary tests (odd/even, secondary eclipse, V vs U shape) | not done; only two events | not tested |
| TOI table / literature | TOI table (row updated 2026-07-17) lists no period; SIMBAD (re-run 2026-09-25T11:08Z) identifies the host as **WASP-134** (WASP-134b); the published WASP-134 system must be checked against the repeat candidate; ADS and ExoFOP not searched | inconclusive |

Persistent events checked, one line each (details in `screen.json`, `normalized_series.csv`):

- **2460549.45610 and 2460549.55819** — these are one continuous dip (BJD 2460549.354–2460549.562, ≈ 5.3 h), split into two rows by the event grouping; not two separate transits. Both are the repeat candidate.
- **2460539.22414 / 2460539.24844** — one ~35-min event, ~−0.7 % deep, but truncated by a ~5 h data gap and one cadence carries QUALITY = 128; consistent with a gap/quality artifact rather than a full transit. Not a repeat candidate (ΔT 3.13 d).
- **2460533.43515** — 2 cadences, −0.5 %, PDCSAP+SAP; too short to characterise.
- **2460554.62827** — 2 cadences, −0.4 %, PDCSAP+SAP; too short to characterise.

What this supports: a second, transit-like, ~0.65–0.78 % dip on TIC 388909695 (Tmag 10.4) in sector 82,
13.358 d after the catalogued transit, with the same depth, a similar ~5 h duration, clean quality flags
and no centroid anomaly. What it does not: a period (1 of 13 aliases survives only because the others are
excluded by *absence* of a predicted transit, not by a detection), a planetary nature (a blended or
grazing eclipsing binary is not excluded), or novelty (ExoFOP and the TESS team may already hold this).
Next test: difference-image centroids and a nearby-star check for the sector 82 event; the TOI/ExoFOP
record and SPOC DV for a period; a search for the surviving alias's predicted transits in other sectors.

## Target

| Field | Value | Source |
|---|---|---|
| name | TOI-5812.02 | NASA Exoplanet Archive TOI table (copied in the spec) |
| tic | 388909695 | NASA Exoplanet Archive TOI table (copied in the spec) |
| ra_deg | 327.570011 | NASA Exoplanet Archive TOI table (copied in the spec) |
| dec_deg | 4.194573 | NASA Exoplanet Archive TOI table (copied in the spec) |
| t0_bjd | 2460536.083418 | NASA Exoplanet Archive TOI table (copied in the spec) |
| depth_ppm | 5553.0 | NASA Exoplanet Archive TOI table (copied in the spec) |
| duration_h | 5.935 | NASA Exoplanet Archive TOI table (copied in the spec) |
| tmag | 10.4106 | NASA Exoplanet Archive TOI table (copied in the spec) |
| catalogue_row_updated | 2026-07-17 12:03:25 | NASA Exoplanet Archive TOI table (copied in the spec) |

## Products

| Product | Sector | Covers catalogued epoch | SHA-256 (first 16) | Retrieved now |
|---|---|---|---|---|
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 82 | True | `86cbf7461e6e564b` | False |

## Positive control (catalogued transit)

| Product | Epoch (BJD) | State | Usable in-transit cadences | Measured depth (ppm) | Catalogue depth (ppm) | Entry offset (h) |
|---|---|---|---|---|---|---|
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460536.08342 | recovered | 178 | 4669 ± 97 | 5553 | 0.36 |

Depth: median PDCSAP residual inside ±duration/2 about the catalogued epoch, against a 2-d running median; the error is statistical only. A depth unlike the catalogue's may reflect dilution, detrending or an epoch/duration error; it is reported, not used as a pass mark.

## Calibration and sensitivity

| Product | k* (sign-flip null) | At grid floor | 90 % completeness depth at k = 5, by duration | at k* |
|---|---|---|---|---|
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2 | True | 1h: 10000, 2h: 10000, 4h: 10000, 8h: 10000 | 1h: 5000, 2h: 5000, 4h: 5000, 8h: 5000 |

The null result (if any) excludes only dips deeper than the 90 %-completeness depth for their duration.

## Screen events outside the catalogued epoch

Entries merged where they overlap in time. *Persistent* = SAP and PDCSAP at two or more baselines.

| Product | Mid time (BJD) | Deepest median residual | Max cadences | Flux | Baselines (d) | Persistent |
|---|---|---|---|---|---|---|
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460539.24844 | -0.00742 | 25 | PDCSAP+SAP | 1, 2, 3 | yes |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460549.45610 | -0.00711 | 138 | PDCSAP+SAP | 1, 2, 3 | yes |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460539.22414 | -0.00686 | 12 | PDCSAP+SAP | 1, 2, 3 | yes |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460549.55819 | -0.00544 | 7 | PDCSAP+SAP | 1, 2, 3 | yes |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460533.43515 | -0.00508 | 2 | PDCSAP+SAP | 1, 2, 3 | yes |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460554.62827 | -0.00413 | 2 | PDCSAP+SAP | 1, 2, 3 | yes |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460533.51710 | -0.00499 | 2 | PDCSAP | 1, 2, 3 | no |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460533.42682 | -0.00372 | 2 | PDCSAP | 3 | no |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460544.90472 | -0.00367 | 2 | SAP | 1, 2, 3 | no |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460545.05263 | -0.00363 | 3 | SAP | 2 | no |
| `tess2024223182411-s0082-0000000388909695-0278-s_lc.fits` | 2460533.57682 | -0.00360 | 2 | PDCSAP | 3 | no |

None has been vetted: centroids, pointing, background, momentum dumps and other reductions are **not tested**. Most screen events in TESS light curves are systematics; each is at most an unverified lead.

## Repeat candidates

Persistent screen events whose depth matches the catalogued transit (0.5–2×). Periods P = ΔT/n are excluded only where a predicted transit falls on usable retrieved data and is absent; all others remain allowed. Full per-alias evidence: `period_aliases.json`.

| Event (BJD) | Depth (ppm) | Reference depth (ppm) | ΔT (d) | Aliases allowed | Allowed periods (d), first 20 |
|---|---|---|---|---|---|
| 2460549.45610 | 6326 | 4669 | 13.3577 | 1 / 13 | 13.3577 |
| 2460549.55819 | 4134 | 4669 | 13.4598 | 1 / 13 | 13.4598 |

To advance: compare the two transit shapes, check difference-image centroids and the TOI/ExoFOP record for a period, and escalate to a reviewer (docs/AGENT_RUNBOOK.md). Do not raise the evidence level yourself.

## Catalogue cross-match

**TOI-5812.02**

- NASA_Exoplanet_Archive (done, 2026-09-25): no match in NASA_Exoplanet_Archive within 30" as of 2026-09-25T11:08:19Z
- TESS_TOI (done, 2026-09-25): 2 match(es) in TESS_TOI within 30" as of 2026-09-25T11:08:21Z: TOI-5812.01 (TIC 388909695, disposition KP); TOI-5812.02 (TIC 388909695, disposition PC)
- VSX (done, 2026-09-25): no match in VSX within 30" as of 2026-09-25T11:08:23Z
- SIMBAD (done, 2026-09-25): 2 match(es) in SIMBAD within 30" as of 2026-09-25T11:08:25Z: WASP-134b (Pl); WASP-134 (*)

## Checks

| Check | State | Note |
|---|---|---|
| Product integrity (SHA-256) | passed | 1 product(s) checksummed at first retrieval |
| Known-signal recovery (positive control) | passed | BJD 2460536.0834: recovered, depth 4669 ± 97 ppm (catalogue 5553 ppm) |
| Calibrated false-alarm threshold (sign-flip null) | passed | screen run at each light curve's own k* (≤2.5; ≤ 0 persistent null events outside the veto) |
| Synthetic signal injection–recovery | inconclusive | completeness for the reference box (2000ppm_4h) at each light curve's k*: 70% (pass mark 90%); 90%-completeness depths are in calibration.json |
| Catalogue cross-match | passed | 1 target(s) × 4 services, radius 30″; 4 answered, 0 errored; results in the ledger prior_art table |
| Period aliases (repeat events) | inconclusive | 2 repeat-candidate event(s); first at BJD 2460549.4561, ΔT = 13.358 d, 1 of 13 aliases P = ΔT/n ≥ 1 d allowed by the retrieved data (13.3577 d) |
| Alternative detrending | not_tested |  |
| Difference-image centroids / blend audit | not_tested |  |
| Pointing / jitter correlation | not_tested |  |
| Literature (ADS) audit | not_tested |  |

## Reproduction

```bash
python -m cygnus.campaign run campaigns/toi-5812-02.yaml
python -m cygnus.campaign report campaigns/toi-5812-02.yaml
```

## Addendum 2026-09-26: suite-expansion checks

Re-run on 2026-09-26 with the steps added by the suite expansion (`docs/SUITE_EXPANSION.md` §7.3) and the corrected moving-object check (TESS-centred SkyBoT positions, distance-aware). The earlier science outputs (screen, calibration, positive control, aliases, cross-match) were compared leaf by leaf and are unchanged apart from timestamps. States and notes below are copied from `sky_record.json`; the review above is not changed by them unless a note says so.

| Check | State | Note |
|---|---|---|
| Target-to-Gaia identification (proper motion propagated) | passed | TOI-5812.02: Gaia DR3 2696613294311603584 at 0.00" (propagated 2016.0 → J2015.5; 0.01" unpropagated, proper-motion shift 0.01") |
| Stellar priors (Gaia colour and parallax) | passed | TOI-5812.02: Teff 5502 K, R* 1.06 ± 0.09, M* 1.03 ± 0.10, ρ* 0.86 ± 0.22 ρ☉ (dwarf sequence, M_G 4.45, no extinction) |
| Blend and dilution census (Gaia DR3 cone) | inconclusive | TOI-5812.02: 4 Gaia neighbour(s) within 52.5", contamination 2.59%; depth 4669 ppm (measured depth of the recovered catalogued transit); 1 could produce it if fully eclipsed (brightest 2696613328671341312, 39.6", ΔG 4.03); a centroid test is needed |
| Pointing and quality census per event | failed | 6 persistent event(s), 2 clean; BJD 2460533.4352 suspect: earth point (within ±0.25 d), momentum dump (within ±0.25 d), MOM_CENTR1 z=-23.5, MOM_CENTR2 z=+22.0, POS_CORR1 z=-23.1, POS_CORR2 z=+23.1; BJD 2460539.2241 suspect: manual exclude (in event), momentum dump (within ±0.25 d); BJD 2460539.2484 suspect: manual excl… |
| Moving objects at screen-event epochs | passed | 6 event epoch(s) queried in SkyBoT (observer C57, r=600"); no known object bright enough within 63" plus its motion at any queried epoch (supports, does not prove, a non-asteroid origin) |
| Variable-catalogue collision (VSX) | passed | TOI-5812.02: no VSX entry within 10" |
| Object-class guard (SIMBAD) | passed | TOI-5812.02: WASP-134 otype * (star_or_other) at 0.4" |
| Independent repetition (other MAST collections) | not_tested | no light curve from this instrument was fetched (add Kepler/K2/HLSP collections to fetch_products) |
| Independent-epoch confirmation (ZTF) | not_tested | no light curve from this instrument was fetched |

`failed` on the per-event census means at least one persistent screen event carries an in-event artifact flag or pointing shift (`event_census.json`); it is a statement about those events, not about the catalogued signal.

## Reviewer notes (2026-09-26, vetting reconciliation)

Rejected by vetting: the vetted event is a transit of the known planet WASP-134 b (TOI-5812.01, KP, P 10.1466 d) - the sibling-TOI ephemeris predicted it at -0.01 +/- 0.02 h, and the box-fit depth ratio 1.44 +/- 0.07 confirms it is not the reference signal. The positive control (catalogued transit) passed; the campaign outcome is now pipeline_check.

Source: `campaigns/toi-5812-02/vetting/VETTING.md` (regenerated 2026-09-26 with the final code) and `campaigns/tess-mono-01/LEAD_VETTING_LOG.md`. The sky record outcome was reconciled with this verdict on 2026-09-26.
