FLUX
Declare the universe. Prove the rule. Ship the contract that was proven.
Declarative
A governed synthetic customer universe is nineteen small YAML documents, not a codebase. Adding a vertical or a rule is a configuration change, validated by one JSON Schema.
Deterministic
Every run is a pure function of a seed — byte-for-byte replayable, golden-regression anchored, with stochastic sweeps and agentic fidelity layered on top, never instead.
Governed
ConsentProfile, sovereignty, and agentPolicy are schema surfaces, not policy docs. Skills give every kind bounded, model-backed variation under an enforced budget.
The FLUID Seam
A Simulation emits streams by referencing the FLUID contract they are proven under — never restating it. What ships to production is byte-for-byte what the twin proved.
Offline Validation
Schema plus reference validator resolve every reference, check every sum and set, and validate the seam against vendored FLUID schemas — no cloud, no running engine.
Open & Apache-2.0
Spec, schemas, validator, and examples in one repo, CI-enforced. Governance and versioning policies written down from day one.
FLUX discovers. FLUID delivers. The seam is where the risk goes to die.
FLUX describes synthetic customer universes: governed digital twins in which candidate rules and data products are discovered, stress-tested and proven before a single production system is touched — then shipped under the exact FLUID contract the twin proved.
The shape of a document
fluxVersion: "0.5.0"
kind: World
id: q3-retention-world
name: Q3 Retention World
metadata:
owner:
team: growth-lab
spec:
seed: 42
vertical: telco
population:
size: 25000
lifecycleMix: { new: 0.15, active: 0.55, atrisk: 0.20, churned: 0.10 }
markets: [mkt-a, mkt-b, mkt-c]
temperature: { engagement: 0.5, campaignResponse: 0.5 }
25,000 synthetic subscribers across three markets, one in five already at risk — declared, never coded.
Where to go next
- Guide — what FLUX is and a hands-on quickstart.
- Concepts — the two-spec substrate, the six families, the seam, and the three properties.
- Schema Reference — the envelope, all nineteen kinds, versions and changelog.
- Examples — the complete telco payment-recovery universe, all nineteen kinds green under CI.
- FLUID — the delivery-side contract standard this spec emits into.