Skip to content

StoredPlate

Defined in: plate.ts:192

The committed plates/<name>.json shape (ADR 0022): the whole Plate already projected in the browser (the in-browser Serialize folds emit + the multi-View gating + classify in one session), so disk holds ONE gated, content-addressed tree + css rather than per-View captures assembled at load. It is a GatedPlate (the structural {tree, css} serializePlate consumes) PLUS the breakpoints the HUD coverage reads — the analysis-only geometry never crosses the wire (ADR 0021). The gen-side runs serializePlate(stored) → Plate (chunks) at module-load, leaving the Tailwind/Bundle passthrough a clean gen-side seam.

  • GatedPlate

breakpoints: number[]

Defined in: plate.ts:197

Width thresholds (view boundaries), pruned to the plate’s OBSERVABLE differences (ADR 0029); the HUD coverage derives its bands from these.


css: string

Defined in: plate.ts:91

GatedPlate.css


name: string

Defined in: plate.ts:89

GatedPlate.name


optional spans?: Span[]

Defined in: plate.ts:204

The bands actually CAPTURED (each surviving island’s range, folded runs merged — ADR 0029). A partial browse session stores only the bands it touched; coverage reads these instead of assuming every band complete. Absent on plates written before the field existed — readers fall back to the historical complete-coverage assumption until a re-capture.


tree: RenderNode | null

Defined in: plate.ts:90

GatedPlate.tree


v: number

Defined in: plate.ts:88

GatedPlate.v