# Cloudy_Day Proof Bundle

A verifiable, tamper-evident record of independent researcher **Ronald Lovelace** (alias **Cloudy_Day**)’s cloud-vendor warnings, the vendors’ replies, and public cloud outages from 2024 through 12 November 2026.

Anyone can check that the files in this folder are the same files that were hashed when the bundle was built, and that they combine into the published Merkle root. A public OpenTimestamps receipt anchors that root; the receipt stays **pending** until Bitcoin confirms it.

This is evidence, not a verdict. Matches between a warning and a later outage are labeled **researcher analysis, not proven causation**.

## What’s in the folder

| Path | What it is |
| --- | --- |
| `items/` | One redacted file per fact: a text excerpt or a PNG (a redacted correspondence exhibit, or a live capture of a public status or news page). |
| `manifest.json` | Every item’s id, date (Pacific Time), type, organization, case number, one-line summary, source, and SHA-256. |
| `merkle.json` | The Merkle root, the scheme, and a proof path for every item. |
| `correlations.json` | Side-by-side analysis. **Not** part of the Merkle tree. Every entry is labeled researcher analysis, not proven causation. |
| `verify.py` | A verifier that uses only the Python 3 standard library. |
| `manifest.json.ots`, `merkle.json.ots` | OpenTimestamps receipts. Pending until `ots upgrade` succeeds. |
| `ots-status.json` | An honest record of whether those receipts are still pending. |
| `UPGRADE.md` | How to finish the Bitcoin confirmation later. |

There are **61** items. The Merkle root is:

```
3196393fa4b82b48527f980ff319574f0ba8ca279eeee960a5e2e1a8f89078ca
```

The bundle was assembled on **2026-11-12 16:57 PT (America/Los_Angeles)**.

## How to verify, in plain English

1. Install Python 3 (3.8 or later). You do not need any extra packages.
2. Unzip the bundle and open a terminal in this folder.
3. Run:

   ```
   python3 verify.py
   ```

4. You should see `RESULT: PASS`, the Merkle root above, and a line for every item hash and every Merkle proof. To check one item:

   ```
   python3 verify.py --item outage-ms365-2026-11-12
   python3 verify.py --file items/exhibit-aws-elevate.png
   ```

You can also do the same checks by hand, or in a browser:

- SHA-256 of a file’s raw bytes should match the `sha256` field in `manifest.json`.
- Sort those hashes as lowercase hex, ascending. Pair them left-to-right. Each parent is SHA-256 of the two raw 32-byte digests concatenated (not the hex text). If a level has an odd number of hashes, duplicate the last one before pairing — the same rule Bitcoin uses. The final hash is the Merkle root, and it should match `merkle.json`.
- To check a single item without hashing everything else, walk the `path` in `merkle.json`: if the sibling’s `side` is `right`, the parent is SHA-256(current then sibling); if `side` is `left`, it is SHA-256(sibling then current). You should arrive at the same root.

A public Evidence page at the WhiteHat Suite does this last step in the browser with WebCrypto, so a reader can press **Verify** on any item.

## What the timestamp does, and what it does not

OpenTimestamps sends the hash of `manifest.json` and of `merkle.json` to calendar servers, which will later embed them in the Bitcoin blockchain. That proves the Merkle root existed at or before the confirmation time. Until a Bitcoin block actually contains the commitment, the receipts are **pending**. That is expected on day one. It is not a failure of the file hashes. See `UPGRADE.md`.

## Redaction and what was left out

- Personal names of correspondents, email addresses, and phone numbers are removed. Organization names, case numbers, and dates stay.
- The researcher’s own name (Ronald Lovelace) and alias (Cloudy_Day) may appear.
- No exploit steps, payloads, or proof-of-concept detail are included.
- Some mailbox items are receipt-only or have a body that was not fully expanded; those limitations are written into the item itself.
- Two attempted live captures from 12 Nov 2026 are **not** in this bundle: the Illinois StatusHub page rendered blank, and the ThousandEyes analysis page returned Access Denied. Microsoft’s official cause language for that day is a contemporaneous transcription from the StatusHub mirror, backed by CNBC, BBC, and Guardian coverage. Azure’s and Microsoft’s own status portals, captured the same afternoon, had already cleared the live incident banner; those “negative” captures are included and labeled honestly.
- The AWS Health dashboard capture was still loading its public list. AWS’s “operating normally” sentence is taken from contemporaneous news, not from that image alone.
- A social-media handle on the CNBC capture was covered so that no at-sign appears in the published image. The rest of the page is the original capture.

## Item types

- `warning` — an outbound report or follow-up from the researcher.
- `vendor_response` — a vendor or coordinator reply, or a documented absence of a reply in a retrieved thread.
- `outage` — a public incident, cited to an official postmortem or a named tracker.
- `official_statement` — a verbatim official-cause excerpt, or a live screenshot of a public status or news page.

## Gaps worth knowing

- No Oracle PSIRT correspondence was found in the mailbox for 2024–2026.
- MITRE requests 1877080 and 1965296 have receipts but no CVE ID in the retrieved threads.
- The final disposition of Google Issue 426398073 was not fully extracted.
- Cloudflare and Akamai threads show outbound reports with no vendor reply in the retrieved mailbox.
- Historical outage durations and categories for some 2024–2026 events come from the Control Plane Cloud Outage Tracker and similar public compilations. Where a provider’s own PIR is cited, that is the primary official source; readers should open it.

Prepared for coordinated disclosure. Motto: Research. Correlate. Validate. Disclose. Improve. — Cloudy_Day
