CEE / 001

Independent file coverage audit · Issue no. 001

Your cloud copy
needs a witness.

Cloud Exit Evidence compares a provider export with the drive you plan to rely on—then names every missing, stale, mismatched, or permission-excluded file.

Audit a sample

Local by construction. No login, upload, tracking, or cloud credentials.

An archival ledger holding a physical drive beside a cloud-shaped hole cut through the paper
Exhibit A. A copied file is not evidence of a complete copy.

§ 01 / The method

Three claims. All inspectable.

  1. 01

    Expected

    Read a JSON, CSV, or rclone listing. Paths are validated; duplicate and escaping paths are rejected.

  2. 02

    Observed

    Walk the physical destination without following symlinks. Compare bytes, dates, and SHA-256 when supplied.

  3. 03

    Accounted for

    Group gaps by folder, type, and month. Declared permission exclusions stay open until explicitly acknowledged.

§ 02 / Local desk check

Try the evidence test.

This browser edition checks names, byte sizes, modified dates, and declared exclusions. Nothing leaves this page. Use the CLI for SHA-256 and encrypted reports.

Native JSON, rclone JSON, or CSV. Paths stay in memory.

2. Choose the physical copy

No folder selected.

No audit yet

Paste a manifest and choose a folder, or load the intentional-gap fixture to see the report call out missing and excluded coverage.

§ 03 / Field edition

Run the full audit offline.

One open-source Rust binary. No daemon. No account. No telemetry.

cargo install --git https://github.com/B-Divyesh/sf-cloud-exit-evidence cloud-exit-evidence
cloud-exit-evidence audit --manifest export.json --destination /media/offline
Inputs
Native JSON, CSV, rclone lsjson
Evidence
Terminal, JSON, Markdown, encrypted .cee
Exit codes
0 pass · 2 gaps · 3 invalid input
License
MIT · free forever

Read the source and manifest specification