The OS still treats every program as you

File permissions are granted to users, not programs. HJFS isolates each program’s files on a stock kernel. Start here for the prototype.

HeartSuite Joint File System | Prototype

Overview: By default, every program you run gets full access to your files, including malware. HeartSuite Joint File System (HJFS) gives each program its own storage area, including programs running as root.

HJFS works on a standard Linux kernel. Which programs run and which network connections they open stay with Root Lock by HeartSuite. On a Root Lock kernel, both can share the host. HJFS also runs on a standard unmodified kernel.

In this section

  • The security problem HJFS solves — Why default OS file permissions enable malware damage and how HJFS closes that gap.
  • HJFS overview — Core mechanisms, per-version storage, secure file transfer, version management, and patents.
  • Walkthrough — A short CLI example showing per-version isolation and rollback in action.
  • Protection limits — Where the file isolation boundary holds, and what to use alongside it.
Your word processor inherits every file you own

Malware encrypts your files with the same open() your editor uses. HJFS keeps custody with you, not with the program you ran.

Each program gets its own storage area

HJFS confines programs to their own files. The OS default — every program inherits your documents — is the hole this closes.

Where the file isolation boundary holds

Where HJFS file isolation holds, where a program can still hurt you inside its own area, and what to run alongside it.

Walkthrough: per-version isolation

Upgrade a program, keep v1’s data out of v2’s reach, roll back. A short CLI walkthrough of HJFS per-version isolation.


Last modified August 25, 2026: docs: publish Root Lock under /rootlock/ (083a3b5)