Plate archive · gapmap 0.1.0 · open source

Missing Sky

$UVSKY

A third of the first complete ultraviolet map of the sky is predicted, not observed. gapmap fills a map's gaps from layers it is related to, labels every pixel measured or predicted, checks itself on hidden measured sky, and looks for the faint circles that a person caught after two automated reviews missed them.

Plate 1 · simulated sky · two thirds measuredmeasured predicted

II

The plate

Drawers

A simulated sky (fictional, with its truth known) surveyed in circular footprints that avoid the bright plane. gapmap learns how the map relates to two complete layers where it is measured, and predicts the rest. Change the sky; every number below is recomputed here.

View through

III

Three checks

Drawers

You cannot score the gap: nothing was measured there. So hide part of the measured sky and score that. gapmap does it three ways. On a simulated sky the true error on the gap is known, so the checks can be checked.

This sky: median relative error

The evaluation: 30 fixed skies, block check against the true error on the gap

The evaluation, averaged over the 30 skies

Validation results
CheckMedian errorWithin 10%
Shown: evaluate() as computed when the site was built.

IV

The circles

Drawers

In the real map a person spotted faint circles in a dim field: single observations still carrying a little atmospheric glow. Two automated reviews had passed it. Such an artifact moves a whole footprint at once, so pixel checks miss it; it shows as a step at the footprint's edge.

Residuals: measured minus model. Rings: the twelve strongest edges.

A diagnostic, not a cure: in the evaluation the offsets follow the true glow but taking them out does not lower the error.

Footprint test evaluation
40 skiesResult

V

Accession record: $UVSKY

Drawers

Plate envelope · accession

Missing Sky — $UVSKY

Contract address

FZu9nxS72VUGqCzdezNbPNfbAduMpnoPfY3dUg8pump
Supply
1,000,000,000
Tax
0%
Site
v1.0

Observing log · live

Live figures
Price—
Market cap—
Volume, 24 h—
Liquidity—
Change, 24 h—

Awaiting the first exposure.

The plate is developing. The chart appears when it arrives.

$UVSKY · 1-second candlesOpen the chart

VI

Your own map

Drawers

Any grid with holes and at least one complete layer of the same size it is related to. CSV: one row per line, values separated by commas, NaN or nothing where nothing was measured. Everything stays in your browser.

VII

Circular

Drawers

Circular No. 1 · 14 October 2026 · gapmap 0.1.0

Labelled, Checked, and Still Wrong Sometimes: Honest Gap-Filling for Survey Maps

The gapmap contributors. Every figure below is computed by the library on this page.

  1. Summary.

    gapmap predicts the unmeasured part of a map from complete related layers, labels each pixel, and attaches an uncertainty to each prediction. On 30 fixed simulated skies its block check on measured sky gave a median relative error of 6.2%, against a true error on the gap of 6.6%: the check was optimistic on 23 of 30 skies. Its footprint test found a glow artifact on 40 of 40 skies and raised 3 false alarms on the same 40 without it.

  2. Background.

    On 8 October 2026 Anthropic published "The missing map of the sky", in which Brice Ménard, an astrophysicist at Johns Hopkins University and a researcher at Anthropic, describes the first complete map of the sky in ultraviolet light, made with Claude Science [2]. NASA's GALEX imaged about two thirds of the sky in some 38,000 observations between 2003 and 2013, avoiding the brightest regions, including the plane of the Milky Way; teams of AI agents gathered and cross-calibrated it with other surveys, and the missing third was predicted by inpainting from visible, infrared and radio data, with ultraviolet light from more than 100 million stars estimated from Gaia [2][3]. Every pixel is labelled measured or predicted, with uncertainty layers; predictions of hidden regions that did have data came within about 10% after several rounds [2]. Ménard noticed faint circles in a dim field, the footprints of single observations carrying leftover atmospheric glow, which two rounds of review by other agents had not caught [2][3].

    Not connected. gapmap, this site and $UVSKY have no connection with Anthropic, Johns Hopkins University, NASA, ESA or the author, and none of them has seen this circular. The sky on this page is simulated; it is not the real map.

  3. The model.

    A ridge regression of the map on second-order terms of the standardised layers, fitted on measured pixels; checked against an independent numpy solve on three skies (largest difference 1e-14). A predicted pixel's uncertainty is the block-check error times the square root of one plus its leverage.

  4. The checks.

    Block (12-pixel squares in five folds), random (scattered pixels) and gap-like (the fifth of measured sky most like the gap). The model uses no neighbouring pixels, so block and random agree; the gap-like check was meant to come closer to the truth and did so on only 11 of 30 skies.

  5. The footprint test.

    For each footprint, the residual step at its edge after a local plane takes out smooth gradients; the null is the same step on same-centre circles at 0.6 and 1.45 radii. The map-level test compares the roughness of the two (log variance ratio, one-sided, alpha 0.01). It found every injected glow, but its false-alarm rate was 7.5% at a nominal 1%, most likely because the normal approximation ignores how neighbouring steps depend on each other.

  6. Offsets.

    Fitting one offset per footprint with the model recovers the pattern (correlation 0.65 with the true glow) but taking the offsets out changed the median error on measured pixels from 7.0% to 7.2%, lower on only 16 of 40 skies: footprint-scale sky structure is partly mistaken for offset. In the real map the glow was fixed at its source [2].

  7. Limitations.

    The skies are fictional and generated by the same people who wrote the model, so they may suit it. The model knows only the layers it is given. The evaluation seeds were fixed in advance and run once; the library was developed on other seeds. The results above are not a statement about the real ultraviolet map.

  8. Use.

    Label every pixel. Report the gap's error as at least the check's error, and say which check. Look at the strongest footprint edges by eye before trusting any map stitched from footprints.

References

  1. gapmap 0.1.0, the library on this page (MIT).
  2. B. Ménard, "The missing map of the sky", Anthropic, 8 October 2026. anthropic.com
  3. G. Cuofano, "Claude Agents Map the Full UV Sky, Predicting a Third of It", FourWeekMBA, 10 October 2026. fourweekmba.com

VIII

Archive

Drawers

gapmap 0.1.0: one file, no dependencies, Node 18 and later and every modern browser. MIT licence. Every file of the repository is a plate in its envelope, with its SHA-256.

Downloads

Quick start

const G = require("./gapmap.js");
const map = G.makeMap(mapCsv, [layerCsv], ["infrared"]);
const f = G.fill(map);           // value, measured, sigma, cv
G.crossValidate(map, { scheme: "gaplike" });
G.footprintTest(map, G.parseFootprints(fpCsv).footprints);
node bin/gapmap.js simulate --glow 0.06 --dir sky
node bin/gapmap.js fill sky/map.csv --aux sky/optical.csv,sky/infrared.csv
node bin/gapmap.js eval            npm test

The catalogue: the API

Plates in their envelopes: the repository