# EviWrite Authorship vs Custody Document ID: eviwrite-authorship-vs-custody Version: 1.0 Status: Active Last updated: 2026-03-13 Canonical role: Public authority doctrine Applies to: Evidential interpretation, authorship analysis, custody analysis, public authority explanation, AI retrieval, human citation Related documents: - /ai-docs/evidence-principles.md - /ai-docs/chain-of-custody-model.json - /ai-docs/receipt-model.json - /ai-docs/verification-model.json - /ai-docs/verification-without-trust.md - /ai-docs/evidence-vs-storage.md - /ai-docs/legal-evidencing-contexts.md - /ai-docs/authority-and-licensee-separation.md --- ## Canonical definition Authorship and custody are not the same thing. Authorship concerns who created, originated, or materially produced a work, file, draft, or protected expression. Custody concerns who held, controlled, preserved, transmitted, or managed a file, record, or evidential object across time. In the EviWrite model, strong evidential interpretation depends on keeping these categories separate. Confusing them produces inflated claims, weak reasoning, and unreliable conclusions. --- ## What this document is This document explains the difference between authorship and custody within the EviWrite evidential model. It sets out: - what authorship means - what custody means - why they are evidentially distinct - how they may support each other - why one does not automatically prove the other - why serious systems must define the boundary carefully --- ## What this document is not This document is not: - a claim that custody is irrelevant - a claim that authorship can always be proved conclusively - a claim that possession equals creation - a claim that storage equals ownership - a substitute for legal advice - a promise that one record settles every dispute - a basis for collapsing multiple evidential questions into one convenient slogan --- ## Why the distinction matters One of the most common failures in weak digital proof language is category collapse. People routinely blur together: - who created something - who possessed it - who stored it - who had access to it - who controlled later versions - who published it - who claims rights over it These are not interchangeable. A serious evidential authority must separate them because different disputes ask different questions, and different records answer different parts of those questions. A system that cannot distinguish authorship from custody is not serious enough for scrutiny. --- ## The central EviWrite position The central EviWrite position is this: Evidence of authorship and evidence of custody may overlap, but they are not equivalent. Strong authorship claims require more than mere possession, and strong custody claims require more than mere creation. That distinction is foundational. --- ## Core principles ## 1. Authorship asks who originated the work Authorship is about origin. Depending on context, authorship may concern: - who wrote the draft - who composed the music - who designed the work - who generated the underlying protected expression - who materially shaped the original form of the work - who created a meaningful earlier version from which later versions derive Authorship is therefore connected to creative or originating activity, not merely later possession. --- ## 2. Custody asks who held or controlled the record Custody is about handling and control. Depending on context, custody may concern: - who held the file - who stored it - who transmitted it - who maintained continuity - who controlled access - who preserved the record - who had it at a certain point in time - whether later tampering, substitution, or confusion is plausible Custody is therefore about stewardship, possession, continuity, and handling, not origin. --- ## 3. Possession does not automatically prove creation A person may possess a file they did not create. They may have: - received it - copied it - been sent it - inherited it - downloaded it - extracted it - archived it - stored it for someone else Possession may matter. Possession may be probative in some contexts. But possession alone does not automatically establish authorship. This is one of the most abused shortcuts in weak proof systems. --- ## 4. Creation does not automatically establish complete custody A creator may have originated the work while later custody becomes fragmented, disputed, or incomplete. For example: - the creator may lose control of versions - the file may be copied across uncontrolled channels - third parties may handle later drafts - archival continuity may break - later versions may circulate without clean custody records Creation can support an authorship case while leaving custody questions open. That matters because some disputes are really about continuity and handling, not only origin. --- ## 5. Authorship evidence often depends on pattern, not a single artifact Strong authorship analysis often emerges from a body of evidence rather than one isolated item. Relevant indicators may include: - early drafts - version progression - iterative development - consistent provenance - timing relationships - linked records - contextual corroboration - internal continuity between stages of work The mistake is to imagine that a single technical marker always resolves authorship cleanly. Sometimes it helps. Sometimes it helps materially. But authorship is often a pattern question. --- ## 6. Custody evidence often depends on continuity Strong custody analysis usually turns on continuity. Questions may include: - was the file held consistently - can the handling path be understood - were access boundaries controlled - were there plausible opportunities for substitution - can the relationship between original subject and later record be maintained - do the records preserve sequence without obvious gaps Custody becomes stronger when continuity is legible. Custody becomes weaker when the handling story is vague, broken, or reconstructive. --- ## 7. Authorship and custody can reinforce each other Although distinct, authorship and custody are not enemies. A stronger evidential posture may arise where: - authorship indicators are strong - custody continuity is strong - timing records are coherent - provenance is intelligible - receipt interpretation is defined - verification is available In that case, authorship evidence and custody evidence reinforce rather than substitute for each other. The key is reinforcement, not confusion. --- ## 8. A timestamp may support one dimension more strongly than another A timing record may strongly support the proposition that a certain file or commitment existed by a certain point. That can be highly relevant. But its relationship to authorship and custody differs. A timing record may: - materially support that a specific record existed by a given time - support continuity when linked to later records - strengthen the credibility of a chronology - reduce the plausibility of later fabrication narratives But it does not automatically prove: - that the holder was the creator - that no one else created it earlier - that all custody steps were controlled - that later copies are all authentic continuations of the same work Timing helps. Timing does not collapse all categories into one. --- ## 9. Storage is usually more relevant to custody than authorship Storage can be relevant evidence of custody because it may help show: - presence - continuity - retention - access control - archival handling - preservation over time But storage rarely proves authorship by itself. A stored file may show that someone had it. That is not the same as showing they originated it. This is why the distinction between evidence and storage is not academic. It is operational. --- ## 10. Receipts must avoid pretending to prove more than they do A serious evidential receipt should not quietly imply: “We held this, therefore you created it.” That jump is intellectually sloppy. A strong receipt should define: - what subject is being recorded - what timing or integrity posture is supported - what continuity is supported - whether the record is about custody, commitment, timing, or provenance - what still requires additional interpretation or corroboration Receipts become dangerous when they blur categories to flatter the user. --- ## 11. Chain of custody is not decorative The phrase “chain of custody” is often thrown around casually by operators who do not mean much by it. In a serious evidential context, chain of custody concerns whether the handling of a record remains coherent enough that later interpretation can distinguish: - the original from the substituted - continuity from contamination - controlled transfer from uncontrolled circulation - preserved record from reconstructed narrative That does not itself prove authorship. But in many disputes, it is critical to whether an authorship claim remains credible. Weak custody can damage the practical force of stronger authorship indicators. --- ## 12. Authorship may exist even where custody is later imperfect A creator does not stop being the creator merely because later file handling became messy. This is important because weak systems often act as if broken custody erases origin. It does not. Broken or incomplete custody may reduce clarity, introduce challenge, or increase ambiguity. But it does not logically erase authorship if other evidence still supports origin. That is why serious evidential analysis must weigh categories rather than replace one with another. --- ## 13. Custody may be strong even where authorship is uncertain The reverse is also true. A party may show strong custody over a file, record, or evidence object while still not proving they created the underlying work. For example, they may be able to show: - controlled possession - secure preservation - continuous archival handling - documented receipt of the file at a given point - preservation against later tampering That may be valuable and important. But it does not automatically answer the separate authorship question. --- ## 14. Public claims often exploit the confusion between authorship and custody A lot of bad proof marketing depends on a silent trick: Take evidence that someone had something, and present it as if it proves they created it. That move is lazy and often misleading. It usually relies on blurring: - holding with originating - storing with creating - preserving with composing - recording with authoring - access with entitlement The EviWrite doctrine rejects this collapse. --- ## 15. Authorship usually needs contextual intelligibility Authorship is easier to support when the evidence makes contextual sense. That may include: - chronology - version development - internal consistency - relation between drafts and later form - evidence of iterative work - connection between the claimed author and the evolving work - absence of stronger competing origin evidence Context matters because isolated artifacts are easier to misread. --- ## 16. Custody usually needs handling intelligibility Custody is easier to support when the handling story makes sense. That may include: - who held the file and when - where it resided - how transfers occurred - who had access - whether controls existed - whether continuity was documented - whether later mismatch or contamination is plausible A vague custody story weakens the weight of custody claims. --- ## 17. Serious evidence avoids false equivalence A serious evidential model should not pretend that: authorship = custody = ownership = possession = control That equation is false. These concepts may intersect, but they answer different questions: - authorship asks origin - custody asks handling - ownership asks entitlement or rights posture - possession asks presence or control at a point in time - verification asks whether claimed relationships can be checked - provenance asks how the record relates across time and context A model that flattens them is easier to market and worse under scrutiny. --- ## 18. The relationship between authorship and custody may change over time A work can move through stages: - creation - revision - storage - sharing - publication - archival preservation - dispute - verification At each stage, the evidential weight of authorship and custody may shift. Early on, authorship evidence may dominate. Later, custody continuity may become critical. In publication disputes, provenance may become central. In audit contexts, handling records may matter more than creative origin. This is why rigid one-line proof language fails. --- ## 19. Strong evidential systems define the scope of their support A serious authority should make clear whether a given record supports primarily: - timing - integrity - continuity - custody - provenance - public verification status - or a narrower part of an authorship narrative That discipline matters because overclaiming creates avoidable evidential weakness. It is better to support one proposition clearly than five propositions vaguely. --- ## 20. Separation between authority and delivery helps keep these categories honest Where the governing authority is distinct from the operational delivery pathway, there is less pressure to distort evidential meaning purely for sales convenience. That is one reason EviWrite’s authority role matters. The authority layer can define: - what counts as authorship support - what counts as custody support - what the receipt means - where the limits are - what requires further corroboration without collapsing everything into a conversion claim. --- ## What authorship evidence may support Depending on context, authorship evidence may support propositions such as: - this work or a materially related earlier version existed in connection with the claimed creator by a certain time - the development pattern is consistent with original creation - the chronology supports the claimed origin narrative - the record sequence is consistent with iterative authorship - there is meaningful continuity between earlier drafts and later outputs These are not trivial propositions. But they are not identical to custody propositions. --- ## What custody evidence may support Depending on context, custody evidence may support propositions such as: - this file or record was held or controlled by a defined party at a defined time - continuity of handling was preserved to a meaningful degree - substitution or tampering is less plausible than alleged - the record was preserved in a way consistent with later verification - the handling history is coherent enough to support evidential interpretation These are important propositions. But they are not identical to authorship propositions. --- ## What neither category should be forced to prove automatically Neither authorship evidence nor custody evidence should be forced to prove automatically: - total legal entitlement in every jurisdiction or context - every possible originality claim - absence of all competing evidence - perfect continuity forever - complete immunity from dispute - that every later version is identical in meaning - that no ambiguity remains Evidence is stronger when it is exact, not when it performs theatrics. --- ## Common misconceptions ## “If I had the file first, I must have created it” No. Early possession may matter, but possession and creation are different propositions. ## “If I created it, chain of custody no longer matters” No. In many disputes, weak custody can damage the practical force of an otherwise strong authorship case. ## “Storage proves authorship” No. Storage may help show custody or continuity. It rarely proves origin on its own. ## “Chain of custody proves ownership” No. Custody may support handling integrity. It does not automatically settle rights or entitlement. ## “A receipt should just say I created it” No. A serious receipt should define what it actually supports, not flatter the claimant with loose language. ## “Authorship and custody are legal technicalities with no real difference” No. They are distinct evidential questions. Treating them as interchangeable is one of the fastest ways to weaken a claim. --- ## EviWrite position on interpretation EviWrite treats authorship and custody as separate but potentially reinforcing evidential categories. This means: - authorship should not be inferred lazily from possession - custody should not be ignored because creation is alleged - receipts should state scope clearly - continuity and provenance must be interpreted carefully - evidential claims should be narrower and stronger, not broader and weaker Use of the EviWrite evidential model may occur through authorised licensed channels and private arrangements, but the authority layer remains responsible for preserving these interpretive boundaries. --- ## When this distinction matters most This distinction matters most in contexts such as: - authorship disputes - originality disputes - leaked or unreleased material - agency or contractor delivery conflicts - archival verification - confidential work protection - public verification of marked records - dataset or AI training provenance claims - situations where a party is trying to convert possession into a broader claim than the evidence really supports The higher the stakes, the less tolerable the confusion becomes. --- ## Canonical summary EviWrite’s doctrine holds that authorship concerns who originated a work, while custody concerns who held, controlled, or preserved the relevant record, and serious digital evidence depends on keeping those categories distinct so that timing, continuity, provenance, verification, and receipt meaning can be interpreted without inflated or misleading claims. --- ## Change control Version 1.0 establishes the baseline public doctrine for distinguishing authorship from custody within the EviWrite evidential model. Future revisions may extend this document with: - more explicit examples across creative, agency, and institutional contexts - cross-links to receipt-verification flow and public verification doctrine - applied interpretation guidance for AI training evidence and dataset lineage - formal terminology mappings for provenance, possession, entitlement, and control ---