How it works

From a source to a spatial memory.

Foldoria adds a local visual model around content. The WebView renders the experience; Rust retains authority over paths, SQLite, native operations and every real filesystem boundary.

The core loop

Four explicit steps

  1. 01
    Windows 11

    Choose a source

    Use a Rust-owned native picker or a single-item Explorer drop. React receives an ID and bounded metadata—not the native path.

  2. 02
    Available

    Place its reference

    The folder becomes a box; a file receives a type-specific shape. Position, color, size, rotation and world relation are saved locally.

  3. 03
    Available

    Explore and organize

    Walk between worlds, browse direct children, create spatial groups, use cabinets and posters, and open supported read-only content.

  4. 04
    Available

    Return without losing context

    Foldoria restores the world layout and player pose while the original external source remains outside ordinary metadata changes.

Authority model

The visual layer asks. Rust decides.

This is the central safety property of the current desktop architecture.

PresentationReact + 3D sceneIDs, coordinates, bounded metadata
Trusted coreRust + TauriValidation, authorization, native actions
Local systemsSQLite + filesystem + WindowsPaths never enter the WebView

Two source modes

Read-only references and managed content

SourceSpatial changesReal file actions
Existing external file or folderFoldoria metadata onlyNone; source stays read-only
Managed Documents\Foldoria contentFoldoria metadataExplicit create, copy, rename, move, ZIP, extract or managed Trash
Public internet-world contentEphemeral viewer stateNo local authority; explicit Save As only