Files
heartwood/crates
Yorgos SaslisandAdrian Duke df62b66d9d cob: Keep only the root's applied descendants in a history
Loading a collaborative object kept every entry reachable from its
refs, also entries that do not descend from the root. They were never
applied, but they were tips, so the next honest update used them as
parents. **Any user could thus make a delegate's change to one object
also apply to another**, or publish an entry with parents as the root
of a new object.

To address this, evaluation now follows three rules:
1. The root has no COB parents, or the object does not load.
2. Only entries that descend from the root are kept; every other entry is
removed together with the entries built on it.
3. An entry is applied only when every one of its COB parents was
applied. After evaluation, only applied entries remain, so new entries
build on the applied tips only.

A COB parent is a git parent other than the identity revision named by
`Rad-Resource` and the code commits named by `Rad-Related`. Honest
clients write a root without COB parents and build every entry on the
object's own tips, so honest histories evaluate as before.

Co-authored-by: Adrian Duke <adrian.duke@gmail.com>
2026-11-06 18:13:51 +01:00
..
2026-10-23 20:17:44 +02:00