Analyze the current topology
Folderbase reads names, types, repositories, generated trees, existing Folderbase boundaries, and other metadata. It treats file contents as untrusted and keeps analysis bounded.
Workflow 02 / Organize
Folderbase can analyze a disorganized folder, ask consequential questions, and propose a previewable, reversible reorganization Change Set.
Folderbase is designed to make a technically rigorous protocol feel understandable at the folder level. This product plate shows the intended experience without hiding the underlying authority or version boundary.
⌄01 Research1 file
Parchitecture.pdf
⌄02 Approved2 files
Wproduct-brief.docx
Ihero-final.png
Folderbase reads names, types, repositories, generated trees, existing Folderbase boundaries, and other metadata. It treats file contents as untrusted and keeps analysis bounded.
The system surfaces ambiguity it cannot safely infer: ownership, lifecycle, sharing scope, canonical sources, or whether two areas should be separate security boundaries.
The proposal names the intended folders, moves, renames, template guidance, and any boundary implications. It is bound to the analyzed source state so a stale plan cannot quietly apply later.
The App presents a before-and-after view. The user can approve the Change Set, exclude changes, answer a question, or keep the original structure.
An approved reorganization publishes through normal Folderbase versioning. Moves retain durable object identity, and rollback can restore the prior materialized layout.
Yes, when you ask it to. It first produces a reviewable proposal rather than moving files during initial setup.
The intended App experience lets a user review the proposed Change Set, exclude changes, answer questions, or skip the reorganization.
No. Templates are versioned guidance for starting and expanding a Folderbase. They do not permanently lock its kind or directory layout.
Explore the Apache-2.0 Core today, or request early access to the Folderbase App and managed Cloud experience.