Flow time variations
This is to specifically look at how we think about the time properties on Intent, Commitment, EconomicEvent. This is to try to sort out the discussions on using the time properties for quantities on schedule-based flows, or for deriving quantities in these situations.
i was thinking about a use case I have experience with, which I documented here https://github.com/valueflows/valueflows/blob/master/use-cases/buying-club.md.
Some possible implications for how we think about time on intents, commitments, events.
- There is something like an accounting period (an order cycle), which in many other cases is financial calendar based, but here based on the actual operational cycles (which are calendar based but not the usual). We have need for accounting period in the budgeting use case too, and I think should consider adding something like this. It might take the place of logging a whole month in the time property for 20 hours of work, in the facilitation example, which is also a real example.
- For the scheduled work, there are the equivalent of intents, commitments, and events. The number of hours could be derived from the calendar time worked, but I think it is just recorded as number of hours, where the commitment and intent schedules are carefully based on calendar times and are what is important for coordination. The quantity of hours isn't that important on the intents and commitments, although it probably helps people understand they are signing up for enough hours.
- For work at home, there aren't formal intents or commitments, people manage that themselves, and generally have the same role for a long time. A finish date is recorded for coordination. The time is recorded for accounting. But of course those could and would be combined in VF. So it would be quantity of hours worked, and finish date.
Generally, I think this and other use cases bear out that we want to keep time for scheduling/availability and coordination. Quantities would be used for accounting and exchange, also analysis. (If some agent wants to derive quantities from times internally, that of course is their choice, but the vocabulary would reflect that derived quantity just like any other quantity.)
And also that we need to be flexible on how people think of the times in flows, as there are a variety of needs. Especially for unscheduled activities or wherever close coordination is not required, often just a date is plenty, and sometimes that is just the finish date. In these cases, the time is for reference and can be loose. Where for close coordination, often an accurate duration is needed (at least for usage and work).