FORENSICS, WITHOUT THE FINE PRINT

Know what protects your data. And what doesn’t.

No magic recovery claims. No mysterious security jargon. Here is the evidence chain, the proposed vault architecture, and exactly what works in this preview.

Working: hashing, browser sealing, 3D coreConcept: file recorder, sync, escrow, purge

CLIENT SPECIFICATIONS / PROPOSED

A familiar drive. A deeper record.

V: CCV

Cube Cognitive Vault

01 / Open V:

The proposed desktop client presents CCV as a virtual drive in your file manager.

02 / Place & identify

Add a file to the workspace. Its contents receive a fingerprint independent of the filename.

03 / Track & mirror

Record changes in a proposed 48-hour ledger; mirror modified files to a separately retained destination.

04 / Inspect & recover

Compare fingerprints, flag exact duplicates, and restore from an available retained copy.

Drive identity
V: — CCV (Cube Cognitive Vault); sample workspace paths use V:\CCV\.
Client availability
No downloadable client or operating-system drive mount is available in this preview. Platform support is not yet specified.
Data & retention
Native file monitoring, access controls, retained-copy storage, and 48-hour history are proposed requirements, not active services.
Security boundary
The armored Cube is a visual metaphor, not a claim of physical indestructibility. Encryption does not guarantee recovery of deleted originals.

Simulated workflow. This website does not mount V:, monitor folders, or store your business files.

01 / EVIDENCE LAYER

Find the contents, not just the name.

Standard search looks at names or indexed text. A content address uses a fingerprint of the file’s bytes. A rename leaves those bytes untouched, so the fingerprint still matches. Identical copies can be flagged. This supports a zero-loss goal only when the original data is safely retained; hashing alone cannot reverse deletion.

AVAILABLE IN THE SAMPLE DEMO

02 / EVIDENCE LAYER

A 48-hour flight recorder for file events.

The commercial design is a rolling 48-hour ledger of file additions, changes, renames, and deletions. Linking entries with fingerprints makes alterations detectable against a trusted checkpoint. It needs a real file monitor, protected reference points, and a retention policy. None is operating in this browser preview.

PROPOSED COMMERCIAL CAPABILITY

03 / EVIDENCE LAYER

Mirror modifications. Skip the unchanged files.

The proposed Robocopy-grade delta mirror compares source and destination, then transfers modified files rather than recopying everything. Here, delta refers to changed files, not guaranteed byte-level patching. Mirroring is not versioned backup: unwanted changes can also propagate. No folders are monitored or synchronized by this app.

PROPOSED COMMERCIAL CAPABILITY

04 / EVIDENCE LAYER

Sealed data. Deliberate deletion.

Today, an optional passphrase seals a note in your browser before its encrypted payload is hashed. The commercial encapsulated vault design adds double-passphrase confirmation before purging records. That confirmation is not implemented in the session-only core. Tamper-evident encryption detects changes; no system should promise literal tamper-proof protection.

BROWSER SEALING AVAILABLE / PURGE IS PROPOSED

THE PLAIN-ENGLISH GLOSSARY

Technical terms. Human answers.

A fingerprint calculated from a file’s contents, not its name. Renaming an unchanged file keeps the same fingerprint; changing its contents produces a different one. It helps spot duplicates and check integrity, but is not encryption or a backup.

Robocopy is a Windows copying tool. Delta sync means copying only what changed, rather than the whole collection again. That saves transfer time. It does not automatically keep old versions or protect you from a bad change.

Find a stored file by a fingerprint of what is inside it, rather than the label on the outside. Identical contents can share one stored copy. Recovery still needs that copy to exist; a fingerprint cannot rebuild a deleted file.

Encryption that turns your note into unreadable data and checks whether the encrypted data was changed. The right passphrase unlocks it. In this app, sealing happens on your device; losing the passphrase means losing access.

The service does not receive the secret needed to read your sealed content. Here, notes are sealed in your browser and stay in this session. This does not hide every detail, such as the kind of note or its encrypted fingerprint.

A flight-recorder-style history of file events. Linked fingerprints can make later edits detectable when checked against a trusted reference. Tamper-evident means changes can be noticed—not that changes are impossible.

Inspect the working core.

3D memory, spoken replies, and optional passphrase sealing. Session-only. No administrator login.

Private Lyra chamber