-
Notifications
You must be signed in to change notification settings - Fork 129
Description
simplicity <-> profit scaling
: #1875 (comment)
As I mentioned that generally devs have to decide where on the scale of simplicity <-> profit scaling they want to sit.
We could illustrate it here by adding a competing example where the ai-analysis would be instead ai-analysis-$0.01 (or $0.001) (and better name :) ) and it would charge one event per cent that is spent on the LLM. This way we already do it in some places like our OpenRouter.
This would clearly ilustrate the trade-off that it is harder for user to predict but safer for dev to scale. I don't think we should prescribe one way or another.
- How to do it correctly? Add another example?
PPE vs PPR: #1875 (comment)
We should definitely have a section to encourage PPE vs PPR. The main thing is that PPR cannot charge for actor-start so it leads to more potential of profit-breaking 0 result runs.
- Where we should put it?
Legacy tag: #1875 (comment)
If we are saying here that something is to become Legacy I would expect a proper timeline. If we don't know the timeline yet I would remove mentiong of making it legacy and focus on this model being not compatibile with AI/MCP. The way it is framed right not I expect that it becoming legacy is somewhere in the future, not now.
- Let's add it with better message, and timeline.