Thank you for your detailed thoughts.
It is true, that managing field update procedure is tricky.
This is where UPlanet Geokeys and “email” tags signatures and crypto coins are useful.
the more a Tiddler gets “email tags”, the more it is considered trustful.
Each TW (associated to an email) benefits from a relative “Web Of Trust”.
And is included in a SECTOR that is get all Tiddlers with > 3 signatures.
it receives “Externals” from “SectorTW”
A Tiddler can be shared “1 by 1” in different sectors.
When a 4th signature is collected, corresponding SECTOR will get it, so this Tid is spread to all “in area TWs”. Then all signers get paid by the last one (Zen is the crypto coin).
In this scenario,
- an external Tiddler overwrites local (with all fields)
only if “external_signatures_nb” > "local_signatures_nb
and if TW wallet have enough to pay "external_signatures_nb “Zen”(0.1 Ğ1)
For now, adding [days[-1]] to filters can do the trick, so UX works in a “day by day” usage.
It will have more complex fusion algorithm later.
But using “Coin” and “WoT” will ease things
About UPPERCASE title, as TW is engaged in such an automatic “blockchain process”.
This was introduced to give user a way to avoid treatments. It is also matching “net ethic” as it is considered as SHOUTING 
I consider it not so klugey.
I am glad I received already so useful help, I want to thank you.
I am sad my “TW programming skills” are still bad…
So I opened the side project to make assistant collecting TiddlyWiki PDF documentation to create a “privateGPT” for TW. This research and service is also part of “UPlanet REGIONS” data handlers (more than 144 signatures would be difficult to deal with TW alone).