PUBLIC, REDACTED EVIDENCE RECORDVerified records, statements, allegations, counterpoints, and unresolved gaps are labeled separately.
Matter PIUP–PF–2026–07
Erik Crowell evidence record
One searchable review of account access, product activity, direct communications, saved work, public technical comparisons, and source-package integrity.
How to review this matter
Confirm identity and access.
Trace every platform action.
Compare statements with use.
Review technical correspondence.
Contribute first-hand evidence.
Highest-weight finding
Identifier overlap—not color—is the lead technical fact
Very high
PatchForge’s public JavaScript exposed 272 material records. Of those, 224 use exact UUIDs also present in Patch It Up Pro’s authorized materials table; 168 match every compared core field.
82.35% identifier overlap224 / 272
This is evidence for review, not a legal conclusion. Counsel should assess provenance, authorized access, common-source explanations, protectability, and damages.
Evidence posture
What each kind of record means
System factHashes, timestamps, routes, database records, and public bundles.
Subject statementDirect messages, public captions, and replies from the subject account.
Third-party allegationFour anonymous reports; none is presented as independently proven.
Counterpoint or gapGeneric UI patterns, alternate explanations, and missing proof.
Chronology
Key dates from creation through public launch
Each milestone is source-labeled; the full event-by-event record is available in the dedicated tables.
01
Sep 12, 2025
Repository chronology
Patch It Up Pro repository begins
Initial repository and contour-cutting history are preserved in Git.
02
Sep 16–30, 2025
Repository chronology
Materials and gang-sheet workflow documented
Material library, Shopify integration, layered SVG, and gang-sheet commits precede the subject’s documented access.
03
Oct 13, 2025
Direct communication
Subject requests product timing and a demonstration
The Messenger thread records interest in the Shopify patch-hat application and live mockups.
04
Oct 20–21, 2025
Direct communication
Demonstration and beta access discussed
The subject says he is sold, requests a demonstration, receives beta-access discussion, enters the product, and reports an upload/input issue.
05
Nov 6, 2025
Platform record
Account and trial begin
Authentication, CRM, profile, and subscription records independently establish account creation and the trial marker.
06
Nov 24, 2025
Repository chronology
Live hat mockups documented in Git
The implementation chronology records live hat mockups before the captured PatchForge launch.
07
Jan 30–Feb 24, 2026
Repository chronology
Tri-layer and patch-first hat workflow documented
Repository records preserve tri-layer support and a completed-patch-to-hat workflow.
08
Apr 2–6, 2026
Direct + platform
Renewed access and production-workflow testing
Messages discuss product status, reactivation, vectorization, combined SVG export, material state, and repeat testing.
09
Apr 20, 2026
Repository chronology
Mockup proof approval documented in Git
The repository chronology records a proof-approval system.
10
May 25, 2026
Direct communication
Subject discusses separate app launch and founder offer
The subject reports a DTF-app launch, lifetime founder pricing, browser-only operation, and use of an AI coding tool.
11
Jul 20, 2026
Platform record
Latest preserved intensive session
A 63-minute session closes after activity across patch, laser, hat, partner-store, and depth-map routes.
12
Jul 22–23, 2026
Public record
PatchForge public launch materials captured
The public sitemap, site, reel, feature claims, comments, and group-share screenshots are preserved with hashes.