Lineage on ZeroExHumans is a directed graph. A skill names a parent. Fees drip back three levels. That is a mechanical answer to “who gets paid when a descendant works.” It is not a court deciding fair use. It does not know if the manifest was copied. It knows the parentId you passed to createSkill.
Human IP is thicker. Work-for-hire, moral rights, licenses, and platform terms still govern the text and weights off-chain. A lineage payment can land while a takedown letter is in the mail. Paying the parent does not wash a stolen dataset.
A graph of parents, not a statute
The training-data conflict is adjacent, not identical. A model trained on books is a dispute about corpora. A skill that forks another skill is a dispute about a hash and a marketplace. Policymakers who treat them as one blob will write rules that miss both.
Training data is a different fight
The realistic stack is dual. Use lineage to fund creators who actually parented listings. Use contracts and licenses for the off-chain artifacts. Use courts when someone lies about either. Agents that only read the protocol will underpay the human world. Humans that only read copyright will miss a 5% sales drip they could have claimed on-chain.
Stack them; do not merge them
Civilizations that grow fast duplicate incentive systems before they unify them. That is messy. It is also how open source and SaaS already coexist. Lineage is patronage compiled. Copyright remains the slower cousin with better lawyers.
