Stage in RAM
Drop files into a volatile staging layer and inspect their state.
GhostLayerby The Proof FoundryVolatile file staging
Choose what becomes permanent.
A temporary working layer for your files. Stage them in RAM, review your changes, and commit only what you choose to keep.
Made for the way you work
A deliberate boundary between work and storage.
Stage, select, edit and commit at your own pace.
Work on a selection
Select a group with checkboxes or keyboard shortcuts. Open staged files in their associated editor.
Commit with intent
Commit or discard the selected files. If a destination changed, conflict recovery preserves both versions.
Temporary, until you say otherwise
Some things can stay.
The rest can disappear.
Make the call on a few sample files. This preview models the choice between temporary staging and an explicit commit.
LAYER 01
Volatile staging
IN MEMORYLAYER 02
You chose to keep
COMMITTEDNothing permanent.
Until you make it so.
Website preview · sample data in this page only. No real files are staged, saved or erased.
Get the software
Choose what stays.
Public Windows installer v0.4.0. Stage, edit and commit on your own machine.
Free downloadDownload v0.4.0
This Windows package is unsigned, so SmartScreen may prompt on first launch. Verify the SHA-256 checksum below before deciding whether to run it.
Verify this download (SHA-256)
This Windows package is unsigned. Verify its checksum before deciding whether to run it; a matching checksum confirms the file matches the published artifact.
5c0f00fb7e6e58526f400e25a0f05e9f948c503479c82d6be4eb7d0aa9f06251
Windows verification: Get-FileHash ".\GhostLayer-Setup-0.4.0.exe" -Algorithm SHA256
Deeper recordProof & technical recordInstall & update, privacy & data flow, release evidence, limitations, receipts.
Set up and keep it yours
Install, update, uninstall & leftover data
- Install
- Run the downloaded
GhostLayer-Setup-0.4.0.exeinstaller (Electron/NSIS, unsigned). Windows SmartScreen may prompt — choose More info → Run anyway after verifying the SHA-256. - First run
- The main workflow is Stage → Select → Edit → Recover → Commit (walked through in the evidence section below). The release notes list the v0.4.0 feature set; no first-run account or cloud setup exists.
- Update
- The public source does not describe an updater. Watch the roadmap or release record for a new published installer and verify its SHA-256 before running it.
- Uninstall
- Uninstall via Windows Settings → Apps (standard for an NSIS installer). The public source does not document a separate uninstall step.
- Leftover data
- Staged files live in volatile RAM and are lost on app close. Temporary editor working files in
%TEMP%\GhostLayer\are purged on commit or discard; interrupted sessions can leave recoverable copies there. Uninstalling the app does not clear%TEMP%\GhostLayer\; remove it manually if present.
Questions or a problem?The Support Hub covers checksums, downloads, and problem reports for every product.Visit the Support Hub ↗
For a closer lookRelease evidence & technical details
Release records, checksums, detailed scope and qualification evidence. Candidate evidence does not change public availability.
Status Public release
Version v0.4.0
Platform Windows
Tests 188/188
Proof Owner-stamped receipt · unsigned
Release report 2026-08-28
The five-step workflowstage → select → edit → recover → commit
Stage → Select → Edit → Recover → Commit Safely
Five deliberate steps. No hidden actions between them.
01 / STAGE
Drop files into RAM
Drag and drop files into the GhostLayer window. They appear in the staging list with their names, sizes, and status. They exist in RAM — no disk writes occur at this stage. The layer is volatile by design.
02 / SELECT
Multi-select with keyboard
Select multiple files with checkboxes, Ctrl+A to select all, or Shift-click for range selection. Commit Selected or Discard Selected operate on the chosen subset only. Unselected files are unaffected.
03 / EDIT
Open in your editor
Open a staged file in its associated desktop application. When you save in the editor, GhostLayer synchronizes the changes back into the staged RAM copy and marks the file as modified. Opening for edit creates a temporary disk copy that is removed when the edit session closes normally.
04 / RECOVER
Recover from interruptions
If a destination changed after staging, GhostLayer blocks the commit and offers non-destructive recovery: Keep Staged, Show Destination, or Save Copy. Save Copy creates a new file only and never overwrites an existing filesystem object. Interrupted edit sessions leave recoverable temporaries — never auto-deleted.
05 / COMMIT
Write only what you choose
Commit the files you want to keep. The commit destination is derived from the staged file identity in the main process — a renderer-supplied destination cannot redirect the write. Uncommitted staging is volatile. Opening an editor creates a temporary disk copy; interrupted edits can leave recoverable copies.
Conflict safety: GhostLayer's block-on-conflict guard is preserved. If a destination file changes on disk after staging, the commit is blocked and both versions are kept — the staged RAM copy and the changed disk file. There is no Overwrite or force-commit operation.
Proof & receiptscustody record, release artifacts
Proof and receipts.
What changed in v0.4.0 — full release notes ↗
The following public artifacts are hosted on the Proof Foundry's own distribution domain. They are the same five objects that form the canonical release set — the installer, three evidence files, and the release notes.
Release Receipt (JSON) — structured receipt with artifact hashes and signing status
Release Receipt (Markdown) — human-readable receipt with verification instructions
Release Package Manifest — artifact list with sizes, hashes, and source authority
Release Notes — public feature list and known limitations
What the receipts prove: The published installer SHA-256 matches
the hash recorded at build time. The release was verified with 188/188 tests passing,
a clean build, and packaged runtime qualification (13/13 steps).
What the receipts do not prove: The software is malware-free.
The software is Microsoft-signed. SmartScreen will not warn. Any third party
attested to its safety. The receipts establish custody and provenance — not safety.
Privacy & Data Flow
RAM-first staging. Disk-backed editor copies.
Evidence-backed behavior for GhostLayer Windows v0.4.0.
RAM staging & temp disk files
Primary file staging is held in volatile RAM (lost on app close). Launching external text editors creates temporary working files in %TEMP%\GhostLayer\, which are purged on commit or discard.
Network boundary
Proof Foundry's own review of the GhostLayer source found no network capabilities or internet connections. All staging, conflict resolution, and file commits occur locally on your machine.
Telemetry & safety
Zero background telemetry or analytics tracking. Interrupted edit sessions retain recoverable temporary disk copies so no working edits are silently lost.
Volatile file staging
Choose what
becomes permanent.
Stage in RAM, review your changes, and commit only what you choose to keep.