What changes the decision?
Explicit rules make rare cases intentional, but teams must maintain the model. A natural-language authoring interface can help define data, yet its output still needs a business oracle. A seed alone does not prove repeatability across clocks, dependencies or exporters.
What should your proof of concept show?
Model an approved payment, a declined payment and an idempotent reversal. Assert which rows should exist and which should not. Freeze source inputs, runtime dependencies and clock before comparing any generated artifacts.