Start the MapleJockey pilot
17 November 2026 | Internal file-recovery rehearsal | Canadian English
Open MapleJockey_Pilot.html from the project package. Start with Run guided synthetic demo. The bundled files are synthetic, and this local rehearsal is already within the authorised scope. No supplier account, purchase or production change is needed.
The pilot asks one useful question: can a bounded set of files be exported, restored against a separately retained source baseline, used for the intended checks and rolled back without changing the original? The bundled case contains eight synthetic files. Its demonstrator target is 60 seconds, and its data-reading task is four CSV observations with a total value of 40.
Five-minute demonstration
| Time | Action | What to show |
|---|---|---|
| 0:00–0:45 | Review the plan and start the guided demo | Synthetic scope, owner, target and explicit exclusions |
| 0:45–1:30 | Inspect the source manifest | Relative paths, file count, byte lengths and SHA-256 hashes |
| 1:30–2:30 | Inspect the restored result | Completeness against the retained baseline, byte equality and supported format checks |
| 2:30–3:15 | Run a negative case | A missing or changed file must fail rather than produce a successful result |
| 3:15–4:00 | Roll back the local restored state | The original baseline remains available; rollback is bounded to the new local copy |
| 4:00–5:00 | Download the evidence report | Scope, timing, passed/failed/untested checks, remaining dependencies and next decisions |
The browser guided demo serialises and re-parses the portable bundle in memory. It does not prove that a downloaded file was saved to disk or that a supplier can recover it. Use the manual export/re-import flow to exercise downloaded bundle handling. The separately recorded command-line rehearsal writes and reads isolated local directories. Those are three different proof boundaries.
Read Eight-file disk rehearsal result for the observed disk result, disk-rehearsal.json for structured checks and pilot-assessment.json for import into the existing assessment companion. These results retain the actual run's scope. The sign-off form is a blank decision worksheet, not an automatic approval.
Manual file route
- Record the owner, objective, source, intended destination and elapsed-time target before the run. The target is a demonstrator threshold unless a workload owner has approved a business objective.
- Choose the synthetic sample, or explicitly select a small set of your own non-sensitive files. Maximums are 200 files, 5 MiB per file and 20 MiB in total. Do not use credentials, personal information, confidential research or controlled defence material.
- Inspect the source manifest. Resolve excluded, unsupported or unsafe files before interpreting the result.
- Download the portable JSON bundle. It contains the file contents in an unencrypted form; base64 encoding is not encryption. Keep it on an approved local device and out of shared or synchronised folders unless separately authorised.
- Re-import that downloaded bundle while the independently retained source baseline is still available. A bundle that only agrees with its own embedded hashes cannot prove agreement with the original source.
- Review integrity and functional checks separately. Unsupported formats remain Not tested. Open the restored files needed for the agreed user task, then record any manual checks and limitations.
- Roll back the restored state, confirm the original remains readable and unchanged, and download the evidence report. Follow the operator's retention decision for any downloaded files; clearing the app does not erase copies already saved elsewhere.
Read the results correctly
| Result | What it establishes | What it does not establish |
|---|---|---|
| Browser in-memory rehearsal | The local serialisation, parsing and comparison path for the selected bytes | Disk durability, provider upload/download or operating-system permissions |
| Manual browser export/re-import | The imported local bundle agrees with the retained baseline for the checks actually completed | Complete supplier migration, server-side storage location, sharing policy or account recovery |
| Isolated disk rehearsal | Fresh local files were written, read back and checked within the recorded run | Dropbox or Sync recovery, cloud version history, identity, support access or production throughput |
The app is a local workbench, not an encrypted evidence vault. Report metadata can include filenames and paths even when file contents are excluded.
Next useful decision
Accept or reject the bounded local rehearsal using Acceptance and sign-off form. The Dropbox-to-Sync route remains documentation-reviewed until the exact accounts, selected destination region, permissions, contract and exit path are evidenced and an authorised provider rehearsal is executed. Nothing in this demo approves a production cutover.