Active system program · local computing

File Manager

Not one application. A nested collection of ideas about how a local computer should present files, remember state, search, and share authority.

Current question

Can every layer remain inspectable and replaceable without giving up a coherent everyday tool?

The pieces

Working / proving

GUI.Forms

A custom-rendered C++ alternative to WinForms, with native macOS output and PE64/Wine proving builds.

Working / proving

Web.Forms

Bounded HTML and CSS compiled into retained native GUI.Forms controls—the path toward visual web-shaped authoring without shipping a browser engine.

Working

Exact search engine

A Go catalogue, live search path, fallback retrieval, and persistent generations for local files.

Working

Cross-platform front end

A C++ file interface with protected-root experiments, read-only defaults, and native UI integration.

Working

Persistent state and policy

Durable catalogue generations in the Engine; bounded settings, capabilities, handlers, and process supervision in the Rust Orchestrator.

Separate research branch

Semantic concept memory

Provider-managed semantic hives live beyond the exact catalogue boundary. They do not get to silently redefine file truth.

Planned

Distributed file and index access

Paired machines should expose bounded availability and index information across a LAN. That branch is designed, not yet delivered.