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.
Countersign · Caseload · Recoup · Threshold — one network
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.
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.
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.
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.
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.
Audits a bill line by line and drafts the recovery paperwork — asserting only what it can prove.
Door · consumer & navigatorNames the benefit programs worth asking about, the paperwork each one wants, and the office that decides.
Turns the intake pile into a triaged queue — behind an attested professional credential, or not at all.
Bench · professionalDrafts the response and holds it behind four release walls until a human with a license signs.
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.
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.
The tool drafts. A human with a license signs.
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.
Enforced by: four release walls · SAMPLE stamps until release · attorney countersignature as the only exit
No attested credential, no output at all.
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.
Enforced by: credential gate before any output · leash table · 46 machine-checked assertions
Asserts what it can prove. Confirms what you tell it.
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.
Enforced by: integer-cent arithmetic · assert-vs-confirm split · declared detector gaps
Knows the door. Never claims the key.
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.
Enforced by: 65 machine-checked assertions · verdict language structurally banned from the schema
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.
"Understand anything they put in front of you."
In the workshop"Every clause, in your favor."
In the workshop"You served. Now make the paperwork serve you."
In the workshop"Entiende cada carta. / Understand every letter."
In the workshopA care navigator for the sandwich generation — the paperwork of an aging parent's care.
In the workshopAfter a person is served, billed, or cited — decodes the legal jargon and frames the response.
In the workshopThe document-asymmetry product for America's small businesses.
In the workshop"Read it before you sign it."
In the workshop"The district has a team. Now you have one too."
In the workshop"You may be paying too much in property tax."
In the workshop"Your county says your house is worth more. Make them prove it."
In the workshop"That IRS letter has a number in the corner. We know what it means."
In the workshop"The clear line through a lifetime of care."
In the workshop"The calm center, after." The paperwork that follows a death.
In the workshopThe B2B2C distribution layer that carries the family to the people who need it.
In the workshop · distribution layerWhat the law says. A registry of cited, attorney-attested rules, served read-only. It never interprets — it is the shelf the rules live on.
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.
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.
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.
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.
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.
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.
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.
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.
Uploads are processed in memory with in-process OCR and are not retained. There is no corpus of user documents — by architecture, not policy.
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.
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.
What a consumer will ever pay to have a Countersign draft released. Free for the consumer, always.
Machine-checked assertions holding Caseload (46) and Threshold (65) to their word on every build.
Release walls between a Countersign draft and the outside world. The last one is a human with a license.
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