Roadmap

Current prototype scope and planned development for HeartSuite Joint File System.

Prototype: HJFS is under active development.

Current capabilities

HJFS currently includes the following capabilities:

CapabilityNotes
Per-program file isolationopen() interception — programs are confined to their own storage area
Per-version storageEach installed program version receives its own isolated storage area
Version rollbackNon-destructive — prior versions and their data remain intact
Secure file transferCopy utility and transfer area for explicit cross-program data movement
Trash-only deletionPrograms cannot permanently delete files. Permanent deletion requires explicit user action through a separate utility
Automatic data file backupEvery data file version is backed up to a protected area inaccessible to ordinary programs
Version management utilitiesHJFS_update_program and HJFS_version_manager

HJFS implements core file organization with the host file system code left unchanged — enabling deployment on standard, unmodified kernels. See Architecture and compatibility for details.

Planned

Next release

ItemNotes
FS source code integrationIntegrates minimal HJFS source code into the host file system’s open() call. Required for production deployment
Kernel registrationRegisters the HJFS-modified file system with the kernel. Requires FS vendor cooperation on non-Linux platforms

Subsequent releases

ItemNotes
Network access controlNew outbound connections are mediated by the OS. Desktop deployments prompt the user for confirmation; server deployments apply policy rules
Python script compartmentalizationConfines individual Python scripts to separate file spaces. Scripts no longer share the interpreter’s storage area. Requires a small amount of kernel cooperation
Advanced protectionSeparates internal and user files and introduces OS-mediated file dialogs. Requires application updates. See Advanced Protection for design details