← The I/1 Edit

Edition 003 · August 2026

Your archive is not a backup.

Downloading the files is not the same as preserving the system that made the work usable.

Most platforms now offer some version of an export button. You can download posts, contacts, documents, photographs, subscriber lists, and account history. That can feel like control.

An export may be the difference between retaining years of work and losing it. But possession of an archive is not proof that the work can continue. A working system also contains why a decision was made, which draft became authoritative, who has permission to use what, how a reader was reached, what an unfinished idea depends on, and what must happen next.

Google, LinkedIn, and Substack provide useful export functions. Instagram, Facebook, TikTok, YouTube, and X do too. Coverage, format, preparation time, eligibility, and preserved data differ. An export may retain content without recreating ranking, reach, monetization status, audience habits, moderation history, account authority, collaboration roles, or a functioning channel elsewhere.

Account structure matters as much as data. Facebook Page access, X delegation, and YouTube channel permissions can distribute operational authority. An archive can preserve content while failing to preserve who may publish, manage collaborators, redirect an audience, receive revenue, or authorize a transition.

A CSV of contacts is not a relationship. A folder of documents is not a method. A collection of posts is not a publication. The mistake is treating storage as continuity.

What an archive usually loses

A finished report may survive as a PDF while its source trail, interview notes, analysis environment, permissions, scope correspondence, version rules, reader list, and updating judgment remain distributed elsewhere. The artifact survives while the capability disappears.

Platforms organize information for use inside their own environments. Search, links, permissions, history, interface, and context are native features. An export necessarily flattens some of that environment. What arrives may be technically complete and operationally unusable.

GDPR Article 20 creates an important data-portability right in specified circumstances. It does not guarantee that another service can reconstruct network effects, permissions, rankings, inferences, or workflow. Portability can move material. Continuity must preserve function.

The working model

The five-layer archive

01

Objects

The visible work: writing, images, audio, video, code, contracts, presentations, datasets, notes, and correspondence.

Ask

Do I possess a usable copy in a format I can open without the original platform?

02

Context

Dates, versions, source links, captions, status, decisions, authorship, and the reason each item exists.

Ask

Six months from now, could I tell what this is, whether it is final, and what evidence supports it?

03

Rights and permissions

The legal and practical authority to reuse, revise, publish, transfer, license, or delete the material.

Ask

Does possessing the file mean I may use it? If not, where is the controlling agreement or permission record?

04

Relationships

Collaborators, sources, readers, clients, vendors, communities, and people who know how the system operates.

Ask

Is the relationship direct and mutually recognized, or only a follower count, username, or platform-mediated history?

05

Routines

The repeatable actions that turn stored material back into capacity: research, review, naming, approval, publication, maintenance, and recovery.

Ask

Could another person—or a future version of me—restart this system from its documentation?

The Recovery Drill

Choose one body of work you would need to continue if access to the original system disappeared tonight. Name its next meaningful action, then attempt that action from the archive alone.

StepAttemptRecord what blocks you
OpenOpen the material with tools you control.Missing file, proprietary format, lost key, or original-platform dependency
UnderstandIdentify the authoritative version, status, provenance, and purpose.Ambiguous names, missing metadata, or undocumented decisions
VerifyReconstruct the evidence, permissions, and approvals behind it.Missing sources, consent, licenses, agreements, or review history
ReachContact the people needed to continue without relying exclusively on the lost system.Platform-only identity, stale contact data, or no mutually recognized route
ResumePerform the next meaningful action.Missing workflow, credentials, configuration, capacity, or authority

This is a recovery drill, not a resilience score or validated assessment. Its result is a list of specific failures to repair. If the attempt fails at Resume, you may have preserved the past without preserving the future.

A necessary boundary

The point is not to copy everything.

Client confidentiality, research obligations, employment agreements, privacy duties, security requirements, and data-minimization principles may limit what a person can or should carry.

The goal is deliberate continuity within those boundaries: know what is yours, entrusted, shared, institution-bound, or subject to a destruction schedule. An Institution of One is not a person who takes everything.

Closing question

If your primary work system disappeared tonight, what would you still possess tomorrow—and what could you actually resume?

This essay offers a structural framework, not legal advice. Access, retention, transfer, and reuse depend on applicable law, contract, confidentiality duties, and platform terms.

Source Desk

Inspect the primary documentation.

  1. Google Account Help — How to download your Google data
  2. LinkedIn Help — Download your data
  3. LinkedIn Help — Export connections
  4. Substack Help — Export posts
  5. Substack Help — Export an email list
  6. Instagram Help — Export your Instagram information
  7. Facebook Help — Export your Facebook information
  8. Facebook Help — Manage Page access
  9. TikTok Support — Requesting your data
  10. YouTube Help — Manage channel permissions
  11. Google Account Help — Share a copy with a third party
  12. X Help — Access and download your X data
  13. X Help — Delegate account access
  14. GDPR Article 20 — Right to data portability

Source status: Primary platform and legal documentation rechecked 7 August 2026. These sources establish described tools and access structures, not identical functionality for every account, region, plan, role, or export. Recheck at publication and application.

Read in sequence

← Edit 002: the suppliers beneath a career

Next: The Exit Is Part of the Architecture →

The I/1 Edit

Follow the research on work, ownership, continuity, and institutional power.

The I/1 Edit

One sharp idea. Every other week. In your inbox.

One original argument about work, power, and ownership—made concrete through real careers. The email is a satisfying read on its own. The web edition adds sources, interactive tools, updates, and more cases to explore.