Governed before it's generated
Synthetic Data planned
There is no generator yet. What is already built is the governance that would force any synthetic data to land proposed — never validated reference data.
What it does
EvalGlass does not ship a synthetic-data generator. When you ask, connect --synth tells you that plainly — it is governance-only. The reason the governance exists first is the whole point: if a generator is ever added, generated data is imported through a path that forces its status to proposed regardless of what the data claims, so it can never masquerade as the validated reference data a metric needs to gate. The discipline ships before the convenience.
Say this to your agent
How would EvalGlass handle synthetic reference data for my app?
Your agent answers honestly: no generator today, and the rule that keeps any future one from manufacturing reference data.
Generated data is never validated reference data.
The generator isn't built — and that's stated, not hidden. What is built is the rule that protects you when it lands: connect --synth is governance-only today, and the import path forces any synthetic data to proposed, so it can never enter as validated reference data (ADR 0025). How governance works →
In the docs