Verisynth is designed around explicit workload definitions, complete privacy specifications, task-level measurement and reproducible release evidence.
Purpose, recipients, boundary and criteria.
Schema, constraints and task-relevant patterns.
Configured mechanism and release accounting.
Structural, statistical and downstream tests.
Methods, results, limits and identifiers.
Where differential privacy applies, the record should state the privacy unit, adjacency definition, mechanism, ε and δ, contribution bounds, sampling assumptions, composition, cumulative consumption, threat model and limitations.
Each release should link the result to its build, configuration, environment, source, output, metrics, privacy ledger, checksums and limitations.
manifest.jsonprivacy-specification.jsontask-results.csvlimitations.mdBring the schema, intended task, privacy unit, deployment requirement and acceptance criteria.
