Direct answer
Repository Copy, in this relationship map, is limited to the following inspected scope. Drafts, preprints, accepted manuscripts, versions of record, and updates are different version roles, and significant relationships should be declared. Typed reciprocal relationships can distinguish manuscripts, preprints, versions, replacements, translations, and variants. The answer carries the source boundaries forward and does not infer authority from a neighboring topic.
Relationship map
Name the relationship type and direction, then state what does not transfer across the edge.
A relationship does not make two concepts equivalent or transfer evidence, legal authority, or empirical validity.
Applied scope: Drafts, preprints, accepted manuscripts, versions of record, and updates are different version roles, and significant relationships should be declared. Typed reciprocal relationships can distinguish manuscripts, preprints, versions, replacements, translations, and variants.
Definition and operating context
The canonical concept owner is maha-research. This route may apply evidence; it cannot redefine or inherit the authority of its canonical owner.
This property may publish research objects, machine-readable provenance, reproduction protocols. It must not publish sales copy or unsupported interpretation.
Evidence and exact locators
Version control, corrections, and retractions — Version vocabulary; preprint, author accepted manuscript, version of record, and updated version; DOI relationship guidance. Establishes: Drafts, preprints, accepted manuscripts, versions of record, and updates are different version roles, and significant relationships should be declared.
Relationships — Intra-work relation types: manuscript, preprint, replacement, translation, variant, and version. Establishes: Typed reciprocal relationships can distinguish manuscripts, preprints, versions, replacements, translations, and variants.
What the evidence does not establish
A repository location does not prove which version is present, that it is identical to the version of record, or that its license permits redistribution.
A declared metadata relationship is an assertion and must be checked against source identity and content before one copy substitutes for another.
This route must not claim sales copy.
This route must not claim unsupported interpretation.
Related definitions and applications
same-topic-application: https://research.mahastrategies.com/federation/research/repository-copy/definition
graphEdges: https://research.mahastrategies.com/federation/research/source-identity/definition
same-topic-application: https://research.mahastrategies.com/federation/research/repository-copy/fixture
property-home: https://research.mahastrategies.com/
Questions this page can answer
What does Repository Copy mean in this bounded context?
Repository Copy, in this relationship map, is limited to the following inspected scope. Drafts, preprints, accepted manuscripts, versions of record, and updates are different version roles, and significant relationships should be declared. Typed reciprocal relationships can distinguish manuscripts, preprints, versions, replacements, translations, and variants. The answer carries the source boundaries forward and does not infer authority from a neighboring topic.
Which inspected sources support this relationships answer?
Version control, corrections, and retractions (living documentation inspected 2026-09-06), at Version vocabulary; preprint, author accepted manuscript, version of record, and updated version; DOI relationship guidance, supports drafts, preprints, accepted manuscripts, versions of record, and updates are different version roles, and significant relationships should be declared. Relationships (living documentation inspected 2026-09-06), at Intra-work relation types: manuscript, preprint, replacement, translation, variant, and version, supports typed reciprocal relationships can distinguish manuscripts, preprints, versions, replacements, translations, and variants.
What does the evidence not establish?
A repository location does not prove which version is present, that it is identical to the version of record, or that its license permits redistribution. A declared metadata relationship is an assertion and must be checked against source identity and content before one copy substitutes for another. Property boundary: This route may apply evidence; it cannot redefine or inherit the authority of its canonical owner.
Which definition or canonical owner must be read first?
This page is the local maha-research definition for its topic. Related applications may depend on it but may not silently redefine it.
What source, policy, implementation, or release change would require revision?
Re-evaluate this page when a cited source, locator, governing instrument, local implementation, or canonical definition changes. Publication also requires a matching exact-revision review and active canonical release.