FILESYSTEM TRUTH · EXACT CATALOGUE · NATIVE INTERFACE

Your files remain
in charge.

File Manager is growing into a local computing system in which search can become intelligent without becoming the owner of the files it describes.

THE NATIVE SURFACE

A file manager that exposes the system behind the folder.

Native File Manager folder surface with home tree, project contents, selected-image preview, and identity properties
Authentic GUI.Forms File Manager capture. The surface keeps folders, contents, commands, selection, preview, identity, path, size, format, and handler information visible together.

Left: admitted places

Local roots, home folders, and unavailable volumes retain distinct states.

Center: current objects

The folder view is a projection of observed filesystem identities, not a database pretending to be the filesystem.

Right: inspect before acting

Preview, exact identity, metadata, edit fields, and handlers belong to the selected object.

THE PROGRAM SPINE

Five owners. No universal database.

  1. 01FilesystemAuthoritative object identity, existence, binding, permissions, and mutation outcome.
  2. 02Engine · GoExact catalogue, immutable generations, live traversal, prefix/name/path search, and bounded candidate channels.
  3. 03Orchestrator · RustCapability catalogue, settings, provider availability, policy, command routing, and local integration contracts.
  4. 04GUI.Forms · C++Retained native controls, layout, painting, input, dialogs, and the visible File Manager surface.
  5. 05Semantic hivesVersioned, optional interpretation beyond the exact catalogue; evidence returns with provenance and availability.

SEARCH WITH ITS EVIDENCE ATTACHED

Exact, extracted, unavailable, and stale are different answers.

Native File Manager search showing exact filename, extracted PDF evidence, offline and stale results, scores, and matched excerpts
Authentic search capture. Exact filename evidence is pinned first; extracted content remains inspectable; offline and stale records remain visible as such.
THE QUERY LAW

Exact identity and exact lexical evidence are not blended into one opaque score. Candidate channels may propose, plugins may extract, and semantic systems may interpret—but the result still says which channel spoke and whether the underlying object is currently available.

DURABLE WITHOUT CONSTANT REWRITING

Generations make the index replaceable and inspectable.

Immutable committed runs

A small atomic manifest selects checked base and delta generations. Readers never observe a partially rewritten index.

Streaming diff

One change among 1.1 million bindings was found in 260.420 ms without materializing a complete change array.

Bounded overlays

Exact queries merge a checked base with bounded immutable change runs while the million-record base remains off-heap.

Background currentness

Filesystem events are hints that command reconciliation. Overflow or discontinuity schedules a full scan instead of inventing certainty.

FULL-SNAPSHOT CONTROL164,201,438+ bytesone changed object / 1.1M bindings
STREAMING DIFF260.420 mssame one-object change
RUN-ONLY AMPLIFICATION≈1.157×4,096 / 10,000-change workloads

MEASURED ON NAMED WORKLOADS

Fast when active. Nearly absent when idle.

<1 ms

Warm exact path

Measured at the Engine boundary.

single-digit ms

Million-record search

Common warm scoped name/metadata top-k queries.

161.8–163.7 ms

Event to current · p50

Two same-revision macOS/APFS repetitions.

201.0–228.2 ms

Event to current · p95

50 ms FSEvents latency and 100 ms maximum observation age.

338–489 ms

4,096-write storm

Across 256 paths with three exact full-generation publications.

0.006654%

Ten-minute idle CPU

One core; generation unchanged; zero application durable writes.

THE FILE, RECHECKED AT COMMIT

Retrieval finds an object. The filesystem authorizes the action.

Native File Manager with restored selection and editable property panel
Authentic selection/property capture. The selected object retains its visible identity while the responsive pane changes extent.
search result→fresh no-follow identity→explicit operation→terminal result→new generation

THE LOCAL INTELLIGENCE

The system may know more without claiming more authority.

Exact catalogue, live search, fuzzy geometry, extracted evidence, and future semantic memory can coexist because none of them is allowed to replace filesystem identity. Intelligence accumulates around the file; the file remains the thing itself.

Open File Manager ↗