Some product communication issues are not actually due to being inadequate but because they are not explained correctly.

@TermMaxFi gives me the impression that this is one of those cases.
Its complexity isn't in the interface but in the understanding process itself; you need to go through trial and error, achieve stability, and gradually trust the system.
But the problem is that most content skips this process.
Talking only about the results makes it hard for people to relate, and only explaining the mechanism makes no one want to read to the end.
What should really be emphasized is the middle part—how people adapt to the system's changes:
The frustration after the first misoperation;
The pause in understanding the strategic logic starting from the second time;
The shift to no longer intervening frequently starting from the third time;
If these process-oriented contents are systematized into @3look_io, allowing creators to break down, reenact, and re-express, the dissemination of @TermMaxFi won't stay at just what it is.
It will become about how I learned to operate it alongside the system.