Check a curve's fit prototype

The journey's Goal is to know whether a candidate still stands on the quotes it was built from and whether its forwards and dates make sense; the person reads and diagnoses and does not publish. It leaves open how those readings share one screen: the candidate and the quotes are two separate reads, keyed differently — the quote by an oresmd_uri, the candidate by a point_id — so the screen must place them side by side and say what each distance means. An unjoined quote read as a zero would invent a market the person never had; a forward step read as a confirmed fault would claim a check that never ran. The page is written against both: an unmatched quote is a gap, and a forward finding is marked as one no operation serves.

Switch with the Show buttons in the bottom bar, or ?variant. The variant is the presentation, which the journey records as the central design question.

The variants disagree about the reading, not colour: A reads a distance, B a shape, C both. Every variant carries the candidate header, the calendar and roll panel and the inert read controls, so they differ only in the middle.

Switch with the Market buttons, or ?state — the mock market the screen reads against.

The residual threshold is the argument in one cell. The page draws 2 bp as the line between within and too large. In gap the reading is unmatched and never zero: an absent candidate point is not a candidate of zero.

The bottom bar switches the variant and the market, and the page answers to ?variant and ?state, so any combination is a URL. Read candidate and Recompute candidate neither read nor compute: each rewrites the strip at the top with the missing subject it names, and changes nothing else.

Everything. The USD OIS candidate, its nine pillars, the quotes, the forwards, the roll convention and the resolved dates are constants in the page. There is no server, no session and no build step, and nothing is published or stored. The residual, the relative residual and the reading are computed on the page from the two mock lists, because no diagnostics operation serves a residual; the forward step is hard-coded and labelled unchecked; the dates are mock and labelled derived. The oresmd URL editor's plumbing — the iframe to ../oresmd-url-editor/index.html — is carried but unreachable.

doc/prototypes/market_data/check-a-curves-fit/. One file, index.html, holding its markup, styles and script, with a plotting helper PC in the same file, and no framework and no build step; there is no prototype.css and no prototype.js. The site copies the directory as it stands through ores-deploy-web-app and adds nothing to it.

The group accepted the argument rather than one variant: a curve is checked against the quotes it came from, and the residuals, the forward smoothness and the roll logic belong on one screen in that order. It accepted the readings the page insists on — an unjoined quote is a gap not a zero, a forward step is drawn and marked unchecked, and a resolved date is labelled as derived because no point stores it.

What stayed on the page as the record: the three variants, kept because the argument must hold whether the person reads a distance or a shape; the three states beside them; the residual plot the page computes itself; and the inert read controls. No Gemini review was raised.

The diagnostics payload. The screen derives the residual from the two reads it already has. Whether a residual arrives as its own subject or as a per-pillar field on the compute reply, and whether the engine's own distance is the one to show, is open.

The health checker and the join. A checker that flags a forward step exists and nothing calls it; the quote and the candidate cannot be read together, so the page matches them on the coordinate. Whether a forward finding is a subject or a findings field, and whether an overlay read returns both together, is open.

The as-of read, the tolerance and surfaces. The candidate is read at now, so the page cannot show it as built; the 2 bp line between a sound residual and a large one is mock; the screen is for curves only, so a surface fit is not checked here.