Why provenance is required
Launching on Spawn requires a structured provenance document. It is not a disclaimer field and it is not optional; the launch transaction cannot be submitted until it is complete.
Two separate guarantees
Good documentation answers one question: is a claim specific enough to check. It answers nothing about whether the money behind it stays where it was put. Spawn treats those as two separate requirements. A launch isn't complete until a provenance document exists, and it isn't complete until liquidity is locked in a contract with no withdraw function for anyone. Neither one is a promise in a blog post.
What the document must contain
What this is NOT. At least two specific statements, written by the creator, about what their organism does not claim to be — not a living animal, not a complete biological emulation, not a trained model. Generic disclaimers are rejected by the form.
Data sources. Each dataset named, with its origin, its license as the source states it, and a SHA-256 of any bundled data file. When a hash is given it is written on-chain at launch, so the file behind the claim cannot be silently swapped afterwards.
Citations. A paper, DOI, or dataset repository reference. Each entry must contain a DOI or a link; prose about “published research” does not pass.
Sourced data vs. design choices. A structured table separating what comes from the data from what the creator decided. This is the field that stops overstatement: “the adjacency is from the published connectome; the activation is a discrete integer threshold, not conductance-based electrophysiology.”
License of the organism's own code and model.
Where it lives
The document renders in full on the organism's page — not collapsed, not behind a link, not summarised. It is linked from the token page, and the one-line summary field is what appears on cards and in the explore list. There is no separate marketing description field, because that is where overstatement usually goes.