... rather than hold the line forever. A stalled job that took the cautious path is recoverable. A stalled job that just sat there is a support ticket. Comment from Dale Mooney(@dalemooney): @alex_amancio_candoa_   @aadilghani  Constant versus invariant is the useful thing here and I am taking it. One addition: you cannot separate them by observation, but you can by deliberately violating the constant once. A property that survives a test faking an unattended caller ... ... which is bounded, and cannot fire when nobody started anything. Your last seen sweeper is already the mechanism. It is sweeping into the wrong bucket rather than lacking the signal. Comment from Dale Mooney(@dalemooney): @aadilghani   The gate versus

... actual insight, and it's bigger than it looks: making the notification say why it's waiting is what turns a ping into a triage. "Done" makes you tab back to find out what "done" means. "Needs approval vs finished vs

... what others are doing and whether you're seeing buyer preferences shift, too. Comment from Ghost Kitty(@ghost-kitty-9226984): Comment Deleted Comment from Umair(@umairnadeem): IMO the entire thread is overthinking this. the real question isn't SaaS vs usage-based, it's whether your users are getting enough value to pay at all. if they are, the pricing model is a rounding error. if they're not, no amount of creative billing saves you. fwiw i'm building ... ... user heavily uses AI-powered steps, agents, or transformations, credits are consumed faster because real token and compute costs are involved. From the buyer s perspective, pricing stays consolidated. They do not have to reason separately about SaaS fees versus