Level 1 of 1 so far — the flow as a black box. Pick a trigger to see what comes out.
Strip away every detail and the flow is one machine: a trigger arrives naming a site and a time pin, and the service freezes that site’s billing inputs for that month into two files in S3.
Downstream invoice calculation reads this frozen pair. Freezing first means the bill is computed against a fixed picture of the site’s rules and transactions, not against data that keeps changing.
create_billing_snapshots.feature — feature description + the trigger/output shape shared by all scenarios. Nothing below this level of detail is shown yet.