Tool independent
The advice must work in ordinary folders and common shared drives without a proprietary feature.
About River Folder
Guidance for the quiet work of keeping files understandable.
River Folder is an independent public reference library about file naming, project folders, handoffs, and archives. It publishes plain guidance and plain files that do not depend on a particular storage vendor.
Editorial purpose
Make project context survive the people and tools that created it.
Most file problems are not caused by a missing feature. They appear when names drift, current work mixes with old drafts, decisions live only in messages, or an archive keeps everything without explaining anything.
River Folder turns those recurring problems into small operating practices. Each guide must define a concrete outcome, show realistic examples, and avoid claiming that one folder pattern fits every team.
Publishing standard
Every guide should pass four checks.
Specific enough to use
Examples, field names, exit conditions, and failure cases should be visible.
Honest about tradeoffs
More metadata and more folders are not automatically better.
Maintained as a system
Guide links, templates, examples, dates, and terminology are reviewed together.
Scope
What River Folder does not provide.
River Folder does not host documents, create user accounts, sync folders, sell storage, or inspect visitor files. The worked workspace is static editorial content.
The library also does not replace legal, records-management, compliance, or security advice. Retention and access decisions should be reviewed against the requirements that apply to your organization.
Found something unclear or inconsistent?
Send the page URL, the wording in question, and the change you recommend.