Abstract
A writer can sign in, see a manuscript, search it, revise it, and share it. Those are meaningful forms of access. They do not, by themselves, settle whether the manuscript can be independently held, interpreted, transferred, or recovered under changed conditions. This white paper introduces custody gap as the difference between present account-enabled access and the wider conditions needed for durable, intelligible, transferable custody. It does not treat an account as a trap, a cloud service as a failure, a local copy as a guarantee, or data portability as an archive. Instead, it offers the Account–Archive Boundary Map, a twelve-field inquiry record that helps writers, editors, program leaders, archivists, and tool stewards make the relevant conditions visible before anyone calls a creative record owned, safe, backed up, or archived. The paper draws on personal digital archiving research, an exploratory study of web-held personal content, official preservation guidance, and bounded EU data-rights guidance. Its final move is a question rather than a prescription: what is known about the record beyond the sign-in that currently opens it?
1. The sign-in is real; the conclusion is premature
An essayist opens a browser, signs in, and finds a decade of work. There are fragments of lectures, drafts of introductions, a complete unpublished manuscript, and a folder of source notes that still opens in the order she remembers. The account is active. The password works. The page looks familiar. Nothing in this scene requires alarm.
She has been asked a smaller question than “Is the work safe?” She has been asked to say what makes the work hers to keep. Her first answer is the ordinary one: “It is in my account.” The answer is understandable. The account gives her a route to the material, perhaps sync, search, collaboration, managed storage, and fewer local tasks to remember. These are benefits, not illusions. A managed service is not a trap merely because it is managed.
The difficulty begins only when the sentence is made to bear conclusions it cannot yet support. Does “in my account” mean that the essayist has a copy outside the present sign-in? That drafts can leave in a form she can understand? That comments, prior versions, descriptions, and file relations travel with them? That a credential, device, plan, or service condition has a known consequence? That a collaborator’s comment or a shared source note can be moved without changing the relation that made it meaningful? None of these questions predicts a failure. Each identifies an assumption hiding behind an apparently complete word: there.
This paper calls the distance between present account access and those further conditions a custody gap.
Custody gap is the difference between being able to access a creative record through a current account and holding conditions sufficient for durable, intelligible, transferable custody.
The phrase is not a legal category. It does not settle who owns a service, a file, a license, a set of comments, or an account. It is a teaching term. Its purpose is to stop an access claim from impersonating an archival conclusion.
The distinction matters because creative work rarely consists of one finished file in one place. Catherine Marshall’s personal digital archiving synthesis describes valued material distributed across local folders, backup media, email, services, and other sites. It also observes that people commonly conflate a short-term backup with a long-term archive.[1] Distribution is not necessarily a mistake. People distribute material because they use it, share it, copy it, post it, edit it, and return to it in different ways. Distribution is often the consequence of work. But a record becomes difficult to describe when its pieces, relations, and access paths have accumulated across places chosen for different purposes.
The important shift is modest. Rather than asking whether an account is “good” or “bad,” a reader asks what conditions must be true for the current access relation to support the claim they hope to make. A current sign-in may be enough for today’s editorial task. It may not be enough to support a claim about independent custody, future rendering, scholarly use, estate planning, donation, collaboration, or recovery after a changed circumstance. Different claims require different evidence.
2. Three verbs that should not merge
The custody gap becomes easier to see when three verbs are held apart: access, custody, and archive.
Access is a present ability to reach or use a record. It may depend on a password, device, network, permission, local folder, browser, application, institution, or another person. Access can be immediate and valuable. It can also be partial: a reader may reach a rendered document but not its history; a collaborator may see comments but not export them; an author may open a draft but not know where its separately stored assets live.
Custody, as used here, is not a claim of legal ownership. It is a practical question about the conditions under which a person or group can hold, locate, interpret, transfer, and recover a record. Custody includes present access, but it also asks about independent copies, descriptions, rendering conditions, account gates, dependencies, collaborators, permissions, and the evidence available for a return path. A person may have strong custody conditions for one part of a collection and weak or unknown conditions for another.
Archive refers to a deliberately sustained relation to material over time. Institutional preservation programs make the difference visible without giving individual writers an impossible standard. The U.S. National Archives and Records Administration describes ongoing usability in relation to authenticity, accuracy, and feasible functionality; its published operations include transfer guidance, metadata, fixity, validation, action records, audits, monitoring, and restoration testing.[2] The National Digital Stewardship Alliance presents its Levels of Digital Preservation as a resource for practitioners who build or assess preservation programs, with implementation guidance, working definitions, assessment, and curation support.[3]
These institutional materials do not imply that every writer needs to reproduce an archive. Their value in this paper is diagnostic. They show that a preservation claim ordinarily refers to more than having bits somewhere, more than active access, and more than a reassuring interface state. The difference is not a reason to dismiss personal practice. It is a reason to make the scale and type of a claim proportionate to available evidence.
Gabriela Redwine’s Digital Preservation Coalition report on personal digital archiving is useful here because it brings planning back to human scale. The report’s case-oriented discussion includes scope, maintenance, backup arrangements, file opening, software, file formats, and folder structures; one trial describes format planning and software use as time-consuming even for a relatively small personal collection.[4] This does not prove that a writer needs a complex plan. It shows why “I can open it now” does not eliminate questions about future opening, maintenance, or record relation.
The three verbs should remain separate because they answer different questions.
| Verb | Narrow question | Evidence that could matter | What the verb does not settle |
|---|---|---|---|
| Access | Can someone reach and use this material under present conditions? | Active sign-in, working device, permission, application, or location. | Whether the material can travel, be interpreted later, or be recovered under a changed condition. |
| Custody | What conditions allow this record to be held, located, interpreted, transferred, and returned to? | Independent copies, record locations, descriptions, account/policy conditions, relational context, and recovery evidence. | A legal ownership determination, a platform ranking, or a full preservation claim. |
| Archive | What deliberate practice sustains usable records over time? | Documentation, integrity attention, maintenance, preservation decisions, and designated-use conditions. | That an institution’s methods are necessary or feasible for every individual. |
A writer can have access without complete custody. A group can have a custody arrangement without maintaining a formal archive. An archive can make access possible for designated users without granting every person unrestricted control. The purpose of the distinction is not to create a hierarchy in which only institutions count. It is to make the next question clearer.
3. An account has a boundary, not a moral character
Accounts are often discussed as though they were either pure convenience or pure dependence. Neither description is adequate. An account can enable cross-device continuity, remote collaboration, searched collections, recovery of forgotten location, managed infrastructure, and the ordinary ease that lets people write rather than maintain systems. It can also become a boundary around a record: a credential, subscription, permission, network path, policy, application, or service operation may be necessary for a particular kind of access.
A boundary is not a verdict. It is a condition worth naming.
The condition becomes especially important when a creative record is web-held or socially embedded. In their exploratory study, Siân Lindley, Catherine Marshall, Richard Banks, Abigail Sellen, and Tim Regan asked fourteen people to tour personally meaningful online content, search for material associated with themselves, and respond to possible ways of viewing and managing that material together.[5] Their analysis rejects a single-archive assumption. It distinguishes different kinds of online content, including material that a person controls, material controlled by others, and material held in ambiguous cloud locations. It also notes that separating material from its original setting can fix or lose web-specific attributes, including comments, tags, and likes.[5]
This finding does not mean that every comment is archival, that every tag must be preserved, or that web-held material is unmanageable. It complicates a much smaller assumption: a downloaded item and the relationship in which that item was made available may not be the same record. A photograph copied from a web service may no longer carry the same comments. A draft exported from a collaborative space may not show the same permission relation. A manuscript can remain useful after such changes. The change must simply be understood before someone calls an export a complete equivalent.
The same is true of current service benefits. A Map that records only deficiencies becomes propaganda. A service may make a particular author’s work easier to coordinate, protect an unusually important form of access, or preserve a useful relation among people and devices. That benefit belongs in the record. The question is not whether the service should be praised or condemned. It is whether a reader can say what the service currently contributes, what it mediates, and what further evidence would be required before drawing a larger conclusion.
The account boundary therefore has at least four dimensions:
| Boundary dimension | What it makes visible | Why it matters | What must not be inferred |
|---|---|---|---|
| Access gate | Sign-in, device, network, permission, or institution required now. | It shows how the record is reached in the present. | That access will be removed or that a gate is inherently improper. |
| Service function | Search, sync, storage, version display, collaboration, or rendering performed through a service. | It clarifies what a change in relation could alter. | That every mediated function makes the record unsafe. |
| Record relation | Comments, attachments, shared sources, references, permissions, or social metadata tied to other people or contexts. | It prevents an exported object from being treated as automatically complete. | That all relation-specific material belongs in every future copy. |
| Policy condition | Terms, data-rights rules, access conditions, or retention questions requiring primary inspection. | It identifies where assumption must give way to reading. | A legal interpretation, a claim of unfairness, or a prediction about a policy change. |
The fourth dimension needs particular restraint. The European Commission’s GDPR guidance states that, in the relevant context, people can receive their personal data in a machine-readable format and send it to another controller; it also describes direct transmission where technically feasible.[6] This is useful vocabulary for distinguishing data portability from a broader archive claim. It does not establish that every piece of creative material is covered, that a ported set retains all relations, that the material remains editable or readable in the same way, or that an account’s service features continue elsewhere. A paper that writes “portability means you own your work” has replaced one vague word with another.
4. The Account–Archive Boundary Map
The Account–Archive Boundary Map is an original inquiry record. It is not a maturity model, legal test, risk score, contract review, or product comparison. It is designed for a writer, editor, program leader, archivist, or tool steward who needs to make one creative record’s present conditions visible without rushing toward a platform verdict.
The Map is most useful when it begins with a bounded object. “My work” is too large. “The lecture-manuscript drafts and source notes from 2014–2024” is workable. “The annotated files shared with three editors for the spring issue” is workable. A bounded record makes it possible to distinguish facts, assumptions, relations, missing evidence, and benefits.
| Field | What to record | Teaching question | Mistake avoided |
|---|---|---|---|
| 1. Creative record | The draft set, notes, media, comments, or working collection under discussion. | What exactly is being called “there”? | Treating a whole writing life as one undifferentiated object. |
| 2. Present access gate | The sign-in, device, network, credential, or permission relation used today. | Through what relation can the record be reached now? | Calling present visibility independent custody. |
| 3. Service dependency | The service function, policy condition, or operational assumption mediating access. | What infrastructure is necessary but not yet named? | Treating an interface as the whole record. |
| 4. Export surface | What can leave the account, in which forms and scopes, with what known omissions or unknowns. | What travels, and what is still untested? | Equating a download button with a complete archive. |
| 5. Independent copy | Any separately held version, its location, and its relation to the working record. | What exists outside the current sign-in? | Calling any duplicate current, readable, or sufficient. |
| 6. Interpretability condition | File, render, software, description, layout, or context needed to understand the record. | What would make this material meaningful later? | Treating stored bits as self-explanatory. |
| 7. Collaboration boundary | Comments, permissions, shared material, other-held assets, or social metadata that matter. | Which relations would change if material moved? | Assuming a solitary file is the entire record. |
| 8. Recovery assumption | The untested story of what happens if location, access, or conditions change. | Where is the presumed return path? | Declaring that recovery will fail or that a person is careless. |
| 9. Policy or jurisdiction boundary | The primary terms, data, or institutional condition that needs direct checking. | What must be read rather than repeated from memory? | Offering legal advice or relying on a rumor about policy. |
| 10. Archival evidence needed | Missing facts concerning copies, scope, readability, relation, integrity, description, or responsibility. | What evidence would change the custody account? | Treating uncertainty as a personal deficiency. |
| 11. Countervailing service benefit | The current gain from sync, collaboration, support, search, continuity, or managed infrastructure. | What useful condition would a change endanger? | Turning the inquiry into anti-service rhetoric. |
| 12. Non-conclusion | A precise statement of what cannot yet responsibly be claimed. | What remains unproven? | Converting an inquiry record into a recommendation. |
The Map is deliberately not a checklist with correct answers. A record may have no independent copy because it is a live collaborative workspace that must first be understood. A record may be fully exportable but still require context to be interpretable. A writer may have an independent copy whose relation to the working version remains uncertain. A service may provide a benefit that makes a change undesirable even after a custody gap has been identified. Unknowns are not failures of the person filling out the Map. They are the information the Map is designed to surface.
The Library of Congress’s personal-records guidance offers a useful practical counterpoint. It asks individuals to locate documents across computers, removable media, and websites; decide which records and versions matter; organize selected material; make copies in distinct places; and periodically check readability.[7] This is not a guarantee. It is a way of converting “I think my work is stored” into inspectable questions about location, versions, copies, and readable return. The Map does not replace such guidance. It gives readers a place to record which aspects of the guidance matter to a particular creative record and which remain unknown.
5. Four non-equivalences that keep the Map honest
The Map can be misused if its fields are turned into a new vocabulary for predetermined conclusions. Four non-equivalences prevent that drift.
5.1 Available is not necessarily transferable
A record may be available through a present account while the scope, format, or relation of anything that can travel remains unclear. This is not an accusation against the service. It is a reminder that access answers a different question from transfer. The relevant evidence might be an export description, a directly tested copy, a policy, a working relationship, or a clear statement that no transfer question is presently at issue.
The EU data-portability guidance is helpful because it is specific without being totalizing. It identifies a personal-data right in a defined legal framework; it does not promise that every creative record travels in every meaningful form.[6] The Map should therefore record the difference between a known export and a presumed equivalent. It should not turn an untested assumption into a legal claim.
5.2 Exported is not necessarily interpretable
A file can leave an account and still require software, context, description, layout information, a source folder, a version relation, or a collaborator’s explanation. NARA’s program materials and the NDSA Levels both point toward ongoing usability and managed preservation conditions rather than storage alone.[2] [3] Their institutional scale is larger than a personal collection’s, but the conceptual lesson is portable: a record’s future use depends on more than the fact that a copy exists.
This does not make export pointless. Export may be exactly the right first move. The Map asks only that it be described accurately. “We have a PDF” is different from “We have a complete, independently interpretable record of the project.” The first may be fully sufficient for an intended purpose. The second requires more evidence.
5.3 Copied is not necessarily archived
A duplicate can protect against a particular loss condition while leaving other conditions unresolved. Marshall notes that people can mistake backup for long-term archive and may not know where a claimed backup is or how to retrieve a particular item.[1] Redwine’s report similarly keeps maintenance, formats, software, and planning in view.[4] Neither source requires a writer to become an archivist. Both caution against granting a copy more authority than it has earned.
The Map’s independent-copy field is therefore paired with interpretability, recovery assumption, and archival evidence needed. A duplicate matters. Its relation to the record also matters. The Map asks whether the duplicate is known, located, readable, and connected to the creative material at issue. It does not rank copies or demand a universal number.
5.4 Service benefit is not necessarily custody proof
This non-equivalence runs in both directions. A service benefit is not proof that custody conditions are complete. But a custody question is not proof that the service should be abandoned. A service can make collaboration viable, simplify return across devices, preserve a useful context, or reduce maintenance beyond what a small group can reasonably perform. These gains belong in the Map because they keep the reader from treating autonomy as a synonym for isolation.
The strongest account is often conditional: this service presently supports an important task; this record also depends on conditions that have not been inspected; a proposed change might protect one condition while damaging another. Conditional language is not indecision. It is a way to keep a complicated record from becoming a simple slogan.
6. A short custody conversation
The Map can be used alone, but it is particularly effective in a small editorial, teaching, archival, or tool-stewardship conversation. The goal is not to have every participant expose their private records. It is to choose one bounded, constructed, or volunteered example and improve the quality of the next question.
| Move | Facilitation prompt | Useful output | What not to do |
|---|---|---|---|
| Name the record | “Which specific draft set, notes, media, or project relation are we discussing?” | A bounded record description. | Begin with a platform category or a verdict about “the cloud.” |
| Name present access | “What lets someone reach it today?” | Access gate and active service benefit. | Treat a working sign-in as proof of all later conditions. |
| Name one boundary | “What would leave, change, or need explanation if this relation changed?” | Export, collaboration, or interpretability question. | Predict a loss event or interpret a contract. |
| Name existing evidence | “What do we know because it has been inspected or tested?” | A labeled fact: copy location, export scope, rendering test, or policy source. | Elevate memory, rumor, or interface familiarity to evidence. |
| Name the missing evidence | “What would we need to inspect before making a broader claim?” | A proportionate next inquiry. | Require a full institutional preservation plan. |
| Retain the countervailing benefit | “What current gain must not disappear from the account?” | A condition to protect in later action. | Equate caution with a mandate to migrate or cancel. |
| Write the non-conclusion | “What cannot yet responsibly be said?” | A bounded statement of uncertainty. | Force a final recommendation. |
Consider the constructed essayist again. Her Map might state that the drafts are available through an active account; that search, sync, and version display are current benefits; that a separately held copy exists but has not been compared to the working collection; that export scope has not been checked; that comments and prior version relations may matter; and that the present evidence does not establish whether the account relation is sufficient for a future archive claim. This result is not an emergency. It is a better record of the question.
The next step might be small: locate one independently held copy, read an official export description, test whether one selected draft opens in another environment, or ask a collaborator which comment relation matters to the project. The Map does not choose the step in advance. It ensures that the step responds to a named condition rather than to generalized anxiety.
7. What this paper does not decide
The Account–Archive Boundary Map does not decide whether a service should be trusted, renewed, paid for, migrated from, or recommended. It does not tell a writer which backup schedule to use, which format to prefer, how to interpret a contract, what data-right applies to a particular service, or whether an individual possesses legal ownership of an account or record. It does not diagnose a person’s competence, security posture, privacy practice, or archival adequacy.
It also does not make a local copy, self-hosted system, removable drive, or public repository into a universal answer. Each can introduce its own conditions of access, maintenance, interpretation, relation, and recovery. WEXLEY-WP-021 addresses architecture as an authorial preservation strategy. WEXLEY-WP-027 will diagnose how backup and recovery work can drift from system to user. WEXLEY-WP-028 studies the format, metadata, migration, and interpretability of literary archives. WEXLEY-WP-043 will offer a distinct action ledger for subscription access, exit, and cancellation conditions. WEXLEY-WP-024 comes before those moves. It makes the boundary visible.
A reader may finish the Map and decide that the current arrangement is proportionate to the work. Another may identify a condition requiring further inspection. A third may learn that a useful service benefit should be retained while another custody condition is strengthened. All are legitimate outcomes. The paper’s final discipline is not to force them into one answer.
8. Closing: the question behind the sign-in
The essayist can still sign in. That fact matters. It provides the present relation from which every other question begins. It should not be dismissed, dramatized, or silently transformed into a claim it cannot bear.
Her work may be accessible, partially transferable, intertwined with a service, independently copied in part, interpretable under certain conditions, dependent on relation-specific context, and still surrounded by unknowns. None of those descriptions tells her to panic. Together they let her replace a vague assurance with a legible custody account.
The question the Map leaves behind is not “Who owns the cloud?” It is narrower, more practical, and more teachable:
If this account works today, what conditions make this creative record legible, transferable, and recoverable tomorrow?
References
[1] Catherine C. Marshall, “Rethinking Personal Digital Archiving, Part 1,” D-Lib Magazine 14, no. 3/4 (2008).
[2] U.S. National Archives and Records Administration, “About the Digital Preservation Program.”
[3] National Digital Stewardship Alliance, “Levels of Digital Preservation,” Version 2.1 (2026).
[4] Gabriela Redwine, “Personal Digital Archiving,” DPC Technology Watch Report 15-01 (Digital Preservation Coalition, 2015), https://doi.org/10.7207/twr15-01.
[5] Siân Lindley, Catherine Marshall, Richard Banks, Abigail Sellen, and Tim Regan, “Rethinking the Web as a Personal Archive,” Proceedings of the 22nd International Conference on World Wide Web, 2013, 749–760, https://doi.org/10.1145/2488388.2488454.
[6] European Commission, “Information for individuals,” GDPR data-protection rights guidance.
[7] Library of Congress, “Keeping Personal Digital Records,” Personal Digital Archiving guidance.