MCRO 77-CLUSTER SWARM INVESTIGATION — PUBLIC DOWNLOAD MANIFEST
===============================================================

Generated (UTC):   2026-04-20T23:51:41Z
OTS stamped (UTC): 2026-04-20T23:56:00Z   (4 independent Bitcoin calendars)
Source case:       State of Minnesota v. Guertin — 27-CR-23-1886
Landing page:      https://mncourtfraud.com/77/
Context:           Investigation conducted by 8 Claude Code autonomous
                   subagents operating in parallel against the MCRO
                   forensic database (Supabase project ibfmjtwahkwqzcmeyqii,
                   READ-ONLY) on 2026-04-20. A 9th synthesis subagent
                   produced the master findings. Every number on the /77/
                   landing page traces to a specific SELECT query in one
                   of these archives.

FILES
-----

  MCRO_77-cluster_swarm-investigation_2026-04-20.zip
    Complete archive. 24 files across 4 subfolders: shared-context (3),
    findings (8), queries (8), plus README.txt.
    Uncompressed: 521 KB  /  Compressed: 131 KB

  MCRO_77-cluster_swarm-investigation_findings-only_2026-04-20.zip
    Readable-prose subset. 3 shared-context + 8 findings.md + README.
    Uncompressed: 311 KB  /  Compressed: 93 KB

  MCRO_77-cluster_swarm-investigation_queries-only_2026-04-20.zip
    SELECT-query-only subset (~180 annotated SELECT queries across 8
    investigative lanes). 8 queries.sql + README.
    Uncompressed: 192 KB  /  Compressed: 37 KB

SHA-256 HASHES
--------------

ddff58915e317119c35f680d90651d7eb4220afb913b70e9da12a83b113df318  MCRO_77-cluster_swarm-investigation_2026-04-20.zip
ec1fed8fe1fd547579f175c7b3800f79f0a98e70716cdfee6e975a2e80d51ea6  MCRO_77-cluster_swarm-investigation_findings-only_2026-04-20.zip
27f6152cf70a778c7a0c5d581c24bb890c005e16c457f3068b77c35e4dcb2bbf  MCRO_77-cluster_swarm-investigation_queries-only_2026-04-20.zip
97cffac212db06017f526bdb36d73032a49866d6078b058f1caf26503b657777  SHA256SUMS.txt
cc657f7e63c22facd537d42fa2ddb0af1bf7905a460f57f4c81be7e8f882adc9  MANIFEST.txt (self)

BITCOIN OPENTIMESTAMPS (.ots RECEIPTS)
--------------------------------------

Every file above is accompanied by a companion `.ots` receipt generated
at 2026-04-20 23:56 UTC and submitted to four independent Bitcoin
calendar servers:

  https://a.pool.opentimestamps.org
  https://b.pool.opentimestamps.org
  https://a.pool.eternitywall.com
  https://ots.btc.catallaxy.com

The OTS receipts cryptographically bind each file's SHA-256 hash to a
specific Bitcoin block, producing tamper-evident proof that the exact
contents of each archive existed at the stated timestamp. A third party
can verify this independently with the `ots` CLI against the live
Bitcoin blockchain — no trust in mncourtfraud.com required.

Receipt files (all served alongside the zips at /77/downloads/):
  MCRO_77-cluster_swarm-investigation_2026-04-20.zip.ots
  MCRO_77-cluster_swarm-investigation_findings-only_2026-04-20.zip.ots
  MCRO_77-cluster_swarm-investigation_queries-only_2026-04-20.zip.ots
  SHA256SUMS.txt.ots
  MANIFEST.txt.ots

VERIFICATION
------------

Standard SHA-256 verification (after download):

  sha256sum --check SHA256SUMS.txt
  -> all three zips should report "OK"

Bitcoin timestamp verification (requires opentimestamps-client):

  pip install opentimestamps-client
  ots verify MCRO_77-cluster_swarm-investigation_2026-04-20.zip.ots
  -> reports the Bitcoin block the file hash is anchored in

Newly-stamped receipts list "PendingAttestation" entries for the first
1–24 hours while the receipt waits to be aggregated into a Bitcoin
block. Once confirmed (typically within 6 hours), running:

  ots upgrade <receipt>.ots

pulls the full Bitcoin block proof into the receipt, after which the
receipt is self-contained — verification requires only a Bitcoin node
or public Bitcoin explorer, not the original calendar servers.

All zips extract cleanly with any standard tool (unzip, 7-Zip, Windows
File Explorer, macOS Archive Utility). Integrity verified at build time
via unzip -t.

METHODOLOGICAL NOTE
-------------------

These files are the actual, unedited output of an autonomous 8-agent
Claude Code investigation conducted on 2026-04-20. The 8 lanes:

  A — Cluster anatomy
  B — Filing-type atlas
  C — Mechanism instruments (NIPs + Rule 20 cascade)
  D — Temporal depth + MH-only clusters
  E — Outcome ladder + revolving door
  F — Judicial officer footprint
  G — Metadata fingerprints
  H — Skeptical control (falsifiability test)

Each agent ran with strict READ-ONLY enforcement. SELECT and WITH...SELECT
queries only. All mutation SQL keywords (INSERT/UPDATE/DELETE/DROP/CREATE/
ALTER/TRUNCATE/GRANT/REVOKE/VACUUM/REINDEX/MERGE/CALL/DO/LOCK) were refused
at the agent level. The Supabase MCP was restricted to execute_sql +
list_tables. No mutation was ever attempted.

WHY OTS
-------

The `.ots` layer is deliberate and consistent with the site-wide
cryptographic posture documented at /authentication/. Hash verification
alone proves the file has not changed since someone wrote down the hash.
OTS verification, by binding the hash to a specific Bitcoin block, proves
the file existed NO LATER THAN that block's timestamp — a property no
re-hashing or after-the-fact editing can forge. Combined with the
READ-ONLY nature of the source database queries, this yields end-to-end
provenance: the queries can be re-run to verify the numbers are real; the
OTS receipts prove the files published here are the same ones that
produced those numbers on 2026-04-20.

---

State of Minnesota v. Guertin — 27-CR-23-1886
MnCourtFraud.com — April 20, 2026