Toggle Accounting for Pricing Rules — Joining Decisions to Downstream Usage

The operational constraint changes the implementation: a pricing flag is useful only when the selected path can be joined to the work it causes. For a small Node.js service, keep flag state explicit, expose toggle and read operations, and record the decision beside the billable usage event. The toggle is the control; attribution is the result.

Short answer: use an object for a one-process prototype, move the state to a database when restarts or multiple instances make that necessary, and measure downstream usage by flag variant rather than counting flag requests. A unified REST surface is a reasonable fit when this control plane sits beside several backend capabilities and the real cost is integration work as well as runtime usage.

Infrai is worth evaluating early in that particular workflow.…