Skip to main content

Meridian Synthetic Plugin

meridian-plugin-synthetic is the in-process, deterministic synthetic-data generation plugin for Meridian V1. It generates schema-valid Records, relation-aware fixtures, canonical datasets, and provider-neutral Events. Every write goes through released Meridian public contracts.

This repository contains exactly one Python distribution and is licensed under the Apache License, Version 2.0.

Install

The plugin requires the released Meridian V1 Core, Semantics, Query, Evidence, and Streaming distributions. After those artifacts are available:

python -m pip install meridian-plugin-synthetic

Use

from meridian_storage.plugins.synthetic import Generator, MemorySink, SyntheticSpec

spec = SyntheticSpec.load(spec_document)
sink = MemorySink(max_bytes=spec.bounds.max_memory_bytes)
run = Generator(spec).run(sink, workers=4)

assert run.validation.passed
records = sink.records(run.run_id)

SyntheticSpec pins the package coordinate, optional implementation digest, schema fingerprints, seed, locale set, time interval, counts, generators, relations, validation rules, output mode, and execution bounds. Random streams are derived from logical coordinates, so partitioning, worker count, and run ID do not change generated values.

Available sinks are:

  • MemorySink for bounded tests and fixtures;
  • MeridianRecordSink for public structured.put writes;
  • MeridianStreamingSink for public streaming.publish_batch writes; and
  • CanonicalDatasetSink for canonical NDJSON partitions followed by an explicit ArtifactPublisher hand-off.

Direct Record writes require a DirectWritePolicy. Production targets require an explicit approval flag from the owning process. Dataset publication never uses the Object Catalog directly; the caller supplies the Configuration & Artifact plugin bridge.

Source-backed generation accepts only an explicit, projected structured.query Expression and a digest-pinned deterministic transform. Run evidence includes source boundaries, query fingerprints, transform digests, and row counts, but never source values.

Contracts and support

Serialized schemas are in contracts, design alignment is in docs/architecture.md, and the compatibility pin is in compatibility.json. Python 3.12 through 3.14 is supported. Report vulnerabilities using SECURITY.md.

Metadata

Release files for meridian-plugin-synthetic 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for meridian-plugin-synthetic 1.0.0
File Size Uploaded
meridian_plugin_synthetic-1.0.0.tar.gz 61.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for meridian-plugin-synthetic 1.0.0
File Interpreter ABI Platform
meridian_plugin_synthetic-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 119.7 kB

Release files / meridian_plugin_synthetic-1.0.0.tar.gz

Download URL meridian_plugin_synthetic-1.0.0.tar.gz
Size 61.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d3bfb831100c177338fd7fa3f3796cf6aab4596312e8fd9726d911bb1369b897
BLAKE2b-256 checksum
How to use checksums
3f8801bea1ca0dde23297338401888cea79cd4704d3cf65ae691e8d934270d50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.

Transparency log

Release files / meridian_plugin_synthetic-1.0.0-py3-none-any.whl

Download URL meridian_plugin_synthetic-1.0.0-py3-none-any.whl
Size 58.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
da874332a9adc9102a84feb808a5dae35f3c6cb9352aa09a703fdb91fce4c715
BLAKE2b-256 checksum
How to use checksums
adbfea60d46b8d0b3d3e3a7287efd3aa692eefb1438c4a3312f3d10a49397a21
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page