This site was built under duress, from a phone, using AI — because that was the only way it was going to get built at all.
Starting in August 2025, I was hit by events faster than I could process them: a serious assault, a building in chemical crisis, simultaneous pressure on a family trust I'm a beneficiary of, and a landlord using every available tool to destabilize me while I was already down. I was sick. At times I couldn't type reliably. My phone was usually the only device available to me.
The priority was documentation. Not polished documentation — documentation that existed at all. If I got sicker, or if things escalated further, I needed a record of what had happened before I lost the capacity to create one. So I used AI to help build and maintain this site, dictating or typing out what I remembered from a phone while events were still unfolding. New things kept happening. Every time I sat down to clean up what was already here, something else required immediate documentation instead.
The inaccuracies that appeared on this site were never intentional. I was being hit by so much at once that I couldn't stop to check every detail — and because I was using a phone with autocorrect and an AI that worked from my imprecise prompts, errors made it into the record. I didn't have the capacity to catch them in real time.
Things have shifted somewhat. The immediate pressure from the landlord has paused for now — and I'm not taking that for granted, but it does mean I'm not being pulled into new emergencies every day. I'm working on getting out of this situation entirely and moving to a new place. I'm also trying to manage and verify everything that's already been documented here.
For the first time in months, I have a brief window where no major new events are actively demanding documentation. I'm using it to go through the record, correct what's wrong, and make sure what's here is accurate. This is that process. It's still ongoing.
I want to be clear about what this site is: a real-time personal record, built under abnormal constraints, by someone who was sick and overwhelmed. It is not a finished product. It has always been a living document, and the edit history reflects that — both the rate at which events were occurring and my attempts to keep up with them.
One of the reasons I chose to build this on GitHub Pages is transparency. Every version of every page is preserved in the commit history. You can see what changed, when, and at what rate — which itself tells part of the story of what I was dealing with.
That was deliberate. GitHub's commit log is a public, cryptographically-chained, immutable timestamp record. Every commit has an author, a date, a hash, and a diff — and none of that can be quietly edited after the fact. I knew from the start that anything I documented here could be challenged, dismissed, or reframed by people with more institutional power than I have. Building on GitHub meant that the forensic record of when I knew what, and when I wrote it down, would be auditable by anyone. The charts below come directly from that log. They're not claims — they're the output of git log on a public repository.
Every commit is a timestamped record of work done. The pattern below isn't what a planned project looks like. It's what responding to events in real time looks like.
115,934 lines written. 45,444 deleted. 70,490 net. Every line represents an event, a document, a legal contact, a timeline entry, or a correction to something that was wrong. The deletions aren't erasure — they're visible in the commit history and represent corrections, reformatting, and page restructuring.
Data source: github.com/thumpersecure/JlegaL commit history. All timestamps are public and auditable. Sessions clustered from git log output (June 22, 2026) — a gap of 2h+ between commits = new session.
The GitHub repo is the production layer. Facebook was the distribution layer — and the two platforms tell the same story, synchronized almost to the day.
| Date | GitHub commits | Facebook posts | What was happening |
|---|---|---|---|
| June 5 | 1 | 30+ | Evening bulk-share of site pages (9:34–11:26 PM; posts at consecutive minutes) |
| June 8 | 0 | 12 | Graveyard session: 12 posts between 2:27–2:47 AM |
| June 12 | 21 | 10+ | Pre-trial push begins; 4 Facebook posts at 3:52–3:53 PM in under 90 seconds |
| June 17 | 37 | 11 | Morning blitz: 11 Facebook posts 9:06–9:38 AM; 37 GitHub commits same day |
| June 18 | 34 | 13 | Sustained afternoon/evening push across both platforms |
| June 19 | 63 | 12+ | Peak day on GitHub; site-wide footer rollout + Facebook spike in parallel |
Source: 4 PDF exports of the Justice Born Facebook profile (captured June 22, 2026 — 27, 35, 58, and 24 pages respectively). Post counts estimated from 3-column grid view density. Engagement metrics (reach/impressions) not available in these exports — Meta Insights export would be required to close that loop.