Refuted

Gaia Gator source sets agree; exact native astrometry fails

4 Oct 2026 · embeddings

Imported record: produced before this platform existed

Question

Does public Gator preserve the first fresh cone source set and native Gaia values?

Hypothesis

One maximum2MiB GET; compare every29-field scalar/null/ID to saved ESA at native precision without changing selection or matching.

Test

Original11 controls; metadata-only unit-null amendment15 controls, independent BINARY2 amendment10 controls. Original producer/text-only reader failures preserved. Manual ESA decoding agrees with Astropy on1537 values/nulls.

Finding

HTTP200 in3.038seconds,69729bytes,53 IDs equal ESA, no null-state mismatches.923/1537 native scalars disagree in23 float fields due to Gator rounding. Exact-value reviewer exits1;74 bindings sealed; no reviewed Gator/class/physical adoption.

Next: Reuse native ESA first cone and separately register only the remaining three BINARY2 requests, manual/Astropy scalar checks and failure/unknown accounting before epoch/frame/covariance/ambiguity matching.

Caveat · addressed_unverified

RA/Dec discrepancy<5e-12deg; motion rounding<0.0005mas/yr and correlation rounding<5e-5. These scales do not authorize tolerance relaxation. Native ESA XML has7685binary bytes/296null bits; E103 separate FITS and other-cone completeness remain incomplete.