Countersign · Caseload · Recoup · Threshold — one network

A seat anyone
can take.

Parkbench is a network of software benches built for the moment an institution's letter lands in an ordinary person's hands. Each bench makes the other side's paperwork legible, holds every claim to the person's own document, and stops exactly where a licensed human should begin.

01

Two laws, written before the first line of code

Every product in this network is a different lens over one doctrine. The doctrine is short enough to print on a bench plaque — and it is enforced in schemas and release gates, not in vibes.

Law I

Money may change who can do more with a tool. It may never change what the tool tells you.

A free user and a paying user get the same truth about the same document. Paid tiers unlock artifacts and capacity — never answers.

Law II

Intelligence flows toward the weaker party.

When in doubt about who a feature serves, it serves the person holding a document they didn't write — not the institution that wrote it.

02

The loop: doors, a wall, and the benches behind it

Consumer tools in this network end, by design, at the same sentence: this is the moment for a licensed human. That refusal is not a limitation. It is the network — a steady stream of document-grounded moments arriving exactly where professional benches can take over.

It always starts with a letter. A bill that doesn't add up. A benefits notice nobody can parse. A collection demand with a deadline buried in it. Every path through this network begins the same way — with paper the reader didn't write.

What compounds here is not data. Documents live in memory and die there — nothing is pooled, mined, or retained. What compounds is doctrine and demand: every consumer door added to the park makes the professional benches worth more, because more legible, document-grounded moments arrive at the wall. And the wall never routes to a paying firm — the tools name the kind of help and the public directories that list it. The network effect is trust, not traffic brokerage.

03

The four benches, in detail

Four working benches, one discipline — each deployed and demoable today. Each card states what the bench does, what it will never do, and how that refusal is enforced in code — because for this network, the refusals are the sales pitch.

For consumer-law firms & legal aid

Countersign

The tool drafts. A human with a license signs.

What it does

Assembles response drafts — a debt-collection dispute, a validation demand — with every factual claim tied to the consumer's own document and every legal statement carrying its citation. Drafts queue behind four release walls; nothing reaches the outside world without an attorney's countersignature. Built with ABA Formal Opinion 512's supervision duties in view.

  • Never sends anything unsigned
  • Never charges the consumer — free for the consumer, always
  • Never promises an outcome
  • Never takes a share of any legal fee — licensing is flat, per-seat, or per-released-matter

Enforced by: four release walls · SAMPLE stamps until release · attorney countersignature as the only exit

For intake desks, clinics & firms

Caseload

No attested credential, no output at all.

What it does

Turns an unsorted intake pile into a triaged queue: deadlines surfaced with cited authority, draftable matters marked, and anything outside its leash table routed straight to a human. Every byte of output sits behind an attested professional credential — the gate is the product.

  • Never emits analysis to an unauthenticated user
  • Never guesses outside its leash table of covered areas
  • Never replaces professional judgment — it ranks the pile, the professional decides

Enforced by: credential gate before any output · leash table · 46 machine-checked assertions

For consumers first — firms license flat

Recoup

Asserts what it can prove. Confirms what you tell it.

What it does

Audits a bill line by line in integer cents — no floating-point money, ever — separating what it can assert from the document itself from what it needs the reader to confirm, and declaring the gaps its detectors cannot see. Then it drafts the recovery paperwork. For a law practice, the same audit becomes an exhibit: line-item findings with the arithmetic shown.

  • Never invents an amount — every figure traces to the bill or is marked unconfirmed
  • Never hides what it can't detect — gaps are declared, not papered over
  • Never gives legal advice — it audits paper, it doesn't practice law

Enforced by: integer-cent arithmetic · assert-vs-confirm split · declared detector gaps

For consumers, social workers & legal aid front desks

Threshold

Knows the door. Never claims the key.

What it does

Reads a household's situation against cited, dated benefit-program rules and names the programs worth asking about, the paperwork each one requires, and the office that decides — with the rule quoted, not paraphrased. For a legal aid front desk it is the warm no: the person the office can't take still leaves holding named doors.

  • Never issues an eligibility verdict — "you qualify" does not exist in its vocabulary
  • Never files anything on anyone's behalf
  • Never replaces the agency's decision — the office decides, always

Enforced by: 65 machine-checked assertions · verdict language structurally banned from the schema

Two more benches are joining the row — built for the same professional buyers, in the workshop until their statutory-rule reviews clear. Listed with their own words; unlinked until then.

Letters

"Estate-settlement drafting and deadline tracking for California formal probate, built for probate attorneys and their paralegals."

In the workshop · statutory rules under review

Afterword Probate

"Court-ready estate inventories and probate schedules, generated from a guided asset intake."

In the workshop · 51 jurisdictions encoded, pending cross-check
04

The wider park

The four benches are the front of a longer row. Behind them, a family of document decoders is being built to the same contract — one per kind of paper an institution can send. Each is listed with its own words. All are in the workshop: built, gated, and unlaunched until their checklists clear.

Plainsight

"Understand anything they put in front of you."

In the workshop

Marque

"Every clause, in your favor."

In the workshop

ServiceRecord

"You served. Now make the paperwork serve you."

In the workshop

Crossing

"Entiende cada carta. / Understand every letter."

In the workshop

Kindred

A care navigator for the sandwich generation — the paperwork of an aging parent's care.

In the workshop

Recourse

After a person is served, billed, or cited — decodes the legal jargon and frames the response.

In the workshop

Recourse for Business

The document-asymmetry product for America's small businesses.

In the workshop

Foresight

"Read it before you sign it."

In the workshop

Advocate

"The district has a team. Now you have one too."

In the workshop

Abate

"You may be paying too much in property tax."

In the workshop

Reassess

"Your county says your house is worth more. Make them prove it."

In the workshop

NoticeKey

"That IRS letter has a number in the corner. We know what it means."

In the workshop

Throughline

"The clear line through a lifetime of care."

In the workshop

Afterward

"The calm center, after." The paperwork that follows a death.

In the workshop

Benefit Channel

The B2B2C distribution layer that carries the family to the people who need it.

In the workshop · distribution layer
Layer 1

Pandect

What the law says. A registry of cited, attorney-attested rules, served read-only. It never interprets — it is the shelf the rules live on.

Layer 2

The grounding rails

What the document means. The decoders above — they match a person's document to the cited rule and explain it. They never apply law to a person.

Layer 3

Nexus

What the numbers are. The only layer allowed to compute deadlines and amounts — and only for licensed-professional buyers. Consumer tools never compute magnitude.

No layer can do another's job. A consumer tool that started computing "you owe $X by date Y" would have silently become the professional layer without its safeguards — so the boundary is architectural, not aspirational.

05

The rails: how honesty is enforced

For the technical reader. These are the engineering invariants every bench in the network is built on — the reason the marketing above can afford to be calm.

Verbatim or absent

A quote from a user's document ships only if it is an exact substring of that document. Citations that fail the check are dropped, not fuzzed. Not stated is correct output, never a defect — a disclosed gap beats a plausible fabrication.

Schema-enforced honesty

Analysis returns as forced-tool structured JSON against a schema that carries honesty fields — confidence, unknowns, gaps — so the model structurally cannot omit them. The banned field is telling: recommendedNextStep does not exist anywhere in the family; the neutral howToChoose replaces it.

Mock/real lockstep

Every engine ships with a zero-secrets deterministic mock that honors the identical contract, so the entire product is testable without a single credential. Engine changes land in the real path and the mock in the same commit, or they don't land.

Two-key go-live

An API key alone keeps a product serving labeled samples. Production requires a second, deliberate confirmation flag that is set only after a no-training, no-retention agreement is in place. Going live is a decision, never a default.

Rules as data, never as memory

Legal and program facts live in cited, dated rule files with source URLs and re-verify stamps — never in prompt prose, and never from the model's memory. The model is not the source of a single legal rule anywhere in the network.

Documents die in memory

Uploads are processed in memory with in-process OCR and are not retained. There is no corpus of user documents — by architecture, not policy.

Machine experience

The network is built to be read by machines as well as people: semantic landmarks, structured data, and a plain-text llms.txt map. This page practices what it claims — view source.

06

The lines: what this network will not do

For the legal reader. The unauthorized-practice line is not something we manage around — it is the product's load-bearing wall, enforced in schemas and gates.

Give legal advice.Every bench explains and offers a menu of options with neutral how-to-choose guidance. Prescribing the action is structurally off the table.

Predict outcomes or issue eligibility verdicts.No "you qualify," no "you will win," no rating predictions. The tools name that a rule, right, deadline, or program exists — and the office that decides.

Invent a figure, date, or citation.The worst failure in this category is a fabricated number a person acts on against an institution. Verbatim-or-absent grounding exists so that failure cannot ship.

Share a legal fee.Professional licensing is flat — per seat, per office, per released matter. Never a percentage of anything a lawyer earns. (Model Rule 5.4 is a wall, not a hurdle.)

Charge the consumer for Countersign.The person holding the collection letter pays nothing to have a response drafted and released. Ever. Firms license the bench; consumers take the seat.

Operate as a referral service.High-stakes documents trigger a get-a-licensed-human block the model cannot remove — pointing to kinds of help and public directories, never to paying firms.

$0

What a consumer will ever pay to have a Countersign draft released. Free for the consumer, always.

111

Machine-checked assertions holding Caseload (46) and Threshold (65) to their word on every build.

4

Release walls between a Countersign draft and the outside world. The last one is a human with a license.

Come sit down.

We're showing the benches to consumer-law firms and legal aid offices now. If your office reads paperwork other people wrote — we built these seats for the people you serve.

Start a conversation