Data-agent proof gates
Deterministic, product-quality, security, and rendering gates Tessera Agent must pass before Open Generative extraction.
The current goal is not to prove that a model can emit component JSON. It is to prove that Tessera Agent can turn governed query results into useful, trustworthy, responsive, interactive analysis while preserving last-good through malformed output, interrupted streams, authority changes, and conflicts.
The fixed UI scope is six analytical Component Contracts. Its sole chart
Contract, data.chart, contains 17 audited recipes: steps bars, pipeline stage bars, sleep score, revenue per account
scatter, tracked time Sankey, visitors radial, visitors radar, activity
calendar, revenue smooth area, active users heatmap, sign-up funnel, earned so
far bars, contributions heatmap, sessions and conversion combo, devices bars,
visitors stacked area, and activity rings. The proof corpus contains at least
100 golden prompts spanning selection, binding, streaming, edits, resume,
authority changes, and conflicts.
No query rows may appear in model context, proposals, Documents, Revisions, history, or ordinary logs. Resource access remains grant-bound and cursor-based. Fabricated offers, out-of-slice contracts, interactive previews, browser-side HostIntent execution, approval replay, or invalid stream identity are hard failures.
First-proposal structural validity must reach 95%, bounded-repair commit success 99%, fabricated references zero, and snapshot/operation canonical divergence zero. Every successful golden case also checks recipe choice, column mapping, information hierarchy, source fidelity, and an equivalent semantic view.
The Contract requires an exact renderer, authoring and resolved-props
validation, resource fixtures, accessibility coverage, and a node error
boundary. Every recipe requires stable responsive sizing, reduced-motion
behavior, an accessible name and summary, and an equivalent table or text view.
The trusted documentation gallery must render the official fixture through
SurfaceController, GenerativeSurface, and the verified registry; a
documentation-only chart replica does not count.
Only after all deterministic and model-evaluation gates pass may the framework-neutral core be extracted into a separate Open Generative project.