rolonic advantage

One of the drivers behind using Rolonic theory for programming is its completeness. In rolonics, everything is a journal, ledger, descriptor or classifier. And everything is a rolon. So there is only so much to be implemented to achieve completeness. With incomplete systems, you are always inventing artifacts to serve special needs because programming theory is so incomplete. This especially applies when dealing with time.

I woke up this morning thinking that, with journals being first-class user objects, we no longer need login events. Journals/transactions ARE events in time. Then I realized that I've created a bunch of special case attributes on transactions where I should have just had classifiers and perhaps even tags. Gotta go back and clean that up.

Finally it occurred to me that a tag match which matches a transaction could be the basis for event programming, the newly created transaction then triggering some activity in the role to which it matches.

Rolonics is so very simple and so universally applicable that its hard to see it sometimes. I've always said that the obvious takes longer.

Bill