Forking

What a fork is

A fork is a remix: you take any public Coil, copy its manifest into your Den, and make it yours — reweight holdings, swap assets, rewrite the thesis, tighten the fuses. The original stays untouched; your fork is a new Coil with its own slug, Coil Health, and receipts.

Lineage: forkOf

Every fork records its parent in the manifest's forkOf field — the slug of the Coil it was forked from. Lineage is permanent and public: viewers of your fork can walk back to the original, and the original's creator gets credit for every downstream remix.

{
  "slug": "mag7-momentum-low-dd-fork",
  "name": "Mag 7 Momentum, Softer Landing",
  "forkOf": "mag7-momentum",
  "...": "rest of the manifest"
}

Reweighting

A fork starts as an exact copy. Any change is allowed as long as the result still validates: weights sum to exactly 10,000 bps, every asset is canonical, and the risk block is complete. A common pattern is keeping the parent's holdings and shifting 1,000–2,000 bps toward ballast (SGOV, USDG) to trade upside for drawdown — a different Venom level on the same thesis.

Citing the original

Fork pages and share cards display the parent’s name and creator automatically. Etiquette is simple: don’t strip a thesis and pass it off as new work — the lineage field will out you anyway. Say what you changed and why.

Why forks matter

Fork lineage is the social proof of the whole system: being forked is the strongest signal a thesis resonated — the fork button is the like button. Forks also compound the public record: every fork carries parentManifestHash in its receipts, so a Coil’s trace shows exactly how an idea evolved and who improved what.