ProperProse is a litigant's-eye view of the legal system, AI tooling, and solo-builder economics — written for the people who don't have a firm, a team, or a safety net. Honest. Useful. Fast. No agency voice. No LinkedIn-poet voice. No "thought leader" voice.
An operator who has been through it, talks like a friend over coffee at 2 a.m., never wastes the listener's time, and laughs at the dumber parts of the system before the listener has to.
Every claim here is backed by a screenshot, a statute cite, an exhibit, a dollar figure, or a timestamp. We sound like someone who has actually filed the paper — not someone summarizing a textbook. The subject matter is heavy. The voice can't be heavy or no one watches. So we keep it dry, dark, and moving.
Three audiences this is built for: the self-filed pro per who just got served and has thirty days; the AI-augmented indie who wants to see a real, ugly, multi-front workflow; the survivor-operator who is tired of being pity-bombed by every "self-help" channel.
Composite anonymization on every active matter. No party names, no case numbers, no judge names. Patterns, not parties.
Each pillar gets roughly twenty percent of the calendar. Listed in priority order for the first thirty days.
"What the rule actually does, what it cost me, what I'd do differently."
CCP, CRC, and FRCP explainers tied to real, dated, anonymized moments. Deadlines decoded. Service rules. Sanctions math. What a tentative ruling actually means. Never abstract — always pinned to a minute-order quote and a dollar figure.
"The stack a one-man docket actually runs on."
Claude for declaration drafting. Midpage for citation checking. Genspark for deep research. Abacus for long-running pipelines. Adobe Acrobat Pro for redlines and signing. Real prompts, real failure modes, real costs — and what the model got wrong.
"What you build when 'shipping' and 'survival' are the same verb."
Build-log notes from a one-person shop. GitHub workflow under deadline pressure. MCP server design. Wyoming LLC math. Indie-funding paths that aren't VC, ranked by what they cost in dignity. The unpaid-founder economics most people pretend not to talk about.
"How to function when the threat doesn't end at 5 p.m."
Routines for PTSD, ADHD, and bipolar under acute litigation stress. What HBOT, sleep, lithium, exercise, and structured note-taking actually do. Function over feelings. Zero wellness packaging. No supplements pitched. No manifestation prompts.
"What it's worth to be customer #7."
How to position yourself as a design partner — not a beta tester — for AI startups. Pricing your feedback. Getting credit for product input. The difference between "feedback" and "co-author." A multi-stack lived case study, not a hypothetical.
Five episodes from Pillar 1 — Legal-system literacy. Sixty seconds each. Receipts on screen, statute on the lower third.
Most pro per motions die before the judge ever reads them. Here's why.
CCP §1005(b) demystified — sixteen court days plus five calendar days, counted backward, with the one-line trick that fixes the most-violated rule in pro-per filings.
If your discovery motion doesn't have this email attached, it's getting denied.
CCP §2016.040 + CRC 3.724 in five load-bearing parts. The redacted M&C email that survives appellate scrutiny — and the one that gets your motion denied.
I've watched three pro per cases die on bad service. Here's what to actually do.
CCP §415.10, §415.20, §1010.6 — three fields people botch on POS-010, why "reasonable diligence" isn't one drive-by, and why service kills cases before merits.
Sanctions aren't a punishment. They're a pricing system. Here's how to read the price tag.
CCP §177.5, §2023.030, §128.7 — three statutes, three prices, one safe-harbor letter. The statute defense picks is a confession of how they're valuing your case in pain.
Most pro per litigants don't know LASC posts the ruling before the hearing.
CRC 3.1308 — "inclined to grant" vs. "matter to be argued," and why missing the 4 p.m. call is how you submit on the tentative without meaning to.
Pillars 2 through 5 enter rotation in week three. Subscribe to get them as they drop.
Eight hundred to fourteen hundred words on what actually happened on the docket, in the build, in the stack, in the room. Free. No paid tier yet. Unsubscribe in one click — no guilt-trip drip campaign, ever.