Library Organization: Virtual Folders and File Links

Curate inbox, catalog, folders, and file links on top of the encrypted registry. library:read / library:write scopes keep operators productive without duplicating Arweave payloads.

Curate permanence like a filesystem — without re-uploading payloads.

Library sits on top of the encrypted file registry. Folders, file links, trash, move, and batch link flows reuse the same txIds you already settled while giving teams a navigable workspace.

Value

Per-key isolation

Each API key gets its own roots and graph partition so tenants never collide in the UI or API.

Scopes that match the job

library:read covers browsing; library:write unlocks structure mutations while uploads stay under Files scopes.

Pairs with bundles

Select files in Console Library to assemble POST /transfers envelopes without hunting raw tx lists.

For operators

• Call GET /library/roots after auth to discover inbox + catalog anchors before listing children.
• Use POST /library/file-links (or batch) to attach existing uploads under a parent folder without new Arweave writes.
• Trash → restore → purge mirrors desktop semantics while retention governance still applies to underlying files.

For buyers

• Reduces support tickets from teams that think in folders, not transaction IDs.
• Keeps procurement stories honest: permanence stays on Arweave, organization stays operational.
• Creates a natural bridge from raw developer APIs to regulated workspace UX.