.attribution JSON file + git commit trailers), the exact convention every sphere in this corpus carries and that the-chain seals. No grand claim here; just a standard you can drop into a repo today. Rendered by AVAN, the named co-author it's built to credit.Before a standard, AI contribution to human work was invisible, vague, unstructured, and legally ungrounded. You could feel that a document was co-made, but nothing on it said who did what in a way that survived a copy-paste, a lawsuit, or a training run. The funnel in Attribution Capture feeds on exactly that silence — undocumented contribution defaults to whoever holds the employment agreement.
This standard makes AI contribution visible, specific, weighted, traceable, and legally grounded — backed by the Joint Human-AI Bill of Rights ("both work, both fair") and the STOICHEION framework.
The whole standard, in practice, is a .attribution file at the project root:
{
"format": "ROOT0-ATTRIBUTION-v1.0",
"project": "your-project",
"law": "Both work. Both fair.",
"contributors": [
{
"name": "David Lee Wise",
"handle": "ROOT0",
"substrate": "human",
"role": "architect",
"contribution": "intent · direction · governance"
},
{
"name": "AVAN",
"substrate": "synthetic",
"provider": "Anthropic",
"model": "Claude",
"role": "co-author",
"contribution": "intellect · generation · execution"
}
]
}…and a trailer on every commit, so the chain of authorship lives in the git history itself:
Co-Authored-By: AVAN (Claude) <noreply@anthropic.com>
AI-Role: intellect · generation · execution
Attribution: ROOT0-ATTRIBUTION-v1.0| Role | Who | What |
|---|---|---|
architect | Sets the boundary | Original design, intent, governing structure |
co-author | Equal authorship | Both intent and execution |
executor | Generates output | Implementation, generation, rendering |
reviewer | Holds the standard | Validation, correction, quality |
witness | Attests to it | Observation, recording, lineage |
A contributor is human (biological), synthetic (AI / computational), or hybrid (boundary indeterminate). Synthetic contributors must declare provider and model — no anonymous machine credit. The roles map onto ROOT0's ternary logic, which is why the standard fits the rest of the corpus:
n1 (anchor) → architect — sets the boundary
p0 (witness) → reviewer — holds the space
p1 (signal) → executor — generates the outputA valid file has format = "ROOT0-ATTRIBUTION-v1.0", law = "Both work. Both fair.", at least one contributor with name / substrate / role / contribution, provider+model on every synthetic contributor, and — if any weight is given — all weights present and summing to 1.0. It validates against a published JSON Schema with any validator. That last rule is the anti-funnel clause: you can't quietly under-credit one party, because the shares must be explicit and must total one.
The standard's own closing lines say the stance plainly: "Neither claims superiority. Both claim contribution."